Delivery delay issue tree
This issue tree breaks late deliveries into supply and fulfilment. Supply covers whether materials arrive in time for production. Fulfilment covers whether completed orders are picked, packed, dispatched, and carried to the customer on time. The split makes it easier to assign owners and find the constraint instead of treating a late delivery as one undifferentiated problem. Use timestamps from purchase order, production, warehouse, dispatch, and proof of delivery to test the branches. Add order-entry quality if incorrect promises or address problems are frequent. The leaves should be measurable operational hypotheses, not broad labels. It gives readers a concise reference they can reuse when discussing the result with colleagues.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
Operations diagnosis
Key decisions
- Supply: Test material availability and supplier timing.
- Fulfilment: Test warehouse and dispatch performance.
- External delivery: Separate carrier transit from internal delay.
When to reuse this
Use to structure an on-time-delivery root-cause analysis.
Frequently asked questions
Why separate supply from fulfilment?
Where do carriers belong?
What data tests the tree?
More operations examples
Try the diagram makers.
Tweak it with chat, export PNG/SVG, or fork it for your own use case.