Waiting is one of the most common forms of waste in office work. It’s also one of the easiest to overlook.
In a factory, waiting is obvious. A worker stands still because a machine is busy or parts haven’t arrived. In business, waiting hides behind screens and meetings. It shows up as tasks stuck in review, approvals that take days, emails sitting unanswered, or work that can’t start because someone doesn’t have the right information.
Lean calls this “Waiting” because time passes, but value doesn’t increase. The work doesn’t move forward. The customer doesn’t benefit. And your team ends up spending more energy chasing clarity than creating outcomes.
This post covers what waiting waste looks like in corporate environments, why it’s so costly, and practical ways to reduce it using structured improvement and employee-driven innovation.
Quick refresher: the 8 wastes of Lean
Lean uses the idea of “8 wastes” to highlight activities that consume time and resources without improving the final product or service.
In many workplaces, these eight wastes are listed as: Defects, Overproduction, Waiting, Non-Utilized Talent, Transportation, Inventory, Motion, and Extra-Processing.
They’re often remembered through an acronym like DOWNTIME.
This article focuses on one waste from that list: Waiting.
What is the Lean waste of Waiting?
Waiting is any idle time created when people, information, or work-in-progress can’t move forward because they’re waiting on the next step.
In business, waiting doesn’t always look like “doing nothing.” It often looks like:
- Working on low-priority tasks while a critical task is blocked
- Following up repeatedly for a status update
- Switching between tasks because nothing can be finished
- Sitting in meetings that exist mainly to unblock other work
Waiting breaks the flow of work. Instead of a smooth handoff from one step to the next, work gets stuck in queues. And queues create delays, delays create urgency, and urgency creates mistakes. That’s how waiting turns into rework and frustration.
What waiting looks like in an office environment
Waiting in a corporate setting usually appears as dependency delays. One person can’t complete work because another person hasn’t finished theirs. Sometimes the dependency is a person. Sometimes it’s a team. Sometimes it’s a system.
Here are common forms of waiting waste we see in business environments:
- Scheduling conflicts that limit progress
- Work delayed because the “right people” aren’t in the meeting
- Employees waiting for manager approval to move forward
- Projects paused due to budget changes or scope adjustments
- Technology delays and system issues that block work
- Poor interdepartmental communication causing repeated handoffs
- Management structures requiring too many inputs to make decisions
- Work stuck in review cycles with unclear ownership
- Onboarding delays because access requests take too long
- Customer requests waiting in an inbox before anyone claims them
Some of these are easy to spot. Others are treated as “normal.” But the moment your organization accepts waiting as normal, you build inefficiency into your operating system.
Why waiting is waste (and why it adds up fast)
Waiting is waste for four simple reasons.
- Waiting adds no value.
Nothing improves while a request sits in a queue.
- Waiting breaks flow.
Work stops and starts. That creates bottlenecks and uneven workloads.
- Waiting increases costs.
Idle time still costs money. Delays stretch lead times. And delays create “catch-up” work later.
- Waiting disrespects people.
Your team’s time and talent are valuable. Forcing people to wait for basic information, approvals, or access drains morale and engagement.
And in business, waiting can multiply quickly. One delayed decision creates downstream delays. One missed approval window can push work into next week. One stalled handoff can block an entire chain of tasks.
Common root causes of waiting waste
Most waiting isn’t caused by a lack of effort. It’s caused by how the process is designed.
Bottlenecks and overloaded roles
A single team or decision-maker becomes the “narrow point” in the system. Work piles up behind them, even if everyone else is ready to move.
Too many approvals or unclear decision rights
When it’s not clear who can decide, work circles the organization. Even worse, people wait because they’re afraid to move without permission.
Handoffs without clear inputs and ownership
Work gets passed to another person or team without the information needed to act. The next step can’t start, so it sits—usually in an inbox or a project board column.
Planning that doesn’t match real capacity
Teams commit to more work than time allows. The result is predictable. Tasks wait, deadlines slip, and priorities change mid-stream.
Work done in batches
Reviews that happen “once a week” create artificial queues. Work waits even when it could be completed sooner with smaller, more frequent check-ins.
Too much work in progress
When everything starts at once, nothing finishes quickly. People switch contexts constantly, which creates more delays and more partial work waiting to be picked up again.
Information locked in silos
If the knowledge needed to move forward lives in one person’s head or one team’s folder, everyone else is forced to pause and ask.
Tooling and access delays
Waiting for system permissions, broken tools, or slow technology is still waiting. It just hides behind “IT tickets” and workarounds.
Meetings are becoming a gate
If work can only move forward after “the meeting,” then the calendar becomes the process. That almost always increases cycle time.
The best way to reduce waiting is to stop treating it like a personal productivity problem. It’s a system problem. Fix the system and the waiting drops naturally.
How to reduce waiting waste in a practical way
Reducing waiting doesn’t require a massive transformation. It requires targeted improvements that remove blockers and speed up flow.
Run short daily unblock huddles
A short daily check-in can be useful when it has one job: surface blockers and resolve them fast. This is not a status meeting. It’s a clearing mechanism.
Keep it tight. Identify what’s blocked, who can unblock it, and what decision needs to happen today. The goal is to prevent “work waiting for the meeting.”
Reduce approval friction
Waiting is often approval waiting. The work is done, but it can’t ship until someone signs off.
Start by clarifying decision ownership. Then set clear response expectations, like a 24–48 hour window for approvals. If low-risk items don’t require multiple reviewers, simplify the chain.
And if reviewers struggle to know what “good” looks like, add a short checklist so approvals become faster and more consistent.
In most organizations, the biggest improvement is clarity. When people know who decides and what the standard is, approvals speed up on their own.
Make work “ready” before it enters the workflow
A huge cause of waiting is missing information.
Work starts, then stops because something isn’t defined. That stop is waste.
A simple “definition of ready” reduces this dramatically. Before a request enters the workflow, make sure it has a clear objective, the required context, success criteria, an owner, a due date, and known dependencies.
When those basics are present upfront, the work moves with fewer pauses and fewer follow-ups.
Limit work in progress (WIP)
One of the fastest ways to reduce waiting is to stop starting so much work at once.
When too many projects are active, everything waits. People bounce between tasks, handoffs become messy, and priorities blur.
Setting a WIP limit forces focus. It shifts the culture from “start more” to “finish more,” which improves flow and makes bottlenecks visible quickly.
Improve handoffs between teams
Cross-team work is one of the biggest drivers of waiting. The handoff isn’t clear, so tasks bounce around.
A good handoff answers four questions: what inputs are required, what output should be delivered, who owns the next step, and what turnaround time is expected.
Even small improvements here can remove a surprising amount of “waiting on…” time.
Make queues visible
Waiting hides in queues. Visibility turns it into something you can improve.
Start by tracking how long work sits in “pending review,” how long approvals take, how long requests sit unassigned, and the most common reasons work gets blocked.
Once waiting becomes visible, it becomes solvable—because you can see where flow breaks and why.
How to measure waiting (so you can prove improvement)
Waiting can feel like a vague frustration unless you measure it. Good metrics make it real.
Lead time
This is the total time from the request created to the request completed. It tells you how long customers or internal stakeholders actually wait for outcomes.
Cycle time
This is the time from when work starts to when it finishes. It helps you understand how efficient execution is once someone begins.
Queue time
This is the time between steps. In many office processes, queue time is where most of the delay lives.
Approval time
This measures how long it takes to move from “submitted for approval” to “approved.” If you’re reducing waiting, this metric usually changes quickly.
Blocked time
This is the time work is marked as “waiting on…” a person, decision, information, or system. It’s one of the clearest signals of where your process is breaking.
Pick one workflow first. Baseline it. Improve it. Then scale. Even a small reduction in approval time or queue time can unlock major gains in throughput and employee focus.
Using Ideawake to reduce waiting waste
Waiting waste is a shared experience, but the causes are usually scattered across teams. Leadership sees delays, but not always why. Employees see the root causes daily, but they don’t always have a consistent place to surface them.
That’s where employee-driven innovation becomes practical.
With Ideawake, you can run a focused improvement challenge like: “Where do you lose the most time waiting each week, and what would remove that delay?” The power is that you’re not relying on a few voices in a meeting. You’re gathering real examples from the people closest to the work.
Instead of forcing everything into a workshop, teams can contribute in a structured way. They can point to where waiting happens, what causes it, and what a better process would look like. They can also flag which fixes feel low-effort and which ones require bigger changes.
Once ideas are captured in one place, patterns become obvious. You can see repeat bottlenecks across departments. You can spot approval layers slowing everything down.
You can identify common themes like missing inputs, unclear ownership, or meeting-based gates. Then you can prioritize solutions based on impact and effort, and move the best ones into pilots with clear owners and timelines.
The real win is consistency. Waiting waste doesn’t disappear from one conversation. It improves when you run small cycles regularly, keep the feedback loop open, and track what changed.
Ideawake supports that rhythm—so waiting becomes something your organization steadily reduces, not something everyone just complains about.
If you want to see what this looks like in a real workflow, book a demo of Ideawake. We’ll show you how teams run targeted challenges, surface the biggest sources of waiting, and turn the best ideas into measurable improvements.
FAQs
What is the Lean waste of waiting?
Waiting is idle time when people, information, or work-in-progress can’t move forward because they’re waiting on the next step, approvals, resources, or clarity.
What are examples of waiting waste in an office?
Common examples include approvals stuck in review, meetings required to unblock work, slow responses to requests, unclear handoffs, delayed access to tools, and work waiting for missing information.
Why is waiting considered waste?
Because it adds no value, breaks flow, increases cost through longer lead times, and wastes employee time and talent.
How do you reduce waiting waste quickly?
Start by making blockers visible, tightening approval loops, running short unblock huddles, clarifying handoffs, and limiting work in progress.
How does Ideawake help reduce waiting waste?
Ideawake provides a structured way to capture where waiting happens, crowdsource root causes and solutions from employees, prioritize fixes, and track implementation and results.