Build a small baseline with clear definitions
See this course’s project requirements
Collect and revise all six lesson outputs into a fictional process-improvement plan. Show how the process works now, starting measurements, a possible cause of the problem, a Plan-Do-Check-Act test, a review of the results, and checks to keep the improvement working. Label it as fictional practice.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Map the bounded current process with decisions and rework.
- Calculate baseline capacity, elapsed time and first-pass accuracy.
- Document a cause hypothesis and one targeted improvement.
- Plan, perform and evaluate the supplied ten-request paper PDCA test against predefined measures; preserve the row-level record and the separate unknown-location exception test.
- Assemble a control plan with ownership, triggers and a response to a failing sample.
Review and revise
Use these criteria to check your work and choose what to improve.
- Accuracy: amounts, classifications and decisions agree with the supplied evidence and stated assumptions.
- Reasoning: each important choice names the rule, observation or comparison that supports it.
- Responsible scope: the packet protects information, respects authority limits and routes unresolved concerns appropriately.
- Usability: a new reader can follow the ordered lesson outputs, identify ownership and see what is complete or still uncertain.
Want more background?
The idea in everyday life
One number rarely explains process performance. Active work time differs from total elapsed time, capacity differs from actual demand, and a corrected output differs from one that was right initially. Define each measure before collecting it. A small baseline can reveal where to investigate, but its size and conditions limit what you can conclude.
Measure speed, capacity and correctness separately because they answer different questions.
One step at a time.
Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.
- 1
Write operational definitions for active time, elapsed time, capacity and first-pass accuracy. State what starts and ends timing, and whether an output corrected later counts as initially correct.
- 2
Calculate each stage’s hourly capacity as sixty divided by its minutes per request. Identify the lowest stage capacity and compare it with the supplied arrival rate under the one-worker assumption.
- 3
Add the active and waiting times for the sample request. Keep the elapsed-time result separate from the stage-capacity calculation; a request’s journey and the line’s throughput are different measures.
- 4
Create a check sheet for the ten baseline requests with seven first-pass successes and three corrections. Calculate the proportion and label the small sample and supplied operating assumptions.
See how it works.
Fictional practice: Fern’s four staffed work stages take 2, 6, 3 and 2 minutes per request; release is included in the last stage. With one worker per stage and steady work, the six-minute completeness check has capacity for 10 requests per hour. The other capacities are 30, 20 and 30. Demand is 12 per hour, so the queue can grow by two per hour under these simplified assumptions. A sample request has 13 active minutes and 17 waiting minutes, totaling 30 elapsed minutes. In a separate ten-request baseline, seven pass the final check initially and three need correction: first-pass accuracy is 70%.
Did you cover these?
- Stage capacities are 30, 10, 20 and 30 requests hourly.
- The bottleneck is the six-minute check and demand exceeds it by two hourly.
- Elapsed time is 30 minutes and first-pass accuracy is 7/10.
What to finish
A baseline sheet with stage capacities, elapsed-time calculation and 70% first-pass accuracy.
Watch for this
Confusing total process time with throughput capacity or counting corrected work as first-pass success.
How can I tell I understand it?
You can demonstrate all three checks and explain the evidence behind your choices without consulting the worked example.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-10
Opened and read routing, workflow mapping, bottlenecks and scheduling in service and production settings. No textbook case studies or exercises are reproduced.
Access: Free page readable without an account; optional further study only.
Reuse: Reference for original Life Starter instruction. Free access does not grant unrestricted reuse; no source exercises, logos or syllabi are copied. Check the source license before redistributing its material.
Source & access notes · checked 2026-09-10
Opened and read check sheets, cause-and-effect tools and comparison with historical process performance. Course thresholds are fictional action triggers, not statistically calculated control limits.
Access: Free page readable without an account; optional further study only.
Reuse: Reference for original Life Starter instruction. Free access does not grant unrestricted reuse; no source exercises, logos or syllabi are copied. Check the source license before redistributing its material.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.