Governance is the discipline that converts a plan into an exit.

The three committee structure that holds.

The disciplined TSA exit uses three governance committees. Workstream committees at the operational level, one per workstream. A program governance committee at the buyer side leadership level. A joint governance committee that brings seller and buyer leadership together for cross party decisions. Each committee has a different role, a different cadence, and a different decision authority.

Workstream committees own the daily execution. They meet weekly. They run a 60 minute agenda focused on progress against plan, blockers, dependencies on other workstreams, and risk items. Membership is the workstream lead from the buyer, the workstream lead from the seller, the systems integrator lead, and the Newco's permanent owner for that function. The buyer's workstream lead chairs.

Program governance committee owns the program level decisions. It meets biweekly, not monthly. The agenda is the rollup of workstream status, change requests above the workstream threshold, financial run rate against budget, and the top five risks. Membership is the buyer's program director, the buyer's PE operating partner or sponsor, each workstream lead, and the systems integrator program manager.

Joint governance committee owns the cross party decisions. It meets monthly. Membership is the operating partner from the buyer, an equivalent senior leader from the seller, the chairs of each workstream committee from both sides, and outside counsel where appropriate. The joint committee handles material change requests, dispute escalation, and amendment negotiation. It is where the parties meet as equals, with the contract as the basis.

The cadence that catches drift early.

Cadence is the discipline that catches issues before they become slip drivers. Weekly at the workstream level is the right rhythm because most issues surface within five working days. Issues caught in the same week they appear get resolved before they ripple into the next workstream. Issues caught a month later have already created dependencies on the seller's actions and lost the resolution window.

The biweekly program rhythm fits the leadership capacity question. A monthly program governance committee misses too many issues. A weekly program governance committee is too heavy and produces meeting fatigue. The biweekly cadence gives leadership real time visibility on rolled up workstream status while keeping the time commitment reasonable.

Monthly joint governance handles the contract level conversations. Most months, the joint committee meets and confirms that things are on track. The meetings matter even when they are routine, because they create the established forum that handles the difficult conversations when they arise. A joint committee that meets monthly through the calm months has the relationships and rhythm to handle the cutover discussion when it matters.

Each meeting has the same format every time. Status against plan. Open issues with named owners and dates. New issues for triage. Decisions required from the committee. Action items. Predictable meeting format compresses the time required and keeps the discussion focused on the work, not on rediscovering the agenda each time. The failure mode this avoids is covered in TSA exit failure modes.

Decision rights in writing.

Decision rights determine who can say yes to what. Without written decision rights, every decision becomes an escalation, which slows the program. With written decision rights, most decisions resolve at the right level and only the genuinely material decisions reach leadership. The writing matters because verbal agreements drift.

A working decision rights matrix specifies dollar thresholds and decision types. Change requests up to $25K can be approved by the workstream lead. Up to $100K by the program director. Up to $500K by the program governance committee. Above $500K by the joint governance committee with operating partner approval. Schedule changes beyond a defined tolerance escalate to program governance. Scope reductions escalate to joint governance.

Decision rights also include the negative authority. Decisions the workstream lead cannot make alone. Anything affecting a critical path workstream other than their own. Anything modifying the TSA itself. Anything affecting an external party, such as a customer or supplier. Anything that resets a milestone date. Each of these escalates by default because the consequences cross the workstream boundary.

The matrix lives in a single document. The document is signed by the operating partner, the program director, and each workstream lead at the start of the program. It is reviewed quarterly and updated as the program progresses. Without the document, decision rights live in individual memories and produce inconsistent decisions across similar situations.

Escalation paths that move within 48 hours.

Escalation paths exist for the issues that cannot be resolved at the workstream level. The escalation path defines who hears the issue first, who decides, and how fast. Without a defined path, escalation drifts. A blocker that should resolve in 48 hours sits for two weeks while emails circulate. The exit slips.

A working escalation path has four steps. Workstream lead raises the issue within 24 hours. Program director receives the escalation, attempts resolution, and reports back within 24 hours. If unresolved, the program director escalates to the program governance committee, which convenes within 48 hours via standing call if needed. If still unresolved, the joint governance committee meets within 96 hours.

Standing call slots reserve the leadership capacity before the escalation arrives. Holding a 30 minute slot every Tuesday and Thursday for program governance and a 60 minute slot every other Wednesday for joint governance lets escalations land in real time rather than waiting for the next scheduled meeting. The slot is cancelled when no escalation arrives. It is used when needed.

The discipline that makes escalation work is willingness to use it. Some programs avoid escalation because escalation creates discomfort. The discomfort is the point. Issues that escalate get resolved. Issues that do not escalate get worse. The buyer's program director should escalate without hesitation when the workstream cannot resolve, and trust that the leadership team will handle the discussion. Detailed milestone setting that depends on this rhythm is covered in TSA exit milestones, explained.

The artefacts governance produces.

Governance produces specific artefacts every week. Status report from each workstream, rolled into a single program status report. Decision log capturing every committee decision, decision date, and rationale. Risk register tracking the top 15 program risks with owner and mitigation. Action item log tracking every assigned action and due date. These four artefacts are the operating system of the program.

The status report is one page per workstream. Red, amber, green against plan. Three bullets on progress this period. Three bullets on focus next period. The top three risks. The top three blockers requiring decisions outside the workstream. A status report that needs more than one page is a status report that is hiding the issues. The discipline of one page forces clarity.

The decision log is the institutional memory. Without it, the same decisions get revisited every month because no one remembers what was decided last time. With it, the program director can trace back any decision in seconds and demonstrate the basis on which the program is operating. Decisions in the log include the rationale, not just the outcome.

The risk register is reviewed every program governance meeting. Risks that materialise become issues with owners and dates. Risks that recede are closed with a note explaining why. New risks are added throughout the program. A risk register that does not change between meetings is a risk register that is not being used. The operating partner who has visibility on the risk register has the strongest position to influence the program. The buyer who keeps it current is the buyer who maintains real control.

More on TSA exit strategy.