Consulting and recruiting
Capturing tacit knowledge before senior partners retire
By SourceX Editorial · Updated
Short answer
To capture tacit knowledge before senior partners retire, start with the judgments only they make, such as scoping, pricing, staffing and reading a client, and pair each partner with a named successor. Case walk-throughs of real past proposals and projects draw out more than abstract interviews, and the output should be playbooks and decision logs successors actually use.
Key takeaways
- Tacit knowledge is judgment, so capture it through real cases rather than general questions.
- Pair every retiring partner with a named successor for each knowledge domain.
- Case walk-throughs of past proposals and projects yield the most usable material for the partner time spent.
- Test the capture by having the successor lead real work while the partner reviews.
- Retirement agreements should confirm that captured playbooks and recordings belong to the firm.
What tacit knowledge does a senior partner hold?#
A senior partner's tacit knowledge is the judgment behind decisions that never made it into a document: why a proposal was scoped narrowly, why a price was held, which consultant was put on a difficult client and which early signs meant a project would slip. Much of it surfaces only when the partner reacts to a real situation.
Split it into four domains before planning capture: client relationship context, commercial judgment on scoping and pricing, delivery judgment on staffing and risk, and firm history, such as why certain service lines were dropped. Each domain suits different methods and often a different successor.
Be realistic about what transfers. Relationships themselves move only through introductions and shared work, but the context around them, such as who decides, what the client values and past friction points, can be written down and handed over.
Which capture methods work, and what do they cost the partner?#
The capture methods that work best put the partner in front of real material and ask them to explain their reasoning. The table compares common methods by the partner effort they need and what they produce.
Match the method to the domain rather than running every method for every partner. Case walk-throughs and decision logs suit commercial judgment, because pricing and scoping leave a paper trail to react to. Reverse shadowing suits relationships, which transfer only through shared meetings. Structured interviews work for firm history, where no single file explains why the firm made its choices.
| Method | Effort for the partner | Output | Best for |
|---|---|---|---|
| Structured interviews | Moderate: a series of focused sessions | Transcripts edited into principles and rules of thumb | Firm history and client context |
| Case walk-throughs | Moderate: the partner explains past proposals and projects | Annotated cases with the reasoning at each decision | Scoping, pricing and staffing judgment |
| Decision logs | Low per entry, ongoing | A dated record of live decisions and the reasons for them | Current engagements and pricing calls |
| Playbook co-authoring | High: the partner corrects drafts written by others | Step-by-step playbooks for a service line | Repeatable delivery methods |
| Reverse shadowing | Moderate: the partner observes the successor and debriefs | Feedback notes tied to real meetings | Client relationship handover |
| Recorded internal reviews | Low: reuses existing project review meetings | Recordings and summaries, with participants' consent | Lessons learned and risk signals |
How to run a capture program, phase by phase#
A capture program runs best as a defined project with a sponsor, a schedule and a named successor for every domain. Start while the partner still leads live work, not in the final stretch before departure, so decision logs can be kept on real proposals.
Budget the partner's time explicitly. Capture sessions compete with billable work and client travel, so put them on the calendar as standing commitments, lower the partner's billable target to match, and give the sponsor authority to protect those slots when a client deadline appears.
| Phase | What happens | Output |
|---|---|---|
| Scope | List the partner's domains, clients and service lines, and name successors | Capture plan with owners |
| Gather | Pull past proposals from the CRM, pricing workbooks, project reviews and key correspondence | Case files for walk-throughs |
| Capture | Run interviews and walk-throughs; start decision logs on live work | Transcripts, annotated cases, logs |
| Codify | Edit into playbooks and rules of thumb; remove client identifiers | Draft playbooks and decision guides |
| Test | The successor leads real proposals and client meetings while the partner reviews | Corrections and remaining gaps |
| Store and govern | File in the KM library with an owner, review date and permitted-use tags | Governed, findable knowledge |
Questions that draw out judgment#
The questions that draw out judgment are specific and tied to a real case, because partners answer abstract questions with principles they do not always follow. Ask them during walk-throughs with the proposal or project file open.
Record answers with consent, transcribe them, and have the successor restate the key points in their own words. Where the successor cannot explain the reasoning back, the capture is not finished.
- On this proposal, what did you leave out of scope, and why?
- What told you this price would hold, and when have you dropped a price and regretted it?
- Why did you staff this engagement with these people rather than others who were available?
- What did you notice in the first client meeting that changed your plan?
- When did you first know this project was in trouble, and what did you do next?
- Which clients need a different style of communication, and what goes wrong when they do not get it?
- What do newer partners most often get wrong when they price this kind of work?
- Which past engagement would you run differently today, and what would you change first?
Illustrative: a founding partner's pricing judgment#
Illustrative: a fictional operations consulting firm's founding partner had priced most of its largest engagements for many years. The reasoning lived in comments on pricing spreadsheets and in the founder's memory, and the managing partner worried that renewals would be mispriced after the founder retired.
The firm pulled past proposals and pricing workbooks from its CRM and ran case walk-throughs in which the founder explained each scope and price decision. A senior manager kept a decision log on live proposals for the rest of the founder's tenure. The output was a pricing playbook with client names removed and a set of annotated cases. The successor led the next major renewal with the founder reviewing, and the playbook went into the KM library with an owner and a review date.
Who owns captured knowledge, and how SourceX views it#
Captured knowledge generally belongs to the firm when partner and employment agreements assign work product and know-how developed in the role, but retirement agreements should confirm that explicitly. Recordings need consent from the people recorded, and material drawn from client engagements must respect each client's confidentiality terms, so remove client names and identifying details while codifying.
Playbooks, decision logs and annotated cases are firm-owned internal records, the kind of material the SourceX Enterprise Data Value Framework assesses for depth and for links between decisions and outcomes. If a firm later chooses to license de-identified versions, the SourceX five-step transaction puts a rights review and privacy preparation ahead of any release, and the SourceX Evidence Packet records what was approved.
Frequently asked questions
When should tacit knowledge capture start?
As soon as a retirement is likely, and ideally well before it is announced. Partners near the end of their tenure often have less patience for long sessions, and some leave earlier than planned. Starting while the partner still leads live work also allows decision logs on real proposals.
What if a partner resists the capture process?
Resistance often comes from worry about relevance or a belief that judgment cannot be written down. Frame capture around the firm's clients and the partner's legacy, use case walk-throughs rather than abstract interviews, and keep sessions short. Including capture in the retirement agreement also helps set expectations.
Should we record capture sessions?
Recording makes transcription and later editing far easier, but get consent from everyone recorded and agree how recordings will be stored and used. Many firms keep recordings in restricted storage and work from edited transcripts with client identifiers removed. Tell participants who can access recordings and when they will be deleted.
Can AI tools help capture tacit knowledge?
They help with the mechanics: transcribing sessions, summarizing walk-throughs and drafting first versions of playbooks for the partner to correct. They do not replace the partner's review, and recordings or notes that contain client details should go only into approved tools under reviewed terms.
What if a partner leaves before capture is complete?
Prioritize the domains with the most revenue or risk attached, usually key client relationships and pricing, and capture those first. A consulting arrangement after retirement can cover the remaining walk-throughs if the partner agrees, with confidentiality terms in place. Keep the successor in those sessions so follow-up questions are answered in context.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.