Read the evidence before inventing a solution
Treat each scenario as a product decision, not a trivia question. Identify what is known, what is assumed, and what the constraint changes.
Self-paced PM judgment practice
Product Management Exercises
Practice realistic Product Management decisions instead of memorizing definitions. Each fictional scenario gives you evidence, ambiguity, a constraint, and a decision to make—then lets you reveal a reasoning guide after you commit your thinking.
11 decision scenariosFoundation → advancedNo loginLocal draft savingNo hiring scoreSelf-paced, not interview-style
Practice method
Scenario → evidence → decision → trade-off → reflection
Product judgment is rarely a vocabulary test. The useful rep is deciding under incomplete information, making assumptions visible, and knowing what evidence would change your mind.
Commit to a decision or a learning action
Write what you would do next, why it beats the alternatives, and what you are deliberately giving up. If the evidence is insufficient, choose what to learn rather than pretending certainty.
Reveal the reasoning guide
Compare your reasoning with strong signals, weak patterns, and alternative defensible paths. There is no hidden perfect answer for judgment-heavy PM work.
Turn the decision into an artifact when useful
Use the linked CraftUp tool, template, course, or interview mode only after the scenario has forced the underlying product judgment.
Self-paced practice lab
Make the decision before you reveal the reasoning guide
Every scenario is fictional. Write your recommendation, rationale, assumptions, and trade-off first. The guide does not grade you; it shows what strong reasoning should consider and where plausible alternatives exist.
DiscoveryIntermediate
Three feature requests, one underlying problem
Scenario
You own a fictional B2B workflow product. Support, Sales, and users are asking for a Slack digest, bulk editing, and mobile approvals. The team can spend one week reducing uncertainty before the next planning cycle, but cannot build a major integration this sprint.
Evidence
- Support tickets mention the Slack digest most often, but many describe the underlying pain as chasing reviewers and switching context to find pending work.
- In recent manager interviews, only one person insisted on Slack specifically; others cared more about knowing what is blocked and who needs to act.
- Usage data shows many invited reviewers never complete a first approval, with a larger drop on mobile than desktop.
- One enterprise prospect has made a Slack integration part of its evaluation, but the deal is not committed.
Constraint
You have one discovery week. You can run targeted interviews, inspect event data, or prototype a lightweight workflow, but you cannot build all three requests to see what happens.
Your task
- 1Identify the user problems that may sit underneath the three requested features.
- 2Separate facts, interpretations, assumptions, and commercial signals.
- 3Choose the next evidence you would gather and explain why it changes the decision.
- 4State what you would not decide yet.
Before revealing guidance
Write down:
- Your current problem framing
- The evidence you trust most
- The riskiest assumption
- Your next learning action
Your answer
No formal score. Use the space to make your reasoning inspectable before reading the guide.
Answers are saved only in this browser.
Use the right surface
Learn, practice, produce, and rehearse are different jobs
Learn
Learning Path
Use a sequence when you need concepts, skill order, and readiness checks before independent practice.
Practice
ProducePM Exercises
Work through a realistic decision yourself, then reveal guidance and challenge your assumptions.
PM Tools & Templates
Use a generator, calculator, canvas, or template when the decision is clear enough to create the real artifact.
RehearseInterview Simulator
Use interview-style prompts, follow-ups, timing, and practice feedback when the goal is performing under interview pressure.
Continue deliberately
Practice the skill that actually limits your next decision
If a scenario exposed a weak area, use the Product Manager Skills map to diagnose the capability, then return to the matching exercise or tool. Repetition is useful when the reasoning changes—not when you simply memorize the guidance.