Map the process as it currently happens
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
Process improvement studies repeated work rather than the schedule of a one-time project. The first map should show current reality, including waits and returns, before proposing a better version. A clear start and finish make observations comparable. This course follows a fictional community program’s confirmation process; all records and measurements are supplied for desk-based practice.
A process repeats; its map shows how an input becomes an accepted output.
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
State the start event, end event, input and acceptable output in one sentence each. Use the supplied definition of a correct confirmation so later measures refer to the same result.
- 2
Draw each current activity in sequence and label the role performing it. Add a decision for missing information and another for a failed final check, with arrows showing where work returns.
- 3
Mark handoffs and any waiting places separately from active work. Do not replace the current process with your preferred future design before observing where the current difficulties occur.
- 4
Test the map with one complete request and one missing its location. Trace both routes and revise any arrow or decision that fails to explain how the request reaches an accepted output.
See how it works.
Fictional practice: Fern Program processes workshop requests. The process starts when a request arrives and ends when a correct confirmation is released. Current stages are intake, completeness check, entry, final check and release. If location or time is missing, the completeness check returns the request to intake for clarification; if final checking finds an error, it returns to entry. The learner draws those loops instead of hiding them in a single “process request” box. Correct means the confirmation contains the requested workshop, approved time and location exactly once. Event delivery itself is outside this process boundary.
Did you cover these?
- The map begins with receipt and ends with correct release.
- Both missing-input and final-error loops are visible.
- The correct-output definition names workshop, time, location and no duplicate.
What to finish
A current-state confirmation-process map with clear boundaries and two rework loops.
Watch for this
Drawing an ideal process that hides the actual waiting and correction work.
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 the public article and read its four-step procedure and small-scale testing description. Optional commercial training links appear on the page; none are required. No ASQ certification is implied.
Access: Public explanation is free; linked training, books or certification may require payment and are optional.
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.