Multi TSA Portfolio
A cutover call you can defend.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
A TSA go no-go decision framework sets the criteria, the evidence, and the authority that decide whether a cutover proceeds. The buyer who fixes the criteria before the meeting, and decides on documented proof rather than confidence in the room, makes the most consequential call of the exit calmly. The go or no go decision is where every thread of day one readiness is pulled together into a single answer.
The go or no go decision is the last point at which a buyer can stop a TSA cutover before it becomes irreversible. Once the seller's service is switched off, reversing the exit is expensive or impossible, so the decision to proceed carries the full weight of the cutover's consequences. A decision of that gravity should never be made on the gut feel of whoever is most senior in the room, because gut feel under deadline pressure reliably tilts toward go.
A framework removes the improvisation by deciding, well in advance, what would make the cutover safe to proceed. The criteria are agreed when nobody is under pressure, and the decision meeting simply tests reality against them. This separation matters because the moment of decision is exactly when judgment is worst: the team is invested, the date has been promised, and the instinct to go is strongest precisely when the evidence most deserves a cold reading.
The framework also makes the decision defensible after the fact. If the cutover proceeds and something goes wrong, the buyer can show the criteria that were met and the evidence behind them. If the cutover is held, the buyer can show why. Either way the decision was made by a process rather than by a personality, which is what allows an investor to trust that the call was sound regardless of how it turned out.
A sound go no-go covers more than the technical migration, because a cutover can fail in any dimension. The criteria should span technical readiness, where the build is complete and tested; business readiness, where the people who will use the new operation are trained and prepared; the support plan, where the hypercare team is staffed and ready; the rollback plan, where a tested path back exists; and the people, where the named operators for the cutover window are confirmed and available.
Each criterion should be binary and evidenced, not a matter of opinion. Testing complete means the execution report shows the cases passed and the open defect list carries nothing above the agreed severity, not that the test lead feels good about it. Business readiness means the training was delivered and the business owner has signed, not that communications were sent. The discipline of phrasing every criterion as a checkable fact is what keeps the decision anchored to reality.
Weight the criteria so the decision is not held hostage by a trivial open item while a serious one is waved through. A blocking criterion, such as an untested rollback, should be capable of forcing a no-go on its own. A minor open item should be recordable as a condition the team will manage rather than a reason to stop. Distinguishing the two in advance prevents both the over caution that holds a ready cutover and the optimism that proceeds past a real blocker.
When the decision is made matters as much as how. Made too early, it relies on readiness evidence that will be stale by the cutover, and the team ends up going live on a judgment that no longer reflects the state of the program. Made too late, it leaves no room to act on a no-go, and the decision collapses into a formality because stopping is no longer practical. The right moment is close enough that the evidence is current and far enough that a no-go can still change the plan.
A common pattern stages the decision. A preliminary checkpoint a week or so out confirms the program is on track to be ready and surfaces any criterion at risk, giving the team a last chance to close gaps. The final go no-go sits a day or two before the cutover, when the evidence is fresh, and confirms that the criteria flagged earlier have actually been met. The staging means the final decision is rarely a surprise, because the program has already seen where it stood.
Align the go no-go with the readiness gates that preceded it. The final gate before cutover and the go no-go are closely related, and a program that has run honest gates arrives at the go no-go with most of its evidence already assembled and validated. When the gate discipline and the go no-go framework reinforce each other, the final decision becomes the confirmation of a known state rather than a fresh and anxious assessment.
The decision rests with the governance body accountable for the exit, but every workstream lead needs the standing to flag a blocking issue in their area. The person responsible for the data migration must be able to say their part is not ready and have that count, because they are the one who knows. A go no-go where only the most senior voice matters loses exactly the front line knowledge that should inform it.
A no-go has to be a respected outcome rather than a failure that costs someone standing. If calling no-go is treated as letting the team down, people will stop calling it, and the framework hollows out into a ritual that always produces go. Leadership sets this tone by treating a well evidenced no-go as the system working: the cost of holding a cutover for a week is real but bounded, while the cost of going live on a broken one cascades through the operation and the deal.
Give an independent voice a place in the room. A buyer-side advisor or assurance lead who is not running a workstream can read the evidence without the optimism that comes from having built the thing, and can ask whether the criteria are genuinely met or merely reported as met. That outside challenge is most valuable precisely at the go no-go, where the people who did the work are least able to see where it is thin and the consequences of proceeding are highest.
When the decision is go, it should trigger the cutover cleanly: the runbook starts, the support window is on standby, and everyone knows the call has been made. A go decision that leaves ambiguity about whether the cutover is actually proceeding wastes the clarity the framework was meant to create. Record the decision, the criteria met, and any conditions the team carries forward, so the cutover lead and the hypercare team inherit a clear picture of where things stood at the moment of commitment.
When the decision is no-go, it should trigger an equally clear path: the gaps that forced the hold, the actions to close them, and a date for the next decision. A no-go that simply postpones without a plan to become ready repeats itself at the next attempt. The value of a no-go is the work it forces, so the framework should turn the decision into owned, dated actions feeding back into the milestone plan and risk register.
Capture the decision and its basis for the lessons learned record. Whether the cutover went well or badly, the criteria used and the evidence behind them are the most useful material for sharpening the framework on the next carve-out. A portfolio that reviews its go no-go decisions learns where its criteria were too soft or too rigid, which is how a buyer makes the hardest call of the exit a little more reliable every time it has to make it.
It is the final decision, made just before a TSA cutover, on whether to proceed with the exit or hold. It is made against criteria fixed in advance and evidenced at the meeting, by the people with the authority to commit the operation to the cutover.
Close enough to the cutover that the evidence is current, but with enough time left to act on a no-go without forcing the team into the window unprepared. A decision made too early relies on stale readiness; one made too late leaves no room to stop.
Evidence based, binary criteria covering technical readiness, business readiness, the support plan, the rollback plan, and the people available to run the cutover. Each criterion is met or not met on documented proof, so the decision rests on facts rather than on confidence.
The governance body accountable for the exit, with each workstream lead able to flag a blocking issue in their area. A no-go should be a respected outcome, not a career risk, because the cost of holding a cutover is far lower than the cost of going live on a broken one.
The gates that assemble the evidence the go no-go relies on.
Read the article →What a go decision triggers, step by step.
Read the article →The body that holds the authority to call go or no go.
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.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →