The Roadmap Reveal
Presenting the plan to the client
Kurosawa Digital, executive boardroom. The projector hums. Ren's slides are loaded — revised three times since last night's rehearsal. Saki stands beside him with a clicker in one hand and a printed backup deck in the other. Director Kudo and four senior leaders sit across the table.
Ren (蓮) "Good morning. What you're about to see is the full roadmap for the XR platform — every phase, every milestone, and how we get from here to a working product by Week 24."
→ Ren frames the presentation around the project lifecycle — giving executives a clear structure they can follow without needing technical depth.
Saki (咲希) "The roadmap is anchored to our approved scope baseline. Each phase has defined deliverables, and we've mapped the critical path to show which activities determine our launch date."
→ Saki grounds the roadmap in formal PM artifacts — scope baseline, deliverables, and critical path — connecting the presentation to documented plans rather than promises.
Director Kudo (工藤部長) "Impressive structure. But let's be strategic — what does the board care about? The demo at Week 12. Tell me that's solid."
Ren (蓮) "The demo milestone sits on the critical path. Zero float. If any of the three activities leading into it slip, the demo slips. We've built buffer into the two weeks before it, but we're not hiding behind it."
→ Ren uses schedule management language naturally — critical path, float, buffer — to communicate risk honestly rather than overpromising.
Saki (咲希) "We've also identified resource constraints. The network diagram shows four activities dependent on a single team member. We have a cross-training plan to mitigate that."
→ Saki references the network diagram without showing it in detail — appropriate for an executive audience that needs confidence, not complexity.
Director Kudo (工藤部長) "I trust the team to manage the details. What I want to hear is: are we on track, and what do you need from us?"
Ren (蓮) "We need sign-off on the scope statement by Friday, and a decision on the AR module requirements Director Kudo raised last month. Those two items are blocking the planning phase exit."
→ Ren converts the presentation into specific asks — tying executive decisions to concrete project gates. This is effective stakeholder communication: making the audience's role in success clear.
Saki (咲希) [quietly, as the executives confer] "Your timing on the buffer slide was perfect. Told you the pause would work."
Ren (蓮) [equally quiet] "Your script notes saved me. I would've rambled through the cost section."
They share the smallest nod. Director Kudo watches them from across the table with an expression nobody can quite read.
Director Kudo (工藤部長) "You'll have your sign-off by Thursday. And I'll make a decision on the AR module by end of week. Good presentation. Both of you."
Tip Tailor depth to your audience. Executives need milestones and decisions. Technical leads need dependencies and constraints. Match the level of detail to what the listener can act on.
Phoenix Project Connection In The Phoenix Project, presenting a unified plan to leadership is the moment when IT earns a seat at the strategy table. The plan must speak in business outcomes, not technical activities.