Practice · 40 scenarios
PM Drills.
A situation, a question, and a way to reason through it. Take 30 seconds to 2 minutes. Think before you scroll.
- 01
Product judgment
The export request
A customer wants a CSV button. The real need is still unclear.
- 02
Product judgment
The buyer’s dashboard
A buyer asks for visibility that daily users may resist.
- 03
Product judgment
The silent interview
Five interviewees approve an idea but show no recent need.
- 04
Product judgment
The oversized MVP
A small launch still avoids the most important risk.
- 05
Product judgment
The one-customer bet
A large renewal competes with work that benefits many accounts.
- 06
Product judgment
The busier home screen
More discovery options make the first useful action harder to find.
- 07
Product judgment
The tiny opportunity
A loud complaint may describe a rare, low-cost problem.
- 08
Technical decisions
The slow upstream API
A dependency cannot respond within the interactive time budget.
- 09
Technical decisions
The hidden admin button
The interface hides an action but the backend still accepts it.
- 10
Technical decisions
The duplicate order
A timeout leaves the final outcome uncertain.
- 11
Technical decisions
The stale price
A cached page and checkout disagree.
- 12
Technical decisions
The second owner
A new relationship affects more than one screen.
- 13
Technical decisions
The green deployment
Automated checks pass while a real workflow fails.
- 14
Technical decisions
The scaling proposal
More services are proposed before the bottleneck is measured.
- 15
Data interpretation
More minutes, fewer returns
A hypothetical listening experiment produces conflicting signals.
- 16
Data interpretation
The post-release drop
Timing suggests a cause but does not prove it.
- 17
Data interpretation
The conversion paradox
The overall rate drops while each platform improves.
- 18
Data interpretation
The early experiment winner
A one-day lead may not justify a launch.
- 19
Data interpretation
Activation by force
A metric improves because the product performs the action for users.
- 20
Data interpretation
The doubled purchase event
Analytics and financial records tell different stories.
- 21
Data interpretation
The customer survey blind spot
Happy active users do not represent everyone who tried the product.
- 22
AI decisions
Ninety-two percent correct
An aggregate accuracy score does not settle acceptability.
- 23
AI decisions
The AI spreadsheet converter
The transformation rules are already fully specified.
- 24
AI decisions
The trustworthy-looking citation
A source link exists but does not justify the answer.
- 25
AI decisions
The smaller model
Lower cost per call may increase cost per useful result.
- 26
AI decisions
The agent that keeps trying
Repeated tool calls increase cost without making progress.
- 27
AI decisions
The approval conveyor belt
Human review exists but reviewers cannot assess the action.
- 28
AI decisions
Instructions inside the document
Retrieved text tries to redirect the assistant's actions.
- 29
Execution
Five days to launch
A manual path can meet the date if its operating limits are real.
- 30
Execution
The partial import
A bulk operation succeeds for most records and fails for some.
- 31
Execution
The vendor dependency
A nearly finished interface is blocked by missing external access.
- 32
Execution
The flag that stayed forever
A temporary rollout control becomes permanent complexity.
- 33
Execution
The support surprise
The release is technically ready but operationally unprepared.
- 34
Execution
The incident blame
An individual mistake is offered as the entire explanation.
- 35
Communication
The buried recommendation
A detailed update leaves the decision unclear.
- 36
Communication
The estimate disagreement
A technical estimate conflicts with an earlier stakeholder expectation.
- 37
Communication
The design opinion
Feedback names a preferred arrangement without explaining the concern.
- 38
Communication
The confident date
A roadmap exploration is being repeated as a launch commitment.
- 39
Communication
The technical headline
A true metric does not yet explain customer impact.
- 40
Communication
The sophisticated option
A general platform sounds attractive before demand is established.