Lean thinking is often associated with production lines, machinery and physical inventory. However, waste: known as muda: appears wherever work, information or decisions flow. In an office, it may be hidden inside an inbox, approval queue, spreadsheet, service desk or project backlog.
The key question is not whether your team is busy. It is whether that activity creates value for the customer or organisation.
The DOWNTIME framework provides a practical way to identify the eight most common forms of waste:
- Defects
- Overproduction
- Waiting
- Non-utilised talent
- Transportation
- Inventory
- Motion
- Extra-processing
In the realm of operations, IT and administration, these wastes can extend lead times, increase rework, reduce employee capacity and weaken customer experience. The good news is that they are measurable: and therefore improvable.
Why Office Waste Is Easy to Miss
Factory waste is often visible: excess stock, machine downtime, long travel distances or defective products. Knowledge-work waste is less obvious because the output is usually digital and the process is distributed across people and systems.
A customer request may pass through:
- A shared inbox
- A ticketing platform
- A spreadsheet
- An analyst
- A team leader
- A compliance reviewer
- A manager
- A final approval queue
Each step may appear reasonable in isolation. Yet, when viewed end to end, the process may contain repeated data entry, unclear ownership, unnecessary approvals and several days of waiting.
This is where Value Stream Mapping becomes valuable. A current-state map shows how information and work move from request to completion. It also captures queues, handoffs, processing time, lead time and rework loops. The Lean Enterprise Institute’s overview of Value Stream Mapping provides useful context on mapping both material and information flow.

The 8 DOWNTIME Wastes in Office and Knowledge Work
1. Defects: Errors That Create Rework
In an office, a defect may be an incorrect customer record, incomplete application, inaccurate report, misclassified IT ticket or contract using the wrong version.
The initial error may take only two minutes to correct, but its total cost can include:
- Additional review time
- Repeated customer contact
- Re-approval
- Delayed downstream work
- Reduced confidence in the process
Track first-pass yield, rework hours, defect frequency and escaped errors. If only 82 of 100 submissions move forward without correction, the process has an 82% first-pass yield and a clear improvement opportunity.
2. Overproduction: Creating More Than the Customer Needs
Overproduction in knowledge work means producing information earlier, in greater volume or at a higher level of detail than required.
Examples include:
- Dashboards that nobody uses
- Reports produced “just in case”
- Long presentations where a decision summary would suffice
- Duplicate project updates across multiple platforms
- Email distributions that include people with no action to perform
A useful measure is output usage rate. If a team creates 20 recurring reports and only 11 are accessed or used in a decision, 45% of that reporting effort may warrant review.
3. Waiting: The Silent Extension of Lead Time
Waiting is frequently the largest source of office waste. Work may be waiting for information, system access, a signature, a response, a decision or an available specialist.
Common examples include:
- IT tickets waiting for assignment
- Invoices waiting for approval
- Analysts waiting for data extracts
- New employees waiting for account access
- Projects waiting for decisions from a steering committee
Measure queue time, approval delay, average item age and total lead time. A process with 35 minutes of actual work but a nine-day completion time is not primarily a productivity problem. It is a flow problem.
4. Non-Utilised Talent: Failing to Use Capability
Non-utilised talent occurs when an organisation does not fully use the skills, experience, creativity or problem-solving ability of its people.
This can appear when:
- Experienced analysts spend most of their time copying data
- Front-line employees are excluded from improvement decisions
- Specialists cannot resolve issues without multiple escalations
- Employees have ideas but no structured improvement channel
- Team members are assigned work below their capability while critical work remains delayed
Track the percentage of time spent on low-value administrative work, escalation rates and the number of improvement ideas implemented. Developing people is not separate from process improvement; it is one of its strongest enablers.
5. Transportation: Moving Information Unnecessarily
Transportation refers to unnecessary movement of materials or information. In an office, this is often digital.
Examples include:
- Copying information between a CRM, spreadsheet and ERP system
- Forwarding a request through several inboxes
- Printing a form for a physical signature
- Moving files between disconnected folders
- Sending data between departments when a shared workflow could provide access
Measure handoffs per transaction, systems touched, duplicate transfers and transport time. Every handoff is a potential point of delay, loss of context or data distortion.
6. Inventory: Backlogs and Work in Process
Inventory is not limited to physical stock. In knowledge work, it includes every incomplete item waiting to be processed.
Examples include:
- Open IT tickets
- Unreviewed applications
- Unfinished reports
- Projects started but not completed
- Emails awaiting action
- Change requests sitting in a backlog
Excess Work in Process creates competing priorities and hides the true workload. Track WIP quantity, backlog age, items older than a defined threshold and the number of parallel projects per person.
A smaller, actively managed queue often improves completion speed more effectively than simply asking people to work faster.
7. Motion: Searching, Switching and Navigating
Motion is unnecessary movement by people. In a digital workplace, this includes physical movement and cognitive movement between systems, screens and sources of information.
Typical examples are:
- Searching across multiple folders for the latest document
- Switching between six applications to complete one request
- Walking to a shared printer or meeting room
- Re-entering information because the original source is difficult to locate
- Repeatedly asking colleagues where a file or instruction is stored
Measure search time, application switches, physical trips and interruptions per task. Standard folder structures, clear naming conventions, integrated systems and visual workplace principles can reduce this waste considerably.
8. Extra-Processing: Work Beyond the Requirement
Extra-processing occurs when a team performs more work than the customer, regulator or next process step requires.
Examples include:
- Three approvals for a low-risk purchase
- Entering the same information into two systems
- Formatting internal reports to publication standard
- Checking data multiple times without a defined risk rationale
- Collecting fields that are never used
- Creating detailed analysis when the customer needs a simple decision
The remedy is not to remove necessary control. It is to distinguish value-adding work, required non-value-adding work and avoidable muda.
A Worked Example: Reducing Waste in Invoice Approval
Consider an accounts-payable process handling 420 invoices per month.
A current-state Value Stream Map identifies:
- Average lead time: 7.2 business days
- Touch time per invoice: 42 minutes
- First-pass yield: 82%
- Average approval handoffs: 6
- Average backlog: 180 invoices
- On-time payment rate: 76%
The team categorises the findings using DOWNTIME:
- Defects: 18% of invoices require correction
- Waiting: Invoices spend 6.4 days in approval queues
- Transportation: Data is copied between email, spreadsheet and finance software
- Inventory: 180 invoices remain in process
- Extra-processing: Low-risk invoices receive the same six-step approval route
The future-state design introduces:
- A standard electronic intake form
- Clear data validation at submission
- A two-level approval route based on invoice value
- A shared visual queue with ownership and ageing
- Automatic reminders after 24 hours
- A weekly review of aged items and recurring defects
After eight weeks, the process achieves:
- Lead time reduced from 7.2 to 2.1 business days
- Touch time reduced from 42 to 29 minutes
- First-pass yield increased from 82% to 97%
- Approval handoffs reduced from 6 to 3
- Backlog reduced from 180 to 55 invoices
- On-time payment increased from 76% to 96%
The improvement did not depend on asking employees to work longer. It improved the system by reducing waiting, defects, transportation, inventory and extra-processing.

Practical DOWNTIME Audit Checklist
Use this checklist during a process walk with operations, IT or administration teams.
Defects
- What percentage of work requires correction?
- How often does an error reach the customer?
- Is first-pass yield measured?
Overproduction
- Which reports, meetings or dashboards are rarely used?
- Are outputs created before demand exists?
- Can the same decision be supported with less information?
Waiting
- Where does work queue?
- How long do approvals, responses or access requests take?
- Which decisions have unclear ownership?
Non-Utilised Talent
- What low-value tasks occupy skilled employees?
- Can front-line staff resolve more issues directly?
- How are improvement ideas captured and tested?
Transportation
- How many times is information transferred?
- How many systems are touched per transaction?
- Are physical signatures or manual forwarding still necessary?
Inventory
- How much WIP is open today?
- How many items are older than the service target?
- Are too many projects active at once?
Motion
- How much time is spent searching?
- How many applications or folders must employees navigate?
- Are workplace layouts and digital workspaces intuitive?
Extra-Processing
- Which approvals or checks do not alter the outcome?
- Is data entered more than once?
- Are teams producing more detail than the customer requires?
Record evidence rather than relying on assumptions. Useful measures include process time, lead time, queue size, rework rate, first-pass yield, handoffs, approval count and WIP age.
Turn Waste Identification Into Capability
DOWNTIME is most effective when it becomes part of a structured improvement method. In the Define phase, clarify the customer and business problem. In Measure, establish reliable baseline metrics. In Analyse, use the Value Stream Map, Pareto analysis and root-cause tools to understand where muda originates. In Improve, test countermeasures. In Control, monitor performance and sustain the gains.
You can also use the Process Cycle Efficiency Calculator to compare value-adding process time with total lead time. For broader capability development, Lean Six Sigma Green Belt Training helps professionals apply data-driven improvement methods to complex operational and administrative processes.
Waste is not a judgement about people. It is a signal that the system can be designed more effectively.
Use the DOWNTIME checklist, map one office value stream and measure the largest source of muda this week. Then pursue accredited Lean Six Sigma training and certification to turn those findings into sustained improvement.








