MELLORCATalk to Mellorca
Moments

Time & Attention

What Changes When Status Updates Stop Being a Chore

"Any update?" arrives several times a day, and each answer means stopping work to describe work. What constant status requests take from people's focus, and what changes when progress records itself as the work is done.

Mellorca Moments2026-10-04

The message says "Any update on the dental practice signage?" It is the third such message before ten o'clock. The person who receives it stops what they were doing, opens two systems and an email thread, works out where the order is, writes a reply that sounds confident, and sends it. Then they try to remember what they were doing before.

On Friday they will write a weekly update that summarises the same orders for the same people. Some of those people will still ask on Monday.

Status updates are not trivial. People need to know where work stands in order to make promises, plan and help each other. This piece is about what happens when the only way to find out is to ask someone, and the only way to answer is for that person to stop working and describe their work.

What the evidence suggests about interruptions

Microsoft's Work Trend Index survey, published in 2023, reported that the average worker in its data spent 57% of their time communicating, in meetings, email and chat, and 43% creating. Sixty-eight per cent said they did not have enough uninterrupted focus time in the workday. A later analysis of Microsoft 365 activity estimated that workers are interrupted roughly every two minutes during core hours by a meeting, email or chat. These are global figures from one vendor's products and customers, not a measurement of South African businesses, but they describe a working day in which focus is already scarce.

A study by Gloria Mark and colleagues at the University of California, Irvine, adds a less obvious finding. In a controlled experiment, people who were interrupted while doing an email-based task completed it in less time than those who were not, with no difference in quality. The researchers suggest people compensate for interruptions by working faster, but that this comes at a price: participants reported more stress, higher frustration, more time pressure and more effort. It was a laboratory study with a limited sample, and should not be stretched too far. It does suggest that the cost of an interruption may not show up in output at all. It may show up in how the work feels.

Why people have to keep asking

Consider an illustrative case: a Durban signage and printing business with about 18 staff. Orders are taken by email and phone, logged in a spreadsheet, and moved through design, approval, printing and installation. Each stage is handled by a different person, and each person keeps track in their own way. The spreadsheet is updated when someone remembers.

When a customer calls, the sales person has to ask production. When the owner wants to know what will be invoiced this month, they ask sales, who ask production. Every question becomes a small investigation. The mechanism has a few familiar parts:

  • Progress lives in people, not in a record. The work moves, but nothing records the move as it happens.
  • Updating the record is a separate task. When updating status means opening a different system after the work is done, it is the first thing dropped on a busy day.
  • Nobody trusts the record anyway. Because the spreadsheet is often out of date, people ask in person even when it is right.
  • Weekly reports repeat the same information. Written summaries are composed from memory and messages, and are out of date by the time they are read.

Mellorca has described this as a systems problem in why chasing people for updates is a systems failure and in when a status update requires a staff member to investigate. The customer's side of the same gap appears in why customers have to ask what is happening.

The human tax: time and cognitive load

Each status request costs a few minutes. The larger cost is what it does to the work around it. The person answering has to drop their current task, reconstruct someone else's question, gather information from several places and then pick up where they left off. If that happens ten times a day, the day becomes a series of short fragments.

There is also a load in being the person who knows. If you are the only one who can say where an order is, you carry the state of every order in your head, ready to answer at any moment. Writing a weekly report from that memory adds a second round of the same effort. Some people do not mind; being asked can feel like being relied on. For others it is a steady drain. Mellorca cannot know which applies to any individual and does not assume.

What could change

The aim is not to stop people asking. It is to make the answer something they can look up.

  1. Record progress where the work happens. If moving a job from design to printing is done by changing its stage on a shared board or job card, the status is updated as a by-product of doing the work, not as an extra step.
  2. Keep stages few and clear. Five well-understood stages that everyone uses are more useful than fifteen that nobody maintains.
  3. Make the record the first place to look. Managers who check the board before asking, and who say so, teach the team that the record matters and is trusted.
  4. Let the weekly report be generated, not written. If status is recorded, a summary of what moved and what is stuck can be produced from it, leaving people to add only the commentary that needs a human.
  5. Keep conversation for the exceptions. When something is blocked or at risk, a direct conversation is still the right tool. The record removes the routine questions so that these ones get attention.

In the illustrative printing business, a simple job board with five stages, updated by whoever moves the job, might answer most of the "any update?" messages without anyone being interrupted. The sales person could tell the customer where the order is in the time it takes to open the board.

Trade-offs

  • Someone still has to update the record. If changing a stage is awkward or slow, people will not do it, and the record decays. The design has to make updating easier than being asked.
  • Visibility can feel like surveillance. A board that shows where every job is also shows who is behind. Used to support people, it helps; used to monitor them, it can create new pressure.
  • Some questions are not really about status. A manager asking "how is it going?" may be checking on a person, not a job. A record cannot replace that kind of contact, and should not try.
  • Fewer conversations can mean less context. Updates given in person sometimes carry nuance that a stage label does not. Teams may need to keep a short weekly conversation for that.

Why it matters

Constant status requests are often treated as a cost of collaboration. Much of the time they are a cost of a missing record, paid in interruptions by the people who know the answer. When progress records itself as the work is done, fewer people need to ask, and the people who used to be asked get long enough stretches of time to finish things.

That is the dividend: attention that stays on the work rather than on describing it. The update stops being a chore because, for most questions, nobody has to give it.

Sources and further reading

Related Mellorca reading

Article summary"Any update?" arrives several times a day, and each answer means stopping work to describe work. What constant status requests take from people's focus, and what changes when progress records itself as the work is done.
Explore our solutionsStart a conversation