The same exception is a surprise every month
People are praised for heroic recovery rather than for removing the condition that required heroics. The process has no owner, so it cannot learn.
Self-check
Operational signals that operations management is overdue
Use this page before you write. If several of these signals are normal in your organisation, informal coordination is no longer carrying the work.
Nobody can draw the path without arguing
Ask three functions how work travels from demand to result. If you receive three incompatible stories, you do not have a strategy. You have folklore.
Approvals age in silence
Work waits on a decision that has no named owner, or that has three owners who each believe the other two will move. Calendar time passes; case time does not.
Handovers are implied, not designed
A team finishes its part and assumes context has travelled. The next team rebuilds the story from chat history. Rework looks like diligence.
Dashboards are busy; waits are invisible
Volume, utilisation, and activity are reported. Queue age, rework loops, and dropped interfaces are not. The organisation is measuring motion.
Growth added people, not a path
Headcount rose after demand rose. Coordination stayed personal. Meetings multiplied to compensate for a missing architecture.
A tool was bought to hide the stall
A platform was expected to impose order. The same informal path simply moved into new tickets. Software cannot replace unnamed ownership.
If these read as familiar, start with a diagnostic or the Diagnostic Sprint. To see how work would run with us, open the engagement path.