Roadmap Stakeholder Updates — Vocabulary and Language
Learn vocabulary for communicating roadmap changes, delays, and re-prioritisation to different stakeholders.
0 / 10 completed
1 / 10
What should a roadmap change communication include?
Roadmap change communication: WHAT changed (Feature X is delayed 4 weeks), WHY (unexpected dependency on the payments infrastructure migration), IMPACT (the activation experiment starts 4 weeks later), NEXT STEPS (revised timeline: X now delivers end of Q3). Keep it factual, brief, and focused on what stakeholders need to know to plan.
2 / 10
What is 're-prioritisation' communication vocabulary?
Re-prioritisation communication: 'Following the new customer commitment to [Enterprise Client], we are elevating the SSO integration from Q3 to Q2. This means the self-serve billing portal moves to Q3. We are informing affected stakeholders now so they can plan accordingly. Full updated roadmap attached.'
3 / 10
What is a 'roadmap FAQ' and when is it useful?
A roadmap FAQ saves communication time: 'Why isn't dark mode on the roadmap?' → 'Dark mode is in our backlog but below our current top priorities. We expect to revisit it after Q3 retention work. Subscribe to our changelog for updates.' This scales answers to common questions without requiring 1:1 stakeholder conversations.
4 / 10
What is 'roadmap confidence level' vocabulary?
Roadmap confidence levels: 'The Q1 items are committed and will ship. Q2 items are planned with high confidence (80%+). Q3 and beyond items are directional — they represent our current thinking but may change based on what we learn in Q1-Q2. Please do not build external dependencies on Q3+ items without checking with us.'
5 / 10
What is the difference between 'committed' and 'directional' on a roadmap?
Committed: 'We are building this, it will ship in Q2.' The team has estimated, resources are allocated, dependencies are cleared. Directional: 'We intend to work on this in the second half of the year, but specifics may change as we learn more.' This distinction manages stakeholder expectations and prevents roadmap items from being treated as promises before they should be.
6 / 10
Sarah, a product manager, is drafting an update for stakeholders regarding a shift in the roadmap. Which of the following statements best reflects the *tone* she should use when communicating this change?
'We've decided to move feature X to Q3 due to unexpected resource constraints.'
Sarah should use a neutral tone when communicating roadmap changes. This demonstrates objectivity and avoids appearing overly controlling or dismissive of stakeholder concerns. It's crucial to frame the change in terms of data (resource constraints) rather than personal preference. Options A & D are inappropriate – they lack transparency and could cause friction.
7 / 10
During a Slack conversation about the roadmap, David asks, 'So, is this still *on track*?' What does David likely mean in this context?
'Has the timeline remained consistent with our original plan?'
'On track' in this context refers to whether the roadmap – specifically the timeline for a feature – aligns with the originally planned schedule and objectives. It's a common idiom used to gauge project momentum. Option A is incorrect; it describes completion, not ongoing progress. Options C & D are irrelevant to the question.
8 / 10
Mark, a senior developer, submits a code review comment on a PR: 'This change introduces a dependency on a new API. We need to ensure this aligns with the roadmap's strategy for integrating external services.' What is Mark *primarily* concerned about?
'The strategic fit of the technical work with the overall product vision.'
Mark's comment focuses on strategic alignment. He's questioning whether adding a new API dependency supports the overall product vision outlined in the roadmap. While code quality and technical feasibility are important, Mark is prioritizing the bigger picture – ensuring consistent direction across all initiatives. Options A & B are related to the PR itself, not the roadmap.
9 / 10
During a standup meeting, Emily states: 'We're continuing to make progress on the Alpha release, and we've updated the roadmap to reflect the increased complexity of integrating with the new payment gateway.' What does 'updated the roadmap' specifically imply?
'Revised the plan based on changes in scope or priorities.'
When a roadmap is 'updated,' it almost always means revisions have been made to reflect new information. In this case, Emily's statement indicates that the complexity of integrating with the payment gateway has necessitated changes to the original plan – likely adjustments to scope or priorities. Options A & B are related to scheduling/budgeting, while option C is a technical change.
10 / 10
Liam, a product owner, sends an email to the development team: 'Given the recent shift in priorities, we're now aiming for a *longer-term* delivery of Feature Y.' What does Liam likely mean?
'The feature is expected to take significantly more time to complete than initially planned.'
'Longer-term delivery' signals a change in the timeline and typically implies increased complexity or unforeseen challenges. It indicates that the feature will not be delivered as quickly as originally anticipated – essentially, its priority has decreased relative to other items on the roadmap. Options A & D are incorrect; they describe speed/scope changes.
What will I learn from the "Roadmap Stakeholder Updates — Vocabulary and Language" exercise?
Learn vocabulary for communicating roadmap changes, delays, and re-prioritisation to different stakeholders.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 10 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Roadmap & OKR exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss roadmap & okr topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 10 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Roadmap & OKR exercises?
See the full Roadmap & OKR exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.