The executive sponsor had committed to the board that all four workstreams would launch simultaneously. By the time the planning team reached the final readout in Step 9, ten weeks of data told a clear story: simultaneous launch carried risks the sponsor hadn’t fully quantified, and the readout needed to make those risks visible without arguing against the sponsor’s position. The principle was to start with the content before the slides: know what the room needs to decide, then design the deck to make that decision legible.
Effective Readouts Present Data Without Taking a Position
The consulting team could have built a readout recommending phased deployment, but this approach would have failed for a predictable reason: executives who have committed to a position publicly (particularly to a board) don’t respond well to being told they’re wrong by the outside firm they hired. The readout needed to present the data the planning team had built together, organized to make the tradeoff between simultaneous and phased deployment visible without taking a position on which option was right. The decision had to belong to the sponsor; the readout’s job was to make sure the decision was informed.
Three Slides Carried the Weight of a Twelve-Slide Deck
The dependency map showed that three of the four workstreams depended on the same enterprise integration layer, and the integration team had capacity to support one workstream’s testing at a time with a two-week turnaround between workstreams. The slide showed the dependencies, the integration team’s capacity, and the implied timeline if all three workstreams required support simultaneously. The room could see that simultaneous launch required three parallel configuration streams, something their own integration lead had flagged during the pre-mortem.
The constraints calendar showed two operational blackouts in the launch window: a system upgrade that froze the integration environment for ten days and a managed care contracting window that restricted field team redeployment for three weeks. The launch window that looked like twelve available weeks on the original plan was seven usable weeks when the blackouts were removed. Presenting the constraints calendar alongside the dependency map showed how the constraints interacted with the simultaneous launch assumption: seven usable weeks with three workstreams competing for the same resource and two unmovable blackout periods.
The risk register, filtered to the top five risks, had been generated during the pre-mortem by members of the sponsor’s own team. Three of the five were directly related to concurrent launch:
- Resource contention on the integration team, compounded by compressed testing windows with no margin for rework
- Change management overload on field teams absorbing four workstream changes simultaneously
Each had been rated high likelihood and high impact using the client’s own methodology.
The Room’s Own Data Replaces the Need for a Recommendation
The slides didn’t include a recommendation. There was no alternative timeline and no “we recommend phased deployment” slide. The data in the readout had been generated by the sponsor’s own team across ten weeks: the dependency map came from architecture sessions; the constraints calendar and risk register came from the pre-mortem. We had facilitated the work, but the content belonged to the room.
Presenting the room’s own data back to leadership, organized to make a specific tradeoff visible, is a different act than making a recommendation. The sponsor isn’t being told they’re wrong; the sponsor is seeing data their own team generated, arranged to show a tradeoff they can now evaluate.
Readouts That Change Minds Let the Decision Belong to the Room
The sponsor studied the dependency map, confirmed the capacity constraint with the integration lead, did the math on usable weeks, then asked the program lead what a phased approach would look like. The program lead walked through a two-phase option that aligned with the integration team’s capacity and avoided both blackout periods. The sponsor approved the phased approach before the session ended.
Readouts that change minds present the room’s own work back to leadership in a format that makes the right decision legible. This is what a readout a CFO will actually read looks like: data organized to produce a decision, not a presentation. When the closing hits this way, the readout becomes the beginning of the transfer of ownership rather than the end of the engagement.
