Foundations of Lean Six Sigma and Operational Excellence

Review questions

Integrated Summary: Foundations of Lean Six Sigma and Operational Excellence

The first subject brings four lines into one picture: selecting an improvement lens, seeing value and waste end to end, understanding flow and capacity, and then reading variation to select a worthwhile opportunity. The governing idea is that the problem comes before the tool. Lean, Six Sigma, Lean Six Sigma, and operational excellence are not interchangeable labels or certifications awarded by this program. Lean helps expose value, waste, and flow; Six Sigma emphasizes variation and data-based process performance; Lean Six Sigma combines the perspectives when the problem needs both; operational excellence places improvement in a broader system of leadership, behavior, monitoring, and continuous learning.

DMAIC provides a structure that helps prevent a jump from complaint to solution: Define clarifies the problem, customer, scope, and outcome; Measure understands the current process and builds a trustworthy baseline; Analyze tests causes; Improve develops and tests solutions; Control sustains gains and responds to drift. Every project does not require every tool, and every problem does not require a full DMAIC project. The level of method should match complexity, risk, and the need for learning.

From a Lean perspective, value is defined from the viewpoint of the recipient. Examine each step and ask whether it changes the output in a way the recipient needs, whether it does not create core value but is currently necessary for safety, control, or enablement, or whether it is unnecessary non-value-adding work and therefore potential waste. Duplicate entry, unnecessary waiting, rework, and excess handoffs are common examples, but classification is contextual. Do not automate a step before asking whether it should exist at all.

The value stream broadens the view from one step or department to the entire journey from request to delivery. Every department can appear fast while work waits hours or days between them. Separate active processing time from the elapsed time experienced by the customer. If active processing takes 12 minutes and the request then waits two days, twelve minutes does not describe the full customer experience. Saving one minute inside a step may matter less than removing a day of waiting between steps.

Flow is affected by the bottleneck. In the example with demand of 25 cases/day and stage capacities of 40, 22, and 35, the 22-capacity stage is the initial constraint. Assuming reasonably stable demand and capacity and no rework or downtime, backlog could theoretically grow by about 25−22=3 cases/day. Raising stage 1 from 40 to 50 does not remove this constraint. Effective capacity can, however, differ from nominal capacity because of downtime, rework, and case mix, and the constraint can move after improvement, so measurement must continue.

Pull connects work release to downstream need and capacity instead of pushing unlimited batches forward. A team can start with a work-in-progress limit and adjust it from observed waiting, completion time, backlog, and starvation. There is no universal number for every process. Keeping every resource 100% busy is not an independent goal if it creates queues and damages system flow.

Variation adds information that an average alone can hide. The observations 10,10,10,10 and 4,8,12,16 both average 10, but their ranges are 0 and 12. These are descriptions of a small sample, not evidence of Cpk, sigma level, or a specific cause. Process capability requires suitable data, specification limits, and assumptions that will be examined in later subjects. Here the useful questions are: how does performance differ, is the measure consistently defined, and which conditions or inputs recur with the pattern?

When selecting an improvement opportunity, do not start with the name of a tool or a favored solution. Look for customer or process impact, recurrence or severity worth attention, a measure that can support a baseline, and a scope the team can influence. A rare problem can move up in priority if its potential consequence is severe; a recurring problem can be important when its effect is clear and measurable. A statement such as “18% of requests in last month’s sample were returned for missing fields, extending response time; the cause has not yet been established” is stronger than “we need more training” because it separates the problem from the remedy and leaves analysis open.

For transfer to practice, choose a simple process and work through this sequence: define the recipient and value, map steps and waiting, classify waste and necessary work, separate processing from elapsed time, compare demand with capacity to identify an initial constraint, observe variation, then write a measurable problem and clear scope before selecting the improvement method. This sequence turns tools from a memorized list into means serving a decision grounded in process understanding.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

Question 1A process has long waiting and many handoffs between teams, while processing time inside each step is relatively stable. What is the most useful starting lens? Lean, focusing on waste and flow. Six Sigma only, because every problem requires variation analysis. Calculate a sigma level immediately. Buy an automation tool before mapping the process.
Question 2Which description best represents Lean Six Sigma in this program? An external certification awarded by this subject. A disciplined combination of waste/flow and variation/data perspectives as the problem requires. Using every Lean and Six Sigma tool in every project. Another name for operational excellence with no scope difference.
Question 3In DMAIC, what is the closest role of the Measure phase? Approve the final solution before collecting data. Sustain the improvement after implementation. Understand the current process and build a trustworthy baseline. Select the root cause by intuition.
Question 4Which statement best distinguishes operational excellence from a single improvement project? It is the name of one statistical test. It ends as soon as one quick gain is achieved in a single step. It means cost reduction only, regardless of quality. It connects continuous improvement with leadership, behavior, systems, monitoring, and sustained results.
Question 5In a service process, which step is the clearest example of potential waste? Re-entering the same data into a second log without a need. Resolving the problem requested by the customer. A currently required safety verification before execution. Sending the final result to the customer.
Question 6What does “non-value-adding but currently necessary” mean? A step the team likes even if it does not serve the process. Any automated step. A step that does not create the recipient’s core value but is currently required for safety, control, or enablement. Every step taking less than one minute.
Question 7Why does value-stream thinking look from request to delivery instead of measuring each department in isolation? Because every department must have the same speed. Because major waste can sit in waiting and handoffs between departments even when each looks efficient alone. Because mapping removes the need for data. Because the customer cares more about the number of departments than completion time.
Question 8Which example best represents pull logic? The upstream unit starts every available request regardless of review capacity. Work is sent in larger batches to keep the next department busy. New work starts on a fixed monthly schedule even when queues accumulate. New cases are released when the downstream stage signals need and capacity under an agreed rule.
Question 9Daily demand is 25 cases and three stage capacities are 40, 22, and 35 cases/day. What is the initial constraint? Stage 1 at 40. Stage 2 at 22. Stage 3 at 35. There cannot be a constraint because total capacity exceeds demand.
Question 10In the same case, stage 1 capacity rises from 40 to 50 while stage 2 remains at 22. What is the most likely effect? System capacity automatically rises to 50. Variation disappears completely. Work may reach the stage-2 queue faster without increasing system flow. The need to measure rework decreases.
Question 11An employee actively processes a request for 12 minutes, but it waits two days before the next step. Which statement is most accurate? The customer time is only 12 minutes. The two days are active processing time. The 12 minutes are part of active processing, while elapsed time also includes waiting. Processing and waiting cannot be compared in the same process.
Question 12Which rule is closest to a pull system? Start all available work each morning. Release new work when downstream work falls below an agreed limit and capacity is signaled. Increase batch size whenever backlog grows. Keep every resource 100% busy regardless of the queue.
Question 13Team A records 10,10,10,10 minutes. Team B records 4,8,12,16 minutes. Which conclusion is supported? Both means are 10, but the observed spread is larger in team B data. Team B definitely has a lower Cpk. Team A operates at Six Sigma. Training is the cause of team B variation.
Question 14The same error repeats across different employees and shifts. What is the strongest process-thinking question? Which employee should we punish first? Which process conditions, inputs, or rules recur with the error? How can we prove the cause is personal before measuring? Can we remove all controls immediately?
Question 15Which is the strongest starting improvement opportunity? A new-tool idea with no defined problem. A rare cosmetic complaint with no known impact. A recurring customer-impact problem with an initial measure and a scope the team can influence. A solution chosen by the manager before current performance is known.
Question 16Which statement is a better problem definition than a preselected solution? We must buy a new system immediately. Everyone must be trained because people cause the error. The approval must be removed because it is slow. 18% of requests in last month’s sample were returned for missing fields, extending response time; the cause has not yet been established.