Multi TSA Portfolio
Milestones that hold to the model.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
A TSA milestone tracking system turns a vague exit timeline into a sequence of dated, owned, verifiable promises. The buyer needs to know not just whether a milestone is late, but whether the milestones ahead of it are still achievable. Disciplined milestone tracking is how day one readiness stays honest from day one through final decommission.
A real milestone has three properties: a date, a single accountable owner, and verifiable exit criteria. A line on a plan that says migration complete with no criteria is not a milestone, because no one can say whether it was met. The milestone is met when the criteria are demonstrably satisfied, not when the owner feels the work is mostly done. That distinction is the entire discipline of milestone tracking.
Exit criteria are the heart of it. For a data migration milestone, the criteria might be that all records are migrated, reconciliation shows zero variance, the receiving system has run a full cycle, and the business owner has signed acceptance. Until every criterion is met, the milestone is not green, regardless of how close it looks. Writing the criteria in advance stops the negotiation about whether a milestone counts as done.
Milestones differ from tasks in scope and visibility. A program has hundreds of tasks and perhaps fifteen milestones. The milestones are the points where the program proves real progress to leadership, and they are chosen because missing one genuinely threatens the exit date. Tracking everything as a milestone buries the few that matter, so the system tracks tasks in the workstream plans and milestones at the program level.
Milestones are not independent. The data migration cannot complete before the target environment is ready, and the seller environment cannot be decommissioned before the migration is verified and the rollback window has closed. A milestone tracking system that shows dates without dependencies hides the real risk, which is that a slip in an early milestone cascades into every milestone that depends on it.
Map the dependencies explicitly so a slip in one milestone shows its effect on the chain. When an early milestone moves a week, the system shows which downstream milestones move with it and whether the exit date itself is now at risk. This is the difference between knowing a milestone is late and understanding what that lateness means for the program, which is the information leadership needs to decide whether to act.
Identify the critical path, the chain of milestones where any slip moves the exit date. The critical path concentrates leadership attention on the milestones that actually govern the timeline, rather than spreading it evenly across milestones that have slack. A milestone off the critical path can slip without moving the exit, and knowing which is which is what lets the program spend its limited attention where it changes the outcome. The dependency work behind this is detailed in the dedicated dependency mapping article.
The enemy of milestone tracking is optimism bias, the tendency of owners to report a milestone as on track until the week it is due, then late. The system counters this by tracking leading indicators, not just the final status. For a milestone due in four weeks, the system asks what proportion of its exit criteria are already met, and whether that proportion is rising fast enough to reach complete on time.
Use a confidence measure alongside the red, amber, green status. An owner who reports green but cannot point to criteria being met is signaling false confidence, and the program office tests that by asking for the evidence. A milestone is only credibly green when the trajectory of its criteria supports the date. This evidence based challenge is uncomfortable and necessary, and it is where an independent program office adds value the internal team often cannot.
Track the date the milestone was first set against the current forecast. A milestone that has been re forecast three times is a different signal from one holding its original date, and the re forecast history exposes the milestones that are quietly slipping through repeated small moves. A single column showing original date, current forecast, and number of re forecasts surfaces this pattern cheaply.
Milestones connect upward to the dashboard and the steering committee, and downward to the workstream tasks and the RACI. The dashboard shows milestone status to leadership. The committee acts on milestones at risk. The workstream plans hold the tasks that deliver each milestone. The RACI names the accountable owner. A milestone tracking system that is not wired into these is a standalone list that nobody acts on.
Tie each milestone to its accountable owner from the RACI so that a milestone at risk has a name attached, not just a status. When the dashboard shows a red milestone, the committee knows immediately who answers for it and can direct the conversation to that owner. Status without ownership produces discussion without resolution, and the milestone system exists to produce resolution.
Feed milestone status into the cost and takeout view. Many milestones gate a cost event: decommissioning a seller environment ends a TSA charge, completing a migration enables a takeout. When a milestone slips, the associated saving slips with it, and tying the two together lets leadership see the financial consequence of a schedule slip immediately. The milestones and the model move together, which is the connection the operating partner needs to report progress honestly.
Establish the milestone baseline early and hold it visible. The baseline is the set of milestones with their original dates and criteria, agreed at program start. Every subsequent forecast is measured against that baseline, which prevents the slow erosion where a series of small re forecasts moves the exit date without anyone noticing the cumulative slip. The baseline is the fixed point that makes drift measurable.
Review milestones at every steering committee meeting, focusing on the critical path and the re forecast history. The review is not a status recital but a decision forum: for each milestone at risk, what is the recovery plan, what decision does the committee need to make, and what is the consequence for the exit date if it slips further. This turns milestone tracking from reporting into control.
Close each milestone formally when its criteria are met, with the accountable owner confirming and the evidence recorded. A milestone closed on evidence is a milestone that will not reopen as a dispute with the seller later. At program end, a complete record of milestones met on evidence is the proof that the exit is genuinely done, and the asset the next carve-out in the portfolio inherits as a proven template.
A date, a single accountable owner, and verifiable exit criteria written in advance. The milestone is met when the criteria are demonstrably satisfied and the business owner accepts, not when the owner feels the work is mostly done.
Around fifteen at the program level. A program has hundreds of tasks but only a handful of milestones, chosen because missing one genuinely threatens the exit date. Tracking everything as a milestone buries the few that matter.
Track leading indicators, not just final status. Measure how many exit criteria are already met and whether that proportion is rising fast enough to finish on time, and challenge any green status that cannot point to criteria being met.
Because a slip in an early milestone cascades into every milestone that depends on it. Mapping dependencies and identifying the critical path shows whether a slip moves the exit date and concentrates attention on the milestones that actually govern the timeline.
The single view that shows milestone progress to leadership at a glance.
Read the article →The fifteen milestones that decide whether a TSA exit lands on schedule.
Read the article →The register that tracks the risks threatening each milestone.
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 →