Multi TSA Portfolio
Knowledge that stays after the people leave.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
A TSA knowledge transfer plan captures what the seller's team knows before the TSA ends and those people move on. The buyer who plans the transfer early, and confirms the receiving team can run the process unaided, keeps the operation working after the experts leave. Knowledge transfer is one of the quietest failure modes in day one readiness, because the gap does not show until the people who covered it are gone.
A TSA buys the seller's services for a window, but it does not buy the seller's people permanently. When the TSA ends, the staff who ran payroll, closed the books, or kept the legacy interface alive go back to the seller or move on, and they take with them everything that was never written down. The systems can be migrated and the data can be copied, but the knowledge of how the operation actually runs is the asset most likely to be lost in the transition.
The risk is silent because it does not announce itself. The process keeps working right up until the moment the person who knew the exception handling leaves, and then the first unusual case stalls because nobody on the buyer's side knows what to do. By then the expert is gone and the seller has no obligation to help. A knowledge gap discovered after the TSA has ended is far more expensive to close than the same gap closed while the people were still on the service.
Treating knowledge transfer as a deliverable with its own plan, owners, and evidence is what moves it from hope to control. The plan does not have to be elaborate, but it has to exist, because knowledge transfer that is left to happen organically during a busy exit reliably does not happen. The buyer who names it, schedules it, and checks it is the buyer who still has a working operation the week after the TSA ends.
The plan starts by mapping the knowledge that matters and the people who hold it. For each service the buyer is taking over, identify the tasks that are run regularly, the tasks that run rarely but matter when they do, and the named individuals who currently perform them. The aim is to find the single points of knowledge, the cases where one person on the seller's side is the only one who understands a process, because those are the gaps that hurt most when the TSA ends.
Distinguish documented knowledge from tacit knowledge, because they transfer differently. A documented process can be read after the author leaves, so it carries less urgency. Tacit knowledge, the workarounds, the manual steps, the reasons a process is done a particular way, exists only in someone's head and disappears with them. The plan should weight its effort toward the tacit knowledge, because that is the part no amount of later reading can recover.
Prioritize ruthlessly, because not all knowledge is worth the same effort to capture. A daily process that the business depends on warrants full transfer and confirmation. A once a year task might be handled by a written runbook and a single walkthrough. Spending equal effort on every task means running out of time before the critical knowledge is secured, so the plan ranks the knowledge by the cost of losing it and works that ranking down.
The single most common knowledge transfer failure is starting too late. Left to the final weeks of the TSA, transfer competes directly with cutover work for the same people's time, and cutover always wins because it has the harder deadline. The seller's experts are also least motivated at the end, when their attention has moved on and their obligation is nearly discharged. Knowledge captured under that pressure is thin and unverified.
Starting early reverses every one of those problems. The seller's people are most available and most engaged while the relationship is fresh, and an early start leaves time for the buyer to confirm the transfer worked and to circle back on the gaps it finds. It also surfaces, well before cutover, the cases where the buyer's team is not ready to take something over, which is exactly the kind of finding a program wants early rather than at the deadline.
Build the knowledge transfer schedule into the milestone plan so it competes for attention on equal footing with the technical work. A transfer session that has a date, an owner, and a place on the tracker happens; one that is everyone's good intention happens last or not at all. Tying transfer milestones to the governance review keeps them visible to leadership, who can then protect the time the experts need rather than letting it be eaten by the cutover crunch.
The deepest error in knowledge transfer is mistaking a session held for knowledge transferred. An expert demonstrating a process while the buyer's team takes notes proves only that the expert knows the process. Confirmation requires the reverse: the receiving team performs the task unaided while the expert watches and corrects only where needed. Transfer is real when the buyer's people can run the process alone, and not a moment before.
A useful pattern moves through three stages. First the expert does the task while the buyer's team observes. Then the team does the task with the expert available to step in. Finally the team does the task alone with the expert only reviewing the result. Only the third stage counts as confirmation, and the plan should record which stage each piece of knowledge has reached so the gaps are visible rather than assumed closed.
Capture the knowledge in a durable form as it transfers, because a person's memory of a session fades. Have the receiving team write the runbook, not the departing expert, because the act of writing it is itself a test of whether they understood. The expert then corrects the draft, and the corrected runbook becomes the durable record that outlasts everyone in the room. That written artifact is what protects the operation when the next unusual case arrives months later.
Track knowledge transfer through the same governance the rest of the exit uses. The plan reports progress against the prioritized list, the confirmation stage each item has reached, and the items still stuck because the buyer's team is not yet ready. A knowledge area that has not reached confirmation as its TSA exit date approaches is a risk, and it belongs on the register with an owner and a mitigation, not in a separate document nobody reads.
Where a gap cannot be closed in time, the buyer needs a deliberate fallback rather than a surprise. That might mean negotiating a short extension on the specific service, retaining a key person on a transitional basis, or accepting the risk with a plan for handling the first failures. Whatever the choice, it should be a decision the governance committee makes with eyes open, informed by the transfer plan's honest view of what is and is not ready.
Feed the experience into the portfolio's lessons learned. The knowledge that was hardest to transfer, the single points that nearly caught the program, and the confirmation approach that worked are all reusable on the next carve-out. A buyer that runs the same transfer discipline across multiple exits builds a template that gets sharper each time, which is how a portfolio stops relearning the same painful lesson with every deal.
It is the structured plan to capture the operational knowledge held by the seller's people before the TSA ends and they move on. It identifies who holds what knowledge, how it will be transferred, and how the buyer will confirm the knowledge actually landed rather than just being presented.
Early in the TSA, not at the end. The people who hold the knowledge are most available and most motivated while the relationship is fresh, and the buyer needs time to confirm the transfer worked. Knowledge transfer left until the final weeks competes with cutover work and often fails.
By having the receiving team perform the task unaided while the seller's expert watches and corrects, rather than the expert demonstrating while the team takes notes. Transfer is confirmed when the buyer's people can run the process alone, not when a session was held.
The undocumented knowledge in a few people's heads: the workarounds, the manual steps, the reasons a process is done a certain way. Documented processes can be read after the people leave; tacit knowledge walks out the door with them unless it is deliberately captured.
Turning transferred knowledge into a durable, step by step record.
Read the article →The support window that catches the knowledge gaps after exit.
Read the article →Where an unconfirmed knowledge area becomes a tracked risk.
Read the article →The 90-day governance, IT, finance, HR and procurement separation plan we run on live carve-outs. Get the playbook plus the bi-weekly Day One Letter — short, signal-heavy, buyer-side.
No spam. Unsubscribe in one click. · Read the overview first →
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Seven buyer-side moves to exit a Transition Services Agreement on time and below budget. The mark-up, the extension-fee curve, exit sequencing, and the 11-month calendar.
A representative $48M-revenue carve-out lists fourteen services in its TSA. When the catalog is vague — scope by reference, exclusions unstated, exit terms set only at the master-agreement level — the same estate drifts to $6.8M over twelve months. Pinned to the per-service template below, it runs to $5.1M in nine.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →