Observable condition
It started as a stopgap. When the online shop launched, orders were copied by hand into the accounting system because the two did not connect. Someone said it would be sorted out once things settled. Three years later the copying has a name ("doing the transfers"), a time slot (every afternoon at three), a backup person for when the usual one is on leave and a page in the induction manual. The latest job advert for an administrator lists it as a duty. When the accounting system was upgraded last year, nobody asked whether the transfers could now be removed; the question was how to keep doing them in the new screens.
Most businesses have several tasks like this. They began as temporary fixes for a gap between systems, a missing report or an unusual customer, and over time they stopped being temporary without anyone deciding that they should.
Realisation
A manual workaround is cheap to remove when it is new. Only one person does it, nothing depends on it and everyone still remembers why it exists. As it ages, it acquires roles, schedules, documentation, dependants and habits. Other processes begin to assume it will happen. At that point removing it is no longer a small change; it is a change to how the business is organised.
The realisation is that there is a window during which manual work can be dealt with easily, and that the window closes quietly. The Lean Enterprise Institute's definition of muda distinguishes waste that can be removed quickly through improvement activity from waste that cannot be eliminated immediately. Manual work tends to drift from the first kind to the second. Recognising the early signs is what lets a business act while the cost of change is still low.
Realisation prompt: list the manual tasks in your business that someone once described as temporary. How many are still running, and how many now appear in a job description or training material?
Identification
This is structural manual work: a task that exists to compensate for a gap in systems or process has become embedded in roles, schedules and dependencies, so it is now treated as part of how the business operates rather than as a fault to be fixed.
It is related to the habits examined in when copy and paste becomes part of the job description, which focuses on the copying itself, and to when manual exceptions become the normal process. This pattern is about the transition: the signals that show a manual task is hardening into structure.
Diagnosis
The visible symptom is a familiar task that nobody questions. The common assumption is that it is simply part of the job. The early signs that it has become structural are specific and observable:
- It has a name. Teams refer to it as a routine, such as "the transfers" or "the Friday reconciliation".
- It has a schedule. It happens at fixed times and other work is planned around it.
- It has cover. Someone is trained to do it during leave, so the business has invested in keeping it alive.
- It is in writing. It appears in induction material, procedure documents or job adverts.
- It has dependants. Reports, approvals or other teams rely on its output and would break if it stopped.
- It survives system changes. Upgrades and new tools are configured to accommodate it rather than to remove it.
- It has its own tools. Spreadsheets, templates or macros have been built purely to support it.
The underlying causes are usually that the original gap was never logged as a problem with an owner, that nobody reviews manual tasks against changes in systems, and that the people doing the work are rewarded for reliability rather than for questioning whether the work should exist.
Commercial impact
The commercial value at stake is capacity, scalability, resilience and the cost of future change.
- Capacity. Structural manual tasks consume a fixed slice of time every day, often from capable people.
- Scalability. Many of these tasks grow with volume, so they become larger as the business grows.
- Resilience. The process works only while trained people are available. Absence or resignation exposes it.
- Change cost. The longer the task runs, the more depends on it and the more expensive it becomes to remove.
- Data quality. Repeated manual transfers introduce errors that flow into reports and decisions.
The size of the effect should be measured from the business's own time and volume data. The approach in how to find the manual work nobody is measuring is a practical starting point.
Common misidentification
The common mistake is to see a well-run manual routine as a sign of good operations. It may well be run with great care, but that care is being spent on a gap. Another is to assume that because a task survived a system upgrade, it must be necessary. Often it survived because nobody asked. A third is to automate the routine exactly as it is, preserving steps that only exist because of the original gap.
Possibility
In a stronger state, every manual workaround is recorded as a known gap with an owner and a review date. When systems change, the list is checked to see which workarounds can now be retired. New manual tasks are allowed, but they are labelled as temporary and come with an exit plan. Tools that observe how work is actually done make the hidden routines visible. Microsoft's overview of task mining describes capturing the steps users perform on their desktops to see how tasks are carried out and pinpoint those that can be automated. Its process mining overview describes using event data from systems of record to show how processes really run.
Intervention
- Run the sign check. List manual tasks and check each against the signs above: name, schedule, cover, written procedure, dependants, survival of upgrades, dedicated tools.
- Trace each back to its gap. Ask what missing integration, report or rule the task compensates for.
- Prioritise by hardening and cost. Tasks showing several signs and consuming significant time are the first candidates.
- Close the gap, not the task. Integrate, add the missing report or change the rule, then retire the routine and update its dependants.
- Keep a workaround register. Every new temporary fix is logged with an owner and review date.
- Review at every system change. Make retiring workarounds part of each upgrade or new implementation.
An illustrative example
The following is illustrative, not a client case. A Stellenbosch wine distributor reviews its administrators' routines and finds that the daily stock adjustment between its warehouse spreadsheet and its accounting system shows every sign: a name, a fixed time, cover during leave, an induction page and a sales report that depends on it. The adjustment was introduced when a warehouse app was dropped five years earlier. A replacement scanning app that writes directly to the accounting system removes the routine, and the sales report is repointed to the accounting data.
Practical diagnostic questions
- Which manual tasks in your business started as temporary fixes?
- How many of them now have a name, a schedule and trained cover?
- Which appear in job adverts or induction material?
- What would break if each one stopped tomorrow?
- When systems last changed, did anyone check which workarounds could be retired?
Bottom line
Manual work becomes structural gradually, through names, schedules, cover, documentation and dependants. Each of those is a visible sign, and noticing them early keeps the cost of change low. Recording workarounds as gaps with owners, and closing the gaps rather than perfecting the routines, stops temporary fixes from becoming permanent features of how the business runs.
Sources and further reading
- Muda, Mura, Muri - Get a Quick Introduction - Lean Enterprise Institute (last verified 10 October 2026)
- Overview of task mining - Power Automate (last verified 10 October 2026)
- Overview of process mining in Power Automate - Power Automate (last verified 10 October 2026)
Related Mellorca reading
- Why Small Tasks Become Expensive at Scale
- Why Teams Keep Building Manual Workarounds
- When Admin Becomes the Bottleneck That Limits the Whole Business