Dimension 1: Where Time Really Leaks in Knowledge Work
- New Way To
- Jan 20
- 3 min read
Updated: Feb 15
It’s rarely the big process. It’s the small, repeated waste.
1) A real-world scenario
You sit in a weekly improvement meeting. The numbers look fine on paper, yet people sound exhausted. A project that should take two weeks keeps taking six. When you ask why, you hear a familiar mix of answers:
“I was waiting for input.”
“I had to reformat it for the template.”
“I could not find the latest version.”
“I had to redo it because expectations changed.”
No one is being dramatic. No one is complaining. They are just describing normal work.
And that is the problem. In knowledge work, the biggest losses hide inside what everyone has learned to accept.
2) The underlying pattern
Most organisations look for waste in the obvious places: slow systems, long meetings, complex processes. Those exist, but they are rarely the main source of lost time.
The real leak is usually a cluster of small frictions that repeat every day:
Searching for information across email, Teams, SharePoint, drives
Copying, pasting, and reformatting between tools
Re-entering the same data because systems do not connect
Working with unclear inputs and fixing it later
Doing work twice because ownership is split
Waiting for an approval that is not clearly defined
Each friction looks minor. Five minutes here, ten minutes there. The uncomfortable truth is that these frictions compound in three ways:
They multiply across people.
If 30 people lose 20 minutes a day, that is 10 hours a day. It becomes invisible capacity loss.
They break concentration.
Time loss is not only the minutes spent. It is the mental restart cost.
They create hidden rework loops.
A small ambiguity early becomes a large correction later.
This is why teams can feel busy all day and still make uneven progress. They are not slow. They are leaking effort.
3) Why common fixes fail
When leaders hear “we lose time,” they often react in predictable ways.
Fix 1: Buy a new tool.
Tools can help, but they rarely remove the micro-frictions by themselves. A new tool layered on top of messy work often adds new steps, new rules, and new training.
Fix 2: Ask people to be more disciplined.
“Use the template.” “Document better.” “Follow the process.”
This sounds reasonable, but it fails when the environment makes the disciplined choice harder than the workaround. People optimise for speed and survival, not compliance.
Fix 3: Run a big improvement program.
Large programs often start at the wrong altitude. They redesign processes at a high level and miss the tiny steps where the time actually leaks. People then conclude that improvement is theoretical.
Fix 4: Automate too early.
Automation applied to unstable or unclear work amplifies confusion. You speed up the wrong thing. You lock in bad handovers. You create exceptions no one understands.
The pattern is simple: you cannot fix effort waste without seeing it at the level where it lives.
4) What actually helps
Effort waste becomes manageable when you treat it as a design problem in daily work, not as a motivation problem.
Here are approaches that consistently work in real organisations.
Make the micro-frictions visible, fast.
Not with long interviews. With a short pulse that collects real examples. The goal is to identify the top friction categories and the tasks where waste concentrates.
Pick one recurring task and follow the work.
The best entry point is a task that happens weekly or monthly, touches multiple teams, and produces a deliverable. Examples: reporting, approvals, customer requests, document creation. Map it at the level of real steps.
Standardise the boring parts.
People resist standardisation when it feels like control. They welcome it when it removes stupid work. Standardise templates, inputs, naming conventions, handover checklists, and decision criteria. Leave room for expertise where it matters.
Reduce duplication by clarifying ownership.
If two roles both “own” the output, you will get duplication and rework. Name who owns the final decision and who provides input. Then make that visible in the workflow.
Create one source of truth, then enforce it gently.
Most time waste is searching and version confusion. Choose one place for final documents and one naming scheme. Then make it easier to do the right thing than the wrong thing.
Use automation and AI as a second step, not the first.
Once the work is clear and stable, automation becomes a lever. Before that, it becomes noise.
5) One reflective question
If you picked one recurring task in your organisation, which part would you expect to be the most wasteful: the core work, or all the small steps around it?
6) And now?
If you want a quick, low-effort way to surface where effort waste shows up across teams, a short Work Friction Pulse often reveals the patterns people have normalised, and helps you choose the right task to look at next.
