Practice the English vocabulary for product strategy discussions: roadmaps, prioritization frameworks, OKRs, and product vision communication.
0 / 33 completed
1 / 33
What is the difference between a 'strategy' and a 'roadmap' in product development?
Strategy defines your competitive position, target market, and how you will win. The roadmap operationalizes the strategy into concrete initiatives with timelines. Without strategy, a roadmap is just a feature list.
2 / 33
What does 'now / next / later' roadmap format communicate?
Now/Next/Later avoids the trap of committing to distant dates that will change. It communicates direction and priority while being honest that plans 6+ months out are directional, not commitments.
3 / 33
What is 'product-market fit' and how is it discussed in startup communication?
PMF (product-market fit) is the holy grail for early-stage startups. Marc Andreessen's original definition: you know you have PMF when you can feel it — waitlists, word-of-mouth growth, users upset when it breaks. The Superhuman metric: 40%+ users would be 'very disappointed' without the product.
4 / 33
What does 'RICE scoring' prioritize features by?
RICE provides a structured way to compare features. Reach = users/month impacted; Impact = effect per user (1-3x multiplier); Confidence = % sure about estimates; Effort = person-months. Higher RICE score = higher priority.
5 / 33
What is 'opportunity sizing' in product strategy discussions?
Opportunity sizing answers 'how big is this if we succeed?' It combines market size (TAM), addressable share (SAM), and realistic capture (SOM). 'If we capture 10% of the 2M-user segment, at $50 ARR, that is $10M ARR' is a classic opportunity sizing statement.
6 / 33
What does 'thesis-driven roadmap' mean?
A thesis-driven roadmap makes assumptions explicit: 'We believe that if we reduce onboarding time from 10 minutes to 3, activation will increase by 20%'. This allows teams to measure whether the thesis was correct and update the roadmap based on evidence.
7 / 33
What is a 'strategy tax' in product development?
Strategy tax is the cost of serving multiple strategic goals simultaneously. A product built for both consumers and enterprises often serves neither optimally. Teams acknowledge strategy tax when they build features required by a major partner rather than their core users.
8 / 33
How would an engineer communicate technical strategy input to the product roadmap?
Engineers influence the roadmap by connecting technical needs to business outcomes: 'delay causes X business impact'. Framing technical work as a dependency for a business goal (enterprise SSO = revenue) is far more persuasive than arguing for technical quality alone.
9 / 33
Reviewer: "This PR doesn't clearly articulate the *why* behind this API endpoint. We need to connect it back to a specific user story or product objective."
The reviewer isn't criticizing the *code* itself, but rather its alignment with the product strategy. A good roadmap discussion connects every feature back to a larger goal—a user story or objective. Options A and D are misinterpretations; this is about strategic context, not just technical correctness.
10 / 33
"Product Manager: Hey team, we're shifting focus to MVP for Feature X. Let's prioritize speed and validation over a fully-featured launch. Think iterative!"
The italicized phrase highlights the core concept of an MVP: prioritizing speed and validation. This aligns with a 'lean' product strategy focused on learning quickly. Option A is incorrect because it suggests a complex approach; option D misinterprets the message as a lack of planning – the PM is advocating for *iterative* development.
This example demonstrates how product strategy information might be structured within an API. The fields (feature, priority, target users) are key elements of a product roadmap discussion. Options A and C misunderstand the purpose; this is *not* just raw data—it's formatted for strategic communication.
12 / 33
"Pull Request Description: 'Implemented new user authentication flow. This improves security.'"
While technically correct, the PR description lacks strategic context. A good roadmap discussion would connect this authentication flow to a broader product goal (e.g., 'Improved user security as part of our enhanced onboarding experience'). Options A and D are relevant; it *is* lacking strategic framing.
13 / 33
"Sarah (Product): 'I'm currently focused on finalizing the user stories for the new payment integration. We're aiming to have a prototype ready by next week.'"
Sarah's statement provides a clear update on her work but doesn't explicitly mention the roadmap. A more strategic update might connect this payment integration to broader revenue goals or user acquisition strategies – demonstrating how it aligns with the overall product vision.
14 / 33
Reviewer: "This PR doesn't clearly articulate the *why* behind this API endpoint. We need to connect it back to a specific user story or product objective."
The reviewer isn't criticizing the *code* itself, but rather its alignment with the product strategy. A good roadmap discussion connects every feature back to a larger goal—a user story or objective. Options A and D are misinterpretations; this is about strategic context, not just technical correctness.
15 / 33
"Product Manager: Hey team, we're shifting focus to MVP for Feature X. Let's prioritize speed and validation over a fully-featured launch. Think iterative!"
The italicized phrase highlights the core concept of an MVP: prioritizing speed and validation. This aligns with a 'lean' product strategy focused on learning quickly. Option A is incorrect because it suggests a complex approach; option D misinterprets the message as a lack of planning – the PM is advocating for *iterative* development.
This example demonstrates how product strategy information might be structured within an API. The fields (feature, priority, target users) are key elements of a product roadmap discussion. Options A and C misunderstand the purpose; this is *not* just raw data—it's formatted for strategic communication.
17 / 33
"Pull Request Description: 'Implemented new user authentication flow. This improves security.'"
While technically correct, the PR description lacks strategic context. A good roadmap discussion would connect this authentication flow to a broader product goal (e.g., 'Improved user security as part of our enhanced onboarding experience'). Options A and D are relevant; it *is* lacking strategic framing.
18 / 33
"Sarah (Product): 'I'm currently focused on finalizing the user stories for the new payment integration. We're aiming to have a prototype ready by next week.'"
Sarah's statement provides a clear update on her work but doesn't explicitly mention the roadmap. A more strategic update might connect this payment integration to broader revenue goals or user acquisition strategies – demonstrating how it aligns with the overall product vision.
19 / 33
Reviewer: "This PR doesn't clearly articulate the *why* behind this API endpoint. We need to connect it back to a specific user story or product objective."
The reviewer isn't criticizing the *code* itself, but rather its alignment with the product strategy. A good roadmap discussion connects every feature back to a larger goal—a user story or objective. Options A and D are misinterpretations; this is about strategic context, not just technical correctness.
20 / 33
"Product Manager: Hey team, we're shifting focus to MVP for Feature X. Let's prioritize speed and validation over a fully-featured launch. Think iterative!"
The italicized phrase highlights the core concept of an MVP: prioritizing speed and validation. This aligns with a 'lean' product strategy focused on learning quickly. Option A is incorrect because it suggests a complex approach; option D misinterprets the message as a lack of planning – the PM is advocating for *iterative* development.
This example demonstrates how product strategy information might be structured within an API. The fields (feature, priority, target users) are key elements of a product roadmap discussion. Options A and C misunderstand the purpose; this is *not* just raw data—it's formatted for strategic communication.
22 / 33
"Pull Request Description: 'Implemented new user authentication flow. This improves security.'"
While technically correct, the PR description lacks strategic context. A good roadmap discussion would connect this authentication flow to a broader product goal (e.g., 'Improved user security as part of our enhanced onboarding experience'). Options A and D are relevant; it *is* lacking strategic framing.
23 / 33
"Sarah (Product): 'I'm currently focused on finalizing the user stories for the new payment integration. We're aiming to have a prototype ready by next week.'"
Sarah's statement provides a clear update on her work but doesn't explicitly mention the roadmap. A more strategic update might connect this payment integration to broader revenue goals or user acquisition strategies – demonstrating how it aligns with the overall product vision.
24 / 33
Reviewer: "This PR doesn't clearly articulate the *why* behind this API endpoint. We need to connect it back to a specific user story or product objective."
The reviewer isn't criticizing the *code* itself, but rather its alignment with the product strategy. A good roadmap discussion connects every feature back to a larger goal—a user story or objective. Options A and D are misinterpretations; this is about strategic context, not just technical correctness.
25 / 33
"Product Manager: Hey team, we're shifting focus to MVP for Feature X. Let's prioritize speed and validation over a fully-featured launch. Think iterative!"
The italicized phrase highlights the core concept of an MVP: prioritizing speed and validation. This aligns with a 'lean' product strategy focused on learning quickly. Option A is incorrect because it suggests a complex approach; option D misinterprets the message as a lack of planning – the PM is advocating for *iterative* development.
This example demonstrates how product strategy information might be structured within an API. The fields (feature, priority, target users) are key elements of a product roadmap discussion. Options A and C misunderstand the purpose; this is *not* just raw data—it's formatted for strategic communication.
27 / 33
"Pull Request Description: 'Implemented new user authentication flow. This improves security.'"
While technically correct, the PR description lacks strategic context. A good roadmap discussion would connect this authentication flow to a broader product goal (e.g., 'Improved user security as part of our enhanced onboarding experience'). Options A and D are relevant; it *is* lacking strategic framing.
28 / 33
"Sarah (Product): 'I'm currently focused on finalizing the user stories for the new payment integration. We're aiming to have a prototype ready by next week.'"
Sarah's statement provides a clear update on her work but doesn't explicitly mention the roadmap. A more strategic update might connect this payment integration to broader revenue goals or user acquisition strategies – demonstrating how it aligns with the overall product vision.
29 / 33
Reviewer: "This PR doesn't clearly articulate the *why* behind this API endpoint. We need to connect it back to a specific user story or product objective."
The reviewer isn't criticizing the *code* itself, but rather its alignment with the product strategy. A good roadmap discussion connects every feature back to a larger goal—a user story or objective. Options A and D are misinterpretations; this is about strategic context, not just technical correctness.
30 / 33
"Product Manager: Hey team, we're shifting focus to MVP for Feature X. Let's prioritize speed and validation over a fully-featured launch. Think iterative!"
The italicized phrase highlights the core concept of an MVP: prioritizing speed and validation. This aligns with a 'lean' product strategy focused on learning quickly. Option A is incorrect because it suggests a complex approach; option D misinterprets the message as a lack of planning – the PM is advocating for *iterative* development.
This example demonstrates how product strategy information might be structured within an API. The fields (feature, priority, target users) are key elements of a product roadmap discussion. Options A and C misunderstand the purpose; this is *not* just raw data—it's formatted for strategic communication.
32 / 33
"Pull Request Description: 'Implemented new user authentication flow. This improves security.'"
While technically correct, the PR description lacks strategic context. A good roadmap discussion would connect this authentication flow to a broader product goal (e.g., 'Improved user security as part of our enhanced onboarding experience'). Options A and D are relevant; it *is* lacking strategic framing.
33 / 33
"Sarah (Product): 'I'm currently focused on finalizing the user stories for the new payment integration. We're aiming to have a prototype ready by next week.'"
Sarah's statement provides a clear update on her work but doesn't explicitly mention the roadmap. A more strategic update might connect this payment integration to broader revenue goals or user acquisition strategies – demonstrating how it aligns with the overall product vision.
What will I learn from the "Product Strategy and Roadmap Language (English)" exercise?
Practice the English vocabulary for product strategy discussions: roadmaps, prioritization frameworks, OKRs, and product vision communication.
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 33 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 Startup & Product Language exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss startup & product language 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 33 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Startup & Product Language exercises?
See the full Startup & Product Language 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.