Work Stalls Silently: The Difference Between Activity and Progress

The Illusion of Movement

Work does not stall loudly. It stalls silently.

Most stalled tickets look fine at a glance. They are open. They have been touched recently. Notes exist. Someone feels responsible for them. And yet, nothing is actually happening.

Days pass, then weeks. Eventually, the ticket becomes background noise – present, but no longer truly active. This is how backlogs rot without anyone noticing.

A ticket without a clearly stated next step is not in progress. It is paused without permission.

To prevent that pause, we apply Rule #6: All Unresolved Ticket Entries End with a WINS.

What is a WINS?

WINS stands for “What Is Next Step?”

It is not a status update. It is not a narrative about what you just did. It is a declaration of intent, the actionable next step required for resolution.

Service delivery is a chain of small decisions:

• Who does the work next?
• What must happen before progress can continue?
• Is the blocker technical, administrative, or external?

If that decision is not made explicit, the system cannot act on it. Coordinators guess. Technicians hesitate. Everyone assumes someone else knows what is going on.

They usually don’t.

WINS forces clarity at the moment it matters most: now. It tells the system exactly what condition must be satisfied for the ticket to move forward again.

WINS Restores Direction

Without a WINS, tickets age for reasons no one can explain. This is particularly damaging in environments with ticket handoffs.

A ticket moves from technician to technician, from team to team, from day to day. Each person adds a note. And each person assumes the next person will know what to do.

Over time, the ticket accumulates information but loses direction.

WINS restores that direction. It forces the ticket to state its destination, not just its history.

Activity vs. Progress

Organizations that resist this rule often do so because they confuse activity with progress.

As long as notes are being added, they assume movement is happening. In reality, the work is circling.

• "Client called back." (Activity)
• "Researched the error log." (Activity)
• "Updated the firewall." (Activity)

None of these notes tell us where the ticket is going. A ticket with a WINS breaks the loop:

• "Client called back. WINS: Schedule remote session for Tuesday." (Progress)
• "Researched error log. WINS: Escalate to Level 3 for vendor support." (Progress)

It is important to understand that the next step does not need to be complex. It does not need to solve the problem. It simply needs to move the problem closer to resolution.

“Awaiting client response” is a valid next step – provided it is explicit. “Waiting” is not.

Exposing the Blockers

WINS also exposes the true nature of many delays.

• Some tickets are blocked by clients.
• Some are blocked by third parties.
• Some are blocked by internal decisions no one wants to make.

When a WINS is required, those blockages surface immediately. The system can see where it is waiting—and why.

That visibility changes behavior. Instead of asking, “Why is this ticket still open?” leadership starts asking, “Why is the next step unresolved?”

That is a solvable question.

Reducing the Mental Load

This rule is deeply connected to the technician's experience.

A clear next step reduces cognitive load. It removes ambiguity. It allows a technician to close a mental loop instead of carrying unfinished work in their head.

Over time, that reduction in mental clutter significantly reduces fatigue and errors.

When a WINS is consistently enforced, something subtle but powerful happens. Tickets start to move faster without anyone working harder. Coordinators can triage effectively. Escalations become cleaner. Work moves toward resolution, regardless of which technician picks up the ticket next.

The backlog becomes a map instead of a mystery. Plus, the client can see you’re on it!

Conclusion

Organizations that do not enforce this rule experience a constant, low-grade anxiety. Work feels heavy, but no one can quite explain why. Everyone is busy, but nothing feels finished. That feeling is not a people problem. It is the absence of direction at scale.

Every ticket must answer the same question, at all times: What Is Next Step?

If the system cannot answer that, the ticket is already stalled – whether anyone admits it or not.

Get the Full Framework

This rule is just one part of a larger system. If you are tired of "controlled chaos" and want to see the full system I use to fix service operations, grab my FREE Info Guide. It’s a fast, no-fluff checklist of the non-negotiable rules for tickets, time, and handoffs.

Download the 10 Golden Rules of PSA

_{Image by mohdizzuanbinroslan | Envato}