“Any update?” looks harmless until it becomes part of the operating model. Sales asks operations. Operations asks finance. Managers ask teams. Customers ask service. Every request consumes attention because the system cannot answer a basic question: what state is this work in now?
Status chasing is a visibility gap
The problem is not that people should communicate less. It is that routine operational facts should not require private conversations to discover. If ownership, state, blockers and expected next actions are not represented in the workflow, people recreate visibility through messages and meetings.
Why the pattern becomes expensive
Status chasing creates interruption, duplicate conversations and delayed escalation. It also makes management reporting unreliable because the same work can be described differently depending on who was asked and when.
Design the workflow to answer the obvious questions
- Who owns the item now?
- What state is it in?
- What is it waiting for?
- When did the state last change?
- What condition should escalate it?
What better looks like
People still communicate when judgment or context matters, but they do not spend their day reconstructing basic operational truth. The system makes routine status visible and directs attention toward exceptions that actually need human action.