FLOW AT
THE SOURCE
THE SOURCE
Observe, Listen, Improve
A Field Journal
A Field Journal
Press → or click anywhere to begin
Flow at the Source
Observe, Listen, Improve
intentionally blank
intentionally blank
intentionally blank
Flow at the Source
How to Use
How to Use This Journal
One arc. Three months.
One habit at the center.
One habit at the center.
This journal is a designed learning system — not a collection of tools arranged in a reasonable order, but a sequence in which each section builds on the one before it. The observational skills of Sections 1 and 2 make the mapping work of Sections 3 and 4 possible. The mapping makes the daily practice of Section 5 meaningful. Appendix B explains why the sequence works; this page explains how to use it.
Phase 1 · §1–2
Learning
to See
to See
30 gemba visits
10 closed loops
Trust through presence
10 closed loops
Trust through presence
Phase 2 · §3–4
Learning
to Map
to Map
One value stream
Your product mix
Data you collected yourself
Your product mix
Data you collected yourself
Phase 3 · §5
Learning
to Lead
to Lead
90 days of practice
Rotating KPI focus
The habit in the routine
Rotating KPI focus
The habit in the routine
§1
Why Observe First
The case for going to the source — read before the habit pages begin.
§2
Habit Pages — 30 Days
The Respect Ladder and 3-Visit Loop. 10 loops. 30 gemba visits.
§3
Value Stream Picture
Build your current-state map one visit at a time.
§4
PQPR Questionnaire
Not all products are equal. Find out which ones demand the most.
§5
3-Month Daily Planner
The habit stays alive in the daily routine. 90 days.
This journal works for anyone
A line supervisor three months into their first role and a plant manager with twenty years of experience use the same journal. So do process engineers, quality leads, and CI coaches — independently, without needing a team leader as a sponsor. Appendix B explains how concurrent use across different roles produces something richer than individual observation.
Appendix A: Operator Observation Register · Appendix B: How This Journal Works
v
One
Section One
WHY
OBSERVE
FIRST
OBSERVE
FIRST
The case for going to the source — before you have an answer, before you have a solution, before you even have a question ready.
In This Section
1
The Day Nobody Saw It Coming
A quality escape. Four days of silence. One operator who tried to tell someone.
2
What Silence Costs
Why operators stop reporting — and what it costs the organization.
3
The Oldest Management Idea in Manufacturing
Ohno's chalk circle. NUMMI. Going to the place.
4
Respect as a Competitive Advantage
The operator knows more than anyone. Listening is a data-access strategy.
5
What Happens When You Just Listen
A two-year rework problem solved in an afternoon by a question never asked before.
6
The Habit You're About to Build
The Respect Ladder and the 3-Visit Loop — previewed.
7
Notes & References
Six annotated citations for readers who want to go deeper.
§1 · Story
Flow at the Source
Chapter 1 · Story
The Day Nobody
Saw It Coming
Saw It Coming
The call came on a Thursday afternoon. A Tier-1 automotive supplier — one that had shipped to the same customer for eleven years without a single line stoppage — was being told that parts were failing in final assembly. Fourteen assemblies rejected. Line down. A premium freight charge that would cost more than the entire month's margin on that part number.
The quality manager drove straight to the floor. She walked to the press cell that had produced the affected run, found the operator who had been running it, and asked him what he knew.
He knew a great deal. He knew the die had been throwing a slight burr since the previous Tuesday. He knew because he had been deburring every third piece by hand, adding roughly four seconds to his cycle time, and logging it nowhere. He had mentioned it to his shift lead on Wednesday morning. The shift lead had said he'd look into it. Nobody came. The run shipped Thursday at noon, two hours before the call arrived.
· · ·
This is not a story about a bad operator, a negligent shift lead, or a failed quality system. Every person in this chain was doing what they had been taught to do. The operator adapted. The shift lead intended to follow up. The quality manager trusted her processes.
It is a story about what happens when the people closest to a problem have learned — through experience — that raising it will not change anything. And so they adapt around it, quietly, until adaptation is no longer enough.
“The defect wasn't new. The silence was.”
1
Flow at the Source
Ch.1
After the line stoppage, the quality manager asked the operator why he hadn't escalated further — gone above the shift lead, called the quality line, flagged someone. He looked at her with the patience of someone who has had this conversation before.
“I did what I was supposed to do. Nobody came.”
She had no answer for that. Because he was right.
The real question — the one this journal is built around — is not how to prevent the next burr. It is how to build an environment where the operator doesn't have to decide whether it's worth raising. Where going to see the problem is so habitual, so expected, so normal, that the person at the press never spends a second calculating whether anyone will listen.
That environment is built one visit at a time. It is built by leaders who show up before there is a crisis, who watch before they speak, and who ask before they answer. It is not built by systems or software or corrective action reports. It is built by people who have chosen, deliberately, to make observation a practice rather than a reaction.
The pattern
The operator who stops telling you things is not apathetic. He has simply run the experiment enough times to know the result. He raised the issue. Nothing changed. By the third occurrence, he adapted without raising it at all. By the fourth, he had forgotten that raising it was even an option. This is a rational response to a broken feedback loop.
That is what you are holding in your hands.
2
§1 · Evidence
Flow at the Source
Chapter 2 · Evidence
What Silence Costs
In 1999, a Harvard professor named Amy Edmondson published a study that would eventually reshape how the world thought about high-performing teams. She had set out to study medical errors in hospitals, expecting to find that the best teams made the fewest mistakes. What she found was the opposite: the highest-performing teams reported more errors, not fewer.
This was not because they were worse. It was because they felt safe enough to say so.
Research Finding
Teams with high psychological safety — where members believed they would not be punished or humiliated for speaking up — showed significantly higher rates of error reporting, learning behavior, and ultimately, better outcomes. Teams where silence was the norm made just as many errors. They simply never talked about them.
Edmondson, A.C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.
The manufacturing floor is not a hospital. But the human equation is identical. When people believe that raising a problem will result in blame, indifference, or — worst of all — more work without more support, they stop raising problems. They adapt. They work around. They absorb the cost of a broken process into their bodies and their routines, invisibly, until the cost becomes impossible to absorb.
“70% of employees in manufacturing environments report awareness of a problem before it became a formal quality event — but did not escalate it. The most common reason: they didn't believe it would be acted on.”
3
Flow at the Source
Ch.2
This is the real cost of a culture that only responds to crises. It is not the cost of the crisis itself — though that is real enough. It is the cost of everything that was known before the crisis, that went unreported, that built quietly toward the moment of failure.
The operator who stops telling you things is not apathetic. He has simply run the experiment enough times to know the result. He raised the issue. Nothing changed. He raised it again. Still nothing. On the third occurrence, he adapted without raising it at all. By the fourth, he had forgotten that raising it was even an option.
This is a rational response to a broken feedback loop. And the only way to repair it is not with a new reporting system or a suggestion box or a corrective action process. Those things address the symptom. The repair happens when a leader shows up in person, watches the work, asks a genuine question, and then — critically — does something visible with the answer.
“The operator who stops reporting is not apathetic — they have simply learned that reporting doesn't help.”
Amy Edmondson — paraphrased from Psychological Safety research
What changes the equation
Visible action, promptly taken, on a problem that the operator raised. Not a thank-you. Not a promise to look into it. Visible action. That is the signal that repairs the feedback loop. One response, delivered fast enough that the operator connects it to their report, is worth more than twelve town halls about open-door policies.
4
§1 · History
Flow at the Source
Chapter 3 · History
The Oldest Management
Idea in Manufacturing
Idea in Manufacturing
In the 1950s, Taiichi Ohno — the Toyota production engineer who would become synonymous with the lean manufacturing movement — had a practice he used with new engineers. He would draw a chalk circle on the floor of the factory, place the engineer inside it, and tell them to stand there and watch.
Not to take notes. Not to look for problems. Just to watch. For hours. Sometimes for an entire shift.
The engineers who went through this ritual described it as transformative and uncomfortable in equal measure. What they were seeing, Ohno believed, was not accessible any other way. Reports could not convey it. Briefings could not convey it. Walking through quickly could not convey it. Only sustained, deliberate, unhurried attention to what was actually happening — in real time, in the place where work happened — could produce the kind of understanding that led to genuine improvement.
This practice — genchi genbutsu, which translates roughly as “go and see for yourself” — became one of the foundational principles of the Toyota Production System. It was not a tool or a technique. It was a discipline. A commitment to never forming a conclusion about a process without first going to observe that process directly.
“Data is of course important in manufacturing, but I place greatest emphasis on facts.”
Taiichi Ohno
5
Flow at the Source
Ch.3
The NUMMI plant — the joint venture between Toyota and General Motors in Fremont, California, that became one of the most studied manufacturing transformations in history — demonstrated what happened when this discipline was applied at scale. A plant that had been the worst-performing GM facility in the country, plagued by absenteeism, quality failures, and adversarial labor relations, became one of the best-performing plants in North America within two years.
Not because of new equipment. Not because of new systems. Because of a different relationship between leaders and the floor — one in which observation was the primary leadership act, and the knowledge of the people doing the work was treated as the primary source of operational intelligence.
The discipline, not the tool
Genchi genbutsu is not a scheduled floor walk. It is not a safety audit or a gemba walk with a clipboard. It is the discipline of forming no conclusion about a process without first going to observe that process directly, with your own eyes, without an agenda. The Respect Ladder in this journal is the structured form of that discipline. The habit pages are where you build it.
You are about to build the oldest management idea in manufacturing. It has survived for seventy years because it works. It works because the floor always knows more than the office. The only question is whether the office is willing to go find out.
Shook, J. (2010). How to Change a Culture: Lessons from NUMMI. MIT Sloan Management Review, 51(2), 63–68.
6
§1 · Evidence
Flow at the Source
Chapter 4 · Evidence
Respect as a
Competitive Advantage
Competitive Advantage
The operator at the press knows something you do not know. This is not a philosophical position. It is a practical fact. She has run that machine for three years. She knows what it sounds like when the hydraulic pressure is slightly low. She knows which cavity of the die wears faster. She knows which jobs arrive with incomplete specifications and which ones arrive correctly. She knows which information on the router is inaccurate and which she can rely on. She has never been asked.
This is not unusual. In most manufacturing facilities, the formal knowledge management system — standard work documents, training records, process specifications — captures a fraction of the operational knowledge that actually drives performance. The rest lives in the minds and habits of the people doing the work, accumulated through years of repetition and problem-solving, and invisible to anyone who hasn't taken the time to ask.
Research Finding
A Cochrane systematic review of 140 randomized controlled trials found that structured observation combined with timely, specific feedback consistently improves professional practice and quality outcomes across settings. The effect was strongest when feedback was delivered promptly and included a clear path to action.
Ivers, N.M. et al. (2012). Cochrane Database of Systematic Reviews, (6), CD000259.
7
Flow at the Source
Ch.4
Respect, in this context, is not a soft concept. It is a data-access strategy. When a leader visits the floor and asks a genuine question — not a leading question, not a trap, not a performance management exercise, but a question to which they genuinely do not know the answer — they open a channel to the most accurate source of operational intelligence available.
“The most important question isn't Why did this happen? It's When did the system first begin drifting away from stable operation?”
Edgar Schein — Humble Inquiry
This is what Edgar Schein meant when he wrote about humble inquiry: the discipline of asking questions to which you genuinely do not know the answer, and listening to understand rather than to respond. It is, Schein argued, one of the rarest and most valuable skills in organizational life — not because it requires unusual intelligence, but because it requires the suppression of the instinct to demonstrate expertise.
The Respect Ladder in this journal is built on this evidence. Each rung is a behavior that, practiced consistently, signals to the operator that her knowledge is valued — not as a management exercise, but as the primary input to problem-solving.
Schein, E.H. (2013). Humble Inquiry: The Gentle Art of Asking Instead of Telling. Berrett-Koehler Publishers.
8
§1 · Story
Flow at the Source
Chapter 5 · Story
What Happens When
You Just Listen
You Just Listen
The weld liner problem had been going on for two years. Every six to eight weeks, a batch of components would arrive at final assembly with a weld liner seated incorrectly — not enough to fail inspection, but enough to cause fitment issues downstream, generate rework at the customer's facility, and consume engineering time in root-cause investigations that invariably concluded with "operator error" and a retraining event that changed nothing.
The retraining happened four times over two years. Each time, the problem recurred within six to eight weeks.
On the fifth occurrence, a new operations manager arrived. She did not order a retraining event. She walked to the station where the liner was seated, stood beside the operator who ran it, watched three complete cycles without speaking, and then asked a single question:
“What makes a good one different from a bad one, when you're running them?”
The operator looked at her for a moment — the look of someone deciding whether this question was a test. Then she answered.
The fixture had a worn locating pin that had been worn for at least eighteen months. Every experienced operator had learned to compensate for it by feel — a slight counter-rotation on the liner before seating that corrected for the pin's drift. They had never documented it because it had never felt like a finding. It had felt like doing the job correctly.
9
Flow at the Source
Ch.5
New operators — or experienced operators returning from leave, or operators cross-trained from other stations — didn't know about the counter-rotation. They ran the liner as specified. And six to eight weeks after any significant staffing change at that station, the problem would resurface.
The fixture pin was replaced that afternoon. Maintenance record: forty-five minutes. Total cost: the price of one locating pin and an hour of a maintenance technician's time.
Two years. Four retraining events. Thousands of dollars in downstream rework and customer relationship cost. One afternoon's conversation.
· · ·
The knowledge of the correct technique had existed for eighteen months — in the hands and habits of experienced operators who had learned to work around a broken fixture without being asked whether the fixture was broken. The question had never been asked because the frame of the investigation had always been "what did the operator do wrong" rather than "what does the operator know that we don't."
The single most important shift
From "what did the operator do wrong" to "what does the operator know that we don't." That reframe, applied consistently, is the foundation of everything this journal is asking you to practice.
10
§1 · The Practice
Flow at the Source
Chapter 6 · The Practice
The Habit You're
About to Build
About to Build
The pages that follow are not a workbook. They are not a checklist, an audit tool, or a documentation system. They are a practice structure — a scaffold for building a habit that, once built, no longer requires the structure.
The Respect Ladder has five rungs. Each rung is a behavior, not a mindset. You do not need to believe in it before you practice it. Practice it first. The understanding arrives through the doing.
1
I went to the place
2
I watched before I spoke
3
I asked, not told
4
I listened until they were done
5
We agreed on one next step
The 3-Visit Loop — Visits A, B, and C — mirrors the structure of a problem-solving conversation extended over time. Visit A surfaces the problem. Visit B deepens the root cause. Visit C confirms whether the countermeasure held. Together, they produce the most valuable thing in operational improvement: a closed loop.
You will complete ten loops in thirty days. Not all of them will reach Visit C. Some will surface problems you don't have the authority to fix. Some will reveal that the problem is more complex than the first visit suggested. That is correct. That is what learning looks like.
11
Flow at the Source
Ch.6
The habit pages begin on the next spread. Before you turn the page, write three things in the space below: the name of the first person you will visit, the station or workcell where you will find them, and the date and time of your first visit.
This is not a goal. It is an appointment. The difference matters. Goals can drift. Appointments have a name and a time attached to them. The research on habit formation consistently shows that implementation intentions — the specific "when, where, and how" of a planned behavior — dramatically increase follow-through compared to intentions stated without those specifics.
Your first commitment
Write the name, the station, and the time before you close this page. Not because the writing itself changes anything — but because the leader who has written it is statistically more likely to show up than the one who hasn't.
Name of the first person you will visit
Station or workcell
Date and time of your first visit
Habit pages begin on the next spread.
12
§1 · References
Flow at the Source
Chapter 7 · Notes & References
For Readers Who
Want to Go Deeper
Want to Go Deeper
Edmondson, A.C. (1999)
Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383. The foundational study on psychological safety; demonstrates that high-performing teams report more problems, not fewer.
Ivers, N.M. et al. (2012)
Audit and feedback: effects on professional practice and healthcare outcomes. Cochrane Database of Systematic Reviews, (6), CD000259. 140 randomized trials; structured observation with feedback reliably improves outcomes.
Ohno, T. (1988)
Toyota Production System: Beyond Large-Scale Production. Productivity Press. The primary source on genchi genbutsu and the chalk circle practice.
13
Flow at the Source
Ch.7
Schein, E.H. (2013)
Humble Inquiry: The Gentle Art of Asking Instead of Telling. Berrett-Koehler. The behavioral case for genuine inquiry as a leadership discipline.
Shook, J. (2010)
How to Change a Culture: Lessons from NUMMI. MIT Sloan Management Review, 51(2), 63–68. The NUMMI transformation as a case study in observation-led culture change.
Womack, J.P. & Jones, D.T. (1996)
Lean Thinking: Banish Waste and Create Wealth in Your Corporation. Simon & Schuster. Systematizes the Toyota principles for a Western manufacturing audience.
A note on sources
The research cited in Section 1 spans three disciplines: organizational psychology (Edmondson, Schein), clinical evidence synthesis (Cochrane), and operational practice (Ohno, Womack, Shook). The convergence across these fields — the same findings emerging from hospitals, factories, and organizational studies — is itself evidence that the human dynamics of speaking up and listening are not industry-specific. They are human-specific.
14
Days
Section Two · 30 Days
FLOW AT
THE SOURCE
THE SOURCE
The Respect Ladder practiced 30 times. The 3-Visit Loop completed 10 times. Problems surfaced, owned, and resolved.
The Core Loop — repeated 10 times
A
Observe & Surface
Go to the place. Watch. Ask one question. Listen. Agree on one action.
→
Action happens
The agreed step is attempted — by the operator, the leader, or together.
B
Check & Deepen
Return as promised. Did it move? What root cause does the team agree on?
→
Countermeasure tested
The root cause is addressed — within authority or escalated with context.
C
Confirm & Close
Return again. Did it hold? What changed in the KPI? Standard updated?
10 loops · 30 gemba visits · 30 days
§2 · Habit Pages
Flow at the Source
Flow at the Source
Loop 1 · Day __ of 30
Where I Am Going
Workcell / Step
Shift / Time
Operator / Lead
Who depends on this step
This Visit Connects To
Safety
Quality
Delivery
Cost
People
What “Good” Looks Like Here
The Respect Ladder — check each rung before leaving
1
I went to the place
2
I watched before I spoke
3
I asked, not told
4
I listened until they were done
5
We agreed on one next step
See & Listen→Learn the Truth→Co-create
1
Flow at the Source
Loop 1
The Loop — 3 Visits
same process · same people · growing trust
A
Observe & Surface
Date: ___________
A3:
Current
State
Current
State
Operator's words — in their own language
Upstream cause they suspect
Downstream impact they feel
Agreed action · Owner · By when
↓ action happens — then return ↓
B
Check & Deepen
Date: ___________
A3:
Root
Cause
Root
Cause
Operator's words — in their own language
Did the action happen? What changed?
New question raised
Countermeasure to test · Owner · By when
↓ countermeasure tested — then return ↓
C
Confirm & Close
Date: ___________
A3:
Confirm
+Std
Confirm
+Std
Operator's words — in their own language
KPI movement (before → after)
What we learned · shared?
Standard updated / next loop / escalation needed
© Palo Seco PublishingLoop 1 of 10
2
§2 · Habit Pages
Flow at the Source
Flow at the Source
Loop 2 · Day __ of 30
Where I Am Going
Workcell / Step
Shift / Time
Operator / Lead
Who depends on this step
This Visit Connects To
Safety
Quality
Delivery
Cost
People
What “Good” Looks Like Here
The Respect Ladder — check each rung before leaving
1
I went to the place
2
I watched before I spoke
3
I asked, not told
4
I listened until they were done
5
We agreed on one next step
See & Listen→Learn the Truth→Co-create
3
Flow at the Source
Loop 2
The Loop — 3 Visits
same process · same people · growing trust
A
Observe & Surface
Date: ___________
A3:
Current
State
Current
State
Operator's words — in their own language
Upstream cause they suspect
Downstream impact they feel
Agreed action · Owner · By when
↓ action happens — then return ↓
B
Check & Deepen
Date: ___________
A3:
Root
Cause
Root
Cause
Operator's words — in their own language
Did the action happen? What changed?
New question raised
Countermeasure to test · Owner · By when
↓ countermeasure tested — then return ↓
C
Confirm & Close
Date: ___________
A3:
Confirm
+Std
Confirm
+Std
Operator's words — in their own language
KPI movement (before → after)
What we learned · shared?
Standard updated / next loop / escalation needed
© Palo Seco PublishingLoop 2 of 10
4
§2 · Habit Pages
Flow at the Source
Flow at the Source
Loop 3 · Day __ of 30
Where I Am Going
Workcell / Step
Shift / Time
Operator / Lead
Who depends on this step
This Visit Connects To
Safety
Quality
Delivery
Cost
People
What “Good” Looks Like Here
The Respect Ladder — check each rung before leaving
1
I went to the place
2
I watched before I spoke
3
I asked, not told
4
I listened until they were done
5
We agreed on one next step
See & Listen→Learn the Truth→Co-create
5
Flow at the Source
Loop 3
The Loop — 3 Visits
same process · same people · growing trust
A
Observe & Surface
Date: ___________
A3:
Current
State
Current
State
Operator's words — in their own language
Upstream cause they suspect
Downstream impact they feel
Agreed action · Owner · By when
↓ action happens — then return ↓
B
Check & Deepen
Date: ___________
A3:
Root
Cause
Root
Cause
Operator's words — in their own language
Did the action happen? What changed?
New question raised
Countermeasure to test · Owner · By when
↓ countermeasure tested — then return ↓
C
Confirm & Close
Date: ___________
A3:
Confirm
+Std
Confirm
+Std
Operator's words — in their own language
KPI movement (before → after)
What we learned · shared?
Standard updated / next loop / escalation needed
© Palo Seco PublishingLoop 3 of 10
6
Midpoint · Loop 5 of 10
Halfway
There.
There.
Five loops in. The habit is forming. The operators have seen you return. The pattern is beginning to matter.
Flow at the Source
Mid-Point
Mid-Point Reflection
Before loops 6–10
Which loop produced the most unexpected finding?
Which operator have you learned the most from?
What pattern have you noticed across multiple loops?
One thing to do differently in loops 6–10
The trust signal
By loop 5, some operators will begin bringing problems to you without waiting for a visit. That is not a coincidence. It is evidence that the habit is working. When an operator seeks you out, the feedback loop is repaired.
8
§2 · Habit Pages
Flow at the Source
Flow at the Source
Loop 6 · Day __ of 30
Where I Am Going
Workcell / Step
Shift / Time
Operator / Lead
Who depends on this step
This Visit Connects To
Safety
Quality
Delivery
Cost
People
What “Good” Looks Like Here
The Respect Ladder — check each rung before leaving
1
I went to the place
2
I watched before I spoke
3
I asked, not told
4
I listened until they were done
5
We agreed on one next step
See & Listen→Learn the Truth→Co-create
9
Flow at the Source
Loop 6
The Loop — 3 Visits
same process · same people · growing trust
A
Observe & Surface
Date: ___________
A3:
Current
State
Current
State
Operator's words — in their own language
Upstream cause they suspect
Downstream impact they feel
Agreed action · Owner · By when
↓ action happens — then return ↓
B
Check & Deepen
Date: ___________
A3:
Root
Cause
Root
Cause
Operator's words — in their own language
Did the action happen? What changed?
New question raised
Countermeasure to test · Owner · By when
↓ countermeasure tested — then return ↓
C
Confirm & Close
Date: ___________
A3:
Confirm
+Std
Confirm
+Std
Operator's words — in their own language
KPI movement (before → after)
What we learned · shared?
Standard updated / next loop / escalation needed
© Palo Seco PublishingLoop 6 of 10
10
§2 · Habit Pages
Flow at the Source
Flow at the Source
Loop 7 · Day __ of 30
Where I Am Going
Workcell / Step
Shift / Time
Operator / Lead
Who depends on this step
This Visit Connects To
Safety
Quality
Delivery
Cost
People
What “Good” Looks Like Here
The Respect Ladder — check each rung before leaving
1
I went to the place
2
I watched before I spoke
3
I asked, not told
4
I listened until they were done
5
We agreed on one next step
See & Listen→Learn the Truth→Co-create
11
Flow at the Source
Loop 7
The Loop — 3 Visits
same process · same people · growing trust
A
Observe & Surface
Date: ___________
A3:
Current
State
Current
State
Operator's words — in their own language
Upstream cause they suspect
Downstream impact they feel
Agreed action · Owner · By when
↓ action happens — then return ↓
B
Check & Deepen
Date: ___________
A3:
Root
Cause
Root
Cause
Operator's words — in their own language
Did the action happen? What changed?
New question raised
Countermeasure to test · Owner · By when
↓ countermeasure tested — then return ↓
C
Confirm & Close
Date: ___________
A3:
Confirm
+Std
Confirm
+Std
Operator's words — in their own language
KPI movement (before → after)
What we learned · shared?
Standard updated / next loop / escalation needed
© Palo Seco PublishingLoop 7 of 10
12
§2 · Habit Pages
Flow at the Source
Flow at the Source
Loop 8 · Day __ of 30
Where I Am Going
Workcell / Step
Shift / Time
Operator / Lead
Who depends on this step
This Visit Connects To
Safety
Quality
Delivery
Cost
People
What “Good” Looks Like Here
The Respect Ladder — check each rung before leaving
1
I went to the place
2
I watched before I spoke
3
I asked, not told
4
I listened until they were done
5
We agreed on one next step
See & Listen→Learn the Truth→Co-create
13
Flow at the Source
Loop 8
The Loop — 3 Visits
same process · same people · growing trust
A
Observe & Surface
Date: ___________
A3:
Current
State
Current
State
Operator's words — in their own language
Upstream cause they suspect
Downstream impact they feel
Agreed action · Owner · By when
↓ action happens — then return ↓
B
Check & Deepen
Date: ___________
A3:
Root
Cause
Root
Cause
Operator's words — in their own language
Did the action happen? What changed?
New question raised
Countermeasure to test · Owner · By when
↓ countermeasure tested — then return ↓
C
Confirm & Close
Date: ___________
A3:
Confirm
+Std
Confirm
+Std
Operator's words — in their own language
KPI movement (before → after)
What we learned · shared?
Standard updated / next loop / escalation needed
© Palo Seco PublishingLoop 8 of 10
14
§2 · Habit Pages
Flow at the Source
Flow at the Source
Loop 9 · Day __ of 30
Where I Am Going
Workcell / Step
Shift / Time
Operator / Lead
Who depends on this step
This Visit Connects To
Safety
Quality
Delivery
Cost
People
What “Good” Looks Like Here
The Respect Ladder — check each rung before leaving
1
I went to the place
2
I watched before I spoke
3
I asked, not told
4
I listened until they were done
5
We agreed on one next step
See & Listen→Learn the Truth→Co-create
15
Flow at the Source
Loop 9
The Loop — 3 Visits
same process · same people · growing trust
A
Observe & Surface
Date: ___________
A3:
Current
State
Current
State
Operator's words — in their own language
Upstream cause they suspect
Downstream impact they feel
Agreed action · Owner · By when
↓ action happens — then return ↓
B
Check & Deepen
Date: ___________
A3:
Root
Cause
Root
Cause
Operator's words — in their own language
Did the action happen? What changed?
New question raised
Countermeasure to test · Owner · By when
↓ countermeasure tested — then return ↓
C
Confirm & Close
Date: ___________
A3:
Confirm
+Std
Confirm
+Std
Operator's words — in their own language
KPI movement (before → after)
What we learned · shared?
Standard updated / next loop / escalation needed
© Palo Seco PublishingLoop 9 of 10
16
§2 · Habit Pages
Flow at the Source
Flow at the Source
Loop 10 · Day __ of 30
Where I Am Going
Workcell / Step
Shift / Time
Operator / Lead
Who depends on this step
This Visit Connects To
Safety
Quality
Delivery
Cost
People
What “Good” Looks Like Here
The Respect Ladder — check each rung before leaving
1
I went to the place
2
I watched before I spoke
3
I asked, not told
4
I listened until they were done
5
We agreed on one next step
See & Listen→Learn the Truth→Co-create
17
Flow at the Source
Loop 10
The Loop — 3 Visits
same process · same people · growing trust
A
Observe & Surface
Date: ___________
A3:
Current
State
Current
State
Operator's words — in their own language
Upstream cause they suspect
Downstream impact they feel
Agreed action · Owner · By when
↓ action happens — then return ↓
B
Check & Deepen
Date: ___________
A3:
Root
Cause
Root
Cause
Operator's words — in their own language
Did the action happen? What changed?
New question raised
Countermeasure to test · Owner · By when
↓ countermeasure tested — then return ↓
C
Confirm & Close
Date: ___________
A3:
Confirm
+Std
Confirm
+Std
Operator's words — in their own language
KPI movement (before → after)
What we learned · shared?
Standard updated / next loop / escalation needed
© Palo Seco PublishingLoop 10 of 10
18
Three
Section Three
BUILDING
YOUR
VALUE STREAM
PICTURE
YOUR
VALUE STREAM
PICTURE
Parts and information flows as they actually happen. Built incrementally, from direct observation, by the person closest to the work.
intentionally blank
§3 · Value Stream
Flow at the Source
What You Are Looking At
One product.
One plant. Door to door.
One plant. Door to door.
This map shows five process steps, two suppliers, one customer, and the complete picture of how parts and information move between them. Everything on this page is observable. None of it requires a computer, a system report, or a management briefing. It requires going to the place, watching what happens, asking the people doing the work, and recording what you find honestly.
“The main intention is going through the process of trying to understand the dock-to-dock flow — not having a perfectly drawn current state map.”
Lean Enterprise Institute · Learning to See
The number in the bottom right of the map — 11.4% value-added ratio — means that of every 100 hours this product spends in the facility, fewer than 12 hours involve actual transformation. The other 89 hours are waiting. This is not unusual. The map is how you find it.
Observation before vocabulary
The symbols are a shared language for things you have already learned to see. You learn to see first. The pages that follow zoom into each element one at a time — not to teach the symbol, but to teach you what to look for on the floor before you draw anything.
1
Flow at the Source
Reading the Map
Elements of the Map
A
Factory / Supplier
Stepped-roof silhouette. Supplier at left, customer at right. Same icon — different relationship.
B
Production Control
Rounded double-border rectangle. Top center of map. Where the plan is made and distributed.
C
Information Arrows
Zigzag = electronic (ERP, EDI). Straight = manual (paper, verbal). Draw what operators actually follow.
E
WIP Inventory Triangle
Filled gold. Piece count above. Wait time below. Timestamp every count.
F
Process Box
One step. C/T, %C&A, FPY, Availability. Four numbers. Built across multiple visits.
G
Push Arrow
Solid filled arrowhead. Upstream decides when to send. The most honest arrow in most factories.
H
NVA / VA Timeline
Upper tier: NVA waiting hours. Lower tier: VA cycle hours. The ratio between them is the story.
The process box — a full spread ahead
The process box is the most information-dense element. Each of its four fields requires a different visit and a different conversation. It gets its own spread before the observation stages begin.
2
§3 · Process Box
Flow at the Source
Magnifying Glass · Element F
The Process Box —
Four Fields, Four
Conversations
Four Fields, Four
Conversations
The process box is the most information-dense element in the map. Each field requires a different observation method and a different conversation with the person doing the work. Filling it correctly is not a paperwork exercise. It is a series of gemba visits compressed into one rectangle.
C/T — Cycle Time
Stopwatch. 3–5 consecutive cycles. Note the range, not just the average. A range of 3.1 to 4.8 hours is more informative than “average 3.9 hours.” What causes the variation?
%C&A — Incoming Complete & Accurate
The field nobody tracks. Ask: “What percentage of the time can you start immediately when work arrives?” Listen for hesitation. A long pause often means the number is low and the operator has adapted to it.
Quality Yield — FPY
Ask the operator first. Count the scrap bin. Verify on a second shift. If no tracking exists, write “unknown” — that is itself a finding, and often a bigger one than any number would be.
Availability
Ask: “What stops you most often, and for how long?” Breakdown, changeover, waiting for material, waiting for information — each is a different problem with a different fix.
3
Flow at the Source
Magnifying Glass
Observation Prompts · Process Box
Process
Main Assembly
C/T
%C&A
FPY
Avail
1
Time 3–5 complete cycles with a stopwatch.
Start when the operator picks up the part. Stop when they set it down ready for the next. Record each cycle separately.
2
Ask: “What percentage of the time can you start immediately when work arrives?”
This is %C&A. Listen for hesitation. A long pause often means the number is low and they have adapted to it.
3
Ask: “Out of ten pieces, how many pass the first time without rework?”
Operator estimate is your starting point. Then count the scrap bin. “Unknown” is itself a finding.
4
Ask: “What stops you most often, and for how long?”
Breakdown / changeover / waiting for material / waiting for information — each is a different problem with a different fix.
Step / Location / Date
Cycle time — visits 1, 2, 3 + range
Operator's words — what stops them / what they wish were different
4
§3 · Stage 1
Flow at the Source
Stage 1 of 4 — First Visit
Walk the Path
with Fresh Eyes
with Fresh Eyes
Before you measure anything — walk the physical path of one product, from shipping back to receiving. On foot. This journal and a pencil. No laptop, no tablet.
Jim Womack · LEI
Begin at the door-to-door level. Start at shipping and walk upstream so you are always asking: where did this come from? One product family. One plant.
Product family I am mapping
Steps in order — raw material to shipping
Step name (floor language)
WIP waiting (pcs · time observed)
5
Flow at the Source
Stages 2–4
Stages 2–4 Overview
Name · Measure · Draw
2
Name What You See
Information flow symbols. What triggers each step. What operators actually follow vs. what ERP says should happen.
3
Measure What Matters
Cycle time (stopwatch), WIP counts (timestamped), FPY (operator + scrap bin), %C&A at each step.
4
Draw What You Found
Transfer to the VSM template. With the team who does the work. The corrections they make are more valuable than the original drawing.
Field observation · tbr ChangeWorks LLC
In every VSM project, the most important moment was when an operator looked at the map and said: “I didn't know that's what happened to it after it left us.” That sentence — which appears in almost every mapping session — marks the transition from isolated process ownership to systemic thinking. No presentation produces it as reliably as a map built by the people doing the work.
6
§3 · Value Stream
Flow at the Source
Stage 4 — Transfer Your Observations
Your Value Stream
Picture — Current State
Picture — Current State
In pencil. With someone who does the work. Blanks are expected — note what you need to observe next to fill them.
Product Family
Takt Time
Date · Drawn by
Production Control
Production Control
ERP / MRP / schedule
ERP / MRP / schedule
Material Flow
Supplier
___
Step
C/T
%C&A
FPY
Avail
___
Step
C/T
%C&A
FPY
Avail
___
Customer
Hand-draw additional steps as needed
7
Flow at the Source
VSM Template
Timeline & Three Key Calculations
___ h NVA
___ h NVA
___ h NVA
___ h VA
___ h VA
___ h VA
Three Numbers That Tell the Story
VA% = VA ÷ Lead Time × 100
What fraction of the journey adds value?
Lead Time = Σ(C/T + Queue)
Total journey time for one product
RTY = FPY&sub1; × FPY&sub2; × ···
True first-time quality across all steps
Total VA Time
Total NVA Time
Total Lead Time
VA Ratio (%)
Rolled Throughput Yield (FPY&sub1; × FPY&sub2; × ···)
The drift warning
This map will begin to go stale the moment you finish drawing it. Each gemba visit is a chance to notice where reality has moved and update the picture. A map updated quarterly is a living document. A map filed after completion is a historical record.
8
Appendix A · Operator Observation Register
YOUR
WORLD,
SEEN
CLEARLY.
WORLD,
SEEN
CLEARLY.
A register for the person doing the work — not a reporting form, not an evaluation, but a tool for making your knowledge visible before the leader arrives.
Flow at the Source
Operator Register
Why This Register Exists
You already know more
about this process than
any map can show.
about this process than
any map can show.
The leader using the other sections of this journal is learning to observe. You are already there. You live in this process every shift. You know what it sounds like when the machine is about to go down.
This register is not a place to report problems so management can evaluate performance. It is a place to make your knowledge visible — to yourself first, and then to the leader who comes to ask.
The democratic design principle
The leader and the operator use the same journal. When both sit together with what they have recorded, the conversation that results is different in kind from a management walk-around. It is a genuine exchange between people who have both been paying attention.
9
Operator Register
Flow at the Source
My Step
What Arrives at My Step
What came in today — and was it ready?
Was anything missing, wrong, or unclear when work arrived?
Out of 10 jobs that arrived, how many could I start immediately?
What information or material was missing most often?
What I Do at My Step
How long did a typical job take today?
Estimate from start to finish — your hands on the work.
Was today faster or slower than usual? Why?
What did I have to do that felt like extra work — not part of the job itself?
Looking for missing parts, redoing setup, waiting for clarification.
What Leaves My Step
Out of everything I completed today, how many passed the first time?
___ passed · ___ needed rework · ___ scrapped
If something needed rework — what was the most common reason?
What does the next step need from me that I sometimes cannot give them?
What Stopped Me Today
Did anything stop my work today?
○ Machine ○ Waiting for material ○ Waiting for information ○ Quality issue ○ Other
How long was I stopped, in total?
Has this happened before? How often?
○ First time ○ Sometimes ○ Every shift ○ Every week
Signal to My Leader — What I Want Them to Know from Today
Most important thing I observed
What I've already tried to fix
What I need someone else to handle
10
Flow at the Source
Running Log
Running Observation Log
My step: _____________ · Week of: _____________
| Date | Shift | What I observed | What I did | Escalate? |
|---|---|---|---|---|
End of week — one thing I want my leader to understand about my step
11
Four
Section Four
NOT ALL
PRODUCTS
ARE EQUAL.
PRODUCTS
ARE EQUAL.
And your systems almost certainly treat them as if they were. This is the most expensive assumption in manufacturing — and the easiest one to test.
intentionally blank
§4 · Story
Flow at the Source
Chapter 1 · Story
The Room That Went Quiet
The leadership team had gathered in Salt Lake City — a medical equipment refurbishment operation, a facility that had been running for years, a team that knew their business. They were there for a kaizen preparation session, and the facilitator had asked a simple question before any maps were drawn.
“How many distinct product configurations do you currently run through this facility?”
There was a pause. Someone said forty-two. Someone else said closer to sixty. A third person mentioned the legacy units — technically a different product line but running through the same stations. By the time the conversation settled, the number was somewhere between eighty and a hundred and ten, depending on how you defined a configuration.
Nobody had known. Not because they were careless — because nobody had ever been asked to count them under a lean lens. The ERP system had the data. It had always had the data. But nobody had ever run the query.
· · ·
A similar scene had played out in Springdale, Ohio. An electrical equipment manufacturer — motor control centers, switchgear, industrial control panels. A facility that took genuine pride in its ability to build anything a customer needed. The pride was warranted. The product mix was extraordinary. And it was killing them.
1
Flow at the Source
Ch.1
Not in any single, visible way. There was no dramatic failure. There was simply a constant state of managed chaos: expedites that consumed the schedule every week, training gaps on low-volume configurations, capital equipment sized for the top runners that created bottlenecks for everything else.
When the leadership team drew a simple matrix — product families across the top, process steps down the side — the room went quiet. The matrix revealed something nobody's mental model had contained: the three highest-revenue product families touched only six of the fourteen process steps. The four lowest-revenue families touched eleven steps each, in different sequences, with different tooling requirements, and always with the highest rework rates.
“The cash cows were subsidizing the complexity. And the complexity was consuming the cash cows.”
Field observation · tbr ChangeWorks LLC · Springdale, OH
Nobody had designed this situation. It had accumulated, one product addition at a time, over years of saying yes to complexity without ever asking what that complexity cost the operation as a whole — or who was paying for it.
2
§4 · Evidence
Flow at the Source
Chapter 2 · Evidence
The Most Expensive
Assumption in
Manufacturing
Assumption in
Manufacturing
Batch production thinking makes a foundational assumption: that all products in the facility are essentially similar in their demands on the system. Scheduling treats them as equivalent units. Training treats them as interchangeable skills. Capital investment treats them as sharing the same bottleneck.
This assumption is almost never true. And the larger and more diverse the product mix, the more expensive the assumption becomes.
What the research shows
In high-mix manufacturing environments, the top 20% of product configurations by volume typically account for 60–80% of revenue but only 30–40% of operational complexity. The bottom 20% generate 40–60% of scheduling exceptions, expedites, rework events, and training demands. The ratio is almost always a surprise when calculated for the first time. It is almost never a surprise to the people on the floor.
Field synthesis · tbr ChangeWorks LLC · consistent across motor controls, switchgear, medical equipment, aeroderivative power generation, and industrial circuit protection programs.
3
Flow at the Source
Ch.2
The mechanism works like this. When a facility adds a new product configuration, the systems designed around existing products do not expand. They absorb. The scheduling system absorbs the new product into existing lead time assumptions. The training system absorbs it into the existing skills matrix. And the people on the floor absorb whatever the systems do not catch — through improvisation, tribal knowledge, and the quiet accumulation of workarounds that never appear on any official process map.
The subsidy mechanism
The cash cows do not merely coexist with the high-complexity, low-volume configurations. They subsidize them. Every time a scheduling exception diverts a key operator from a top-runner line, the top runner absorbs the cost. The subsidy is invisible in the P&L because it never appears as a line item. It appears as missed delivery targets, quality escapes, and overtime — attributed to the schedule, never to the product mix that made the schedule impossible to execute as written.
There is a second, less visible dimension: the customer side. In markets where customers design products that suppliers build, the customer often knows the producer's complexity cost structure better than the producer's own scheduling team. A sophisticated purchasing organization can extract pricing concessions on your Runners while directing your most complex, least-well-priced configurations to you by default, because no one else will take them at the price the customer wants to pay.
“Product proliferation is an adaptation. Product rationalization is a decision. Most organizations are very good at the first and rarely make the second.”
4
§4 · Framework
Flow at the Source
Chapter 3 · Framework
Runners, Repeaters,
and Strangers
and Strangers
Before you draw the routing matrix, you need a shared vocabulary for a conversation that most leadership teams have never had: which products the facility was actually designed to build, which ones it builds regularly but not always well, and which ones it encounters as if for the first time, every time.
Runners
The facility was built for these.
High volume, high frequency. Process is well-understood. Standards exist and are current. Most operators can build them. Lead times are predictable. These are your cash cows — and your baseline for what good looks like when the system is working as designed.
Repeaters
The facility can build these — usually.
Moderate volume, irregular frequency. Process is understood by some operators but not all. Standards may exist but may not be current. These are where tribal knowledge lives — and where it disappears when the wrong person is absent.
Strangers
The facility encounters these as a surprise every time.
Low volume, infrequent or irregular. Process is held in the memory of one or two people, or reconstructed from scratch each time. Standards are absent or irrelevant. Lead times are promises, not commitments. Sources of your most damaging expedites.
5
Flow at the Source
Ch.3
Observation Prompts — RRS Sort
1
List your top 10 product configurations by revenue. Which three generate 80% of your output?
These are almost certainly your Runners — but verify. A product can generate 80% of revenue while consuming only 30% of your scheduling attention. Or the reverse.
2
Which products generated the most expedites in the last 90 days?
In most facilities: they are not on the top-10 revenue list. The gap between the expedite list and the revenue list is the invisible cost.
3
For each product: how many operators per shift can build it reliably without supervision?
A product only two people can build is a Stranger regardless of volume. Write the number. It will surprise you.
4
Which products cause the operator to stop and look something up, ask someone, or improvise?
Ask operators directly — not supervisors. Supervisors often underestimate this because the improvisation is invisible to them.
Quick RRS Sort
Runners
Repeaters
Strangers
What surprised you about this sort?
6
§4 · The Core Tool
Flow at the Source
Chapter 4 · The Core Tool
The Routing Matrix
A grid with product families across the top and process steps down the side, and a mark in each cell where that family passes through that step. What makes it powerful is what it reveals when you look at the whole picture at once.
Patterns emerge that no dashboard surfaces: which steps are touched by almost every product family (your true bottlenecks), which products follow wildly different sequences (structural sources of scheduling complexity), and which families share almost no steps at all (candidates for separate value streams).
The ERP paradox
Everything needed to build this matrix is already in your ERP system — updated with every order. The analysis is not technically difficult. It is organizationally neglected because nobody has been asked to look at it under a lean lens. In every facility we have worked with, the routing matrix built from observed reality and the ERP data disagreed in ways that were immediately actionable.
7
Flow at the Source
Routing Matrix
Example Matrix — How to Read It
Read horizontally: one product's journey. Read vertically: which steps carry the most load.
| Product family | Step 1 | Step 2 | Step 3 | Step 4 | Step 5 | Step 6 | Step 7 | Step 8 | Steps |
|---|---|---|---|---|---|---|---|---|---|
| Standard Config A High vol · Runner | ✓ | ✓ | — | ✓ | ✓ | ✓ | — | — | 6 |
| Standard Config B High vol · Runner | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | — | — | 7 |
| Mid-range Config C Med vol · Repeater | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | — | 7 |
| Custom Config D Low vol · Repeater | ✓ | ✓ | ✓ | ✓✓ | ✓✓ | ✓ | ✓ | R | 9+R |
| Legacy Config E Very low · Stranger | ✓ | — | ✓ | ✓✓ | ✓✓ | ✓ | ✓ | R | 9+R |
| Special Config F Sporadic · Stranger | ✓ | ✓ | ✓ | ✓✓ | ✓✓ | ✓ | ✓ | R | 10+R |
| Step load | 6 | 5 | 5 | 6★ | 6★ | 6 | 5 | 4R |
✓ Standard✓✓ Extended timeR = Rework loop— Not required★ = Bottleneck
8
§4 · Your PQPR
Flow at the Source
Chapter 6 · Your PQPR
Building Your Own
Routing Picture
Routing Picture
The pages below are yours to fill. They do not require a formal data pull from ERP — though that data should be used to verify what you record here. The PQPR is not a one-time exercise. The product mix changes with every new order. A PQPR built once and filed is a historical document, not a planning tool.
Step 1 — Name your product families
Products (floor names)
Volume · RRS class
Step 2 — Name your process steps
Steps 1–5
Steps 6–10
9
Flow at the Source
Routing Matrix
Step 3 — Draw the Routing Matrix
| Product | Step 1 | Step 2 | Step 3 | Step 4 | Step 5 | Step 6 | Step 7 | Step 8 | Total |
|---|---|---|---|---|---|---|---|---|---|
| Step load |
✓ Standard✓✓ ExtendedR = Rework— Not required
Step 4 — What the Matrix Tells You
Steps touched by every product — my true bottleneck(s)
Product with highest step count — my most complex Stranger
The product family I would map in detail first — and why
10
Months
Section Five · 3 Months
THE HABIT
IN THE
ROUTINE
IN THE
ROUTINE
90 days. Rotating KPI focus. The gemba habit stays alive, the metrics stay visible, and the leader stays connected to the floor.
Rotating KPI Focus — Weekly Cycle
Monday
Quality / FPY
What moved quality today? What held it back?
Tuesday
Delivery / OTD
Did we ship what we promised? What got in the way?
Wednesday
Cost / Waste
Where did time and material disappear today?
Thursday
Safety
What condition did I see today that I need to address?
Friday
People / Engage
Who needs support? Who showed initiative? Who was quiet?
Why rotation matters
Leaders who track only what they measure tend to improve only what they track. The rotating focus ensures that safety, people, and cost receive the same deliberate attention as quality and delivery — every week, for 90 days.
§5 · Daily Planner
Flow at the Source
Month 1 of 3
Month 1 Overview
Su
Mo
Tu
We
Th
Fr
Sa
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Monthly priority / improvement focus
Top 3 KPI targets this month
Gemba visit commitment — frequency / locations
Month 1 intention
By the end of this month, the gemba visit should no longer require a decision. It should be what you do.
1
Flow at the Source
Month 1
End of Month 1 Review
What changed?
What held?
What surprised you?
What held?
What surprised you?
How many gemba visits this month? (target: 12+)
Which operator taught me the most this month?
Which KPI moved most — and what caused it?
Which loop or conversation from this month will I reference next month?
One thing I want to do differently next month
The signal at each month-end
Month 1: Operators are starting to expect your visits. Month 2: Operators are bringing problems to you without waiting. Month 3: Other leaders are asking what you're doing differently.
2
intentionally blank
§5 · Daily Planner
Flow at the Source
Days 8–90
85 additional daily pages
follow the same format.
follow the same format.
KPI rotates Mon–Fri each week.
Motive changes daily (12-motive cycle).
Month 2 and Month 3 overviews included.
Motive changes daily (12-motive cycle).
Month 2 and Month 3 overviews included.
8
intentionally blank
§5 · Daily Planner
Flow at the Source
Month 2 of 3
Month 2 Overview
Su
Mo
Tu
We
Th
Fr
Sa
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Monthly priority / improvement focus
Top 3 KPI targets this month
Gemba visit commitment — frequency / locations
Month 2 intention
The gemba habit is established. Now deepen it: focus this month on a process family from your PQPR that you have not yet observed closely.
9
Flow at the Source
Month 2
End of Month 2 Review
What changed?
What held?
What surprised you?
What held?
What surprised you?
How many gemba visits this month? (target: 12+)
Which operator taught me the most this month?
Which KPI moved most — and what caused it?
Which loop or conversation from this month will I reference next month?
One thing I want to do differently next month
The signal at each month-end
Month 1: Operators are starting to expect your visits. Month 2: Operators are bringing problems to you without waiting. Month 3: Other leaders are asking what you're doing differently.
10
§5 · Daily Planner
Flow at the Source
Month 3 of 3
Month 3 Overview
Su
Mo
Tu
We
Th
Fr
Sa
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Monthly priority / improvement focus
Top 3 KPI targets this month
Gemba visit commitment — frequency / locations
Month 3 intention
By day 90, the habit is not a practice — it is an identity. This month: share what you have learned with someone who has not yet started.
11
Flow at the Source
Month 3
End of Month 3 Review
What changed?
What held?
What surprised you?
What held?
What surprised you?
How many gemba visits this month? (target: 12+)
Which operator taught me the most this month?
Which KPI moved most — and what caused it?
Which loop or conversation from this month will I reference next month?
One thing I want to do differently next month
The signal at each month-end
Month 1: Operators are starting to expect your visits. Month 2: Operators are bringing problems to you without waiting. Month 3: Other leaders are asking what you're doing differently.
12
B
Appendix B
HOW THIS
JOURNAL
WORKS
JOURNAL
WORKS
A designed learning system — built for the floor, usable by anyone, and structured so that repetition builds the habits that reports and training courses cannot.
Appendix B
Flow at the Source
How This Journal Works
Why this appendix exists
For the curious reader,
the institutional buyer,
and the engineer who
wants to know why.
the institutional buyer,
and the engineer who
wants to know why.
Most people will never read this section. They will open Section 1, find the story about the quality escape, and keep going. That is exactly what this journal is designed for. You do not need to understand how the learning system works in order to benefit from it.
But if you are a process engineer wondering whether this applies to you without a team leader involved — it does. If you are in learning and development and want to know whether the sequencing is defensible — it is. If you are a line supervisor who has completed a loop and wants to understand why it felt different from a training course — this page explains it.
And if you are simply curious why five sections arranged in this particular order produce a different outcome than five sections arranged in any other order — this is that explanation.
One orienting fact
The skills in this journal are introduced in the order they must be practiced. Observation comes before mapping. Mapping comes before strategic analysis. Daily practice comes after all three — not as a review, but as the mechanism that keeps the earlier skills alive. This is not arbitrary. It reflects how operational habits actually form in people who have to use them under pressure, on a shift, in real conditions.
B2
Appendix B
Flow at the Source
The Learning Arc
Why this sequence, in this order
Learning to See.
Learning to Map.
Learning to Lead.
Learning to Map.
Learning to Lead.
The three phases of this journal correspond to three genuinely different levels of operational skill. They are not arbitrary divisions of content. Each phase requires the one before it.
You cannot map what you have not learned to see. A value stream map drawn without the observational foundation of Sections 1 and 2 is a diagram — an arrangement of symbols that reflects official process documentation rather than what actually happens. The map is only as good as the observations that feed it.
You cannot lead from data you have not collected yourself. The daily planner in Section 5 is not a generic planning tool. It is a structure that keeps the skills of the first four sections present in the decisions you make every day. Without those skills, it is a notebook with good questions. With them, it is a feedback loop.
Phase 1 · §1–2
Learning
to See
to See
Going to the source before forming a conclusion
Listening before offering solutions
Detecting gaps from standard through direct observation
Closing loops — returning as promised
Earning trust through repeated presence
Phase 2 · §3–4
Learning
to Map
to Map
Following one product's journey door to door
Capturing time, quality, and flow data from observation
Building a shared picture of how work actually happens
Seeing where value is added vs. where time disappears
Differentiating products by demand, risk, and resource needs
Phase 3 · §5
Learning
to Lead
to Lead
Anchoring operational rhythm to observed reality
Rotating KPI focus across all five dimensions
Connecting daily decisions to the value stream picture
Sustaining the gemba habit as a permanent practice
Becoming the model that others want to follow
B3
Appendix B
Flow at the Source
The Learning Arc
What changes at each phase
The skills compound.
The confidence follows.
The confidence follows.
At the end of Phase 1 — roughly thirty days of structured gemba visits — the leader has built a kind of credibility with the floor that no announcement, town hall, or open-door policy produces. Operators have seen them return. They have watched problems get addressed. A few have begun bringing problems forward without being asked. This is the signal that Phase 1 has worked.
At the end of Phase 2 — the value stream picture and the PQPR analysis — the leader has something more durable than credibility: they have data they collected themselves, from the floor, from the people doing the work. The VA ratio they calculated is more persuasive in a budget conversation than any consultant's slide because they can describe exactly where every hour came from. The routing matrix they drew is more accurate than the ERP system's version because they walked the actual path.
Phase 3 does not add new skills. It preserves the skills built in Phases 1 and 2 against the most powerful force in operational leadership: the urgent displacing the important, every single day, indefinitely. The daily planner is a structure designed specifically to resist that displacement. Every day it asks whether a gemba visit happened. Every week it rotates the KPI focus. Every month it asks what the leader learned and what they want to do differently. These are not motivational prompts. They are the minimum viable feedback loop for a skill that will atrophy without it.
By day 90, the habit is not a practice. It is an identity. Other leaders observe it. Operators expect it. The organization begins to calibrate around it.
This is the only durable form of operational culture change. Not the workshop. Not the initiative. Not the poster. The habit, practiced enough times by enough people at enough levels, until it becomes what leadership looks like here.
B4
Appendix B
Flow at the Source
Who Can Use It
No hierarchy required
The journal works
for any person in
any role — at the
same time.
for any person in
any role — at the
same time.
Most operational learning systems are cascaded: the manager learns first, then teaches the team. This one is not. A frontline leader, a process engineer, a quality technician, and a shift supervisor can all be in Section 2 simultaneously — each building the same observational habits, each practicing the Respect Ladder in their own context, each accumulating the same repetitions.
The leader is not a prerequisite for the engineer. The engineer is not a prerequisite for the team member. The hierarchy of the org chart does not determine the sequence of the learning. What it determines is the vantage point — and that difference is exactly what makes concurrent use valuable.
The combined picture
A frontline leader doing a gemba visit, a process engineer timing cycle times at the same step, and an operator filling in the observation register at the end of their shift — these three records, compared side by side, produce a picture of that process that no individual observation can generate. Each person sees what their position allows them to see. The journal makes all three visible in the same format.
This is not a coincidence of design. The operator register (Appendix A), the habit loop right-hand page, and the process box observation prompts in Section 3 are all structured around the same four questions: what arrived, what happened, what left, and what got in the way. Different language, different fields, same underlying inquiry. Any three people using any combination of these pages are asking the same questions from different positions in the same system.
B5
Appendix B
Flow at the Source
Who Can Use It
What each role brings and builds
CEO · Plant Manager
VP Operations
VP Operations
Models the behavior that cascades without being mandated
Uses the VSM section to see their system holistically, not through reports
PQPR section informs capital, technology, and resource decisions with observed data
Daily planner anchors operational rhythm in direct observation
Becomes visible to the floor in a way that changes what people bring forward
Frontline Leader
Shift Lead · Supervisor
Shift Lead · Supervisor
Primary user — closest to where change actually happens
Respect Ladder gives structure to conversations they already have
VSM section builds a picture of their process that no one else has drawn
Operator register creates a genuine feedback loop with their team
By loop 10, operators bring problems rather than waiting to be asked
Process Engineer
CI Coach · Quality
CI Coach · Quality
Uses journal independently — no team leader required as sponsor
VSM section accelerates pre-kaizen data gathering with a consistent format
PQPR section structures product family selection for improvement prioritization
Same journal shared with operators democratizes the observation work
Process box data collected across multiple visits produces richer baseline than a single event
On educational background
This journal was written so that the language of lean manufacturing is never a prerequisite. Every technical term is introduced in context, defined in plain language, and practiced before it is named. A person who has never heard of a value stream map can complete Section 3 and produce a useful current-state picture. The concepts arrive through the work, not through the vocabulary.
The same applies to formal education. A line supervisor with twenty years of experience and a shift lead three months into their first leadership role are not using different versions of this journal. They are using the same one — and the observations the newer leader brings are often more unfiltered and more useful than those of someone who has learned to interpret the floor through management's explanatory frameworks.
B6
Appendix B
Flow at the Source
Why Repetition Works
What the 139 repetitions are for
A habit is not a decision
you make every day.
It is a decision you
stopped having to make.
you make every day.
It is a decision you
stopped having to make.
The research on habit formation — across occupational psychology, behavioral science, and clinical practice — consistently locates the consolidation threshold somewhere between 60 and 90 days of consistent practice. Below that threshold, a new behavior requires deliberate effort and is vulnerable to displacement by competing demands. Above it, the behavior becomes automatic: it runs without conscious initiation, it persists under stress, and it feels effortful to suppress.
This journal spans exactly that window. Section 2 covers 30 days of structured gemba visits. Section 5 covers 90 days of daily practice. Together, they provide the repetition density that research associates with lasting behavioral change — not because 90 is a magic number, but because it is enough time to have the habit disrupted by reality, recovered, disrupted again, and recovered again. That recovery cycle is where the habit actually forms.
The 139 built-in repetitions across the journal are not an accident of content. They are the minimum viable dose for a skill that has to survive a missed day, a bad week, a staffing change, and a quarter-end crunch — and still be present on the other side.
B7
Appendix B
Flow at the Source
Why Repetition Works
Why this is different from a training course
The course ends.
The journal doesn't.
The journal doesn't.
A training course delivers content once, in a controlled environment, to a group of people who have been removed from the conditions in which they will need to apply it. The content may be excellent. The instruction may be skillful. But the course ends — and re-entry into operational reality immediately begins displacing what was learned, because the course did not build a structure that survives re-entry.
This journal is structured differently. The content is not delivered once. It is encountered repeatedly, in the conditions where it is needed, with a structure that requires application rather than comprehension. You do not pass Section 2 by understanding the Respect Ladder. You pass it by climbing it — thirty times, in thirty different conversations, with thirty different people who know whether you actually listened or just waited for them to stop talking.
The operating room insight
Atul Gawande's work on checklists in surgery found that experienced surgeons resisted using them — not because they were incompetent, but because they believed their expertise made structured prompts unnecessary. The research found the opposite: checklists improved outcomes precisely because they exerted the most value at the moments when experienced practitioners were most likely to skip steps under pressure. The Respect Ladder is that kind of structure. It is not for beginners. It is for people under operational pressure who need a structure that holds even when the temptation is to skip to the answer.
The daily planner in Section 5 is also not a reminder system. It is a commitment device — a structure that makes the cost of skipping the gemba visit visible every single day, in the form of an empty checkbox, rather than invisible in the form of a forgotten intention. The difference between a leader who builds this habit and one who doesn't is almost never motivation. It is almost always structure.
The skills in this journal were not designed to be learned. They were designed to be practiced until they no longer feel like skills.
B8
Appendix B
Flow at the Source
For L&D Readers
For learning & development professionals
The design logic,
in your language.
in your language.
This journal follows an ADDIE-informed design logic — Analyze, Design, Develop, Implement, Evaluate — the instructional design framework widely used in corporate, military, and organizational learning contexts. The table below maps the journal's five sections to the five phases, not to claim a rigid methodology, but to make the structural decisions legible to practitioners whose work depends on that vocabulary.
| Phase | Journal section | What it does in this journal |
|---|---|---|
| Analyze | §1 — Why Observe First | Establishes the gap: the distance between what leaders currently do (form conclusions from reports, manage by walking past) and what produces reliable improvement (go to the source, listen before speaking). Creates the motivation to change. |
| Design | §2 — Habit Pages | Structures the practice into a repeatable loop: pre-visit contract, 5-rung behavioral ladder, 3-visit arc, documented outcomes. The design provides the scaffold for a skill that cannot be transferred by explanation alone. |
| Develop | §3–4 — VSM & PQPR | Builds on the observational foundation to produce genuinely new capability: reading a value stream, calculating lead time and VA ratio, differentiating products by process demand. Skills that require the Phase 1 foundation to be useful. |
| Implement | §5 — Daily Planner | Deploys the skills into operational routine. The 90-day structure provides the implementation scaffold: KPI rotation, gemba checkbox, reflection prompt. Makes application a daily default rather than an occasional intention. |
| Evaluate | Monthly reflections & loop closures | Built into every section: Visit C of the 3-visit loop, the mid-point reflection at loop 5, end-of-month reviews in the daily planner. Evaluation is embedded in the practice, not appended to it. The learner generates the evidence. |
Two things distinguish this design from a standard ADDIE application. First, the evaluation phase is not external — the journal does not wait for a trainer to assess performance. The learner assesses their own performance through the loop closure structure and the monthly reflection prompts. Second, the implementation phase (Section 5) is not the end of the learning. It is where the earlier learning is preserved and deepened. The daily planner is a maintenance system for skills that atrophy without practice.
B9
Appendix B
Flow at the Source
For L&D Readers
For institutional and cohort use
What changes when
a team uses it together.
a team uses it together.
When an individual uses this journal, they build a habit. When a team uses it concurrently — a plant manager and two shift leads, or a CI coach and three process engineers — something additional happens: the observations compound.
The frontline leader sees what their authority makes visible — what happens when they arrive, what people bring forward, what the operator says when a manager is present. The process engineer sees what their technical lens makes visible — cycle time variation, process step sequence, the gap between standard work and what operators actually do. The operator sees what proximity makes visible — what arrives, what stops the work, what the next step will need that they sometimes cannot provide.
None of these observers has the full picture. Together, using the same journal at the same time, they produce a triangulated view of the same process that no individual observation method generates. This is the institutional case for cohort use — not efficiency, but epistemic richness.
For facilitators and trainers
The journal requires no facilitator to function. But it benefits from one in a cohort setting. The facilitator's role is not to teach the content — it is already in the journal — but to create the conditions for shared observation: scheduling joint gemba visits, convening the monthly reflection as a group conversation, and helping participants connect what they saw from different vantage points. Two hours a month, consistently, is enough. The journal does the rest.
For organizations using this journal as part of a formal learning program, the monthly reflection spreads in Section 5 serve as the evaluation data. A facilitator reviewing twelve end-of-month reflections from a cohort has a rich qualitative dataset about skill development, organizational barriers, and the specific conditions that help or hinder the gemba habit. No separate assessment instrument is required.
For licensing, cohort pricing, and facilitator guide inquiries: tbrchangeworks.com
B10
Appendix C · A3 Problem Solving
ONE PAGE.
ONE PROBLEM.
THE WHOLE
STORY.
ONE PROBLEM.
THE WHOLE
STORY.
The A3 is a discipline, not a form. It forces the problem-solver to think through a complete problem on a single page — from current condition to confirmed resolution. The 3-Visit Loop in this journal is an A3 in practice.
Flow at the Source
What is an A3?
What is an A3?
A complete problem-solving
conversation on one page.
conversation on one page.
The A3 report gets its name from the paper size — A3, roughly 11×17 inches — on which Toyota engineers traditionally summarized a complete problem-solving process. The constraint of a single page is the point. It forces clarity: you cannot put everything on one page, so you must decide what matters.
An A3 is structured in two halves. The left side captures the problem: background, current condition, goal, and root cause analysis. The right side captures the response: countermeasures, implementation plan, and follow-up. The document is read left to right, as a narrative. The story it tells is: here is what we found, here is what we did, here is whether it worked.
The connection to this journal
The 3-Visit Loop in Section 2 mirrors the A3 structure exactly. Visit A = left side (current condition, background, root cause). Visit B = transition (countermeasures decided and tested). Visit C = right side (confirmed results, standard updated). A leader who completes 10 loops has done the intellectual work of 10 A3s — without being required to know the name.
You do not need to use the A3 format to benefit from A3 thinking. The thinking is the discipline of holding a problem in structured sequence — understanding before acting, confirming before closing — and that discipline is already embedded in the habit pages you have been practicing.
C2
Appendix C · A3
Flow at the Source
The A3 Structure
Left Side — Understanding the Problem
Background & Context
Why this problem matters. What process, what product, what customer impact.
Current Condition
What is actually happening, observed directly. Data and visual. Not hearsay.
Goal / Target Condition
What good looks like. Specific, measurable, time-bound.
Root Cause Analysis
The chain from symptom to cause. 5 Whys, fishbone, or direct observation evidence.
Right Side — Acting and Confirming
Countermeasures
The specific actions taken to address the root cause. Owner. Due date.
Implementation Plan
Who does what, by when. Not more than 3–5 actions.
Follow-Up & Confirmation
Evidence that the countermeasure held. Before/after data. Standard updated?
C3
Flow at the Source
Structure
The 3-Visit Loop as A3 Practice
How the 3-Visit Loop maps to the A3
Visit A
Observe & Surface
Left side of A3: background, current condition, root cause hypothesis
Visit B
Check & Deepen
Transition: root cause confirmed, countermeasures decided and tested
Visit C
Confirm & Close
Right side of A3: confirmed results, standard updated, loop closed
The A3 is valuable not because of the form, but because of the thinking discipline it enforces. That discipline — understand before acting, confirm before closing — is already embedded in every habit loop you have completed in Section 2.
If you want to formalize your A3 practice — for escalation, for institutional documentation, or for cross-functional problem-solving — the blank template below provides the standard structure. But the most important A3 skill is already in your hands: the practice of closing the loop.
A note on A3 ownership
An A3 is written by the person closest to the problem — not by a manager summarizing what they were told. The operator who identified the issue in Visit A is often the most qualified person to co-author the A3 that documents its resolution. This is not an accident of the method. It is the point.
C4
Appendix C · A3
Flow at the Source
A3 Write-In — Left Side
Problem title
Date · Owner · Loop ref
1 · Background & Context
2 · Current Condition — what you observed directly
3 · Goal / Target Condition
4 · Root Cause Analysis (5 Whys or direct evidence)
C5
Flow at the Source
A3 Template
A3 Write-In — Right Side
5 · Countermeasures
6 · Implementation Plan — who / what / by when
7 · Follow-Up & Confirmation — did the countermeasure hold?
Loop connector
KPI before
KPI after
Standard updated / new loop required
C6
Appendix D · 4C Problem Solving
CONCERN.
CAUSE.
COUNTERMEASURE.
CONFIRM.
CAUSE.
COUNTERMEASURE.
CONFIRM.
A structured approach to problem resolution that can be completed in a single conversation at the source. Faster than A3. More rigorous than informal discussion. Built for the frontline leader and operator working together.
Flow at the Source
What is 4C?
What is the 4C Method?
Four questions. One
conversation. One page.
conversation. One page.
The 4C method — Concern, Cause, Countermeasure, Confirm — is a structured problem-solving approach designed for frontline use. It is faster than an A3 and more disciplined than informal discussion. It asks four questions in sequence, in the place where the problem is happening, with the people who know it best.
The 4C is not a substitute for deeper analysis. Problems that recur, affect multiple processes, or require cross-functional action belong on an A3. But many of the problems surfaced in a gemba visit can be resolved — fully, durably — through a well-executed 4C conversation at the source.
The difference between 4C and A3
The A3 is a document. The 4C is a conversation that may or may not produce a document. An A3 typically requires multiple sessions, multiple stakeholders, and formal sign-off. A 4C can be completed in one visit if the cause is clear and the countermeasure is within the team's authority. Use 4C for speed. Use A3 for depth and escalation.
The 4C maps directly to the 3-Visit Loop in this journal. Visit A is the Concern and initial Cause hypothesis. Visit B is the Countermeasure, tested. Visit C is the Confirm. The 4C gives the loop a vocabulary. The loop gives the 4C a practice structure.
The 4C method is widely used in automotive, aerospace, and industrial manufacturing environments as a rapid problem-resolution tool. It requires no training beyond this page.
D2
Appendix D · 4C
Flow at the Source
The Four Cs — Structure
C
C1 · Concern
What is the problem — precisely?
Describe the gap from standard. Not the cause — the symptom, in observable terms. Where, when, how often, how bad. The operator's words are the starting point.
What did you observe? What should be happening instead?
C
C2 · Cause
Why is it happening?
Direct cause first: what physical condition produces this symptom? Then root cause: why does that condition exist? The 5 Whys is a useful structure. The operator's hypothesis is the most valuable input.
Direct cause / Root cause (5 Whys if needed):
C
C3 · Countermeasure
What will address the root cause?
The action that removes the cause — not the action that contains the symptom. Containment is sometimes necessary; it is not a countermeasure. Owner, action, and due date for each.
Countermeasure / Owner / By when:
C
C4 · Confirm
Did it work?
Return after the countermeasure has been implemented. Observe the same condition that produced the Concern. Is the gap closed? Is the standard restored? If not — the Cause was incomplete. Return to C2.
Evidence that the countermeasure held / KPI before and after:
D3
Flow at the Source
4C Template
4C Write-In — Your Problem
Problem / station / date
Loop reference · Visit
C
C1 · Concern
Describe the gap from standard in observable terms. Operator's words first.
C
C2 · Cause
Direct cause → Root cause. Ask Why until you reach something actionable.
C
C3 · Countermeasure
Action that removes the root cause. Owner. Due date.
C
C4 · Confirm
Return after implementation. Did the gap close? KPI before → after.
4C and the 3-Visit Loop
C1+C2 = Visit A (Observe & Surface). C3 = Visit B (Check & Deepen). C4 = Visit C (Confirm & Close). When you complete a 4C, you have completed a loop. The names are different. The discipline is the same.
D4
← → keys to navigate · click left / right halves · F = fullscreen
1 / 53