Engineering Design Challenge: Optimizing Clinic Flow (Systems Engineering)

Universal Lesson Context: This lesson is designed as a simulation and design challenge. In a classroom setting, learners can be grouped to fill the roles. In a homeschool/small group setting, the learner can cycle through the roles, or a parent/facilitator can act as the "patients" while the learner acts as the engineer/data collector.

Materials Needed

• Paper and drawing utensils (markers, pens, colored pencils)
• Sticky notes or index cards (for labeling stations)
• Stopwatch (a phone application works well)
• Ruler or straight edge (for drawing flowcharts)
• Scenario Map Template (a simple drawing of 4-5 connected boxes representing clinic stations)
• Data Collection Sheet (a simple table template for timing 5 "patients")

Introduction: The Bottleneck Busting Challenge

Hook: How Long Do You Wait?

Think about the last time you had to wait in a long line—at the DMV, the grocery store, or a doctor's office. How did that wait make you feel? Frustrated? Bored? In the world of systems engineering, those long waits aren't just inconvenient; they're expensive and they erode customer (or patient) trust. Your job today is to fix a system that is failing its users.

Learning Objectives (By the end of this lesson, you will be able to):

1. Define the concept of a "bottleneck" in a process flow.
2. Apply the Observe, Analyze, Design, Implement (OADI) model of systems engineering.
3. Collect and analyze basic time-motion data to identify system inefficiencies.
4. Design a low-cost, low-complexity solution to improve patient satisfaction and flow.

Success Criteria

You have successfully completed this challenge if your proposed redesign achieves two goals:

• The redesigned flow reduces the average patient total visit time by at least 20%.
• The solution relies on changing the process (flow/protocol), not purchasing expensive new technology or hiring new staff.

Body: The Systems Engineering Process

I Do: Modeling the Problem (The Baseline)

Context: You are systems engineers studying the "Midtown Wellness Clinic." Leadership reports that the average patient visit takes 90 minutes, and patients are complaining. We must establish a baseline first.

The Baseline Clinic Flow (Draw this simple map):

1. Arrival/Reception (Station 1): Check-in, verifying insurance, collecting co-pay.
2. Triage/Nursing (Station 2): Weight, height, temperature, patient history update.
3. Physician Exam (Station 3): 1-on-1 time with the Doctor.
4. Checkout/Scheduling (Station 4): Scheduling follow-up, final billing.
5. Exit.

Instruction (Modeling Data Collection): We need to measure the baseline cycle time. I will show you how to act as the Data Collector/Timer. For each "Patient" (represented by a sticky note or role-player), you will start the timer at Arrival and record the time spent *waiting* and *processing* at each station until they Exit. I will model timing one patient flow completely, verbally narrating where the delays occur.

We Do: Baseline Measurement and Analysis

Activity 1: Baseline Simulation Run

Roles (If solo, use tokens/objects as patients; if in a group, assign roles):

• Patients (x5): Start at Station 1.
• Clinic Staff (1 person per station): Move the patients/tokens through the process.
• Data Collector/Timer (Engineer): Measures and records time for all 5 patients.

Simulation Rules: Clinic staff can only handle one patient/token at a time. If a station is busy, the patient must wait.

Guidance: Run 5 patients through the baseline flow. Record the time (in seconds/minutes) for each step and the total time. Calculate the average total visit time for the 5 patients. (This average is your critical baseline measurement).

Activity 2: Bottleneck Identification (Analyze)

Discussion & Analysis: Review your data. Where did the longest waits occur? Where was the process slowest?

• If all 5 patients waited longest at Station 3 (Physician), that is the bottleneck.
• If most patients waited longest at Station 2 (Triage) because the nurse was also handling phone calls, that is the bottleneck.

Formative Assessment Check: Ask: "Based on our data, which single station, if improved, would have the biggest impact on the total patient time?" (The bottleneck should be clearly identified.)

Transition: Now that we know the problem, we must apply engineering creativity to solve it under budget!

You Do: Redesign and Proposal

Activity 3: Constraint-Based Design (Design)

The Goal: Redesign the clinic flow to eliminate the bottleneck and meet the 20% reduction goal, strictly using only low-cost changes (e.g., changing location, changing staff order, using simple paper forms). We cannot buy new X-ray machines or hire a second doctor.

Brainstorming Prompts (Think-Pair-Share/Self-Reflection):

• What if we did the check-out process before seeing the doctor?
• Could the basic triage data (weight/height) be collected in the waiting room by a family member or using a self-service kiosk (a sheet of paper)?
• Could two activities happen simultaneously instead of sequentially?

Activity 4: The Redesign Simulation Run

Instruction: Draw your new process map, showing the optimized flow (e.g., Stations 1, 2, 3, 4 may be in a different order or combined). Run 5 new patients through your redesigned flow, collecting data exactly as you did before.

Data Comparison: Calculate the average total visit time for the redesigned system. Compare it to your baseline average.

Activity 5: Engineering Proposal (Implement/Present)

Prepare a brief report (or oral presentation) to the clinic leadership detailing your findings and proposal.

Your Proposal Must Include:

1. The average baseline time vs. the new average time (Show the percentage reduction).
2. A clear drawing of the new, efficient process flow.
3. A brief justification explaining why this redesign is low-cost and sustainable (i.e., "We utilized existing staff by cross-training the receptionist to pre-screen data, eliminating the nurse bottleneck").

Conclusion: Reinforcement and Feedback

Recap: Systems Thinking

We started by feeling the pain of waiting and ended by fixing the system. Remember, systems engineering is less about fixing individual machines and more about optimizing the flow and relationship between all the moving parts (people, information, and equipment). We used data (time) to identify the problem rather than just guessing.

Assessment (Summative Evaluation)

The learner submits or presents their proposal from Activity 5.

Grading Focus:

• Did the redesign meet the success criteria (20% time reduction and low cost/complexity)?
• Was the new process flow logically documented and justified by the data?

Differentiation and Extension

Scaffolding (For learners needing more structure):

• Provide the initial data sheet template pre-labeled with the calculation columns (e.g., Total Time, Average Time).
• Restrict the redesign options to only two variables (e.g., only change the order of stations 1, 2, and 4; do not combine them).

Extension (For advanced learners or longer engagement):

• Cost Analysis: Assign a dollar value to the physician's time ($2/minute) and the patient's time ($0.50/minute). Calculate the estimated annual savings of their redesign, justifying the implementation.
• Risk Assessment: Identify one new risk or problem their redesign might create (e.g., moving triage forms to the waiting room might increase data entry errors) and propose a mitigation strategy.