A useful first answer
Make the reason and the consequence visible
Do not present a priority as a mysterious ranking. Name the user or product problem, the evidence or constraint that changed, and the consequence for other work. Acknowledge the value of the item that moves later. Then state the next decision point. This makes disagreement possible without turning the conversation into a contest between departments.
State the decision
Say which item moves and which item moves later. Avoid making the listener infer the change from a roadmap slide.
We are moving account recovery ahead of saved report filters.
Give the decision basis
Connect the choice to a user need, product goal, performance evidence, risk, or capacity constraint.
Recovery failures prevent affected users from completing any account task.
Name the trade-off
Explain what benefit is delayed and why that cost is acceptable for now.
Saved filters would reduce repeated setup, but users can still complete the reporting task without them.
Set the next review point
Say what will be checked, by whom, or when the order can change again.
We will review recovery volume and engineering capacity at Friday’s planning session.
Worked conversation one
Explain why a requested feature moved later
A sales stakeholder challenges the new order+
A customer export requested by sales has moved behind an account-recovery problem.
Why did the export move again? We told two customers it was our next priority.
The export is still valuable, and I understand the customer expectation. We moved account recovery ahead because affected users cannot reach any account feature after a failed reset.
Couldn’t the team do both?
With current capacity, doing both would split the two engineers who know the recovery flow and extend both deliveries. The trade-off is delaying the export discovery by one planning cycle so we can restore the blocked task first.
What can I tell the customers now?
Tell them the export remains planned but does not have a confirmed delivery date. I will bring an updated scope and capacity view to Friday’s review.
The answer recognises delayed value, explains the capacity trade-off, and gives a review point without inventing a delivery date.
Worked conversation two
Change the order without pretending the old decision was foolish
New evidence changes a launch priority+
A usability session reveals that customers cannot understand a required setup step shortly before a planned launch.
We need to move setup guidance ahead of the optional notification controls. In the latest sessions, several participants could not complete the required setup without help.
The notification work is already designed. Are we throwing that work away?
No. The design remains useful, but the new evidence changes the launch risk. Notification controls add choice after setup; the guidance addresses a failure in the required path.
What is the smallest guidance change we can test before launch?
Let’s test the revised setup explanation first. If participants complete the required step without help, we can decide whether the notification controls return to the current release.
That gives us a clear condition. I’ll prepare the guidance variation and preserve the notification design for the next review.
The update explains how new evidence changes the decision and states when the delayed work will be reconsidered.
This is the highest-value feature.
This item addresses a failure in the required setup path, while the other item improves an optional step.
Engineering does not have capacity.
The same two engineers are required for both items, so parallel work would extend both timelines.
Adapt the update
Choose language for urgency, uncertainty, and disagreement
- For an urgent incident: lead with the user harm or operational risk, state what pauses, and name the next status time.
- For uncertain evidence: call the change temporary, say what you are testing, and give the condition for keeping or reversing it.
- For an executive update: state the decision, business or user effect, major trade-off, and requested support in four sentences.
- Choose two fictional backlog items and write the user need, evidence, capacity need, and risk for each.
- Give a 45-second update using decision, basis, trade-off, and review point.
- Answer “Why can’t we do both?” without blaming another team or promising an unknown date.
- Repeat the update for an executive in 25 seconds, keeping one meaningful trade-off.
Choose how to continue
Use independent voice practice for repetition, or choose teacher guidance for a broader learning plan.
Rehearse the priority conversation aloud
Keep your spoken English active between meetings with Flalingo: AI Speaking Coach. Try voice conversations and get feedback after you speak.
Explore the AI speaking coachBuild broader stakeholder communication with a teacher
For planned live English lessons and teacher support across longer-term professional communication goals, review the Flalingo method.
Explore the Flalingo methodSources
- Deciding on priorities
GOV.UK Service Manual · Reviewed 10 Sept 2026
Used for regular prioritisation based on performance analysis, user research, stakeholder input, clear methods, and capacity. It does not require one framework for every product team.
- The 2020 Scrum Guide
Scrum Guides · Reviewed 10 Sept 2026
Used for Product Goal transparency, ordered backlog items, and explicit trade-offs. The lesson does not claim that the reader’s organisation uses Scrum or shares its accountabilities.