Continuous Improvement Event Room

Prepare one focused improvement event Fictional example: Northstar Works is examining delays between completed assembly and parts staging. Use this page to frame the question, guide the discussion, and hand off what the team learns; it is not an operating or safety procedure. Set the boundary before the discussion Name the process, observation window, participants, and limits. Event question: What is happening between an assembly batch being marked complete and the associated parts reaching staging? Illustrative scope: Review one agreed sample window on a defined line and trace the handoff from batch completion to staging arrival. Include people who perform or coordinate those steps across the shifts represented in the sample. Out of scope: Do not use this event to change product specifications, equipment settings, controlled work instructions, or safety-critical work. For regulated, safety-critical, or sensitive topics, follow the approved local reference and involve the trained role responsible for that domain. Illustrative 90-minute agenda Sample time boxes for planning; adapt the sequence to the event's approved scope. Time Part Purpose and output 0–10 min Frame the observation Agree the question, sample window, and what is outside scope. 10–30 min Map current work Mark the handoff points and note differences participants can verify. 30–50 min Choose a bounded trial Describe one reversible, in-scope change and the condition it will be compared with. 50–70 min Review evidence Check the same defined measure in both conditions and record relevant context. 70–90 min Agree the handoff Summarize findings, name the next-review owner role, and capture unresolved questions. Prompts that keep the conversation grounded Ask for something a participant can point to, describe, or verify. Separate observation from interpretation Ask, “What did we directly see or record, and during which sample window?” Example observation: “Three staging requests arrived after the assembly batch was complete during the sample window.” “Staging is always late” is an interpretation until the team checks broader evidence. Surface shift differences Ask each represented shift to describe the same handoff: what signal starts it, what information travels with it, and where the next person can see that it is ready. Keep the trial bounded Ask, “What is the smallest in-scope change we can compare, and what must stay unchanged for the comparison to be useful?” Route any proposed change affecting controlled or safety-critical work through the applicable approved process. Compare like with like Define the measure and observation window before the trial begins. Write the comparison before collecting For the Northstar Works example, the team could define elapsed minutes from batch completion to staging arrival for a stated sample of completed batches. The measure, start and end points, sample window, and source of each observation should be agreed before comparing conditions. Use the same start point, end point, and recording method in both conditions. Record the sample size and observation window beside the result. Note context that could affect interpretation, such as a shift change or an unusual interruption. Report evidence separately from explanation A comparison can show what was recorded; it does not by itself establish why a difference occurred. Keep observations, interpretation, and the next question visibly distinct. Evidence: “For the defined sample, the recorded elapsed minutes were lower in the trial condition.” Context: “The comparison covered one sample window on the selected line.” Open question: “Would the same pattern appear on another shift or in another window?” Prepare the sustainment handoff Leave the next role with a clear account of what was tested and what remains unknown. Summarize the bounded change State what changed, where and during which sample window. Keep the description specific enough for the next reviewer to understand the comparison. Record evidence and limits Include the measure, comparison conditions, sample size, observation window, relevant context, and any limits on what the evidence can support. Name the next-review owner role Identify the role responsible for reviewing the evidence and the point at which that review should occur; do not imply the review has already happened. Check before broader use List the applicable approved references and domain-owner questions that must be addressed before anyone considers extending the change to another line, shift, plant, or supplier. Carry forward open questions Record what the event did not resolve and route those questions to the relevant domain owner through the organization's established process. Ownership and limits Content owner: Manufacturing Operations and Quality. Local domain owners determine which approved references and handoffs apply to their work and location. This event-room page is an authored reference, not a system of record, live work queue, approval, or substitute for an approved operational procedure. Treat agenda timings and the Northstar Works example as illustrative coordination material, not measured results or required standards.