90%
Office Work Is Waste
8
Wastes Apply Here Too
Invisible
Office WIP Hides in Email
Flow
Same Principle, Different Medium

Why Lean in the Office?

Most lean efforts focus on the shop floor — but the office processes that surround production often have worse waste ratios. An order that takes 2 minutes to enter might wait 3 days for approval. An engineering change that takes 1 hour of actual work sits in a queue for 2 weeks. A quality report takes 30 minutes to write but 5 days to route, review, and act on.

The same lean principles that transform the factory — flow, pull, waste elimination, standard work, visual management — apply directly to office and administrative processes. The challenge is that office waste is invisible: it hides in email queues, shared drives, and approval chains.

The 8 Wastes in the Office

WasteFactory ExampleOffice Equivalent
TransportationMoving parts between buildingsForwarding emails, routing documents through unnecessary approvers, hand-carrying paperwork
InventoryExcess WIP between stepsEmail backlog, unprocessed orders, reports sitting in review queues, open tasks in project management tools
MotionOperator walking for toolsSearching for files, toggling between systems, walking to printers, looking for information
WaitingMachine waiting for materialWaiting for approvals, waiting for information from another department, waiting for a meeting to make a decision
OverproductionMaking more than neededReports no one reads, CC'ing everyone, creating data nobody uses, meetings with no decisions
Over-processingTighter specs than neededFormatting reports beautifully when a quick email would do, triple-checking low-risk items, over-engineering presentations
DefectsScrap and reworkData entry errors, incorrect orders, wrong information sent, rework of documents
SkillsNot using operator knowledgeOverqualified people doing routine tasks, no one asking frontline staff for input, underutilized expertise

Making Office Work Visible

The biggest challenge in lean office is that work is invisible. On the factory floor, you can see WIP piling up. In the office, WIP hides in email inboxes and shared drives. Making it visible is the first step:

Factory ToolOffice EquivalentPurpose
Production board (hour-by-hour)Team task board with daily targetsShow plan vs. actual in real time
Kanban cardsWIP limits on process stages (e.g., max 10 orders in "awaiting approval")Prevent overloading any step
Visual management boardTeam SQDCM board for office KPIsDaily performance review
Standard work sheetProcess checklist with screenshots/stepsConsistent execution, faster training
Value stream mapProcess map with cycle time and wait time for each stepSee where orders/information get stuck

Office Process Improvement Steps

Map the current processFollow one transaction (order, ECN, purchase request) from start to finish. Record every step, every handoff, every queue, every approval. Note the process time (actual work) and lead time (total elapsed time including waiting). The ratio will shock you.
Identify the wasteFor each step, ask: does the customer (internal or external) value this? If not, it is waste. Common offenders: redundant approvals, re-entering data between systems, reports that exist "because we always have," and meetings that could be emails.
Eliminate handoffsEvery handoff creates a queue, a potential error, and a delay. Can one person do steps 3, 4, and 5 instead of three people each doing one? Can you eliminate the approval step for low-risk transactions?
Create flowProcess work in the order it arrives (FIFO), not in batches. Do not let emails accumulate for hours — process them in defined windows. Set WIP limits: if the approval queue exceeds 10 items, stop accepting new ones until the queue clears.
Standardize and sustainWrite the improved process as standard work with screenshots and checklists. Train everyone using the TWI method. Review metrics weekly. Improve continuously.

The Process Time to Lead Time Ratio

In most office processes, the actual work takes 5-15 minutes but the total lead time is 3-10 days. That means 95%+ of the time, the work is sitting in a queue waiting. The improvement opportunity is not in making the 15 minutes faster — it is in eliminating the 9.9 days of waiting.

Four lead times, one ruler Taking the work from 15 minutes down to nothing — the whole of the make-it-faster idea, at its physical limit — moves the end of a ten-day transaction by 0.10%. Deleting one three-day approval queue moves it by 30%.

Both numbers in the baseline bar are the callout's own: "the actual work takes 5-15 minutes but the total lead time is 3-10 days", and its next sentence pairs the top of each range — "not in making the 15 minutes faster ... eliminating the 9.9 days of waiting". So the drawn baseline is 15 minutes of work inside 10 days, and 10 days is 14,400 minutes. Everything on the ruler is arithmetic on those two numbers. 15 / 14,400 = 0.104% of the lead time is work, so 99.90% is waiting — which is the callout's own 9.9 days, since 10 days less 15 minutes is 9.99 days. Row B halves the work to 7.5 minutes: 9.9948 days, −0.05%. Row C sets the work to zero. That is not a strawman but the ceiling of the whole strategy — no method can save more than the 15 minutes that are there — and it gives 9.9896 days, −0.10%. Row D is the figure's single imported number, taken from "Why Lean in the Office?": "An order that takes 2 minutes to enter might wait 3 days for approval". Deleting one such wait leaves 14,400 − 4,320 = 10,080 minutes, exactly 7.0 days, −30.0%. It is the same kind of wait the page's other worked examples describe: an order, 2 min in 3 days, is 0.046% value-adding; an engineering change, 60 min in 14 days, is 0.298% value-adding; a quality report, 30 min in 5 days, is 0.417% value-adding. The two dashed ghosts in row A are not corrections. They are the widths the page's own round figures would give the work if you drew them: 10% of the lead time — the stat grid's "90% office work is waste" — is 1 day, and 5% — the callout's "95%+ of the time" — is 12 hours. Both figures are floors and both are correct; across every corner of the page's own 5-15 minute by 3-10 day band the work is 0.035% to 0.347% of lead time, so the waiting is 99.65% to 99.97%. The true sliver is 96 times narrower than the first ghost and 48 times narrower than the second, because one day of queue is 1,440 minutes — 96 times the entire work content. In drawn pixels, at 52 px to the day: the work sliver is 0.54 px, row B's right edge moves 0.27 px, row C's moves 0.54 px and row D's moves 156.00 px. The hairline in row A is drawn a few pixels taller than the bar so that it can be found at all; only its width is to scale. The detail strip magnifies by 14,400 / 60 = 240: the same width that holds ten days above holds one hour below, which is the only scale at which the 7.5 minutes row B saves can be seen at all.

✅ Lean Office
  • Office processes mapped with cycle time and lead time
  • WIP limits on queues (max items in each stage)
  • Visual boards for team workload and metrics
  • Standard work for recurring processes
  • Meetings have agendas, time limits, and action items
❌ Office As Usual
  • "That is just how it works" — no process mapping
  • Unlimited WIP — everyone drowning in backlogs
  • No visibility into who is working on what
  • Every person does the process differently
  • Meetings end with "let's schedule another meeting"

🎯 Key Takeaway

The office has more waste than the factory — it is just harder to see. Map your key transactional processes, measure the ratio of actual work to waiting time, and attack the queues, handoffs, and approvals that create 95% of the lead time. The same tools work: visual management, standard work, WIP limits, and kaizen. Start with one process, show the improvement, and expand from there.

Interactive Demo

Streamline an office process. Apply lean tools to eliminate waste and reduce lead time.

⚡
Try It Yourself
Lean Office Process Optimizer
▼
Apply lean tools to each step of an office process. Eliminate unnecessary steps, combine adjacent steps, or simplify complex ones. Watch lead time shrink and touch time ratio improve.
Office Process Flow
1
Receive Request
Touch: 10m | Wait: 2.0h
Wait: 2.0h
2
Manager Approval
Touch: 5m | Wait: 4.0h
Wait: 4.0h
3
Data Entry
Touch: 15m | Wait: 1.0h
Wait: 1.0h
4
Verification Check
Touch: 20m | Wait: 3.0h
Wait: 3.0h
5
Filing & Archiving
Touch: 10m | Wait: 1.5h
Wait: 1.5h
6
Send Confirmation
Touch: 5m
Lead Time Comparison
Before12.6h (Touch ratio: 9%)
After Lean12.6h (Touch ratio: 9%)
Touch time Wait time
0%
Lead Time Reduction
9%
— 0% vs baseline
Touch Time Ratio
6/6
Steps Remaining
755m
— 0m vs baseline
New Lead Time
Ready for the full knowledge check? Test your understanding with guided scenarios and data export.
PROTake the Pro Knowledge Check →
Free forever · Every feature included

Stop reading, start modeling

Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.

Open Workbench → Pro Knowledge Check

Take this to a room

The running order

For an administrative team. They should leave having measured the ratio of work time to lead time on one process.

7 beats · 10 min
  1. 1

    The office has more waste than the factory

    It is just harder to see, because it has no piles you can point at.

    • Roughly 90 per cent of office work time is non-value-adding.
    • Nobody walks past a queue of emails and notices it.
    • Office WIP hides in inboxes, approval queues and drafts.

    Ask the room How many things are currently waiting for someone's approval here?

  2. 2

    Measure the ratio

    The one number that makes the case, and it takes an afternoon to get.

    • In most office processes the actual work takes 5 to 15 minutes.
    • The total lead time is 3 to 10 days.
    • So 95 per cent or more of the time, the work is sitting in a queue.
  3. 3

    The improvement is not in the 15 minutes

    This follows directly, and it redirects the whole conversation.

    • Making the work faster changes nothing meaningful.
    • Eliminating the 9.9 days of waiting is the opportunity.
    • Which means attacking queues, handoffs and approvals rather than typing speed.

    Ask the room How many handoffs does our order process have?

  4. 4

    The same eight wastes

    They all apply. Naming the office version makes them visible.

    • Overproduction: reports nobody reads.
    • Waiting: work sitting in an approval queue.
    • Motion: hunting for a document across three systems.
    • Defects: rework from incomplete information on the first pass.
  5. 5

    Make the work visible

    You cannot manage a queue you cannot see, and office queues are invisible by default.

    • A physical or digital board showing every item in process.
    • WIP limits per person or per stage.
    • The moment the queue is visible, its length becomes a conversation.
  6. 6

    Attack the approvals

    Approvals are the most common single source of office lead time and often the least examined.

    • How many are there, and what has each one ever caught?
    • An approval that has never rejected anything is a delay with ceremony.
    • Delegate the threshold rather than removing the control.
  7. 7

    Start with one process

    Map it, measure the ratio, fix the biggest queue, show the result.

    • Pick one transactional process with a clear start and end.
    • Measure work time and lead time honestly.
    • Fix the largest wait, then measure again and publish the difference.

    Ask the room Which process do we map first?