Software/Discipline Gap Audit
A leadership-team exercise that scores what your planning software does against what your planning discipline does, phase by phase across Woodring's Loop.
What Software/Discipline Gap Audit is.
Software/Discipline Gap Audit. The Software/Discipline Gap Audit measures the distance between the predictive-planning software an organization has bought and the predictive-planning discipline it actually runs. It scores each phase of Woodring's Loop — Scan, Story, Stake, Steer — twice, once for software and once for discipline, and reads the gap as a map of where the real leadership work is.
What it is
Software can be procured. Discipline has to be installed by a leadership team, and the two are constantly confused. The Software/Discipline Gap Audit exists to make that confusion visible. It forces a company to state, out loud and in the room, what its planning platform does for each phase of the Loop versus what its people and operating rhythm actually do.
How to run it
For each phase of Woodring's Loop — Scan, Story, Stake, Steer — score two numbers from 0 to 10. The first is what your current software does for that phase. The second is what your discipline does for that phase. Run it with the executive team in the room, not as a procurement exercise, and score honestly. The point is not to grade the vendor — it is to see the gap clearly enough to act on it.
What the gap reveals
Wherever the gap is widest, the leadership work is largest. The most common pattern in companies that have bought a planning platform is a high software score with a low discipline score — and that reading says the next dollar should go to the discipline, not the next license. The reverse — strong discipline, weak software — is rarer and easier to fix, because a platform can simply be bought.
Common questions.
- Isn't buying a predictive-planning platform the same as installing the discipline?
- No, and confusing the two is the exact error the audit is built to catch. Software supports a discipline — it does not install one. A CFO who buys the platform and declares planning modernized has usually bought an expensive way to keep doing what they were already doing.
- Where does software actually help across the Loop?
- Software earns its keep at the edges — Scan (ingesting signals at volume) and Steer (watching actuals unfold against the model). It is largely beside the point in the middle. Story and Stake are where leadership shows up or doesn't, and no platform changes that.
- How often should you run the audit?
- Run it as a standing quarterly exercise with the leadership team. Because the discipline is the thing that moves — not the software — the numbers that matter are the discipline scores, and those only climb when the leadership work gets done between audits.
Source: Chapter 4 — Why Software Won't Save You · Predictive Planning (Colloquial Media, 2026)
More of the vocabulary.
- Woodring's Loop
The four-phase continuous cycle at the core of predictive planning — Scan, Story, Stake, Steer — that turns weak signals into strategic decisions.
- Cycle Audit
A diagnostic that measures what your annual planning cycle actually costs — in senior attention, budget, and frozen strategic conversation — before you decide to retire it.
- AI/Human Split
The allocation rule inside Woodring's Loop: give the volume work to the machine and keep the judgment work for the people whose names are on the decision.
- Stake Sizing Matrix
A decision tool in Woodring's Loop that sizes any strategic commitment against two axes — the team's conviction in the scenario and the cost of being wrong.