Issue Tree: Why Are Our Deliveries Late?

A ready-made issue tree. Open it in Razn and fill it with your numbers.

Open this tree in Razn

Free during beta · no card needed

Late deliveries cost money twice: once in the delay and again in refunds, churn and rush shipping. Adding trucks or staff is expensive and often misses the real cause. This tree follows an order from promise to doorstep, so each delay falls into exactly one branch. Measure where the late minutes accumulate and you will know whether the fix sits in planning, the warehouse, transport or the last mile.

Why are our deliveries arriving late?

  1. Was the promise realistic?

    • Are quoted delivery dates shorter than our actual lead time?
    • Did order volume spike beyond plan?
  2. Do orders leave the warehouse late?

    • Is picking and packing slower than before?
    • Are items out of stock when the order arrives?
  3. Is transport slower?

    • Are carriers missing pickups or transit times?
    • Are routes or schedules inefficient?
  4. Does the last mile fail?

    • How many deliveries fail on first attempt?
    • Are addresses or delivery windows wrong?

How to use this tree

  1. Confirm the root question and who makes the call. If they would phrase it differently, rewrite it first.
  2. Put a number on each branch with data you already have. A rough figure beats a long debate.
  3. Cut the branches that explain little, so the effort goes where the gap is.
  4. Write the answer first: one sentence with the main driver and what you will do about it.

Going further

Your problem is a bit different? Describe it and Razn builds the tree for you.

Structured with Razn → try free