Issue Tree: Why Do We Have Too Much Inventory?

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

Excess inventory ties up cash, eats storage costs and ends in markdowns. Before launching a clearance sale, find out how it piled up. This tree separates planning errors, buying decisions, demand changes and product problems. Look at which SKUs carry the most excess days of stock and trace each one back to a branch. The pattern tells you whether to fix forecasting, purchasing rules or the assortment itself.

Why do we have too much inventory?

  1. Did we forecast too high?

    • Did we plan on last year's peak instead of current demand?
    • Are forecasts updated when sales change?
  2. Did we buy too much at once?

    • Are minimum order quantities or volume discounts driving big orders?
    • Are long lead times forcing us to order far ahead?
  3. Did demand drop?

    • Did a competitor, price change or season shift cut sales?
    • Did a marketing push underperform?
  4. Is the assortment wrong?

    • Do we carry too many slow-moving SKUs?
    • Are discontinued items still being reordered?

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