Phase 1: Cut the Clutter

Introduction to Phase 1

Phase 1 is about understanding the Current State of the process and identifying opportunities for improvement. Value Stream Mapping and Process Mapping expose the bottlenecks, delays, and Waste. The goal: a clear, detailed, honest map of the current process that improvement can be built on.

When documenting Phase 1, follow these steps:

1. Go to Gemba: visit the place where the work is done. Observe the process in action and identify potential Waste; this may involve time studies, spaghetti mapping, and other observation tools.
2. Identify the inputs and outputs: list the materials, information, and resources going in, and the products or services coming out (the SIPOC makes this systematic).
3. Map the process: create a flowchart or diagram of the steps and the decisions made along the way.
4. Identify the problems: list the defects, delays, and bottlenecks encountered during the process.

Everything in this phase feeds the phases that follow: you cannot fix a Flow you have not honestly seen.

Going to Gemba

Gemba is a Japanese term meaning "the real place." In Lean, it is the place where Value is added, where the work actually happens. Go there, and you see what reports and meetings can never show you. The key principles:

• Observation: watch what actually happens to understand the work and spot problems or opportunities.
• Asking questions: seek input from the people doing the work to understand their needs, challenges, and ideas.
• Respect for people: listen to concerns, stay open to suggestions, and never treat the visit as an inspection.
• Continuous improvement: Gemba visits are a recurring practice, not a one-time event.

To conduct a visit: identify the purpose (understand a process? find problems? gather ideas?), plan it (who you will meet, what you will observe, what you will ask; get permission for the time and area), go and observe, asking for clarification freely, and debrief afterward with your team to gather feedback and ideas.

One caution the book is emphatic about: at Gemba you are not there to solve problems, change processes, or interrupt the Flow of the work. You are using observation and interviewing judiciously to inform the Current State Map, gap analyses, and Root Cause analyses that come next.

SIPOC

A SIPOC is a high-level process map used to quickly visualize a process and its components: what goes in, what the process does, and what comes out. SIPOC stands for Suppliers, Inputs, Process, Outputs, Customers, the headers of the diagram's five columns. Each process step gets one or more rows identifying all its inputs and outputs.

The book's example is building a website for a client: the client is the Supplier of the Input (product information) that goes into the copywriting Process, which has an Output (refined page copy) for the Customer (the web developer who builds the page).

Pro tip: if the team struggles to start at the Supplier column, jump to the Process column first and list all the process steps in rows (from the Current or Future State Map, depending on how far along you are). Then work outward: find the Inputs and Suppliers to the left, then the Outputs and Customers to the right.

A robust SIPOC has many linked rows, and the Customer at the end of one row often becomes the Supplier of subsequent rows. Beyond defining the process, the SIPOC tells you exactly who should be involved in the improvement effort: the Suppliers and Customers of each Process step.

Takt Time and Cycle Time

Takt Time and Cycle Time are the heartbeat of a process. They are closely related, with a distinction that matters:

Example: a factory operating 8 hours a day that must produce 100 units per day has a Takt Time of 4.8 minutes per unit (8 hours / 100 units). A unit must come off the line every 4.8 minutes to keep pace with demand. If it actually takes 5 minutes to produce a unit, the Cycle Time is 5 minutes, and the factory is falling behind.

The goal of Lean is to minimize Cycle Time and bring it as close as possible to Takt Time: demand met on time, with no wasteful overcapacity.

Takt and Cycle at Starbucks

The book works the numbers with a morning rush at Starbucks:

• Takt Time: the store receives 100 customers per hour. To meet demand, a drink must be produced every 36 seconds (60 minutes / 100 customers).
• Cycle Time: taking the order and charging the customer takes 30 seconds, preparing the drink takes 60, and handing it off takes 30. Total: 120 seconds per drink.

Cycle Time (120s) is far greater than Takt Time (36s), so one barista cannot possibly keep up. The fix is resourcing: four baristas produce four drinks about every two minutes, averaging 30 seconds per drink, which beats the 36-second Takt Time and meets demand.

The comparison works in both directions:

• Cycle Time longer than Takt Time: you are not producing fast enough. Queues grow, waits lengthen, customers leave unhappy.
• Cycle Time much shorter than Takt Time: you are producing faster than necessary, wasting employee time and capacity.

Knowing both numbers turns staffing and process decisions from guesswork into arithmetic.

5S for Success

If your Gemba observations note a lack of 5S and Visual Management, make a separate appointment with the process owner to either conduct a 5S of the area or train the process participants to 5S their own areas.

5S and Visual Management are core to Cut the Clutter, and here is the interesting consequence the book flags: a good 5S may improve the area so much that you need to return and redo your Gemba observations to find the new baseline for the improvement effort.

That is not wasted work. It means the cheapest, fastest tool in the kit already banked an improvement before the formal effort even started, and your maps will now describe the process as it truly runs rather than the clutter that was hiding it.

Map Out the Current State

With Gemba insights in hand, return to the team and build a Current State Map together, reaching consensus from the participants. This is the nitty-gritty map of all permutations of the process. It is your "bad" baseline: do not improve, polish, or minimize any negative details. Document every instance of Waste and waiting, including:

• Bottlenecks, delays, and excessive work in progress
• Lost information and broken communication channels
• Hidden workarounds and wandering branches off the happy path
• Steps that generate complaints (especially customer complaints)
• Cost overruns and lost income
• Inputs and outputs (from the SIPOC)
• Safety concerns

How to run it: the easiest Process Mapping is sticky notes on a wall, whiteboard, or large paper, with everyone holding a sticky pad and pen. Begin with the official Start and Stop: what triggers the process, and what signifies its end? If the process is part of a larger Value Stream, the Start and Stop may connect to other processes; resist the temptation to merge them and keep the scope within the defined process.

Map the happy path (the easiest route) first. Then go back through and document every branch and workaround, official or unofficial, at each step. Get into the minutiae: capturing the down-and-dirty real Current State is what makes it fixable later. Add special stickies or a different ink color for Waste, bottlenecks, waiting, lost information, and dead ends. If unrelated topics come up, park them in a parking lot space to address later.

Attributes and True North Metrics

Your Current State Map should also carry an Attributes table: tangible measurements and intangible findings that describe life in the current process. Real examples from the book: "Satisfaction scores below 60%", "22 minutes to get a soggy sandwich", and "Frustration that feels like bailing neverending bathwater with a slotted spoon while sitting in an overflowing tub."

One way to categorize Attributes is by the True North Metrics of perfection:

• Quality: goal of zero defects
• Cost: goal of 0% Waste, 100% Value
• Speed/Timeliness: goal of 100% on-time, zero delays
• Human Development: 100% engaged and satisfied

"While perfection is unattainable, the pursuit of perfection is the only way to truly achieve excellence."

Attributes in the Current State become the focal point for developing the antithetical Attributes you want in the Future/Target State: "22 minutes to a soggy sandwich" points directly at "5 minutes to a fresh one."

The Value Exercise

Now evaluate every step of the Current State Map for Value. Colored dots or markers work best; most practitioners use Green, Yellow, and Red:

• Green = Value-Added: perfect as it is and where it is. Value-generating from the receiver's perspective; something a customer would pay extra for if it did not exist.
• Yellow = Non-Value-Added But Necessary: the process cannot exist without it (regulation, policy, law), even though it generates no Value for the receiver.
• Red = Non-Value-Added: no Value to the receiver and not required. Customers would not pay for this.

The two keys to doing this exercise honestly:

1. Value is only determined by the receiver, usually a customer of the process. Internal processes have internal customers, who are typically not the people working in the process.
2. Assume every step is Red first. The team must reach consensus to upgrade a step to Yellow (with the regulating documents handy for review) or Green (with agreement that it is what the receiver actually seeks).

In the book's sample exercise, 13 of 19 steps could be improved or eliminated, four were necessary-but-valueless, and only two steps actually contributed Value to the customer. That ratio is typical, and it is why this exercise changes how teams see their own process forever.

Magic in the Ideal State

Before drafting the Future State Map, get the creativity flowing with a little magic. The Ideal State is a version of the process with no constraints at all: immediate Value to the customer in every step, zero Waste, and fulfillment for everyone involved. It is the perfect state. The Disney state. The Star Trek state. Unbridled magic.

Show the team an Ideal State that reads:

Start → ✨ Magic! ✨ → End

It sparks chuckles, and then it sparks big ideas about what that magic would actually look like. Those big ideas matter: they surface possibilities nobody would have volunteered inside "realistic" conversation, and they often inspire practical ideas for the Future State that would never have come up otherwise.

Take the big magic ideas into Future State Mapping, then add the constraints of the real world to scale them down to what is possible.

Go Into the Future (State)

The Future State Map starts with the same Start and End triggers as the Current State, so improvement can be measured like-for-like. Then apply the carry-over rules:

• Carry over Green steps that are working perfectly. If the customer gets all the Value they can from it, keep it, but watch how any reordering affects that Value.
• Carry over Yellow steps governed by a handbook, policy, rule, or law. Changing governing documents is typically out of scope; if one can actually be changed during the effort, add that to the Phase 2 solution list instead.
• Carry over a Red step only if moving it in the process order turns it Green or Yellow, or some other improvement in the process turns it Green or Yellow. Otherwise, Red steps do not survive.

In the book's Future State example, the team reorganized and refined steps to eliminate Waste: the total number of steps decreased, and Non-Value-Added steps were converted to Value-Added for the customer.

Done well, the Future State Map is as close to the Magic State as the constraints of the project and organization allow, ideally reflecting only Green and Yellow steps: the maximum amount of Value getting to the customer.

At the end of Phase 1 you have a clear understanding of the process and the outcomes you hope to achieve. Phase 2 finds the causes of the problems and selects solutions; Phase 3 implements them and locks in the results.

Try It Yourself

Reflect

Think of a process you know well. Where is its Gemba? Who is the true receiver of its Value, and what would they mark Green?

Activity

Pick a small personal process (making breakfast, paying bills, starting your workday). Write its Start and Stop triggers, map the happy path in sticky notes or a list, add the workarounds you actually use, then run the Value Exercise: everything starts Red; upgrade only what earns it. Count your Greens. If the ratio surprises you, you have just experienced Phase 1.