Define the decision
Decide what the example teaches: a missing laminate, a booking clash, uncertain treatment or a changed specification. State at the beginning that the scenario is fictional or illustrative. Give enough context to explain the decision without inventing a named customer, partner endorsement or operational achievement.
Build a usable record
If numbers are needed, label them as illustrative inputs and show the calculation and units. Keep assumptions, boundaries and unknowns visible. Avoid adding a dramatic saving or impact percentage that the lesson does not need. A fictional decision trail should still behave honestly: an unconfirmed collection cannot become a confirmed treatment result.
Check the evidence boundary
Keep educational examples out of real financial and environmental totals. Distinguish scenario records from actual project records in exports and reporting. Images, captions and headlines must preserve the fictional label. Source links can support the method, but they do not turn an invented story into evidence of a platform’s past performance.
Worked example — illustrative
In a fictional example, a team compares a retained frame with a new frame across four planned deployments. Acquisition and refresh costs are entered solely to demonstrate the method. One scenario lacks transport cost, so the example reports a partial subtotal and no complete winner. The four deployments are not claimed as completed work.
Put the method into practice
Use publication approval to check scenario labels, calculations, evidence limits and every channel derivative. Invite readers to enter their own scoped data in the programme tool. Leaf’s worked examples teach methods; actual case studies require permission, a real project record and support for each published outcome.
- Label fiction at the start.
- Show illustrative units and assumptions.
- Keep examples out of real totals.
- Review captions and derivatives.