Not Defiance. Execution.
The tracker isn’t the rebellion. It’s the diagnosis.
In the two previous posts (here and here), we described a solution that was designed without operator input and built on top of data that doesn’t reconcile. Even if both of those problems were solved, even if the design process had included the right people and the underlying numbers were clean, there is still a reasonable chance that operators would build their own tools anyway. That isn’t a failure of discipline. It’s the subject of this post.
The Wrong Diagnosis
When leaders discover that operators have built their own trackers outside the official system, the instinct is to read it as a discipline problem. Somewhere, someone didn’t get the message, and a reminder goes out. Sometimes a policy follows, restricting access to spreadsheets or banning unsanctioned tools outright.
This diagnosis misses what is actually happening. Operators are not rejecting structure; they are solving a problem that the official solution does not solve for them. The tracker exists because it answers a question the dashboard doesn’t, using numbers the operator can verify, in a format built around how the work actually gets done. That is not insubordination; it’s execution. The mission still has to get done, and the operator is doing what is necessary to do it.
We told a version of this story in The Spring and the Aqueduct. The villagers were given a grand new system and quietly went back to the wooden channel that had always worked. Nobody organized a protest. They simply returned to what answered their needs. That is precisely the behavior we are describing here, stripped of the fable.
Solving for a Different Customer
This is the same problem we raised in No Facts Inside the Building: the customer of the official solution and the person who has to live with it are often two different people. A dashboard built for a higher echelon is calibrated to the questions that echelon is asking. Those are rarely the same questions an operator needs answered before the next decision point.
When a tool doesn’t answer your questions, you build one that does. This is not a new behavior introduced by bad culture or poor compliance. It is what people in operational roles have always done when the systems above them don’t meet the need. The spreadsheet, the side tracker, the personal notebook: these are old tools wearing a new name. What has changed is the scale and visibility of the gap, not the underlying behavior.
Why Banning the Workaround Doesn’t Work
If the goal is a single, trusted source of truth, restricting access to alternatives does not get you there. It only removes the operator’s ability to compensate for a system that still does not meet their needs. The underlying problems, the discovery gap and the trust gap, remain exactly where they were. All that changes is that the symptom is no longer visible.
A more durable approach starts from the two problems already named in this series. Build the solution with the people who have to use it, so it answers their actual questions and not just the commissioning level’s, and resolve the data integrity problems at the source, so the numbers it relies on are ones operators can actually believe. Do both of those things, and the workaround tracker loses its reason to exist. Ban it without doing either, and you have only made the problem harder to see.
Where This Leaves Us
Across this series, we have argued that a discovery problem and a trust problem, left unaddressed, produce a predictable outcome: operators quietly build what they need, using what they trust, to answer the questions that matter to them. That outcome is not defiance; it is the rational response of people trying to do their jobs well inside a system that was not built with them in mind.
If your organization is wrestling with shadow trackers, parallel systems, or a dashboard initiative that isn’t getting the adoption leadership expected, the pattern is usually traceable back to one of these two problems. Storm King Analytics is glad to help you find which one it is and work through it. Reach out at info@stormkinganalytics.com.