Operational Excellence: Assessment & Transformation

A practical, self-paced introduction to operational excellence for organizations in energy, manufacturing and health care. You will learn to assess maturity and find operational gaps, engage stakeholders in process improvement, and execute transformation plans that deliver measurable results. The course closes with a framework for daily management, leadership routines and scaling improvement across divisions.

Course structure

• Module 1: Foundations of Operational Excellence (5 lessons). What operational excellence is, the principles behind it, how it applies in high-stakes industries, and how to make the case for change.
• Module 2: Assessment: Finding the Gaps (5 lessons). Run a maturity assessment, observe work at the gemba, map processes and value streams, and turn findings into a prioritized gap list.
• Module 3: Measuring and Analyzing Performance (5 lessons). Choose KPIs that drive the right behaviour, measure equipment effectiveness, read variation and find root causes with structured methods.
• Module 4: Engaging People and Transforming Processes (5 lessons). Engage stakeholders, lead the people side of change, charter projects, build standard work and test changes safely.
• Module 5: Sustaining and Scaling the Gains (4 lessons). Build daily management, leadership routines and strategy deployment so improvement lasts and spreads, then plan your first 90 days.

Interactive labs

• Operational Excellence Maturity Assessment: Score your organization on seven dimensions of operational excellence to see your maturity profile and the areas holding you back.
• Value-Added or Waste?: Sort real activities from manufacturing, energy and health care into value-added, necessary non-value-added and waste, then check the explanations.
• OEE Calculator: Enter one shift of data from a machine, line or asset to calculate availability, performance, quality and overall OEE.

How it works

• Work through 24 short lessons at your own pace. Each has key takeaways, an exercise for your own workplace and a quick knowledge check.
• Try the three interactive labs as you reach them in the course.
• Pass the 20-question final exam (70% or higher, unlimited retakes) to unlock your Chmltech certificate of completion.
• Free, with no sign-up. Your progress is saved in this browser.

Operational excellence (OpEx) is not a single tool, a project or a poster on the lunchroom wall. It is a way of running an organization in which every person can see how value flows to the customer, notices when that flow breaks, and fixes problems at the root, every day. The goal is consistent, predictable performance that keeps getting better.

Many SMEs confuse OpEx with a one-time cost-cutting exercise. Cost cutting removes resources; operational excellence removes the reasons the resources were needed in the first place: rework, waiting, searching, firefighting and unclear handoffs.

Three things OpEx is, and three things it is not

A simple working definition

For this course, use this definition: operational excellence is the ability to deliver what the customer values, safely, at the right quality, on time and at the lowest sustainable cost, and to improve that ability continuously. Notice the word sustainable. A shop that hits its numbers by running overtime every weekend is not excellent; it is borrowing from next quarter.

Worked example

Imagine a 40-person fabrication shop that ships on time most months but only because the owner personally expedites the late jobs. On paper, delivery looks fine. In reality, the process depends on one person's heroics. An OpEx view asks different questions:

• Why do jobs become late in the first place?
• What would happen if the owner went on vacation for three weeks?
• Where does work wait, and who knows about it before the customer does?

Answering those questions moves the shop from heroics to a system. That shift, from people compensating for a weak process to a strong process that supports people, is the heart of operational excellence. The rest of this course gives you a structured path to make it happen: assess where you are, engage the people who do the work, transform the processes that matter most, and build habits that sustain the gains.

Every serious operational excellence approach, whether it is called Lean, the Toyota Production System, Six Sigma or a company-branded system, rests on a short list of principles. Tools come and go; principles stay. When a tool does not seem to fit your situation, go back to the principle and ask what it is trying to achieve.

Five principles to anchor your work

1. Start with customer value. Define value from the customer's point of view: what they would willingly pay for, or in health care, what improves the patient's outcome and experience.
2. Make the work flow. Work should move steadily from step to step without waiting, batching or backtracking.
3. Standardize, then improve. A process that is done five different ways cannot be improved; it can only be argued about. The current best known method becomes the standard and the baseline for the next improvement.
4. Go and see. Decisions are made from direct observation and data at the place where work happens, not from reports alone.
5. Respect for people. The people doing the work know the most about its problems. Leaders build their capability and give them time and permission to fix things.

How the principles show up in practice

Worked example

A clinic's intake desk asks every new patient to complete a paper form, which staff then retype into the scheduling system. Applying the principles: the patient values being seen promptly and accurately, not filling in forms twice (value). Retyping creates a queue at the desk (flow). Each staff member enters fields differently (standardize). The manager has never timed the process (go and see). Front-desk staff have suggested pre-visit online forms for months (respect for people). The principles alone point to the improvement before any advanced tool is needed.

Operational excellence matters everywhere, but in energy, manufacturing and health care the stakes are higher. A missed step can mean an injury, an environmental release, a product recall or harm to a patient. In these settings OpEx is closely tied to safety and regulatory compliance, and improvement must never trade away control.

What is different in high-stakes settings

• Safety comes first, always. Every change passes through a management of change (MOC) or equivalent review before it touches live operations.
• Regulation shapes the process. Some steps exist because a regulator, code or accreditation body requires them. These are not waste, even if the customer never sees them.
• Variation is dangerous. A small deviation in a pressure, a dose or a torque value can have large consequences, so standard work and verification carry extra weight.
• Shift work and handovers. Many failures occur at shift change or patient handoff, so communication standards are part of the process.

Typical focus areas by sector

Worked example

Consider a field services company that inspects wells. Crews spend part of each morning waiting for work permits to be signed. A purely cost-focused view might suggest skipping the sign-off. An OpEx view keeps the safety control and redesigns the flow around it: permits are prepared the evening before, the supervisor reviews them at a fixed time, and a simple board shows which crews are cleared. The control stays intact; the waiting disappears.

In high-stakes work, the question is never "can we remove this check?" but "how do we make this check fast, reliable and easy to do right?"

This mindset protects people and the licence to operate while still freeing capacity. Throughout this course, treat safety and compliance requirements as design constraints, not obstacles.

Before an organization invests time in assessment and transformation, leaders need a clear reason to act. A strong case for change connects operational problems to things the business already cares about: safety, customers, cash, capacity and people. Without it, improvement becomes a side project that loses to the next urgent order.

The cost of poor quality

A useful lens is the cost of poor quality (COPQ): the money spent because things were not done right the first time. It usually falls into four buckets.

Most SMEs do not track COPQ formally, so start with a rough estimate from a few weeks of data. A rough number that leaders believe is more powerful than a precise number nobody trusts.

Worked example

Imagine a 25-person cabinet manufacturer. Over four weeks the team logs remakes caused by measuring errors: 12 remakes averaging 3 labour hours and $180 in material each. At a loaded labour cost of $55 per hour:

• Labour: 12 x 3 x $55 = $1,980
• Material: 12 x $180 = $2,160
• Four-week total: $4,140, or roughly $53,800 a year if the pattern holds

That number does not yet include delayed installs, unhappy customers or the overtime used to catch up. It is enough to justify a focused improvement effort.

Elements of a one-page case for change

1. The problem, in plain language, with one or two facts
2. Why it matters now (customer, safety, growth, cash)
3. What happens if nothing changes
4. What success would look like in 6 to 12 months
5. What is being asked of leaders and teams

Keep it to one page and test it with a supervisor. If they cannot repeat the message in their own words, simplify it.

Operational excellence efforts fail most often not because of the wrong tools, but because of the wrong sequence: launching training before understanding the gaps, or running improvement events with no system to hold the gains. This course follows a simple roadmap that keeps the work in order.

The four phases

Why assessment comes first

Assessment gives you three things you cannot get any other way: a shared picture of reality, a baseline to measure against, and a list of priorities based on evidence rather than the loudest voice. It also builds early engagement, because people who help find the problems are more likely to help fix them.

Sizing the effort for an SME

A large corporation may run a multi-year program with a dedicated team. An SME can follow the same phases at a smaller scale:

• Assess one value stream in two to four weeks
• Run one or two focused improvement projects over the next 90 days
• Introduce a short daily team huddle alongside the first project
• Review results, then choose the next value stream

Worked example

A regional HVAC distributor wants to reduce order errors. Instead of buying new software straight away, the team assesses the order-to-ship process, finds that most errors start at manual order entry, runs a 60-day project to standardize entry and add a simple check, and then starts a 10-minute daily huddle to review errors. Only after the process is stable do they evaluate whether automation would add further value.

Keep this roadmap in mind as you move through the modules. Each lesson fits into one of the four phases.

A maturity assessment is a structured self-check of how well your organization's management system supports excellent operations. It does not measure how hard people work; it measures how well the system helps them succeed. Done well, it creates a shared language and a starting point for planning.

A five-level maturity scale

Typical dimensions to assess

• Leadership and strategy deployment
• Process standardization
• Performance measurement and KPIs
• Problem solving
• Workforce engagement and capability
• Customer focus
• Continuous improvement culture

How to run it well

1. Use a mixed group. Include leaders, supervisors and front-line staff. Leaders often score higher than the floor does; the gap itself is useful information.
2. Ask for evidence. For every score, ask "what would we show a visitor to prove this?" No evidence means the score drops.
3. Score independently, then discuss. Have each person score privately, then compare. Discuss the dimensions with the widest spread.
4. Do not chase a perfect score. The point is to find the two or three dimensions that are holding the operation back.

Worked example

A 60-person machine shop runs the assessment with six people. Leaders score process standardization at 4; machinists score it at 2. When asked for evidence, the team finds work instructions exist for only a third of part families, and most are out of date. The honest score is 2. That dimension becomes a priority, and the gap between leader and floor perceptions becomes a talking point for the engagement plan.

After this lesson, use the maturity assessment lab to score your own organization and see your profile as a radar chart.

Gemba is a Japanese term meaning "the real place", the place where value is created. In a plant it is the production floor; in a clinic it is the intake desk and exam rooms; in an energy company it may be a well site or a maintenance shop. A gemba walk is a planned visit to observe the work, ask questions and learn, not to inspect or blame.

The purpose of a gemba walk

• See the actual process, including the workarounds that never appear in procedures
• Understand problems from the point of view of the people doing the work
• Check whether standards exist, are visible and are followed
• Build trust by showing genuine interest

A simple gemba walk routine

1. Pick a focus. One process or one question, for example "why do work orders wait before release?"
2. Tell people why you are coming. Explain that you are learning about the process, not evaluating individuals.
3. Watch first. Spend at least ten minutes observing before you ask anything.
4. Ask open questions. "Walk me through what happens next." "What gets in your way?" "How do you know this is done right?"
5. Write down facts. Times, counts, distances, quotes. Avoid conclusions on the spot.
6. Close the loop. Thank people and come back to tell them what happened with what they shared.

Common mistakes

Worked example

An operations manager at a pipe distributor walks the shipping area with the focus "why are some orders shipped late?" Watching for 20 minutes, she sees pickers walk to the office three times to ask about unclear pick tickets. One picker says, "The tickets don't show which yard the pipe is in." That single observation, which never appeared in any report, becomes the first improvement target.

Before you can improve a process, everyone must agree on what the process is. Mapping makes the invisible visible. Two complementary tools work well for SMEs: the SIPOC for the high-level view, and the swim lane map for detail.

SIPOC: the 30,000-metre view

SIPOC stands for Suppliers, Inputs, Process, Outputs and Customers. It defines the boundaries of a process in one page and is often the first tool used in a Six Sigma project.

Build a SIPOC from the middle out: list the process steps first, then outputs and customers, then inputs and suppliers. Keep it high-level; detail comes later.

Swim lane maps: who does what, and where it waits

A swim lane map shows each role or department as a horizontal lane and draws the steps in the lane of whoever performs them. Every time work crosses a lane, there is a handoff, and handoffs are where delays and errors tend to happen.

• Map the process as it actually runs today, not as the procedure says
• Use sticky notes on a wall so people can move steps easily
• Mark waits, rework loops and decision points clearly
• Note the time each step takes and how long work waits before it

Worked example

An engineering office maps its drawing approval process in swim lanes: designer, checker, project manager and client. The team counts 9 handoffs and finds that drawings wait an average of 3 days in the project manager's inbox, while checking itself takes about 2 hours. The map shows clearly that the delay is in waiting, not in the work. The team agrees to a daily 15-minute approval slot, a change that the map made obvious.

Whatever tool you use, the conversation while mapping is often worth more than the map. People discover how their work affects others, which builds the engagement you will need later.

A value stream is every step, value-adding or not, required to take a product or service from request to delivery. Value stream mapping (VSM) draws that flow along with the information that triggers it, and adds timing data so you can see how much of the total time actually adds value.

Key VSM measures

• Process time: the time someone is actually working on the item
• Lead time: the total elapsed time from request to delivery
• Process cycle efficiency: value-added time divided by lead time

The 8 wastes

Lean thinking classifies activities as value-added (the customer pays for it), necessary non-value-added (required by regulation, safety or current constraints) or waste. A common memory aid for the eight wastes is DOWNTIME.

Worked example

A pump repair shop maps its repair value stream. Teardown, repair, assembly and testing add up to 6 hours of process time. But the total lead time from pump arrival to shipment is 10 working days, or about 80 working hours. Process cycle efficiency is 6 / 80 = 7.5%. The rest is waiting for quotes, parts and customer approval. The map makes it clear that the biggest gains are in the information flow, not in faster wrenches.

Low process cycle efficiency is normal in a first map; do not be discouraged. It simply shows where the opportunity lies. After this lesson, use the classification lab to practise sorting real activities into value-added, necessary non-value-added and waste.

After assessment, mapping and gemba walks, most teams have more problems than they can solve. The risk now is trying to fix everything at once and finishing nothing. The final step of the assessment phase is to convert findings into a short, prioritized list of gaps linked to the case for change.

From observations to gap statements

Write each finding as a clear gap statement: current state, desired state, and impact. For example: "Changeovers on Press 3 take 90 minutes; target is 30 minutes; the gap costs about 6 hours of capacity per week."

Simple prioritization criteria

Add the scores and rank the gaps. Treat the ranking as a guide for discussion, not a formula that replaces judgement. A safety gap goes to the top regardless of score.

Worked example

A small food processor lists five gaps after assessment. Scored by a team of four:

• Long sanitation changeover between allergen runs: 5 + 3 + 4 + 5 = 17
• Paper-based batch records with frequent errors: 4 + 3 + 4 + 4 = 15
• No daily production meeting: 3 + 5 + 2 + 5 = 15
• Supplier late deliveries: 4 + 2 + 3 + 2 = 11
• Outdated ERP system: 4 + 1 + 2 + 3 = 10

The team chooses the sanitation changeover as its first project, starts a daily production meeting immediately because it is low effort, and parks the ERP question until processes are stable.

Keep the list short

For an SME, two or three active improvement projects at a time is usually the most a leadership team can support properly. Everything else goes on a visible backlog so people know their ideas were heard.

What gets measured shapes what people pay attention to. Good key performance indicators (KPIs) tell teams whether the process is healthy and help them act early. Poor KPIs create busywork, hide problems or encourage gaming.

Leading and lagging indicators

Leaders need both. Lagging measures confirm whether strategy is working; leading measures let teams correct course before the month is lost.

A balanced set: safety, quality, delivery, cost, people

Many operations organize KPIs under five headings, sometimes shortened to SQDCP. Choose one or two measures under each heading for each level of the organization. A front-line team might track:

• Safety: near misses reported today
• Quality: first-pass yield
• Delivery: jobs completed versus plan
• Cost: overtime hours
• People: improvement ideas submitted

Tests for a good KPI

1. The team can influence it through their own actions
2. It is updated often enough to act on (daily or weekly at the front line)
3. It has a clear definition and a single source of data
4. It is paired with a measure that prevents gaming, such as speed paired with quality

Worked example

A clinic tracks only the average time from check-in to seeing a clinician. Staff begin checking patients in later to make the number look better. The clinic redefines the measure to start from the scheduled appointment time, adds a leading measure (charts prepared before the patient arrives), and pairs speed with a short patient feedback question. The measures now reward the behaviour the clinic actually wants.

Overall Equipment Effectiveness (OEE) is a standard measure of how well a machine, line or asset is used during the time it is planned to run. It combines three losses into one number and, more importantly, shows which loss to attack first. Although it began in manufacturing, the same logic applies to a compressor station, a CT scanner or a laboratory analyzer.

The three factors

OEE = Availability x Performance x Quality. Run time is planned production time minus downtime.

Worked example

A CNC cell is planned to run one 8-hour shift with a 30-minute break, giving 450 minutes of planned production time. During the shift:

• Downtime (one changeover and a tool breakage): 60 minutes, so run time = 390 minutes
• Ideal cycle time: 1.5 minutes per part
• Total parts produced: 220; good parts: 209

1. Availability = 390 / 450 = 86.7%
2. Performance = (1.5 x 220) / 390 = 330 / 390 = 84.6%
3. Quality = 209 / 220 = 95.0%
4. OEE = 0.867 x 0.846 x 0.950 = about 69.7%

Here, availability and performance losses are similar in size. The team looks at the changeover (availability) and tracks minor stops for a week (performance) before choosing a project.

Using OEE wisely

• Use OEE to compare a machine with itself over time, not to rank machines or crews against each other
• Agree on the ideal cycle time from the equipment's design rate or best demonstrated rate, and keep it fixed
• Collect downtime reasons, not just minutes; the reasons drive the improvement
• Apply OEE to bottleneck assets first, where every lost minute is lost output

After this lesson, use the OEE calculator lab with numbers from one of your own assets.

Before you change a process, you need a baseline: a measure of how it performs today. Without one, you cannot prove an improvement worked, and you risk reacting to normal ups and downs as if they were real problems.

Two kinds of variation

Statistical process control, developed in the early twentieth century, distinguishes two types of variation:

• Common cause variation: the natural noise built into a stable process. Reacting to each high or low point makes things worse.
• Special cause variation: a signal that something specific has changed, such as a new supplier lot, a worn tool or a staffing gap. It deserves investigation.

Start with a run chart

A run chart plots a measure over time with a median line. It is simple enough to draw by hand on a whiteboard. Common rules of thumb for spotting a signal include:

1. A run of six or more points in a row all above or all below the median
2. Five or more points in a row steadily going up or down
3. One point far outside the usual range

When you have enough data, a control chart adds calculated limits that make the distinction more rigorous.

Worked example

A distribution centre tracks daily picking errors for 20 days. The median is 4 errors per day. A supervisor wants to retrain staff after a day with 7 errors. Looking at the run chart, the team sees that 6 and 7 have appeared several times without any pattern; the process is simply noisy. Then, starting on day 15, six days in a row fall above the median. Investigation shows a new product line with similar-looking labels was introduced on day 14. That is a special cause, and the fix is better labelling, not retraining.

Practical baseline guidelines

Most organizations are good at fixing symptoms. They replace the broken part, re-send the shipment, apologize to the patient. The same problem then comes back next month. Root cause analysis (RCA) asks why the problem happened until you reach a cause that, if removed, would stop it from recurring.

The 5 Whys

Ask "why?" repeatedly, usually around five times, each answer based on facts rather than guesses. It works best for problems with a fairly straight chain of cause and effect.

1. Why did the customer receive the wrong valve? The picker pulled the wrong part number.
2. Why? Two valves with similar numbers sit in adjacent bins.
3. Why? Bins are assigned by part number order, not by appearance.
4. Why? The slotting rule was set up when the catalogue was much smaller.
5. Why has it not been revisited? No one owns warehouse layout reviews.

The fix moves from "tell the picker to be careful" to "separate look-alike parts and assign an owner for slotting reviews."

The fishbone (Ishikawa) diagram

For problems with many possible causes, a fishbone diagram organizes ideas under standard categories. A common set for operations is the 6Ms:

Rules for good RCA

• Focus on the process, never on blaming a person
• Verify each suspected cause with data or observation before acting
• If the answer is "human error", ask why the process allowed the error
• Choose fixes that make the error hard or impossible to repeat (error-proofing)

Some problems are too complex for a quick 5 Whys: the causes are unclear, several factors interact, or the stakes are high. Six Sigma's DMAIC method gives these problems a disciplined, data-driven structure. It has five phases, each with a clear exit question.

DMAIC versus PDCA

PDCA (Plan, Do, Check, Act) is a shorter improvement cycle used for everyday problems and quick experiments. DMAIC is a longer, more rigorous path for problems where the cause is unknown and the impact is large. Many organizations use PDCA daily and reserve DMAIC for a handful of projects each year.

Worked example

A plastics moulder has intermittent short shots on one product. Quick fixes have not worked. Using DMAIC:

• Define: reduce short-shot scrap on Part 220 from 4% to under 1% in 12 weeks
• Measure: the team confirms operators classify defects consistently and collects four weeks of data
• Analyze: a Pareto chart shows most short shots occur in the first hour after a resin lot change; a test confirms moisture content varies between lots
• Improve: the team adds a resin drying check before lot changes and pilots it for two weeks; scrap falls to 0.8%
• Control: the check is added to standard work and scrap is charted daily, with a response plan if it rises

The structure prevents jumping to solutions and makes sure the gain is locked in before the team disbands.

Process improvement changes how people work, so people must be part of it from the start. Engaging stakeholders is not a courtesy; it is how you get accurate information, workable solutions and lasting adoption. Two tools help: a stakeholder map and a RACI chart.

The stakeholder map

List everyone affected by or able to influence the change, then place them on a simple grid of influence and interest.

Front-line staff often appear as "low influence" on an organization chart but have very high practical influence: if they do not adopt the new method, nothing changes. Place them honestly.

RACI: clear roles for each decision or task

• Responsible: does the work
• Accountable: owns the outcome and signs off (only one per task)
• Consulted: gives input before the decision
• Informed: told after the decision

Worked example

A home health agency is redesigning its client intake. Its RACI for three tasks:

Building the RACI revealed that no one had previously owned triage rules, which explained why they varied by coordinator.

Common RACI pitfalls

• More than one A on a task, which means no one is truly accountable
• Too many Cs, which slows every decision
• No R on the front line, which leaves improvements designed for staff, not with them

A technically perfect process redesign can still fail if people do not understand it, believe in it or know how to do it. Change management gives structure to the people side. Two widely used models are Kotter's eight steps, aimed at organizational change, and ADKAR, aimed at individual change.

Kotter's eight steps (summarized)

1. Create a sense of urgency
2. Build a guiding coalition
3. Form a strategic vision
4. Communicate the vision widely
5. Remove barriers and empower action
6. Generate short-term wins
7. Sustain acceleration
8. Anchor the change in the culture

ADKAR: what each person needs

ADKAR is especially useful for diagnosing resistance. When someone is not adopting a change, find the first element that is missing and work on that one.

Worked example

A utility's maintenance crews are asked to start using a mobile work order app. Six weeks in, one crew still uses paper. The supervisor works through ADKAR: they know why (awareness) and are open to it (desire), and they attended training (knowledge). But in the field, the app needs a signal that several sites lack, so they cannot use it (ability). The fix is offline mode, not more training or pressure.

Practical tips for SMEs

• Communicate through direct supervisors; people trust their own leader most
• Expect and welcome questions; resistance often contains useful information
• Celebrate early wins publicly and credit the people who made them

Turning a priority gap into results needs a clear project structure. The project charter is the single most useful document for this. It aligns sponsors and team members before work begins and protects the project from drifting.

Elements of a one-page charter

Kaizen events versus longer projects

• Kaizen event: a focused three- to five-day workshop where a cross-functional team analyzes and improves a narrow process, such as a changeover or a supply room. Good for problems with a clear scope and quick solutions.
• Improvement project: runs over weeks or months, often using DMAIC, for problems that need data collection and analysis.

The sponsor's role

Every project needs a sponsor who can remove barriers, provide time and resources, and hold the team accountable. In an SME, this is often the owner or general manager. A sponsor should meet the project lead briefly every week or two.

Worked example

A machine shop charters a project: "Average changeover on the vertical machining centre takes 75 minutes (four-week baseline). Reduce to 30 minutes by end of quarter without increasing first-piece rejects. In scope: VMC 2 and its fixtures. Out of scope: purchasing new equipment." The team includes two machinists, the setup lead and a supervisor, with the operations manager as sponsor. Using a single-minute exchange of die (SMED) approach, they move setup tasks to before the machine stops and pre-stage tooling on a cart, reaching 35 minutes in six weeks and 28 minutes after standard work is in place.

Notice the balancing measure: speeding changeovers is only a win if first-piece quality holds.

Once a team finds a better way, standard work captures it so it is done the same way every time, by every shift. 5S creates the organized, visual workplace that makes standard work easy to follow. Together they are the foundation for every other improvement.

What standard work contains

• Sequence: the steps in the best known order
• Timing: how long each step should take, linked to customer demand where relevant
• Key points: the quality, safety and "knack" points that make the step succeed
• Standard inventory: the materials that should be on hand at the workstation

Good standard work is short, visual and posted where the work happens. Photos beat paragraphs. It is written with the people who do the job and updated whenever someone finds a better way.

The 5S method

Many safety-focused organizations add a sixth S for Safety, checking for hazards as part of each step.

Worked example

A field service company's maintenance shop applies 5S to its tool crib. Before, technicians spent time each morning looking for torque wrenches and calibrated gauges. After sorting, shadow boards and a simple sign-out sheet, missing tools become visible at a glance. The shop then writes standard work for the morning truck-loading routine, with a photo of a correctly loaded truck. Crews leave for site earlier and with the right tools.

Why 5S fails

5S often becomes a one-time clean-up that fades within months. It sustains when it is tied to the work (people see that it saves them time), when leaders check it during gemba walks, and when the team owns the standards rather than having them imposed.

New ideas should be tested before they become the new standard. The Plan-Do-Check-Act (PDCA) cycle, popularized by W. Edwards Deming, is the simplest way to run a controlled experiment in a live operation. In high-stakes settings, it is also how you change processes without creating new risks.

The PDCA cycle

1. Plan: state the problem, the change you will test, and what you predict will happen. Define how you will measure it.
2. Do: run the change on a small scale, such as one shift, one line or one clinic room.
3. Check: compare the results with your prediction and the baseline.
4. Act: adopt, adapt or abandon the change. If adopted, update the standard. Then plan the next cycle.

Designing a safe pilot

Worked example

A medical imaging clinic wants to reduce late starts. Plan: the team predicts that calling patients the day before with prep instructions will cut late starts on morning appointments from about 1 in 4 to 1 in 10. Do: one staff member makes the calls for morning slots for two weeks. Check: late starts drop to about 1 in 8, but calls take longer than expected. Act: the team adapts by switching to a scripted text message with a callback option, then runs a second two-week cycle.

Scaling after the pilot

• Only scale a change that has met its goal and been written into standard work
• Expect to adjust when moving to a different shift, site or product
• Keep measuring after rollout; pilots run with extra attention and results can drift

Improvement projects fix specific problems. Daily management is the system that catches new problems early and keeps processes performing at their new standard. It is the difference between organizations that improve once and those that keep improving.

Tiered huddles

Short, standing meetings at each level of the organization, held at the same time every day, connect the front line to leadership in hours rather than weeks.

In a small business, there may be only two tiers. The principle is the same: problems that cannot be solved at one level move up quickly, and answers come back down.

What goes on a visual board

• SQDCP measures with simple red and green status against target
• Today's plan and staffing
• An issues list with owner and due date
• Improvement ideas in progress

The board should let anyone walking by understand, within a minute, whether the team is having a good day and what help it needs.

Worked example

A regional distributor starts a 10-minute Tier 1 huddle at the start of each shift in the warehouse, and a Tier 2 huddle at 9:00 with the warehouse, purchasing and customer service leads. On Tuesday, the warehouse flags that a supplier's pallets arrive without labels. The issue reaches Tier 2 by 9:00 and purchasing calls the supplier that morning. Before tiered huddles, the same issue might have surfaced at a monthly meeting.

Keeping huddles effective

1. Start and end on time, standing up
2. Focus on exceptions, not reporting everything that went well
3. Every issue gets an owner and a date, or is escalated
4. Review the issues list for overdue items every day

A continuous improvement culture is built by what leaders do every day, not by what they say at town halls. Leader standard work makes those daily behaviours explicit and repeatable. Coaching routines then build problem-solving capability in every team.

What leader standard work looks like

Leader standard work is a short, written list of the routine activities each leadership level commits to, with times and frequency. The higher the level, the more of the time is flexible, but no level is exempt.

Coaching with questions

Toyota Kata, described by Mike Rother, offers a practical coaching routine. The coach asks a short set of questions regularly, often daily, to help the learner work toward a target condition through small experiments. A simplified version:

1. What is the target condition?
2. What is the actual condition now?
3. What obstacles are preventing you from reaching the target? Which one are you working on now?
4. What is your next step, and what do you expect to happen?
5. When can we see what you learned from that step?

The power is in the repetition. Over weeks, the learner builds a habit of scientific thinking, and the coach resists the urge to give answers.

Worked example

A plant supervisor coaches a line lead whose target is reducing minor stops on a packaging line. Each day at 2:00 p.m., they spend 10 minutes at the line board using the five questions. Early on, the supervisor notices the lead jumping straight to solutions. By asking "what do you expect to happen?" each time, the lead begins making predictions and checking them, and the experiments become sharper.

Making it stick

• Post leader standard work where others can see it
• Have each leader's manager check it periodically
• Protect coaching time on the calendar like any other meeting

Once a site or department has proven results, leaders naturally want to spread them. Scaling is harder than it looks. A solution that worked brilliantly in one place can fail in another because the context, people or volumes differ. Successful scaling spreads the thinking and the management system, not just the solution.

Strategy deployment (hoshin kanri)

Hoshin kanri, often called strategy deployment, aligns improvement work across the organization with a few breakthrough objectives. Its key practice is "catchball": objectives are passed down, teams respond with what they can contribute and what they need, and plans are adjusted until they are realistic and owned.

• Pick no more than three to five breakthrough objectives a year
• Translate each objective into measurable targets at each level
• Review progress monthly and adjust plans, not just report numbers

Three ways to spread a proven improvement

A practical scaling sequence

1. Document the improvement: problem, root cause, solution, results and standard work
2. Have the receiving team visit the original site and see it working
3. Let the receiving team run its own assessment and PDCA cycles
4. Assign a peer from the original site as a contact for questions
5. Track results at each new site separately

Worked example

An energy services company with three yards cuts truck loading time at its Alberta yard using shadow boards and standard loading lists. Leadership first orders the other yards to copy it. One yard adopts it quickly; the other struggles because its crews service a different equipment mix. The company switches approach: the struggling yard's crew visits, then designs its own loading standard using the same principles. Loading time improves there too, and the crew owns the result.

The lesson for SMEs: scale people's capability and the daily management system first, and solutions will follow.

You now have a complete framework for operational excellence: assess where you are, engage stakeholders, transform priority processes, and sustain and scale the gains through daily management and leadership routines. The final step is turning that framework into a concrete plan you can start on Monday.

The framework at a glance

A 90-day plan for an SME

1. Days 1 to 30, Assess: run the maturity assessment with a mixed group, do three gemba walks, map one value stream, establish baselines for two or three KPIs, and agree on a prioritized gap list.
2. Days 31 to 60, Engage and start: write the case for change, map stakeholders, charter one improvement project with a sponsor, and launch a Tier 1 huddle with one team.
3. Days 61 to 90, Transform and sustain: complete root cause analysis, run PDCA pilots, update standard work, introduce leader standard work for supervisors, and review results against the baseline.

Questions to answer before you start

• Who is the sponsor, and how much of their time is committed?
• Which one value stream will you assess first, and why?
• Which two or three KPIs will show whether you are making progress?
• How will front-line staff be involved from the first week?
• When will you review the plan, and who will be in the room?

Worked example

A 50-person precast concrete producer uses this plan. In month one, the assessment shows low scores in problem solving and performance measurement, and the value stream map points to long mould changeovers. In month two, the owner sponsors a changeover project and the yard starts a daily huddle. By day 90, changeovers are shorter, the huddle is catching material issues earlier, and the team chooses its next value stream.

Start small, start with facts, involve the people who do the work, and build the habit before you build the program.

Complete the final exam to earn your Chmltech certificate of completion, and revisit the labs as your operation matures.