For my Facebook fans you already know about this great feature. But for those of you that are not connected to A Lean Journey on Facebook or Twitter I post daily a feature I call Lean Tips.  It is meant to be advice, things I learned from experience, and some knowledge tidbits about Lean to help you along your journey.  Another great reason to like A Lean Journey on Facebook.

Click this link for A Lean Journey’s Facebook Page Notes Feed.

Here is the next addition of tips from the Facebook page:

Lean Tip #4111 – Waiting for Approvals Is Still Waste

A production line can be perfectly balanced and still lose days because someone is waiting for an approval. The same thing happens in engineering, purchasing, quality, finance, and other support functions. Work gets completed, but the next step cannot begin because a decision is sitting in someone’s inbox.

Waiting is one of the classic forms of Lean waste, yet organizations often overlook it when the waiting happens in an office. A purchase order waits for approval. An engineering change waits for review. A quality disposition waits for a signature. Meanwhile, the customer, production team, or supplier waits for the process to move forward.

The first step is to make the waiting visible. How long does work actually sit between process steps? Who has the authority to make the decision? Does every approval add value, or has the approval simply become part of the process because “that’s the way we’ve always done it”?

Lean thinking challenges us to examine the entire value stream, not just the physical movement of material.

If a decision is necessary, make it flow. If it isn’t necessary, eliminate it. A process doesn’t create value while it’s waiting for someone’s approval.

Lean Tip #4112 – Email Is Not a Process

How many times have you searched through your inbox trying to determine the status of an important issue? Someone sent an email, someone replied, another person forwarded it, and now five people are involved—but nobody is quite sure who owns the next action.

Email is a communication tool. It is not a process management system.

Lean organizations design processes so that work, ownership, status, and problems are visible. When email becomes the primary way of managing work, information becomes scattered across individual inboxes. People spend time searching, forwarding, following up, and recreating information that already exists somewhere.

This creates several forms of waste at once: waiting, overprocessing, motion, and often defects. A planner waiting for a response can delay production. An engineer searching for the latest revision can work from outdated information. A customer service representative may have to ask three people for an answer that should have been readily available.

The solution isn’t necessarily to eliminate email. It’s to stop using email as a substitute for a well-designed process.

Ask yourself: If one person were out of the office tomorrow, could someone else easily determine the status of their work? If the answer is no, you may have an information-flow problem disguised as a communication problem.

Lean Tip #4113 – Searching for Information Is Waste

Walk into a manufacturing area and you can quickly recognize wasted motion when an operator searches for a tool. In an office environment, the same waste is often invisible because it looks like someone simply “working.”

Consider how much time people spend searching for drawings, specifications, procedures, purchase orders, customer information, reports, or the latest version of a spreadsheet. Multiply those minutes across dozens or hundreds of employees, and the hidden cost becomes significant.

Lean teaches us to make the flow of information as intentional as the flow of material. Information should be available where it is needed, when it is needed, in a form that is easy to understand. That requires disciplined document control, logical file structures, visual management, and clear ownership.

There is another cost that is harder to measure. Searching interrupts concentration. An employee who spends ten minutes looking for information may lose much more than ten minutes because it takes additional time to regain focus.

The next time someone says, “Give me a minute, I need to find that,” pay attention. It may be a small inconvenience, or it may be evidence of a much larger process problem.

If people have to search for information repeatedly, don’t just help them search faster. Improve the system that makes them search in the first place.

Lean Tip #4114 – Meetings Should Move the Work Forward

Meetings are one of the most accepted forms of waste in modern organizations. We rarely question them because meetings are considered part of doing business. But ask a simple Lean question: Does this meeting create value, or does it simply consume capacity?

Not every meeting is waste. Collaboration, decision making, problem solving, and alignment can create tremendous value. The problem is the meeting that exists because it has always existed, includes people who don’t need to be there, reviews information everyone could have seen beforehand, and ends without a decision or clear action.

A Lean approach starts by understanding the purpose. What problem are we solving? What decision needs to be made? Who actually needs to participate? What should be completed before the meeting? What should happen afterward?

This is essentially applying standard work to communication.

Try observing your team’s meetings for one week. Look for recurring meetings where the same information is reviewed repeatedly, decisions are postponed, or actions are assigned without clear ownership. Then ask whether the meeting can be shortened, redesigned, combined, replaced with visual management, or eliminated altogether.

Respect for people includes respecting their time.

A 30-minute meeting with ten people consumes five hours of organizational capacity. Make sure you’re getting something valuable in return.

Lean Tip #4115 – Protect the Flow of Attention

We spend a great deal of time talking about material flow in Lean Manufacturing. We discuss batch sizes, bottlenecks, transportation, queues, and interruptions. But there is another flow worth examining: the flow of people’s attention.

Every interruption creates a potential break in that flow. A message arrives. A meeting starts. Someone walks over with a question. A notification appears. Then another urgent request arrives before the original task is complete.

Individually, these interruptions seem harmless. Collectively, they create a significant productivity problem. Employees constantly switch between priorities instead of completing work from start to finish. This is especially costly for engineers, planners, analysts, and other employees performing work that requires concentration.

Lean thinking asks us to identify and reduce unnecessary interruption just as we would reduce unnecessary movement on the factory floor.

That might mean establishing blocks of uninterrupted work time, improving visual management so employees don’t need to constantly ask for status, creating clearer escalation paths, or addressing the root causes behind recurring “urgent” requests.

We often tell people to be more productive. Perhaps we should spend more time designing a system that makes productive work easier.

Don’t just manage people’s time. Design the work so their attention can flow.

Lean Tip #4116 – Too Many Reports, Too Little Insight

How many reports does your organization produce every week? And how many of them actually help someone make a decision?

It is surprisingly easy for reporting to become its own form of waste. A report gets created because someone once asked for it. Then another person adds a metric. A new manager requests a different view. Before long, people are spending hours compiling, formatting, emailing, and reviewing reports that may no longer serve a useful purpose.

The Lean question is simple: What value does this report create?

A report should help someone understand what is happening, identify a problem, make a decision, or take action. If it does none of those things, it deserves to be questioned. Even reports that provide useful information may contain unnecessary detail that makes the important information harder to see.

This is where visual management can make a difference. Instead of creating another 30-page report, ask what information people actually need to manage the process. Put the critical measures where they can be seen, establish clear triggers for action, and eliminate information that doesn’t support the work.

I’ve seen organizations spend more time preparing reports than actually responding to the problems the reports reveal.

Don’t confuse more information with better management. In Lean, the goal isn’t to report everything. It’s to make the important things visible.

Lean Tip #4117 – Re-entering Data Is Pure Waste

A planner enters an order into one system. Someone else copies the information into a spreadsheet. Another person takes that spreadsheet and enters the same information into a different system.

Nothing has been improved. No customer value has been created. Yet people can spend hours every week doing exactly this.

Lean calls this overprocessing, and office environments are particularly good at hiding it. Because the work happens behind a computer screen, it can look productive. Someone is busy. A spreadsheet is being updated. Data is moving. But if the same information is being manually entered multiple times, we’re paying people to move information rather than improve the process.

The first question shouldn’t be, “How can we automate this?” It should be, “Why are we entering this information more than once?”

Maybe the systems don’t communicate. Maybe the process was designed around an old limitation. Maybe nobody trusts the source data. Or perhaps each department created its own version of the process.

Automation can certainly help, but automating a bad process simply makes waste happen faster.

Walk the information flow from beginning to end. Identify where data is created, where it is copied, where it is transformed, and where it is entered again. Then eliminate unnecessary steps before considering technology.

If the same information is being entered twice, that’s not a productivity opportunity. It’s a process problem waiting to be solved.

Lean Tip #4118 – Find the Decision Bottleneck

Sometimes work isn’t waiting on a machine.

It’s waiting on a person.

A production supervisor may be waiting for Engineering to approve a deviation. A buyer may be waiting for Finance to approve a purchase. A project team may be waiting for leadership to decide which option to pursue. Meanwhile, everyone downstream is stuck.

This is a bottleneck, even though it may not look like one on a traditional process map.

Lean teaches us to look at flow. In an office process, that means following information and decisions just as carefully as we would follow material through a factory. When work repeatedly accumulates in front of the same person or function, there is probably a constraint worth investigating.

The solution isn’t necessarily to tell the person to “work faster.” First understand why the decision is concentrated there.

Does that person have information nobody else has? Are approval levels unnecessarily complicated? Are decisions being escalated because people don’t have clear standards? Is there a lack of trust in the process?

Sometimes the best improvement is to move decisions closer to the work.

Give people clear criteria, appropriate authority, and the information they need to make routine decisions without constantly escalating them.

If work is always waiting for the same decision-maker, don’t just manage the queue. Improve the system that created the queue.

Lean Tip #4119 – Context Switching Is a Hidden Waste

“Can you just take a quick look at this?”

Five minutes later, you’re back to your original task—except you’ve lost your train of thought.

Office work has a form of transportation waste that doesn’t require anyone to walk across the building: context switching. Moving between emails, meetings, spreadsheets, instant messages, reports, and projects may feel like multitasking, but every interruption has a cost.

The problem becomes especially serious when the work requires concentration. A quality engineer investigating a recurring defect, a planner resolving a supply problem, or a project manager working through a complex issue needs time to think. Constant interruptions break that flow.

Lean asks us to create flow in our processes. We should apply the same thinking to knowledge work.

That doesn’t mean eliminating collaboration or putting everyone behind closed doors. It means being intentional about how work is organized. Batch similar administrative tasks. Establish times for communication. Protect focused work when it matters. Reduce unnecessary meetings and notifications.

And look at the process itself. If people are constantly interrupted because they are the only person who knows how to answer a question, that’s a capability problem—not simply a time-management problem.

Sometimes productivity isn’t about helping people do more things. It’s about helping them finish the important thing they’re already doing.

Lean Tip #4120 – Office 5S: Organize Information, Not Just Workspaces

Most Lean practitioners understand the visual impact of 5S on a production floor. Tools have a home. Materials are organized. Abnormal conditions are obvious.

But what would 5S look like on your computer?

Think about the shared drive with thousands of files. The Teams channel with documents scattered across conversations. The desktop covered with spreadsheets. The folder containing five versions of the same procedure, each with a slightly different name.

That’s information waste.

The principles of 5S apply surprisingly well to digital work. Sort what is actually needed. Set in order so people can find information without asking around. Shine by removing obsolete and duplicate files. Standardize naming, ownership, and storage conventions. Then sustain the system through simple routines.

The objective isn’t to create a perfectly organized computer. It’s to make the right information easy to find and the wrong information difficult to mistake for the right information.

I’ve watched people spend 20 minutes searching for a document that should have taken 30 seconds to locate. Multiply that by dozens of employees and hundreds of searches, and the hidden waste becomes significant.

5S isn’t about having a neat workspace. It’s about making the workplace support the work. Your digital workplace deserves the same attention.

Lean Tip #4121 – What Daily Management Really Means

Daily management is sometimes reduced to a morning meeting, a production board, and a handful of KPIs.

Those are tools. Daily management is the system that connects them.

A good daily management system helps people understand the current condition of the business, identify abnormalities quickly, respond to problems, and stay focused on what matters most.

Consider a production team that missed yesterday’s schedule. A weak system simply reports the miss. A strong system asks: What happened? What should have happened? What is the gap? What needs to happen today to recover?

The same thinking applies to quality, delivery, customer complaints, supplier issues, repair backlogs, and administrative processes.

The goal isn’t to create more meetings or more reports. It’s to establish a daily rhythm for seeing, responding, and improving.

Daily management isn’t about reporting what happened yesterday. It’s about creating the conditions for better performance today.

Lean Tip #4122 – Make Abnormalities Visible

If everything on your daily management board is green, you may have a great process.

Or you may have a process that isn’t telling you the truth.

One of the fundamental purposes of Lean daily management is to make abnormalities visible. When actual performance differs from the expected condition, people should be able to see the gap quickly—not discover it weeks later in a monthly report.

Suppose the daily production target is 100 units and the team produces 82. Recording “82” captures a number. Showing 82 against a target of 100 creates a reason to ask why.

The same applies to quality, delivery, safety, or customer service. The abnormality should be visible to the people who can do something about it.

There is one important leadership responsibility here: don’t punish people for exposing problems. If red means trouble for the person reporting it, eventually the board will always be green.

Problems can’t be improved until they can be seen.

Lean Tip #4123 – Manage the Process, Not Just the Results

The easiest thing to manage is the result.

The problem is that by the time you see a bad result, the process that created it has already happened.

A production manager sees that yesterday’s output missed target. A quality manager sees defects increase. A service manager sees the backlog grow. The natural reaction is to focus on the number.

Lean management asks a different question: What is happening in the process that is creating this result?

If on-time delivery falls from 96% to 88%, telling the team to “catch up” may not address the problem. The real issue could be material shortages, an engineering change, an approval delay, or another process condition.

The result is the symptom. The process contains the clues.

Outcome measures still matter, but good daily management also looks for the conditions that influence those outcomes.

Don’t wait for the scoreboard to tell you that you’ve lost. Manage the process closely enough to see the problems developing.

Lean Tip #4124 – The Power of a Good Daily Huddle

A daily huddle shouldn’t be a meeting where everyone takes turns reading yesterday’s numbers.

If that’s what yours has become, you may have created a reporting ritual instead of a management system.

A good huddle is short, visual, and focused on abnormalities. The team understands the current condition, identifies what isn’t going as expected, and determines what needs attention.

The meeting doesn’t need to solve every problem. If a critical component is missing, for example, the huddle might simply identify the owner, establish the recovery action, and determine when the issue should be escalated.

I’ve seen daily meetings turn into 45-minute problem-solving sessions. That’s usually a sign that the meeting isn’t designed properly.

The huddle should create alignment and action, not become the place where every problem gets investigated.

If your daily huddle doesn’t change what people do today, ask yourself whether you’re managing the work—or simply talking about it.

Lean Tip #4125 – Metrics Should Drive Action

A metric without a response is just a number.

Yet many organizations have dashboards filled with measures that people review every day without changing what they do because of them.

Lean daily management starts with a better question:

“What action should this metric trigger?”

If first-pass yield drops below standard, who responds? If a customer complaint reaches 30 days, what happens? If the production schedule starts falling behind, when does the team intervene?

These responses should be clear before the problem occurs.

This is also why KPI overload can be dangerous. Twenty or thirty measures may provide plenty of information, but if nobody knows which ones require action, you’ve created a dashboard—not a management system.

A smaller number of meaningful measures, with clear ownership and defined responses, is usually more powerful.

Don’t just ask what you should measure. Ask what you need to manage—and what the measure should cause you to do.