“We help teams prioritise” gives a prospect little to inspect. A short demonstration can show what you notice, what you ask and why you choose a particular next action. You can teach that reasoning with an example written from scratch, even when your client work cannot be shown.
Keep the task narrow. This lesson answers: “Which decision is preventing the next launch handoff?” It does not attempt to teach every way to rank a backlog. The fictional team has already chosen page publication as its next required handoff.
Give the viewer enough input to follow the decision
| Task | Current state | Dependency |
|---|---|---|
| Approve the final price | Waiting for the price owner's decision | The order page needs an approved price. |
| Publish the order page | Blocked | Cannot proceed until the price is approved. |
| Correct an FAQ typo | Ready | Independent of the launch handoff in this exercise. |
The ready typo fix is easy to start, but finishing it will not answer the open pricing question. For the stated goal, the useful discussion is with the price owner. The method's rule here is to identify the unresolved decision blocking the next required handoff. Another goal or a safety-critical defect would require a different review.
Turn that reasoning into something you can say
- Set the question
“This is a made-up launch backlog. Which decision is stopping the order page from going live?”
Show the three cards before choosing one. Keep the fictional label on the exercise.
- Trace the dependency
“The FAQ typo is ready to fix. The page is waiting for an approved price. Finishing the typo won't release the page.”
Point from the approval card to the blocked publication card.
- Name the next action
“Ask the price owner for a decision before the next launch review. If approval is still missing, keep publication on hold.”
The ending gives an action and an unresolved condition. It does not invent a completed launch.
Before recording, check whether this rule matches the method you actually use. If your service prioritises risks, customer impact or another factor, write a different example around that rule. A familiar-looking board is not enough; the viewer needs the information that makes your choice intelligible.
Let the viewer test the rule
Change one condition: the final price is approved, but the page editor is waiting for the product photograph. Ask what blocks the handoff now. The useful answer is the missing photograph, not “always discuss price first.” This variation checks whether the viewer followed the dependency rather than memorising the card you selected.
Use your own blank board, cards or illustrations. Copying a client's board and replacing its name can preserve recognisable task wording, relationships and dates. If you want to use a real engagement, follow the separate client-work publication review and obtain the required approval.
Write a brief the editor can execute
Record the question, input, decision rule and information the lesson deliberately leaves unresolved. This also gives you a review standard: another person should be able to explain why the chosen action followed from the three cards.
Prepare and download a method-explainer brief
This is an original teaching method example, not an approved client case or reviewed sample video. The educational Shorts guide covers the next commercial step: giving an interested viewer a relevant way to continue.

