Multi TSA Portfolio
A program office that steers, not just reports.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
A TSA PMO staffing model sets the roles, seniority, and size a program office needs to run an exit without going thin or bloated. The buyer who staffs the PMO with real authority and the right experience runs an exit that gets steered, not just reported on. The program office is the spine of day one readiness, the function that turns a collection of workstreams into a coordinated exit.
The program office runs the exit, but it does not do the technical work. The workstreams migrate the systems, separate the data, and stand up the new operation. The PMO owns the layer above: the plan and the dependency map, the milestone and risk tracking, the governance cadence, the escalation path, and the drive to push decisions to closure. It is the function that holds the workstreams together and keeps the whole exit moving in one direction.
Confusing the PMO with administration is the most common way to underpower it. A PMO staffed as a reporting function collects status, formats it into a deck, and presents it, but it cannot make anything happen. A PMO staffed as a control function reads the same status, sees where the program is slipping, and acts: reallocating resource, escalating a blocker, forcing a decision that the workstreams cannot resolve among themselves. The difference is authority and experience, not headcount.
The PMO is also the keeper of the artifacts that the rest of the program depends on. The dependency map, the milestone tracker, the risk register, the runbook structure, the gate criteria, and the lessons log all live with the program office, which maintains them and ensures they tell a consistent story. When those artifacts are owned and current, the exit can be governed; when they are nobody's job, the program drifts on optimism between meetings.
A few roles carry the program. A senior program lead with the standing to make decisions and hold workstreams accountable sits at the center. Workstream leads own the delivery of each area, from finance to IT to HR, and are accountable for their part of the plan. A program coordinator keeps the trackers, the cadence, and the documentation current. On a larger exit, a dedicated risk or readiness lead and a cutover lead add depth where the complexity warrants it.
The seniority mix is where many program offices go wrong. A PMO staffed entirely with junior coordinators can track status but cannot drive the hard calls, and a TSA exit is full of hard calls under deadline pressure. A PMO staffed entirely with expensive senior people wastes money on tasks a coordinator could do and tends to argue rather than execute. The model that works pairs a small number of senior decision makers with enough coordination capacity to keep the machinery running.
Define each role by what it is accountable for, not just what it does. The program lead is accountable for the exit hitting its dates and budget. Each workstream lead is accountable for their area's readiness at each gate. The coordinator is accountable for the artifacts being current and the cadence being kept. Clear accountability is what lets the program office function as a control rather than a committee, because everyone knows whose call each decision is.
There is no fixed ratio for PMO size, because the right number depends on the number of workstreams and the complexity of the exit. A single, contained TSA might be run by a lead and a coordinator, with the workstream owners drawn from the operation. A multi service carve-out spanning finance, IT, HR, and operations needs a workstream lead for each area plus a central core that holds the cross workstream view. The structure scales with the surface area of the exit.
Both extremes of sizing cost the program. Too large a PMO generates reporting overhead for its own sake, holds meetings to coordinate the coordination, and slows the workstreams down with demands for status. Too small a PMO loses control of the detail, misses the dependency that needed catching, and arrives at the cutover with gaps nobody had the capacity to see. The right size is the smallest team that can actually maintain the artifacts and drive the decisions the exit demands.
Flex the staffing across the program's phases rather than holding it flat. The early phase needs design and planning capacity to build the dependency map and the plan. The middle is steady execution. The run up to cutover and the hypercare window need a surge of capacity for the runbook, the rehearsal, and the post go live support. A model that staffs for the average leaves the program thin at exactly the moments that matter most, so the plan should anticipate the peaks.
Most program offices are a blend of the buyer's own people and specialist advisors, and the blend is usually right. The buyer holds the accountable roles and the decisions, because the exit is the buyer's to own and the consequences are the buyer's to live with. Advisors bring the exit experience the internal team has not built, the pattern recognition that comes from having seen the same problems on other carve-outs, and the surge capacity the buyer cannot keep on staff for a one time program.
The line to hold is that the buyer owns the program rather than outsourcing the judgment. An advisor who runs the PMO and makes the calls leaves the buyer dependent and without the institutional learning the exit should produce. An advisor who supplies experience, structure, and capacity while the buyer's lead holds the decisions gives the buyer both the benefit of the experience and the ownership of the outcome. The buyer-side advisor's job is to make the buyer's team better, not to replace it.
Use advisors most where the gap between the buyer's experience and the exit's demands is widest. A buyer running its first carve-out benefits from heavy advisory support on the structure and the hard moments like the go no-go and the cutover. A portfolio that has run several exits and built its own playbook needs less, and uses advisors for capacity and for the specialist areas its team has not seen. Matching the support to the gap is what keeps the engagement efficient rather than open ended.
For a single exit, the PMO is stood up, runs the program, and stands down. For a portfolio running multiple carve-outs, the program office can become a standing capability that carries the playbook, the templates, and the experience from one deal to the next. That continuity is worth a great deal, because the second exit run by a team that ran the first starts with the dependency patterns, the gate criteria, and the cutover structure already understood.
A portfolio program office also smooths the staffing peaks across deals. The surge capacity that one exit needs at cutover can come from the team between phases on another, so the portfolio carries a more efficient total headcount than each deal staffing its own peaks independently. The same people who built the runbook on one carve-out bring that hard won skill to the next, and the firm stops rebuilding the capability from scratch every time.
Whether the PMO is a one time team or a standing function, feed its experience into the lessons learned process so the staffing model itself improves. The roles that were missing, the seniority that was too thin, the phase where the team was overrun are all lessons that sharpen the next exit's staffing plan. A buyer that treats its program office as a capability to refine, rather than a cost to minimize, is the buyer whose exits get faster and surer with every deal.
The program office runs the exit: it maintains the plan and the dependency map, tracks milestones and risks, runs the governance cadence, drives decisions to closure, and keeps the workstreams coordinated. It does not own the technical work; it owns the coordination, the visibility, and the accountability that hold the work together.
Sized to the number of workstreams and the complexity of the exit, not to a fixed ratio. A single TSA might need a lead and a coordinator; a multi service carve-out needs workstream leads plus a central core. Too large a PMO creates reporting overhead; too small a PMO loses control of the detail.
Often a blend. The buyer holds the accountable roles and the decisions, while specialist advisors bring exit experience the internal team has not built. The key is that the buyer owns the program rather than outsourcing the judgment, with advisors supplying capacity and pattern recognition.
A senior program lead with the authority to make decisions and hold workstreams accountable. A PMO staffed only with junior coordinators can track status but cannot drive the hard calls, and a TSA exit is full of hard calls under deadline pressure that need someone with the standing to make them.
The body the program office reports into and escalates to.
Read the article →How PMO roles map to accountability across the workstreams.
Read the article →How the program office turns each exit into a sharper next one.
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 →