Stuck Is Not Failed

A few weeks ago, something behind this website stopped moving.

Not broken. Just... stopped.

Publishing a post here depends on one machine doing its job, and that machine went offline. It happened three times in about a week.

Here is the part that stayed with me. Nothing ever told me.

No alert. No red flag. No email. The status just read "pending," because nothing had failed. It was waiting. And the only way anyone found out was me opening the page and looking.

Failure raises its hand. Stuck does not.

That gap is not a software problem. I see the same gap on almost every team I work with.

When something fails, it makes noise. A client complains. A number misses. Someone finally asks why it was not escalated. Failure has a shape people recognize, so it travels upward on its own.

Stuck has no shape. It looks like a task sitting in the same column it was in last month. A proposal that is "with legal." A hire that is "in process." A decision that is "waiting on finance."

Nothing is wrong, exactly. Nothing is moving either.

So it stays quiet. And quiet things do not get escalated.

Your reporting only catches one of the two

Look at how your team reports progress. Done, in progress, blocked, at risk.

"In progress" covers a task that moved yesterday and a task that has not moved in five weeks. Same words. Same green square on the slide.

The thing that costs you a quarter is rarely a failure. It is usually something that sat still while everyone assumed it was moving.

By the time it turns into a real miss, you are not solving the problem. You are explaining it.

Nobody wants to report a week of nothing

There is a human reason underneath this, and it is worth sitting with.

Put yourself in your team member's chair. They are waiting on a vendor. Or another department. Or on you. There is no progress to report, and saying that out loud feels like showing up empty handed.

So they say "still working on it." Which is true. And they tell themselves they will have real news by the next check-in.

That is not dishonesty. It is a very ordinary instinct... and it is exactly why stuck hides.

If your people believe they need a result to be worth mentioning, you will hear about problems late. Every time.

Three things that surface it

Ask a different question. "How's it going?" gets you a feeling. "What moved on this since we last talked?" gets you a fact. And if the honest answer is nothing, the question leaves room to say so.

Put an age on things. Not a deadline. An age. How many days has this sat in the state it is in right now? Old and on track is fine. Old and nobody noticed is the problem. Age makes stuck visible without anyone having to confess.

Make the first report cheap. If raising a block costs someone a hard conversation, they will wait one more day. Every time. On the teams that catch this early, saying "I'm stuck" is boring. It happens often, help shows up, and nobody remembers it a week later.

That third one is culture, and it takes the longest to build. It is also the one that makes the other two work.

The one you have to find yourself

Here is the uncomfortable part.

My site sat still for days because the only way to notice was to go and look. I had not built any way to be told.

Most leaders are in the same spot and do not know it. Your read on what is moving comes from people choosing to tell you, and people mostly tell you about finished things and broken things.

Everything in between, you have to go looking for.

So pick the three things that matter most this quarter. For each one, ask when it last moved. Not whether it is on track. When it last moved.

I would guess one of those answers surprises you.

If you are not sure how to ask that question without it landing like an audit, that is usually where coaching starts. Here is how I work with leaders.