Sergio D'Amico, CSSBB

Stop looking for safety in manuals.
Start looking at the lines under your feet.

Simple lines can save lives.

But most people walk past them.

Let’s fix that.

Here’s how color lines keep your floor safe:

🟡 Yellow = Walk here
Use it for paths and lanes.

🟢 Green = It’s good to go
Keep your finished goods here.

🔵 Blue = Start of the line
Raw materials wait in this box.

🟠 Orange = Check it first
This stuff needs an inspection.

🔴 Red = This is not okay
Scrap, defects, and danger zones.

⚫ Black = Still in the works
This is work in progress.

⚪ White = Gear goes here
Put tools or carts inside the white box.

⚫⚪ Black-White = Let them through
Used for places people need to reach.

⚫🟡 Black-Yellow = Warning zone
Stay out unless you're meant to be there.

🔴⚪ Red-White = Emergency space
Keep this spot clear for safety equipment.

One line can stop one injury.

Imagine what ten can do.

***

🔖 Save this post for later.
♻️ Share to help others use color codes the right way.
➕ Follow Sergio D’Amico for more on continuous improvement.

P.S. Want fewer accidents at work?
Start by looking at the floor.

The House That Toyota Built
Built for People, Not Just Cars.

What if your company learned from Toyota’s “House”?

Two pillars.
One goal.

Zero waste.
Endless improvement.

Toyota’s secret starts with people.
Their thinking shapes the system.

The TPS House is a simple model.
But the lesson is powerful.

Every part supports the other.
Every part serves the customer.

At the roof is the goal:

→ Highest quality
→ Lowest cost
→ Shortest lead time
→ Customer first

This is why the system exists.

Better quality.
Faster flow.
Less waste.

At the center are two pillars:

→ Jidoka
→ Just-in-Time

Jidoka means stop problems right away.

→ Build quality at every step
→ Make problems visible
→ Fix the cause, not just the defect

Just-in-Time means make only what is needed.

→ Right part
→ Right amount
→ Right time
→ Less waste

At the base is the foundation:

→ Stability
→ Standard work

Stability helps teams avoid firefighting.
Standard work helps improvement last.

The support concepts make it stronger:

→ Heijunka balances the work
→ Kaizen improves every day
→ Visual tools reveal problems
→ Teamwork helps people win
→ Leaders go see the work

This is where the culture shows.

Problems are made visible.
People are trusted to speak up.

Leaders support the work.
Teams improve the work.

Toyota’s real lesson goes beyond the car.
It shows how better thinking builds better work.

Lesson for leaders:

→ Strong tools need strong people
→ Strong people build strong systems
→ Strong systems build better results

People.
Process.
Purpose.

That is the house Toyota built.

***

🔖 Save this post for later.
♻️ Share to help others learn from the Toyota way of thinking.
➕ Follow Sergio D’Amico for more on continuous improvement.

The 5 Levels of Process Maturity.
From firefighting to continuous improvement.

Want to know where your process really stands?

Use the 5 levels of process maturity.

They help leaders see:
→ Where work is today.
→ What good looks like next.
→ Where improvement should start.

The goal is simple:
Move from firefighting
to steady improvement.

Here are the 5 levels:

1️⃣ Ad hoc / Initial

→ Work depends on people, not process.
→ Results change from shift to shift.
→ Problems need hero effort to fix.

Few words:
Unpredictable, reactive, inconsistent.

2️⃣ Managed

→ Basic routines start to exist.
→ Some tasks happen the same way.
→ Discipline still changes by team or shift.

Few words:
Basic routines, partial consistency, emerging control.

3️⃣ Defined

→ Core processes are documented.
→ Teams are trained on the same method.
→ Work becomes more standard across the business.

Few words:
Documented, standard, teachable.

4️⃣ Predictable

→ Key processes are tracked with KPIs.
→ Leaders can see variation.
→ Decisions are based more on facts.

Few words:
Measured, controlled, data-driven.

5️⃣ Optimized

→ Continuous improvement is part of daily work.
→ Teams solve root causes.
→ The system keeps getting better.

Few words:
Kaizen, innovation, excellence.

***

Why this matters:

Better focus

→ You know where you are.
→ You know what to improve next.
→ You stop trying to fix everything at once.

Better control

→ Work becomes more stable.
→ Standards reduce variation.
→ Metrics show gaps before they grow.

Better improvement

→ Teams speak the same language.
→ Leaders coach from facts.
→ Daily action builds a stronger system.

That’s the journey.

From reactive work.
To stable routines.
To standard work.
To measured control.
To continuous improvement.

Process maturity shows how well
your business can repeat good work.

The stronger the process,
the less firefighting teams face.

The better the discipline,
the more stable the results.

***

🔖 Save this post for later.
♻️ Share to help others learn process maturity.
➕ Follow Sergio D’Amico for more on continuous improvement.

PS: I teach this framework
in my Business Process Management
and Improvement course.

The course is in French via Mouvement québécois de la qualité

You can find it here: https://lnkd.in/ebhv4nHQ

This is the best insight I’ve ever taken from a plant tour:
It was seeing an Obeya room placed right in the middle of the Gemba.

Want an Obeya Room that improves daily leadership?

Place it where the work happens:
in the middle of the Gemba.

That was my biggest insight during a plant tour.
The Obeya Room was right inside Operations.
It was the best example I have seen.

The idea is simple:

An Obeya is a visual room that connects
strategy, performance, problems, risks, and actions.

It helps teams see the same facts,
discuss the same gaps, and act faster.

A strong Obeya Room shows:

Mission, vision, and values
→ Why the work matters.

Strategy and Hoshin board
→ Where the business is going.

SQDC daily performance
→ Safety, Quality, Delivery, and Cost gaps.

Planning and commitments
→ Milestones, due dates, and resources.

Problem solving
→ A3 thinking and root cause work.

Risks and issues
→ Problems before they grow.

Action log
→ Owners, due dates, and follow-up.

But the biggest lesson was the location.

When the Obeya's in the Gemba,
leaders stay close to the real work.

Communication improves because teams and leaders
look at the same problems together.

Accountability improves because employees can see
that leaders are present and involved.

That's what stuck with me.

Leadership belongs close to Operations.
Close enough to see.
Close enough to act.

***

🔖 Save this post for later.
♻️ Share to help others learn about Obeya Rooms.
➕ Follow Sergio D’Amico for more on continuous improvement.

PS: I now believe the Obeya Room should be
in the middle of Operations. Do you agree?

The Floor Management Development System (FMDS).
Raise Issues, Develop People and Drive Results.

Want a shop-floor system that develops people daily?

Make work visible, make gaps clear, and coach in real time.

Toyota developed FMDS as a daily shop-floor management system.

The goal is simple:

Connect daily work to company goals.

FMDS combines a visual board, daily routines, and coaching.

It helps leaders see problems early.
It helps teams act before problems grow.
It helps people learn by solving real issues.

Here is how FMDS works:

Hoshin alignment
→ Links shop-floor priorities to company goals.
→ Keeps daily work tied to strategy.
→ Prevents teams from chasing disconnected tasks.

Five key missions
→ Safety, Quality, Productivity, Cost, and People Development.
→ These measures keep the team focused.
→ They balance results with people growth.

Gap to standard
→ The board shows target vs actual.
→ Abnormal conditions become easy to see.
→ A gap is a signal to act now.

Problem solving
→ Problems feed Toyota Business Practice.
→ Issues become structured improvement work.
→ The board turns concerns into action.

Action tracking
→ Each problem needs an owner.
→ Each action needs a due date.
→ Follow-up closes the gap.

On-the-job development
→ Leaders coach during real work.
→ Team members learn by solving real problems.
→ Development becomes part of the daily routine.

History binders
→ Past A3s and kaizen sheets are stored.
→ Teams can reuse lessons learned.
→ Knowledge stays in the workplace.

Why this matters:

Better visibility
→ Teams see the same facts.
→ Problems surface faster.
→ Leaders manage by fact, not guesses.

Better response
→ Abnormalities are raised quickly.
→ Problems are owned and solved.
→ This builds trust and accountability.

Better leadership
→ Supervisors do more than manage output.
→ They coach people through real issues.
→ Daily practice builds stronger leaders.

Better improvement
→ Problems become learning moments.
→ Learning becomes a team habit.
→ Kaizen becomes part of the work.

FMDS builds discipline around daily management.

It gives leaders a simple way to:

→ See the work.
→ See the gap.
→ Coach the team.
→ Close the problem.
→ Then repeat tomorrow.

That is how daily management becomes daily development.

***

🔖 Save this post for later.
♻️ Share to help others learn FMDS.
➕ Follow Sergio D’Amico for more continuous improvement insights.

PS: Toyota developed FMDS to manage work and develop people.
The board only works when leaders coach around it.

The Yamazumi Chart.
The Visual Tool for Leveling Work Across Stations

Yamazumi means “stack up.”
That's what the chart does.
It stacks each task by time.

Each bar shows one operator or station.
Each block shows one work element.
The full bar shows total cycle time.

The goal is simple:
Balance work to takt.
Reduce waste.
Protect flow.

***

Why it matters

A Yamazumi chart helps teams see three problems:

→ Mura: uneven work
→ Muri: too much load
→ Muda: waste inside the work

The team sees the work.
The pressure becomes something they can fix.

***

How to read it

→ X-axis: operators or stations
→ Y-axis: cycle time in seconds
→ Takt line: the pace customers need

→ Green: value work
→ Yellow: needed support work
→ Red: waste to remove

***

What the bars reveal

Tall bars show where flow breaks.
The tallest bar is often the bottleneck.

Short bars show open capacity.
Waste blocks show where to improve first.

Bars above takt need attention.
Bars below takt may take more work.

***

How teams use it

Stand in front of the chart.
Move tasks between stations.
Test a better work sequence.

Cut walking, waiting, and searching.
Update standard work.
Train to the new method.

Then rebuild the chart.
Check the new balance.
Repeat until flow improves.

***

Why it works

The chart makes the work better.

Less opinion.
More facts.
Better kaizen.

The best charts are built at the gemba.

With operators.
With real times.
With real tasks.

Because the people doing the work
often know how to balance it better.

***

🔖 Save this post for later.
♻️ Share to help others balance their production lines.
➕ Follow Sergio D’Amico for more on continuous improvement.

P.S.
I shared a prompt in the comments to build one in Excel.
Use it for your first Yamazumi chart.

Stop trying to organize clutter.
If you haven’t sorted, you’re just rearranging chaos.

5S starts with Sort. And Sort starts with you.
Because no system works in a messy space.

5S is a method to make your workspace better.
The first step is called Sort.

Here’s what Sort means:

→ Remove things you don’t use
→ Keep only what you need
→ Throw out broken or old tools

When you skip this step, problems grow:
→ Tools get lost
→ Shelves fill with junk
→ You waste time searching

So how do you Sort the right way?

→ Things you use every day? Keep them close
→ Things you use sometimes? Store them up high or low
→ Things you never use? Tag them and move them out
→ Broken tools? Throw them away

Also, label everything clearly.
Same spot, same size, same font.

And don’t make room for what doesn’t belong.
Only tools you use should stay.

A clean space helps you:

→ Work faster
→ Stay focused
→ Feel less stress

Remember:

Less junk = more time
Less mess = more results

***

🔖 Save this post for later.
♻️ Share to help others start 5S the right way.
➕ Follow Sergio D’Amico for more on continuous improvement.

P.S. Want 5S to work?
Start strong with Sort.

Bad Gemba walks start with answers.
Good ones start with questions.

Anyone can walk the floor.

A real Gemba walk takes discipline.

You must slow down.
You must listen well.
You must see the work clearly.

***

The 3 habits are simple:

→ Observe without judgment
→ Ask why
→ Show respect

***

Observe without judgment

→ See the facts.
→ Watch the steps.
→ Notice delays and workarounds.

The point is to learn:
See reality as it is.

***

Ask why

→ Dig past the symptom.
→ Look for root causes.
→ Learn with the team.

Good questions help people think.

***

Show respect

→ Listen first.
→ Value the operator’s view.
→ Focus on the process.

People doing the work
often see the truth first.

***

A Gemba walk is a daily learning habit.

Use it to see problems early.
Use it to build trust.
Use it to improve together.

***

🔖 Save this post for later.
♻️ Share to help others improve Gemba walks.
➕ Follow Sergio D’Amico for more continuous improvement.

P.S. On your next walk,
will you look for blame
or look for understanding?

The Shift Handover Board:
Helping teams start each shift with the right information

Stop starting each shift with missing information.

A Shift Handover Board makes the work clear.

It shows what happened.
It shows what needs action.
It shows what the next team must know.

That matters.

Because every shift should begin with the same clear facts.

***

What the board shows

→ Shift status:
Is the line running, stopped, or at risk?

→ Output:
What was the target?
What was the actual result?

→ Quality check:
What defects, rework, or checks need attention?

→ Open issues:
What problems must the next shift see?

→ Action list:
Who owns the task?
When is it due?

→ 5S check:
Is the area clean, safe, and ready?

→ Handover notes:
What happened during the shift?
What should the next team watch?

→ Next plan:
What comes next?
What are the main priorities?

***

Why this works

A good handover board helps teams:

→ Start faster
→ See problems sooner
→ Reduce missed actions

→ Keep safety visible
→ Make quality issues clear
→ Escalate problems faster

→ Assign owners
→ Set due times
→ Build better daily habits

The best boards are simple.

They use short words.
They use clear colors.
They use checkboxes and owners.

Green means okay.
Yellow means watch.
Red means act now.

***

How to use it

At the end of the shift:

→ Update the board
→ Write only key facts
→ Add owners and due times

Then walk the next team through it.

Keep the talk short.
Keep it clear.
Keep it focused on action.

A good handover should answer:

→ What's the current status?
→ What changed today?
→ What problems are still open?

→ Who owns each action?
→ What must happen next?
→ What needs support now?

***

The real power is discipline.

The board alone does nothing.

The daily habit makes it work.

Update it.
Review it.
Act on it.
Escalate when needed.

That's how teams protect flow
from one shift to the next.

***

🔖 Save this post for later.
♻️ Share to help others improve shift handovers.
➕ Follow Sergio D’Amico for more on continuous improvement.

Without action, a Kaizen board is just decoration.

It’s not the ideas that fail. It’s the follow-through that does.

Teams love to talk about improvement.
But talking is not doing. And doing without tracking is wasted.

Why most Kaizen setups do not work:

→ No one owns the ideas
→ There is no follow-up process
→ Wins do not get shared across the team
→ Ideas sit idle in “in progress”
→ The board feels full but achieves little

Here are some habits that make the board work:

→ Add owner photos to every idea
→ Show before and after photos to build belief
→ Block time weekly to review progress
→ Use color codes to clarify each stage
→ Share quick wins to keep morale high

The board itself will not drive change.
Your system and habits will.

Kaizen needs more than just sticky notes and good intentions.
It needs structure, ownership, and visibility.

When people see:

→ Who is responsible
→ What progress looks like
→ How wins get recognized

Then the board turns into a real driver of change.

The magic is not in the tool.
It is in the behavior around it.

***

🔖 Save this post for later.
♻️ Share to help others build Kaizen boards that work.
➕ Follow Sergio D’Amico for more on continuous improvement.

The Daily Tier Meeting Cascade
Problems rise. Help returns. Every morning.

A strong plant needs daily alignment at every level.

It also needs fast escalation when issues appear.

The daily tier cascade creates both.
Each meeting has a clear time and purpose.

At 7:00 AM, Tier 1 begins.

→ Operators and team leaders hold a ten-minute huddle.
→ They track SQDCP and raise blockers.

If the team cannot solve it, the problem moves.

At 8:30 AM, Tier 2 begins.

→ Team leaders meet with the production manager.
→ They spot trends and remove shared friction.

Cross-team resources go where they matter most.
If needed, the issue moves again.

At 10:00 AM, Tier 3 begins.

→ Managers meet with the plant director.
→ They review plant-wide system issues.

Leaders set priorities and give strategic support.
Then support moves back down.

→ Decisions reach the shop floor.
→ Resources reach the right teams.

Information flows upward.
Support flows downward.

→ Leaders avoid floor-level micromanagement.
→ Frontline teams feel heard and supported.

Problems stay visible, tracked, and owned.
Rumors lose power.

Teams act from the same facts.

***

🔖 Save this post for later.
♻️ Share to help others drive daily alignment.
➕ Follow Sergio D’Amico for more on continuous improvement.

Value Stream Mapping reveals what meetings often miss.
The hidden waste buried inside your daily process.

Stop guessing where waste hides.

Value Stream Mapping makes it visible.

It shows each step,
each delay,
and each chance to improve.

***

VSM is a simple visual tool.

It shows how work moves
from supplier to customer.

It helps teams see waste
before they try to fix it.

***

Why teams use it

→ Faster production
→ Less wasted time
→ Lower costs
→ Better teamwork
→ Happier customers

***

Where it came from

VSM has roots in Toyota
and Lean Manufacturing.

The goal was simple:

See the flow.
Find the waste.
Improve the work.

***

When to use it

→ Slow processes
→ High costs
→ Customer complaints
→ Quality issues
→ New process launches

***

How to build one

→ Map the current process
→ Note delays and waste
→ Use real data
→ Involve the team
→ Design the future flow

Go see the work.

Do not guess from a meeting room.

***

Key symbols

→ Arrow = material flow
→ Box = process step
→ Lightning bolt = delay
→ Triangle = inventory stock

***

Mistakes to avoid

→ Skipping steps
→ Ignoring data
→ No team input
→ Rushing solutions

The map only starts the work.

The real value comes
when the team takes action.

***

🔖 Save this post for later.
♻️ Share to help others see hidden waste.
➕ Follow Sergio D’Amico for more on Lean improvement.

The Kaizen Event Action Plan Board
A visual board to track actions, owners, and results.

Want your Kaizen event to create real follow-through?

Use a simple Action Plan Board.

The goal is simple:

Turn ideas into action.
Make ownership clear.
Prove the process improved.

The board helps the team see:

What needs to be done.
Who owns the task.
When it is due.
What the status is.
What proof shows it worked.

A Kaizen event creates energy.

But energy alone does not sustain improvement.

Follow-through does.

That is where the Action Plan Board helps.

Here is how the board works:

Event scope
→ Show the area, dates, team, and goal.
→ Make the problem clear to everyone.
→ Keep the team focused on one process.

Action list
→ Turn ideas into clear tasks.
→ Use simple words people understand.
→ Avoid vague actions like “improve setup.”

One owner
→ Name one person for each task.
→ Shared ownership often means no ownership.
→ One owner makes follow-up easier.

Due date
→ Every action needs a finish date.
→ Dates create urgency.
→ They also reveal delays early.

Clear status
→ Use green, yellow, and red.
→ Green means done or on track.
→ Yellow means in progress or needs attention.
→ Red means blocked or late.

Result proof
→ Do not just close tasks.
→ Show evidence that the process improved.
→ Use photos, numbers, or updated standards.

30-day check
→ Go back after the event.
→ Confirm the new method still works.
→ Make sure gains are being held.

Why this matters:

Better visibility
→ Everyone sees the same plan.
→ Problems are easier to spot.
→ Delays do not stay hidden.

Better ownership
→ Each task has a clear owner.
→ Each owner knows the expected result.
→ Accountability becomes part of the work.

Better follow-through
→ Ideas become actions.
→ Actions become results.
→ Results become the new standard.

The best boards are simple, current, and visible.

They stay close to the work.

They are reviewed every day.

That is the real purpose
of the Kaizen Event Action Plan Board.

It turns improvement ideas
into owned tasks,
visible progress,
and proven results.

***

🔖 Save this post for later.
♻️ Share to help others improve Kaizen follow-through.
➕ Follow Sergio D’Amico for more on continuous improvement.

PS: Good ideas need good follow-up.
That is where real improvement happens.

There's a lifecycle behind every high-impact Kaizen team. Leaders who understand it build trust faster and get better results.

Kaizen teams do not perform perfectly on day one.
They grow through stages.

Each stage needs different leadership.

Tuckman’s model gives leaders a simple map.
For Kaizen teams, that map matters.

The leader’s role must change as the team matures.

Here’s the lifecycle:

1️⃣ Forming

The team is polite, unsure, and dependent.

Leader’s role:
→ Set direction.
→ Create safety.
→ Define the Kaizen charter.
→ Set clear boundaries.

Confusion kills early momentum.

2️⃣ Storming

Tension shows up.
People debate, clash, and push back.

Leader’s role:
→ Coach through conflict.
→ Keep focus.
→ Use facts.
→ Prevent the team from splitting.

Storming is normal.
Guide it before it gets worse.

3️⃣ Norming

Trust starts to build.
Roles get clearer.
Collaboration improves.

Leader’s role:
→ Reinforce standards.
→ Strengthen shared habits.
→ Clarify how the team works.

4️⃣ Performing

The team gains speed.
Problem-solving gets stronger.

Leader’s role:
→ Step back.
→ Empower the team.
→ Remove barriers.

5️⃣ Adjourning

Results are reviewed.
Wins are celebrated.
Learning is captured.

Leader’s role:
→ Lock in learning.
→ Hand off ownership.
→ Sustain the gains.

That is how Kaizen teams move
from uncertainty to impact.

***

🔖 Save this for your next Kaizen event.
♻️ Share it with a leader building stronger teams.
➕ Follow Sergio D’Amico for more on continuous improvement.

PS: The team’s behavior tells you what leadership style is needed.

The Power of the Gemba Walk.
The Best Leaders Don't Wait for Reports. They Go See.

Want leaders who understand the real work?

Go to Gemba.

The goal is simple:
See the work.
Respect the people.
Improve the process.

A Gemba Walk helps leaders
see what is really happening
where value is created.

Here's how to do it well:

Go to the place
→ See the actual process.
→ Let facts guide the discussion.

Observe the process
→ Look for standards and waste.
→ Compare planned work to real work.

Talk with people
→ Ask open questions.
→ Listen before giving advice.

Show respect
→ Treat operators as process experts.
→ Learn from those closest to the work.

Coach, don’t tell
→ Help people see problems clearly.
→ Develop problem solvers.

Follow up
→ Turn insights into action.
→ Assign owners and due dates.

Why this matters:

Better visibility
→ Leaders see problems firsthand.
→ Waste becomes easier to spot.

Better teamwork
→ People feel heard.
→ Standards become clearer.

Better kaizen
→ Small issues get fixed sooner.
→ Improvement becomes a daily rhythm.

The best Gemba Walks are simple,
consistent, and respectful.

Go see.
Ask why.
Show respect.
Follow up.

That is how leaders turn
daily observation
into daily improvement.

***

🔖 Save this post for later.
♻️ Share to help others learn the power of the Gemba Walk.
➕ Follow Sergio D’Amico for more on continuous improvement.

PS: A Gemba Walk starts with
seeing, listening, and respect.

The DMAIC Project Room
From root cause to lasting results, all in one place.

Most people know DMAIC as a method.

But many teams still run DMAIC projects through:

→ scattered files
→ random meetings
→ disconnected charts
→ unclear ownership
→ weak follow-up
→ forgotten control plans

That is why a DMAIC Project Room can be a good idea.

It turns improvement work
from a hidden document exercise
into a visible management system.

Everyone can see:

→ what problem is being solved
→ what data supports the work
→ what root causes were tested
→ what actions were taken
→ what results changed
→ what controls keep gains in place

This makes DMAIC easier to understand,
easier to review,
and easier to sustain.

Define shows the problem.

Measure shows the baseline.

Analyze shows root causes.

Improve shows what changed.

Control protects the gains.

Daily management keeps the work moving.

Why this works:

Better visibility
→ The full project story stays clear.
→ Teams see the same facts.
→ Leaders know where to focus.

Better decisions
→ Data stays connected to actions.
→ Teams avoid guessing.
→ Discussions stay grounded in facts.

Better sustainment
→ Control plans stay visible.
→ Gains are easier to protect.
→ Problems are less likely to return.

Better learning
→ Real projects become training examples.
→ People see how tools connect.
→ Problem-solving discipline grows.

DMAIC should not live
inside a PowerPoint deck.

When the project is hidden in files,
people forget the story.

When the project is visible,
the team can follow the logic.

A DMAIC Project Room
makes problem solving visible.

Not fancy.

Just clear.

And clarity helps teams
make better decisions.

***

🔖 Save this post for later.
♻️ Share to help others build a DMAIC room.
➕ Follow Sergio D’Amico for more CI insights.

PS: When the story is clear,
the next step becomes easier to see.

Here's how I plan Kaizen events.
Teams stay focused from start to finish.
The lifecycle follows PDCA.

1/ Prepare and scope: weeks one through four.
→ Set charter goals, business case, and success measures.
→ Define boundaries so the scope stays controlled.
→ Select the right team before improvement work begins.

2/ Execute: event days one through five.
→ Go to Gemba and observe work at the source.
→ Build simple cardboard prototypes before making changes.
→ Run several trials and choose the best solution.

3/ Present and report: day five.
→ Show before-and-after data to show improvement.
→ Make the improved method the official standard.
→ Document lessons before the event closes.
→ Present results to your sponsor and steering committee.

4/ Then I check back at 30, 60, and 90 days.
→ Audit the process and confirm the method stays.
→ Track key measures after the event ends.
→ Confirm old habits haven't returned.

Plan it. Run it. Share it. Sustain it.
That's how I keep Kaizen gains from slipping.

🔖 Save this post for your next Kaizen event.
♻️ Share to help others run better Kaizen events.
➕ Follow Sergio D’Amico for more continuous improvement.

📌 P.S. Do you plan Kaizen events the same way?

Genchi Genbutsu means go and see.
It helps teams solve problems with less guessing.

The method has three simple parts.
Each part gives you a clearer picture.

→ Genba: The real place.
→ Go where the work happens.
→ Watch the process with your own eyes.

→ Genbutsu: The real thing.
→ Hold the part, tool, or material.
→ Inspect it instead of using only photos.

→ Genjitsu: The real facts.
→ Check real numbers before making choices.
→ Test each guess with facts you can prove.

You need all three for a strong answer.

The place shows what surrounds the problem.
The thing shows details a report may miss.
The facts show what really happened.

Use this order when the next problem appears.
Go there. Check it. Prove it.

Which real does your team use best?

***

🔖 Save this post for later.
♻️ Share to help others make better shop floor decisions.
➕ Follow Sergio D’Amico for more on continuous improvement.

Batch Production vs One-Piece Flow
From Hidden Waste to Visible Flow

Batch work can look busy while orders still move slowly.
One-piece flow helps work move step by step.
Each part goes forward without sitting in a pile.

Here is what batch production often creates:
→ Parts wait in long queues.
→ Problems stay hidden until the batch ends.

→ Large changeovers push teams toward bigger lots.
→ Each step stays busy, yet delivery stays slow.

One-piece flow changes what teams can see:
→ Each part moves right away.
→ Problems show up fast.

→ Quality gets checked at every step.
→ Lead time gets shorter because waiting drops.

This is what you need to know:
Batch production keeps machines busy.
One-piece flow keeps the work moving.

Busy machines can still hide waste.
Smooth flow makes delays easier to spot.
Better sight helps teams fix issues sooner.

Start with one product and one clear path.
Test a smaller batch or one-piece flow.

***

🔖 Save this post for later.
♻️ Share to help others improve flow.
➕ Follow Sergio D’Amico for more continuous improvement.

P.S. Where could your team improve flow first?

The 7 Quality Management Principles.
The foundation behind every great quality management system.

Quality management starts with daily choices.

How leaders lead.
How teams work.
How problems get solved.

How customers are heard.
How facts guide decisions.
How partners work together.

The 7 Quality Management Principles
give teams a strong base.

They help leaders build better work.
They help teams serve customers better.
They help problems become easier to see.

1/ Customer Focus
→ Know what customers need.
→ Then work to meet it.

2/ Leadership
→ Set clear direction.
→ Help people move together.

3/ Engagement of People
→ People do better work,
→ when they feel trusted and valued.

4/ Process Approach
→ Better results come from clear processes.
→ Every step affects the next step.

5/ Improvement
→ Keep looking for better ways.
→ Small gains add up.

6/ Evidence-Based Decision Making
→ Use facts and data.
→ Do not depend only on opinions.

7/ Relationship Management
→ Work well with suppliers and partners.
→ Quality does not stop at your walls.

A strong quality system needs all seven.

Miss one, and the system gets weaker.

Use these principles as a mirror.

Check where your team is strong.

Then fix where the system is weak.

Source: ISO - International Organization for Standardization

***

🔖 Save this post for later.
♻️ Share to help others build stronger quality systems.
➕ Follow Sergio D’Amico for more on continuous improvement.