A quiet diagnostic for leaders who carry consequences
I was reporting on every critical initiative inside the organization. Weekly status. Color-coded. One of them had been red for weeks.
I sat with the executive team and asked the question directly: what are we going to do when this initiative does not move?
Nobody had an answer.
Not a bad answer. Not a disagreement. No answer at all. What the group did agree on was that they wanted to “keep a pulse on it.” So I kept the pulse. I reported on it the following week, and the week after that.
There was no sign of it being a priority for anyone else in the organization.
Week over week, I told the leadership team the same thing: “Either this is not a priority, or we need to set a new expectation and be clear about who owns the responsibility of driving it forward.”
As a collective, they agreed to have me monitor it.
It was a complete waste of time and energy. Not just mine. The meeting’s. The ritual of reviewing something nobody would decide on had become the substitute for the decision itself. The group was not clear or organized around what their actual priorities were. And the structure of the meeting let that stay invisible.
That is Decision Drift. Not a failed decision. A decision that was never made explicit. Ownership that was never named. Responsibility that lived in a status color instead of a person.
This test exists because that scene is not unusual. It is the default in most organizations carrying real consequences. The question is whether yours has the same pattern running right now, somewhere you have not looked yet.
Most organizational failures are not caused by bad decisions. They are caused by decisions that were never made explicit.
Risk rarely announces itself. It migrates quietly through launches, integrations, escalations, and commitments. Carried by people until it surfaces as cost, damage, or blame.
This diagnostic is not motivational. It is not a framework to install. It is a mirror.
Answer it privately. Do not debate the questions. Notice where certainty ends.
This takes about five to ten minutes.
Do not answer aspirationally. Answer based on what is true right now, not what you are building toward.
“Unsure” is not a sign of failure. It is the most honest signal in the test. If everything reads “yes,” either your system is genuinely strong or you have not looked closely enough.
Use it as a signal of the system you are in.
Answer as honestly as you can. For each statement, mark Yes, No, or Unsure.
If “Yes” clearly outweighs “No” and “Unsure,” your system is likely holding.
If not, consider that these may already be occurring in your organization:
If the organization is replacing roles with AI, that situation will likely amplify. AI inherits the structure it is given. If ownership is ambiguous now, automation makes the ambiguity move faster.
Clarity does not force action. It returns agency.
Once something is explicit, someone chooses to own it. Or the system accepts the consequence. Both are legitimate.
What is not legitimate is pretending the choice does not exist.
That executive team I sat with? They were not bad leaders. They cared about the initiative. But the structure of the meeting let “keeping a pulse” stand in for ownership. Nobody had to say “this is not a priority” out loud. Nobody had to name who would drive it. The red status existed so the conversation could feel responsible without anyone being responsible.
The test above surfaces that pattern. Not to assign blame. To return the choice to the people who should be making it.
The diagnostic is available as a printable PDF. Use it privately. Share it with your leadership team if it surfaces something worth naming.
This is not a lead capture. No email required. If it is useful, you will know where to find the rest.
Download the Explicitness Test (PDF)