Multi TSA Portfolio
One view leadership actually trusts.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Designing a TSA exit dashboard means choosing the few metrics that actually move a decision and discarding the rest. A buyer needs one view that shows milestone progress, open risk, cost against plan, and readiness, refreshed on a known cadence. A dashboard is where the reporting discipline of day one readiness becomes a picture leadership can read in a minute.
A dashboard exists to let leadership see the state of the exit in a minute and decide where to spend attention. It is not a data archive and not a substitute for the status report. The status report carries the narrative and the asks. The dashboard carries the picture: where the program stands against plan, what is at risk, and whether the trajectory is improving or deteriorating.
The test of a dashboard is whether it changes a decision. A metric that looks interesting but never alters what the operating partner does next is clutter, and clutter erodes trust because it makes the reader hunt for the signal. Every panel should answer a question leadership actually asks: are we on schedule, what could derail us, are we on budget, are we ready to cut over.
Build it for the operating partner and the steering committee, not for the program office. The program office lives in the detail and does not need a dashboard to know the state of the program. The dashboard translates that detail into the few signals leadership needs to govern, which means it shows less than the program office sees, deliberately.
The first panel is milestone progress. It shows the critical milestones, their target dates, their current status as red, amber, or green, and the trend since the last refresh. This is the panel leadership reads first, because the milestone dates are the promises the program made to the deal model, and a slipping milestone is the earliest credible signal that the exit is at risk.
The second panel is open risk and issues. It shows the count and severity of open items, the aging of the oldest reds, and the few specific risks that could move a milestone. Aging matters more than count, because a risk open for four periods is a stuck risk, and stuck risks are where exits fail quietly. The panel should make the stuck items impossible to miss.
The third panel is cost against plan. It shows TSA charges and exit program spend against budget, plus the takeout committed and realized to date. This panel ties the program to the value creation plan, and it is the one the investor cares about most, because a technically clean exit that misses the takeout has failed on the measure that matters. The fourth panel is readiness, a simple view of how many exit criteria each workstream has met against the total required, so leadership can see at a glance which functions are ready to cut over and which are behind.
Put the four panels on a single screen with no scrolling. The moment a dashboard requires scrolling or a second tab, it stops being a glance and becomes a report, and leadership stops opening it. The constraint of one screen forces the same discipline the one page status report forces: decide what matters and cut the rest.
Use consistent color meaning across every panel. Red, amber, green must mean the same thing everywhere: red is action needed now, amber is a managed risk to watch, green is on plan. When colors drift in meaning between panels, the reader has to interpret rather than absorb, and the dashboard loses the speed that justifies it. Color is the language of the dashboard, and it must be spoken consistently.
Resist the request to add metrics. Every stakeholder wants their number on the dashboard, and a dashboard that grants every request becomes a wall of numbers that signals nothing. The program office protects the dashboard by holding the line at the four panels and directing detailed metrics to the underlying reports. A disciplined dashboard says no to most of what could be shown.
Refresh the dashboard on a known cadence tied to the reporting rhythm, usually weekly. A dashboard with no refresh discipline becomes stale, and a stale dashboard is worse than none because it shows a state that is no longer true. State the as of date prominently so the reader always knows the currency of what they are seeing.
Drive the dashboard from the same source as the status reports, not from a parallel data set maintained by hand. When the dashboard and the reports disagree, trust collapses, and reconciling two sources consumes the program office time that should go to the work. One source feeding both the narrative report and the visual dashboard keeps them consistent and keeps the maintenance burden low.
Automate the refresh as far as the tooling allows, but never at the cost of accuracy. A dashboard that updates automatically from a milestone tracker and a cost model is ideal, because it removes the manual step where errors enter. Where automation is not possible, a disciplined weekly manual refresh from the single source is acceptable, provided the as of date is honest. The milestone tracking that feeds the first panel is covered in its own dedicated work.
The first failure is the vanity dashboard, full of green that hides the reds inside aggregated metrics. A dashboard that rolls everything into a single overall status loses the specific signals that matter, and an overall green that masks a red critical milestone is actively misleading. Show the components, not just the aggregate, so the one red item cannot hide behind nine green ones.
The second failure is the dashboard nobody trusts because it disagrees with reality. This happens when the dashboard is maintained separately from the work, when its refresh lags, or when its definitions are loose. Trust is the entire value of a dashboard, and once leadership learns it is wrong, they go around it, which defeats its purpose. Protect trust by tying the dashboard to one source and a known refresh.
The third failure is the dashboard that shows state but not trend. A snapshot tells leadership where the program is, but not whether it is getting better or worse, and the trajectory is often the more important signal. A milestone that is amber and improving needs different attention from one that is amber and deteriorating. Adding a simple trend indicator to each panel turns a snapshot into a story, and the story is what drives the decision.
Four panels: milestone progress against target dates, open risk and issue aging, cost against plan with takeout committed and realized, and readiness measured as exit criteria met per workstream. Anything that does not change a decision is clutter.
The status report carries the narrative, the asks, and the detail. The dashboard carries the picture: where the program stands against plan, what is at risk, and whether the trend is improving. Both should draw from the same single source.
Weekly, tied to the reporting rhythm, with the as of date shown prominently. A stale dashboard is worse than none because it shows a state that is no longer true and quietly erodes trust.
Usually because they are maintained separately from the work and disagree with reality, or because they aggregate everything into an overall status that hides a red item inside green. Tie the dashboard to one source and show components, not just the aggregate.
The tracker that feeds the milestone panel and proves the exit is on schedule.
Read the article →The reporting rhythm and single source that the dashboard visualizes.
Read the article →The risk register that drives the open risk and aging panel.
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 →