Nothing is skipped, and no level can be bought.

A maturity model is not a scorecard and it is not a sales instrument. It is a way of answering one question that matters more than any measure of forecast accuracy: how much of the structure is actually in place, and therefore what is the next thing that would hold.

That is worth having because planning capability is cumulative in a way most business capabilities are not. You cannot run a credible scenario process on a demand number nobody owns. You cannot automate a decision that has never been made the same way twice. Each level is built out of the one below it, so the useful question is never how good could this be, it is what is the next level that would actually stand up.

We call this the WhiteBox SCM Planning Maturity Ladder. The six levels below are the same six that appear on the framework page, set out here with what distinguishes each one.

Read across rather than up. The filled track is cumulative scope, so level five is visibly five sixths of the way to autonomous planning rather than simply taller than level four, and what arrives at each level is named on the right.

There is no marker on it. Putting one there would mean asserting where you sit, or worse where some population of manufacturers sits, and neither is a thing this site can honestly claim to know. Placing yourself is the next section, and it is done from symptoms rather than from a self-assessment, because self-assessments of planning maturity are famously generous.

Not by which capabilities you have bought or which processes are documented. By what the working week looks like on a bad week. Read down until one of these stops being a description of somewhere else.

The honest way to use this is to read from the bottom and stop at the first description that is uncomfortably familiar, rather than reading from the top and stopping at the first one you could argue for.

Every level is made out of the ones below it, which sounds like a platitude until you watch what happens when it is ignored. Scenario planning laid on top of a process nobody follows produces scenarios nobody acts on. An integrated cycle imposed on functions that do not own their own numbers produces a longer meeting with the same outcome. Automation pointed at a decision with no owner produces the wrong answer faster and with more confidence attached.

This is also why a level cannot be purchased. Software can deliver the capability that belongs at a level, but the level itself is a property of the organisation: who owns what, where trade-offs get settled, and whether a decision made in March is still being made the same way in September. Those are not features.

Almost always three things, and rarely a tool. Someone is given ownership of a decision that previously had none. A forum is given the authority to settle something it previously escalated. And a measure is introduced as a learning measure, understood and argued with before anyone is judged against it.

That is unglamorous work and it is slower than buying something, which is the main reason it gets skipped. It is also the only work that moves the level, because the level is a description of exactly those three things.

It does not tell you that you should be at level six. The right level for a business depends on how volatile its demand is, how long its lead times are, how much a wrong call costs and what it can sustain once the project ends. A business running level four properly is in a considerably better position than one running a fragile level five, and the second is more common than the marketing around planning technology would suggest.

It also does not tell you which capability to build next, only which levels are available to you. That question needs the seven blocks rather than the six levels, because it is the framework that says what a level is made of.