There is a task sitting with someone in your business right now that should not be there. It arrived because they are reliable and it stayed because nobody else picked it up. It is consuming somewhere between two and five hours of their week, it does not require their judgment, and they have stopped raising it because raising it never changed anything.
This is not a staffing problem or a management problem but an infrastructure problem, and it is far more expensive than it appears because the cost is not the task itself but what the task is displacing.
The mechanism that puts the wrong work on the right people
In most organisations, the allocation of operational tasks follows an unofficial rule: when something needs to get done and there is no clear system for doing it, it goes to the person most likely to do it correctly. That person is almost always one of the most capable people in the business, which is why the task gets done reliably, and also why it stays with them indefinitely.
The mechanism is self-reinforcing - The capable person completes the task well, which confirms that they are the right person for it, which means it comes back to them the next time it needs doing. Over months and years, senior people can accumulate a significant portfolio of tasks that arrived this way: each one small enough to seem manageable, together consuming a meaningful fraction of the time they should be spending on work that actually requires them.
The organisation rarely notices this happening because the output is maintained. The work gets done, the capable person absorbs the load without visible complaint because absorbing load is part of how they became capable, and the cost sits in the work that does not happen because of the hours this person is spending on tasks a well-designed system could handle automatically.
What this costs in practice
The direct cost of misallocated senior time is straightforward to calculate once it is made visible. A person earning $150,000 per year costs the business approximately $75 per hour, meaning five hours per week on work that does not require their skills costs $375 per week, $1,500 per month, and $18,000 per year, and that is before accounting for the opportunity cost of the thinking and judgment that did not happen in those hours.
Across an organisation of 50 to 200 people, where this pattern is replicated across multiple senior staff, the total misallocation of skilled capacity is typically significant, often running to several hundred thousand dollars per year when the full picture is assembled honestly.
The harder cost to quantify is the one that does not appear as an expense at all: the strategic work that was deferred, the client relationship that was not developed, the operational improvement that was never examined because the person who would have examined it was occupied with a task that a system should have been handling for the past three years.
The categories of misallocated work that appear most consistently
Across the businesses we work with, certain categories of misallocated work appear regardless of industry or scale.
The first is exception handling. Most operational processes produce exceptions, and exceptions require judgment, but in many organisations the volume of exceptions reaching directors and senior leaders is far higher than it needs to be because the upstream process is poorly designed, generating cases that a better-built system would triage and resolve automatically before they surface as decisions requiring senior intervention. The leader becomes a de facto quality control layer for a process that should never have reached them, and the cost is not just their time but the interruption cost of context-switching out of higher-order work every time an exception lands.
The second is performance and operational reporting. In many businesses, the work of assembling board packs, operational dashboards, and divisional performance summaries involves significant manual effort from people whose value to the business lies in interpreting what the data means, not in producing it. The data exists across multiple systems, and the effort of extracting, reconciling, and formatting it into something a leadership team can act on falls to senior finance or operations staff who spend two or three days per month on work that contains no analytical judgment whatsoever. That time is recoverable in full.
The third is cross-functional coordination and governance that should be handled by infrastructure. In organisations where significant work crosses team or entity boundaries, the coordination of handovers, approvals, and status visibility often defaults to senior people because they have the organisational authority to make things move. The activity looks like leadership because it involves senior people and consequential decisions, but much of it is process administration: chasing sign-offs, consolidating inputs, and maintaining visibility over workflows that a well-designed system should be tracking automatically. The senior person is not adding judgment to these interactions but providing organisational friction to compensate for the absence of infrastructure.
Why it persists
The reason this pattern persists in otherwise well-run organisations is that addressing it requires stepping back from the day-to-day to examine it, which requires exactly the time and attention that the pattern itself is consuming.
There is also a deeper, more human reason. The people carrying this work are often reluctant to raise it because doing so feels like complaining about their own effectiveness, and the organisations they work in have implicitly rewarded their willingness to absorb it. Asking a capable person to stop doing something they do well in order to free them for work that has not yet been defined requires a degree of structural confidence that many leadership teams do not have available when they are running at capacity. This is why these kinds of problems benefits from an external perspective, because the internal people best placed to solve the problem are the ones most embedded in the conditions that created it.
The structural fix
The resolution is not a conversation about priorities or a reorganisation of responsibilities. It is the construction of infrastructure that removes the task permanently, by building a system that handles it reliably without requiring senior involvement.
When this is done well, the capable person does not lose work but gains back the hours that were being consumed by tasks beneath their skill level, and those hours become available for the judgment-intensive work that only they can do. The organisation does not get smaller when this happens: it gets more of what it was already paying for.
The question worth asking honestly is not whether this pattern exists in your business, because it almost certainly does, but how many hours per week your best people are currently spending on your worst work.
Karst is an operations and technology firm that designs and implements Intelligent Operating Systems to deliver commercial outcomes. Built by operators. Powered by AI. Measured in outcomes.
