The term “In Progress” might seem helpful at first glance, but it’s one of the most misleading statuses in any system. It hides what’s really happening, weakens meaningful reporting, and allows tasks to linger in limbo far longer than anyone realises.
Why “In Progress” Is Meaningless When it Comes to a Task
“In Progress” doesn’t reveal anything about the actual state of a task. It could be waiting on someone, actively being worked on, stuck on a question, or even abandoned—yet it all appears the same. This lack of clarity makes it difficult to assess real workloads, spot bottlenecks, or determine when something needs attention.
Because it’s so ambiguous, “In Progress” often becomes a refuge for discomfort. People move tasks there to signal “I haven’t forgotten about this” or “please don’t chase me,” even if nothing has been done for days. The board looks busy, but the system gives a false impression of how much work is actually moving and what task is actually being done.
The Psychology Behind Vague Statuses
Statuses act as social signals as much as process indicators on a task. “In Progress” feels safe because it doesn’t commit to anything: no deadline, no stage, no specific requirement to push it forward. When teams are overwhelmed or uncertain, they naturally retreat to that sense of safety.
But that safety comes with consequences. Leaders begin to lose trust in the board and turn to side updates, meetings, or messages instead. Individual contributors feel scrutinised because no one believes the statuses. The more people bypass the system, the less honest everyone becomes about their capacity and the obstacles they’re facing.