Six phrases for presenting a roadmap clearly — from opening to close. Tap each card to reveal the meaning, then we'll talk about it.
What's usually the first thing you'd want people to understand about a roadmap?
How do you usually signal moving from one phase of a plan to the next?
Why is it useful to be upfront about what a phase depends on, rather than just saying it'll happen?
How do you usually hedge timing when you're not 100% sure of a date?
How far ahead do you think is actually useful to show on a roadmap before it starts feeling too speculative?
How do you like to close out a roadmap presentation — a summary, a call to action, something else?
Walk your team through a roadmap for the next two quarters — made up on the spot. Open it clearly, sequence the phases, flag one dependency, hedge the timing, and close it properly.
I'll play a team member — I might ask what something depends on, or push on a date.
Same roadmap, higher stakes: present it again to senior leadership, who are more skeptical about timing and want to know what could go wrong.
I'll play a senior leader — expect at least one tough question about a date or a dependency.
Three short tasks to lock in this week's phrases. Should take about 15 minutes total.
Sentence A:
Sentence B: