Knowledge Management & Enablement Lead

<p><em>"No one can whistle a symphony. It takes a whole orchestra to play it." — H.E. Luccock</em></p> <h3>Role Overview:</h3> <p>Mercury's Vendor Strategy team is hiring a Knowledge &amp; Enablement Lead to own the frameworks and governance for how Mercury's risk operations — and the BPO partners who deliver them — document, learn, and prove what they do, as we scale toward bank readiness.</p> <p>This is one role spanning two disciplines: knowledge management (the single source of truth for how work gets done) and training (how internal and vendor teams learn to do it). It is a system design and framework role with real execution target behind it. You will set the requirements, standards, and review cadence that risk operations documents and trains against, you will directly manage a BPO-based team of content writers who produce against those standards, and you will drive adoption through enablement practitioners embedded on other teams.</p> <p>If you need positional authority to make change happen, this is the wrong role. If you can set a knowledge and enablement standard so clearly that people adopt it because it's obviously better, it's the right one.</p> <h3>About Our Team:</h3> <p>The Vendor Strategy function at Mercury manages risk outsourcing across two principal domains — company-wide Business Process Outsourcing (BPO) and Risk Platform SaaS (KYC, KYB, IDV, AML, etc.) — and is building the enablement backbone of policy, procedure, standards, and training that lets that ecosystem scale. We're growing the team to manage an expanding vendor ecosystem, address rapidly evolving needs, and drive strategic value for Mercury.</p> <h3>Key Responsibilities:</h3> <ul> <li><strong>Own the knowledge framework.</strong> Define the architecture for the canonical library of risk-operations procedures — the ownership model, versioning, last-published and next-review dates, deprecation rules, and a live annual review cycle. Design for how knowledge is increasingly accessed and applied through AI-powered tools, not only how it is documented and stored. This is a systems problem before it is a writing problem.</li> <li><strong>Set policy, procedure, and documentation standards.</strong> Own the standards, templates, and structural conventions that govern how policy and procedure get written across risk operations — structured so business risk can build RCSAs and controls directly from them, and so compliance can approve regulatory content against a consistent format rather than a bespoke one each time.</li> <li><strong>Govern adoption and quality.</strong> Run the governance layer that keeps standards live: review cadence, compliance against the standard, exception handling, and escalation when programs drift. Own the audit and examination readine