Observable condition
The most capable person in a team is also the person who formats the board pack, chases three suppliers for missing delivery notes, corrects the purchase order a colleague captured incorrectly, books the courier for an urgent consignment and answers the same question about the pricing spreadsheet four times a week. None of these jobs is difficult for them. That is the point: they are fast, accurate and dependable, so the work keeps arriving.
Ask them what they did last week and the answer is a list of small things. Ask what happened to the supplier review, the pricing analysis or the client proposal they were meant to lead, and the answer is usually that it moved to next week. The calendar of a senior estimator, a financial manager or an operations lead fills up with tasks that would be described, if anyone wrote them down, as administration.
An illustrative example: a 60-person electrical contracting business in Gauteng has one senior quantity surveyor who prices every large tender. She is also the only person who can update the rates file, the person site managers phone when a variation needs pricing, and the person who checks every subcontractor invoice against the order because she once caught an expensive mistake. Tender deadlines are met, but late at night, and the business quietly declines some tenders because she does not have the time to price them.
Realisation
The usual reading of this condition is personal. The person is too helpful, does not delegate, or has not been given an assistant. Sometimes that is true. More often, the low-value work is reaching the best people because of how the business is built rather than how they behave.
Work flows to the point of least resistance. If a task has no defined home, no clear owner, no reliable instructions and no system that can do it, it goes to whoever can finish it without asking questions. In most businesses that is the most experienced person. The organisation is therefore spending its scarcest capacity on its least valuable work, and it is doing so automatically, every day, without anyone deciding that it should.
This is a common experience rather than an unusual one. Microsoft's Work Trend Index, based on a survey of 31,000 workers in 31 countries, reported that 64% of people say they struggle with having the time and energy to do their job, and 62% say they spend too much time searching for information during the workday. Asana's Anatomy of Work research, drawing on a survey of 9,615 knowledge workers, makes a similar point: a large part of the working week goes on coordination and repetitive tasks rather than the skilled work people were hired to do.
Realisation prompt: if your most capable person had one free day a week, what would the business ask them to do with it, and why is that not happening now?
Identification
This is a work-design and capacity-allocation problem. The visible symptom is senior people doing junior work. The common assumption is that the individual needs to delegate or that the team needs another administrator. The structural cause is that routine work has not been given a designed path, so it collects around competence.
It is related to, but different from, the condition described in Why High-Value Employees Become Human Middleware. That Pattern is about skilled people bridging data between systems. This one is wider: it includes chasing, correcting, formatting, answering, checking and rescuing, much of which has nothing to do with integration.
Diagnosis
When the low-value work is traced back to its source, it usually comes from a small number of mechanisms.
- Concentrated access. Only one person has permission to change the rates file, approve the supplier or edit the template. Everything that touches that asset routes through them, however trivial.
- Undocumented know-how. The task is simple once you know how, but the knowledge has never been written down or built into a form, so only the experienced person can do it quickly.
- Upstream quality failures. Work arrives incomplete or wrong, and the senior person becomes the correction layer. They are not doing the task; they are repairing it.
- No intake or routing. Requests arrive by phone, chat and corridor conversation. Without a queue, people go to the person who will answer, not the person who should.
- Trust gaps. A past mistake led to a rule that the experienced person checks everything. The check was never replaced by a control that could run without them.
Each mechanism looks reasonable in isolation. Together they create a system in which the best people are permanently interrupted. The distinction between a people problem and a systems problem matters here, because coaching someone to say no does not remove any of these mechanisms.
Commercial impact
The commercial value sits mainly in capacity, revenue, margin and risk.
Capacity is the obvious dimension. Every hour of chasing or correcting is an hour not spent on the work that only that person can do. In the contracting example the visible cost is not the quantity surveyor's salary; it is the tenders the business never prices.
Revenue and margin follow. The deferred work is often the work that wins or protects money: pricing, proposals, supplier negotiation, client relationships, forecasting. When it is squeezed into evenings, it is done less carefully, and margin leaks through rushed estimates and unchallenged supplier terms.
Risk rises too. When routine work depends on one person, absence or resignation stops it. That is the key-person dependency problem, and it is often discovered at the worst possible moment. The broader cost of this condition is set out in the cost of high-value employees doing low-value admin.
Common misidentification
Hiring an assistant is the usual response. It can help, but if the work is unclear, uncontrolled or caused by upstream errors, the assistant inherits the same problems and the senior person becomes their supervisor. The work moves one desk along without being reduced.
Time-management training is another. It treats a structural flow of work as a personal habit. People can protect their diaries for a while, but the requests keep coming because nothing about the system has changed.
Possibility
A better operating state keeps experienced people on judgement, relationships and decisions, and gives routine work a home that does not depend on them. Requests come through a defined intake and are routed by type. Reference information, such as rates and templates, is maintained in one controlled place that others can read. Routine checks run against rules, and only genuine exceptions reach a senior person. Work that arrives incomplete is rejected at the point of entry rather than repaired downstream.
For the quantity surveyor, that might mean site managers submit variations through a short structured form, invoice checks against orders are automated with mismatches flagged, and the rates file is published read-only. She still owns the pricing logic. She no longer performs every routine step of it.
Intervention
- Log the interruptions. For two weeks, ask the three or four most capable people to note every task they did that someone else could have done. Record what it was, who asked and why it came to them.
- Group by cause. Sort the list by the mechanisms above: access, know-how, upstream quality, routing or trust. Most items will cluster.
- Fix the cluster, not the task. Widen read access, document or template the know-how, add validation where errors originate, introduce a simple request queue, or replace a person-based check with a rule-based one.
- Automate only after redesign. Where a task is repetitive and rule-based, automation or integration can remove it. Doing this before the work is understood tends to automate the confusion. The Insight on finding the manual work nobody is measuring covers this step.
- Re-measure. Repeat the log after a month. The aim is not zero interruptions; it is a visible shift of senior time back to senior work.
Diagnostic questions
- Which tasks reach your most experienced people only because they are the quickest to finish them?
- Which assets, files or approvals can only one person change?
- How much of their checking is repairing work that arrived wrong?
- Which strategic tasks have been postponed more than twice this quarter?
- If that person left tomorrow, which routine processes would stop?
Bottom line
When your best people spend their day on low-value work, it is rarely because they choose to. Work without a designed path collects around the most reliable person in the room. Giving routine work a proper home, through access, documentation, validation, routing and selective automation, is how a business returns its scarcest capacity to the work that actually grows it.
Sources and further reading
- https://www.microsoft.com/en-us/worklab/work-trend-index/will-ai-fix-work (last verified 10 October 2026)
- Anatomy of Work 2023 - Rise of the Connected Enterprise (last verified 10 October 2026)
Related Mellorca reading
- When Manual Exceptions Become the Normal Process
- When People Are Used to Move Data Instead of Make Decisions
- The Work Your Staff Do Because Your Systems Don't