Learn vocabulary for communicating product and technical roadmaps: Now/Next/Later, milestones, and roadmap updates.
0 / 10 completed
1 / 10
What is the 'Now/Next/Later' roadmap framework?
Now/Next/Later (popularized by Janna Bastow) is a horizon-based roadmap: Now = in development now, Next = clearly planned, Later = directional/aspirational. It avoids the false precision of date-based roadmaps while communicating direction. Later items acknowledge uncertainty honestly.
2 / 10
What is the difference between a 'feature roadmap' and an 'outcome roadmap'?
Feature roadmap: 'Q1: dark mode, Q2: offline support, Q3: team collaboration.' Outcome roadmap: 'Q1: Improve new user activation (dark mode, onboarding improvements), Q2: Increase B2B retention (offline support, admin controls).' Outcome roadmaps explain WHY features are being built and connect to business goals.
3 / 10
What does 'roadmap slippage' mean in product vocabulary?
Roadmap slippage is common and must be communicated proactively: 'The mobile redesign is slipping by 3 weeks due to unexpected API complexity discovered during implementation. Revised delivery: end of Q2. Impact: the user retention experiment will start 3 weeks later than planned. No other items are affected.'
4 / 10
What is 'product discovery' in roadmap vocabulary?
Product discovery (Teresa Torres, Marty Cagan) is the work that happens BEFORE items go on the roadmap: understanding the problem, validating assumptions, prototyping solutions. A healthy roadmap reflects discovered, validated opportunities — not just feature requests or executive demands.
5 / 10
What is a 'technical roadmap' and how does it differ from a product roadmap?
A technical roadmap covers: platform migrations, infrastructure upgrades, technical debt paydown, developer experience improvements, compliance work. It makes invisible technical work visible to leadership and justifies investment. Often presented alongside the product roadmap to show the full picture of engineering work.
6 / 10
Sarah from the frontend team just posted this Slack message: 'Just finished implementing the new user onboarding flow. Looks good to me! 👍'. What does 'looks good to me!' primarily convey in this context?
'Looks good to me!' is a common Slack idiom used to indicate that something appears satisfactory without needing detailed examination. It's often used during early stages of development or when a quick check confirms functionality. It doesn't necessarily mean no further action is needed – it simply signifies initial approval, and the reviewer might still provide minor comments. Options A, C, and D are inappropriate for this casual Slack message.
7 / 10
Mark, the Product Manager, is drafting a pull request description for a new API endpoint. He writes: 'This PR introduces the ability to retrieve user profile data via the /users/{userId} endpoint.' What's the most important reason Mark should also include information about *why* this endpoint was created in his description?
A clear PR description should always explain *why* a change was made. Developers using this API need to understand its purpose and how it fits into the overall system. Simply stating the endpoint's name doesn't convey that information; context is crucial for effective integration. Options A, C, and D are technically relevant but not the primary reason for including the 'why' in a PR description.
8 / 10
David is discussing the roadmap with the development team. He says: 'We need to prioritize features based on their impact on our key performance indicators (KPIs).' What concept is David primarily referring to?
David's statement highlights the importance of prioritizing roadmap items based on their impact on KPIs – quantifiable measures of success. This is a core element of product discovery and prioritization, where decisions are made using data to maximize value. Agile Sprint Planning focuses on short-term tasks, Technical Debt Management addresses long-term code quality, and Release Cycle Optimization relates to deployment frequency.
9 / 10
Emily, a Senior Developer, is preparing for a standup meeting. She says: 'Yesterday, I spent time researching the new OAuth 2.0 implementation and evaluating different libraries.' What type of activity is Emily describing?
Emily's description – researching and evaluating new libraries – falls squarely into the category of product discovery. This involves exploring potential solutions, understanding their capabilities, and assessing their suitability for future projects. Bug Fixing addresses existing issues, Technical Debt Reduction focuses on improving code quality, and Feature Implementation is about building new functionality.
10 / 10
Ben writes in his roadmap documentation: 'The goal of this release is to improve user engagement by increasing daily active users (DAU) by 15%.' Which of the following best describes Ben's approach to roadmap communication?
Ben's statement demonstrates a focus on aligning the roadmap with business objectives – specifically, improving user engagement as measured by DAU. Roadmaps should communicate how technical work contributes to achieving tangible outcomes. Prioritizing based on developer preference or ignoring user feedback is not effective roadmap communication.
What will I learn from the "Roadmap Communication — Vocabulary and Language" exercise?
Learn vocabulary for communicating product and technical roadmaps: Now/Next/Later, milestones, and roadmap updates.
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.