Practice resources
Three stakeholder scenarios for practising PM judgment
Rehearse sales pressure, engineering uncertainty and an executive deadline with role cards, constraints, observer criteria and sample responses.
Run a ten-minute roleplay
Use three people if possible: PM, stakeholder and observer. Read the shared facts, let the stakeholder add pressure, and stop after four minutes. The observer should quote what was said before suggesting improvements. All scenarios here are synthetic.
The goal is to produce a clear next decision while preserving the working relationship. Agreement is not always the right outcome. A defensible pause or escalation can be a better result than an invented promise.
Scenario 1 — sales needs a promise
Shared facts: one engineer has six days. A prospect requests a reporting export before a demo. The team is also investigating an invitation problem affecting new workspaces. No purchase commitment has been made.
Sales role card: you need a credible demo story and worry that “we will investigate” sounds evasive. Ask the PM for a date.
PM task: acknowledge the commercial need, clarify the required workflow and explain the capacity trade-off. Offer a bounded next step without assigning work you cannot approve.
Sample opening: “What does the buyer need to demonstrate with the export? If a sample output answers that question, we may be able to support the demo while we confirm the full workflow. A production export would displace the invitation work, so I need the decision owner to review that trade-off before I promise a date.”
- Observer: did the PM ask about the underlying need?
- Observer: was the opportunity cost stated without blaming engineering?
- Observer: is there a clear owner and time for the next answer?
Scenario 2 — engineering cannot estimate yet
Shared facts: leadership wants a launch estimate. The team has not checked a third-party integration’s rate limits or failure behaviour. A two-day spike could reduce uncertainty.
Engineer role card: you are being pushed for a single number and fear it will become a commitment. Explain what you do not know.
PM task: separate the date needed for planning from the evidence needed for a reliable commitment. Agree on what the spike will answer and what will happen afterwards.
Sample opening: “Which unknown could change the estimate most? Let’s define what the spike will establish, including failure handling. I will communicate a planning range with the assumptions today and a review point after the spike, rather than label it a committed launch date.”
- Observer: did the PM make uncertainty visible?
- Observer: does the spike have a question, owner and time limit?
- Observer: can leadership understand what is provisional?
Scenario 3 — an executive wants a bigger launch
Shared facts: a small rollout has encouraging feedback but only eight active teams. An executive wants a company-wide announcement next week. Support coverage is limited.
Executive role card: you see momentum and want the team to be ambitious. Ask why they are waiting.
PM task: explain what the evidence supports, identify operational risk and offer a launch scope that can be supported.
Sample opening: “The eight teams give us useful evidence about these workflows, but not about every segment. I recommend expanding to the next eligible cohort with support coverage and a rollback owner. We can announce that availability accurately while collecting the evidence for a broader launch.”
- Observer: were small-sample limits explained without dismissing the feedback?
- Observer: is there a feasible alternative?
- Observer: are support and rollback responsibilities explicit?
Debrief and repeat
The stakeholder’s real concern was: The PM acknowledged it by saying: The constraint or trade-off became clear when: An unsupported promise or assumption was: The next decision, owner and review time are: One sentence to change on the second attempt:
A useful second attempt
Repeat the same scenario with one change: the prospect signs, the integration test fails, or support capacity doubles. The PM should revisit the decision when the evidence changes. Defending the original answer at all costs is not the aim.
These public role cards work with a colleague. Product Mastery also offers exercise practice and, on eligible plans, AI voice coaching. The seven-day Free practice plan uses written and interactive exercises, not paid voice sessions.