'On Track' Is Not a State.
Teasing out where the work actually is, before the date decides for you.
What does hidden delay sound like?
Most delay does not announce itself. It hides inside a sentence that sounds like progress.
Status updates manage conversation but often fail to describe state accurately. The same words can describe completely different realities. “Almost done” might mean twenty minutes of focused work, a week sitting in someone else’s queue, or that the work changed shape and the change has not been said out loud yet. When those realities collapse into the same comfortable phrases, waiting, ownership gaps, and dependency risk become hard to see and therefore hard to price.
Borrow an idea from software. A code smell is not a bug; it is a cue to look closer. Status has the same tells. Four worth recognizing.
Incomplete Report. “Waiting on the data team.” This sentence names a blocker, but it does not specify what is needed, who owns the next move, or what would count as “unblocked” in observable terms.
Blurred Time. “Credentials are still pending.” The calendar can show a month while the actual effort is thirty minutes; the missing information is where the time is really going and whether the work is work or pure queue.
Ownerless Handoff. “The request is in.” The work has left the team’s field of view, but the update does not name who owns the next state change, what signal will indicate movement, or when it becomes reasonable to follow up.
Normalized Queue. “Access takes a week.” The week has stopped being a question and started being an assumption; it gets added to plans as if it were a law of nature, even when it is a recurring cost that might be worth challenging.
Each one says the work exists. None of them say what would move it.
The Second Question
“QA is blocked,” someone says.
“What does QA need to unblock?” asks a teammate.
“They need the test results.”
“Who owns the next move?”
“Sam does. He’ll send them this afternoon.”
Two questions turn a status update into a description of state.
The shift is subtle. Instead of accepting “blocked” as a category, the conversation forces the blockage to take a shape. “Test results” is a concrete artifact; “Sam” is a concrete owner; “this afternoon” is a concrete next signal to watch for. Now the delay can be located. If the results are already produced and just not sent, the work is internal. If the results require a run that only happens overnight, the work is constrained by a system loop. If QA is actually waiting on an environment, then “blocked on QA” was misfiled; the dependency is elsewhere.
Four weeks on the calendar, thirty minutes of actual work. The rest was waiting, and that gap is where the opportunity hides.
Once the gap is visible, decisions about delays become possible. Sometimes the right move is escalation because the value unlocked by clearing the queue is high. Sometimes the right move is resequencing (do the next useful step that does not depend on the blocked one, and come back when the signal arrives). Sometimes the right move is acceptance (the wait is real, the cost is understood, and pushing on it would only shift cost to another part of the system). Some of those waits are fixed constraints, a change window, a safety review, an external dependency that cannot be safely compressed, and accepting them on purpose is a decision, not a failure. A clean handoff needs nothing; if the next owner is clear and the next signal is observable, the work can wait without becoming mysterious.
Keep it curious, keep it useful
A question this useful is easy to misuse. The same follow-up that surfaces a hidden wait can do harm when it is turned on people, asked of everything, or answered for show. Three ways it goes wrong, each a way of forgetting what the question is for.
Interrogation. Point it at a person and it curdles into an accusation. “Who owns the next move?” is about the work. “Why isn’t this done yet?” is about them. The first locates a wait. The second teaches people to answer for cover instead of accuracy, and the real state goes back into hiding.
Bureaucracy. Ask it of everything and it stops being a question and becomes paperwork. Not every “on track” hides a wait. Decompose the ones that smell off and let the rest pass, or the team spends more time accounting for the work than doing it.
Theater. Reward the polished answer and polished answers are what you get. When a good update becomes a performance, people learn to produce one whether or not the work is in the state it describes, and the original problem comes back wearing a nicer font.
None of this is a risk when the question is asked in good faith. It is not an audit and it is not a trap. It is one teammate genuinely trying to see where the work is, asked out loud so everyone can see the same thing and move it forward together. Curious keeps it honest. Sparing keeps it useful.
An update that can be questioned is an update that can be trusted.
A peer asking the Second Question is looking for the same thing you are, what would move it.
Consider a configuration change that depends on another group. The baton-passing version sounds fine and carries no state. “The request is in.” The state-carrying version makes the boundary legible without pretending to control it. The request is assigned to a named reviewer on the other side. The current blocker is one specific detail they are waiting on. The next signal is an acknowledgment in the ticket that the detail was accepted. And the follow-up trigger is the point where it becomes rational to escalate or reroute if that signal never comes. None of that makes the queue any shorter. What changes is that the wait is now manageable. It has an owner, an expected signal, and a moment where “still waiting” turns into a decision instead of a shrug.
Once a wait has a shape, you can also count how often it appears. A single slow approval is an inconvenience. The same approval, twelve times a year, is a pattern with a price. Complaints don’t travel upward. Costs do.
“The request is in.” “We’re waiting on approval.” “Almost done.” “Access takes a week.”
Listen for the signals. What other ones do you hear in conversations?