ER inefficiency brief

Open your materials, follow the steps, then turn in your work.

Write a brief that identifies a specific ER inefficiency and frames it as a design problem.

1. Open your materials

Use the materials named in the first step below. Open lesson resources.

2. Start the work

Choose one bottleneck from your workflow as the target problem.

Show all 5 required steps
  1. Choose one bottleneck from your workflow as the target problem.
  2. Describe the inefficiency with specific, observable detail.
  3. Explain which stakeholders it harms, using your map.
  4. State the inefficiency as a one-sentence design problem.
  5. Submit the ER inefficiency brief as the weekly summative.

Lost your place? Confirm you have chosen one bottleneck from your workflow, described the inefficiency with specific observable detail, named which stakeholders it harms using your map, and stated it as a single-sentence design problem; then submit the brief as the weekly summative.

Check your work before submitting

  • Your brief names a specific, evidence-based inefficiency.
  • You can frame the inefficiency as a solvable design problem.

3. Turn in your work

DueCheck Schoology
Hand in
ER inefficiency brief: specific bottleneck observation, stakeholder harm linked to the map, and a one-sentence design problem statement.
How to submit and name your file

Use the submission route shown on today's page.

In Schoology, open your course and the assignment for this lesson. Attach your file, select Submit, and check that it appears in the submission.

PDF upload help

You get two school days for every day you were absent, so this deadline moves with you.

How this lesson connects

Keep using what you learned last class: Measure the wait before choosing the fix. Today: A design problem must be specific, observable, and tied to real harm so that it can guide a real solution, because a vague problem gives the designer nothing measurable to build or test against.

Optional: listen or watch a unit review
Optional unit study notebook
Designing a biomedical solution around real stakeholders and patient flow.
Open the notebook
Optional review video
Audio overviewVideo overviewMind mapStudy guideFlashcardsQuizData table
Need help? Warm-up, timing, and directions

💡 Big idea: A design problem must be specific, observable, and tied to real harm so that it can guide a real solution, because a vague problem gives the designer nothing measurable to build or test against.

  1. 0-10Review the brief rubric: what makes a design problem statement specific and evidence-based?
  2. 10-25Select the bottleneck: choose one from your analysis and describe it in observable detail
  3. 25-45Stakeholder harm analysis: explain which stakeholders are harmed using your map as evidence
  4. 45-60Draft the one-sentence design problem and check it against the rubric
  5. 60-75Submit the ER inefficiency brief as the weekly summative
  6. 75-80Self-assessment: rate your brief on specificity and evidence quality
Mr. Mendoza's 5-minute intro
  • This week you have built a stakeholder map, a patient-flow diagram, and a team contract.
  • Today you bring those tools together into an ER inefficiency brief -- the document that frames your design problem.
  • A brief is only as good as the evidence behind it, so every claim you make must trace back to something you observed or read.
  • This is also your first weekly summative: the quality of your brief sets the standard for the rest of Problem 1.
Know by the end
  • How to transform a bottleneck observation into a one-sentence design problem statement.
  • How to use your stakeholder map as evidence when describing who is harmed by the inefficiency.
  • What makes a design problem brief specific enough to guide solution development.

PLTW connection and today's work

Open Problem 1 in your myPLTW course shell and locate the brief or needs-assessment activity to review the expected format and evidence standards.

Today's stopping point: Use your stakeholder map and workflow diagram to connect the bottleneck and stakeholder harm in the ER inefficiency brief, today's weekly summative.

PLTW activity titles identify the course connection. If your account will not open, use the posted materials for today and tell Mr. Mendoza. Do not mark an online activity complete unless you completed it.

Course connection

  • Activity 1.1.1 Mission: Innovation

Use the turn-in directions at the top of this page. Do not create a second submission unless your teacher asks for one.

Show another explanation or a smaller first step

Need help? Choose a starting point

Need a running start
Warm up by taking the bottleneck from your workflow and adding one number or one observable detail to it, so your problem starts concrete instead of vague.
On track
Write the full brief: pick one bottleneck, describe the inefficiency with observable detail, use your stakeholder map to name who is harmed, and compress it into one precise design-problem sentence.
Stuck? Get unstuck
If you were out, take the bottleneck your group identified and write just the one-sentence problem statement naming the inefficiency and one harmed stakeholder. Use this starting point to rejoin, then complete the ER inefficiency brief.
Push me further
Write two versions of your problem sentence, one framed around speed and one around equity, and argue which framing will lead to the better solution, because how you state a problem steers every design that follows.
Lesson resources: reading, slides, and vocabulary
Socratic teaching slide deck

The deck carries the prior idea forward, lets you inspect an analogy, maps the rule to biology, and ends with the same evidence decision and exit ticket used on this page.

Generated from this lesson's canonical data with a red-team citation check.

Carry forward

Measure the wait before choosing the fix.

Daily take-home

A design problem must be specific, observable, and tied to real harm so that it can guide a real solution, because a vague problem gives the designer nothing measurable to build or test against.

Inspect the analogy

An engineering team tests one prototype feature at a time against a written criterion and records each failure before revising.

  1. Which criterion is being tested?
  2. What stays controlled between trials?
  3. Which result justifies a specific revision?
Rule

A useful prototype test links a controlled trial to a measurable criterion and turns the result into a documented revision decision.

Where it breaks

A classroom test can reveal a design weakness without establishing clinical , effectiveness, durability, or regulatory readiness.

Map the analogy to biology
  • The written criterion maps to the pass condition.
  • Repeated controlled trials map to test evidence.
  • The revision log maps to the next design change and its rationale.
Read this first

Driving question: You found the bottleneck and mapped who it hurts. Now write the one sentence that names your ER inefficiency so precisely that a stranger reading it knows exactly what to fix and who is being harmed by not fixing it.

What you already know: Measure the wait before choosing the fix.

New idea: A design problem must be specific, observable, and tied to real harm so that it can guide a real solution, because a vague problem gives the designer nothing measurable to build or test against.

Visual or model: F1. F1. Teaching model of routes from Entry to Discharge, with Exam and Imaging branches. What to notice: Trace Entry to Discharge on thick arrows; this model supplies no verified staff handoffs or measured bottlenecks.

  1. Observe or measure the relevant feature in ER inefficiency brief.
  2. Organize the observation with a stable evidence ID.
  3. Apply this rule: A useful prototype test links a controlled trial to a measurable criterion and turns the result into a documented revision decision.
  4. Choose the option the evidence supports and state the limit of the conclusion.

Real biomedical example: You found the bottleneck and mapped who it hurts. Now write the one sentence that names your ER inefficiency so precisely that a stranger reading it knows exactly what to fix and who is being harmed by not fixing it.

What the evidence supports: E1-E3 and F1 support the daily take-home when the response meets the stated success criteria.

What it cannot prove: The package does not support claims beyond this lesson's or any real patient diagnosis.

Vocabulary:
  • : Sorting patients so that limited staff, time, and supplies do the most good. In everyday emergency care that usually means the most urgent first, but in a mass-casualty event it means treating those who benefit most, which is not always the most badly injured.
  • stakeholder: Any person or group affected by a project or decision, such as users, patients, families, or the team building a solution.
  • : The ordered sequence of steps and handoffs used to carry a task from start to finish in a consistent, repeatable way.
  • constraint: A limit or requirement that a design must work within, such as a budget, available time, materials, or rules.
  • : The study of how people interact with tools, devices, and systems, used to design healthcare equipment and workflows that reduce human error.

Use it now: Choose one decision option. Cite E1 and E3, then explain how the rule connects the evidence to your choice.

Go further, optional: The source links below are optional enrichment. Every fact required for today's local evidence decision appears in this lesson package.

Evidence set and decision
E1 · Source fact

A biomedical design advances when test evidence is compared with explicit user needs, criteria, constraints, risks, and failure modes, then used to justify a documented revision.

Limit: A classroom prototype, , presentation, or does not establish clinical , effectiveness, manufacturing quality, or regulatory clearance.

E2 · Teaching model

A useful prototype test links a controlled trial to a measurable criterion and turns the result into a documented revision decision.

Limit: A classroom test can reveal a design weakness without establishing clinical , effectiveness, durability, or regulatory readiness.

E3 · Task criterion

Your brief names a specific, evidence-based inefficiency.

Limit: E3 defines the classroom product or success criterion. It is not independent scientific evidence and cannot justify a clinical or causal claim.

PLTW-BFH-2027-02-09 · Simulated classroom evidence scenario

Your role: biomedical design team member

Decision: Use today's evidence to practice a reasoned decision for your ER inefficiency brief. This practice is not a separate submission.

  • State that the ER is inefficient, because a broad problem sounds more important than one narrow complaint.
  • Hold the brief until you can attach a measured wait or count to the step you plan to name.
  • Write one narrow, observable sentence naming the delay, the step it happens at, and who it harms.

Response: Reasoning practice: State one choice, cite at least two evidence IDs, explain the rule that connects them, and add one limitation. Use this practice for today's final product; do not submit it separately.

Claim ceiling: Today's evidence supports a classroom claim about ER inefficiency brief. It cannot prove causation, diagnose a real patient, or justify action outside this room.

Composite case file · PLTW-BFH-2027-02-09

Reason for review: Use today's evidence to practice a reasoned decision for your ER inefficiency brief. This practice is not a separate submission.

Context: A well-framed design problem is specific, observable, and tied to real stakeholder harm, because vague problems can only produce vague solutions.

Timeline:
  • T1: Choose one bottleneck from your as the target problem.
  • T2: Describe the inefficiency with specific, observable detail.
  • T3: Explain which stakeholders it harms, using your map.
  • T4: State the inefficiency as a one-sentence design problem.
  • T5: Submit the ER inefficiency brief as the weekly summative.
Evidence records:
  • E1: A biomedical design advances when test evidence is compared with explicit user needs, criteria, constraints, risks, and failure modes, then used to justify a documented revision.
  • E2: A useful prototype test links a controlled trial to a measurable criterion and turns the result into a documented revision decision.
  • E3: Your brief names a specific, evidence-based inefficiency.

Measurements: Use only the measurements, units, graph, or counts supplied in today's task. No additional patient measurement is implied.

Figure finding: Teaching model with six route nodes ending at Discharge and thick route arrows; thin staffing and human-factor lines are separate. It does not show verified staff handoffs or measured bottlenecks.

Uncertainty: This is a composite classroom scenario. Missing history, measurements, or confirmation tests remain unknown and limit the conclusion.

Math moment
Formula or setup

Mean = sum of values / number of values. Median = middle ordered value. Range = maximum - minimum.

Worked parallel example

For 2, 4, 4, and 10: mean = 20 / 4 = 5, median = 4, and range = 10 - 2 = 8.

Units and reasonableness

Mean, median, and range keep the measurement unit. Order the values before finding the median.

Try it with today's data

Calculate the requested summary for today's supplied values, then write what it reveals and what it hides.

Design record
Criteria
  • The solution must address the stated need in ER inefficiency brief.
  • The decision must be supported by E1-E3.
  • The final product must make the success criteria visible.
Constraints
  • Complete the work inside the 80-minute block.
  • Use only supplied or teacher-approved materials and evidence.
  • Do not trade , accessibility, or privacy for speed.
Tradeoff weights
  • and evidence quality: must pass before scoring other criteria.
  • User need and effectiveness: highest scored criterion.
  • Time, cost, and ease of use: compare only after and effectiveness pass.

Test evidence: For each option, record the E1-E3 result that supports or fails each criterion. Do not assign a score without a named observation.

Iteration log
  1. Version or option tested
  2. Criterion met or missed
  3. Evidence ID and result
  4. Revision made
  5. Reason for the revision
Decision record
  1. Need and user
  2. Criteria and constraints
  3. Chosen option and evidence
  4. Test result
  5. Revision and reason
Watch the trap

Students often think Students think a bigger, broader problem statement is a stronger one, so 'the ER is inefficient' sounds more important than a narrow claim.. The trap: The trap is that a broad statement gives a designer nothing to build toward, because you cannot solve 'inefficient' but you can solve 'one nurse creates a 45-minute wait for the sickest arrivals.' Specific and observable beats big, since a problem you can measure is a problem you can test a solution against.

Worked example · a parallel case (guides, does not reveal)
Worked brief
Completes: A parallel-case model that pins down one observed inefficiency in a school health office, links it to the stakeholders it harms, and reframes it as a one-sentence design problem, so students can copy the format without copying the answer.

Worked brief: school health office. Illustrative scenario only. The 12-minute wait and 4-minute goal are sample values, not verified school records. Use the structure, not this content, for your ER brief.

Observation: In this example, scheduled medication visits average 12 minutes; one nurse also handles walk-ins, calls and cabinet access.

Stakeholders: Late doses and missed class affect students; interrupted lessons affect teachers; competing tasks affect the nurse.

Bottleneck hypothesis: Cabinet access may limit the workflow because each scheduled dose depends on one nurse. This description alone cannot prove it is the highest-impact cause.

One-sentence design problem: Design a midday medication workflow that meets a 4-minute goal during a fixed window, reducing missed class time without hiring a second nurse.

Limit: Four minutes is a design target to test, not a medical rule or a proven safe standard.

Why this matters

This model shows the level of evidence and organization needed to complete: A parallel-case model that pins down one observed inefficiency in a school health office, links it to the stakeholders it harms, and reframes it as a one-sentence design problem, so students can copy the format without copying the answer.

Build yours step by step
  1. Write one defensible claim.
  2. Choose specific evidence that supports the claim.
  3. Explain the scientific rule that connects the evidence to the claim.
Change it for a new task

Keep the structure. Replace the question, facts, measurements, and evidence. Then recheck units, vocabulary, and whether the conclusion goes beyond the evidence.

Also due today: Submit the ER inefficiency brief on Schoology.

See the full worked example
Portal terms
CER:
Claim, Evidence, Reasoning: make a claim, back it with evidence, explain your reasoning.
SOP:
Standard Operating Procedure, the exact steps to follow (especially in a lab).
Tracker:
Your PLTW progress log where you record completed evidence.
myPLTW:
The PLTW course site where you do the online activities. Find it in Clever with your Microsoft sign-in, right next to Schoology.
This unit's vocabulary

Tap the speaker to hear a term. Add two of these to your notebook glossary with a definition and an example in your own words.

Build your vocabulary · optional, for extra credit

Pick just 2 or 3 words from today and make them yours: write what each one means in your own words, name the context clue or evidence that helped, then give one example from what you actually did in ER inefficiency brief. Try your own words first; the glossary is there if you get stuck. This is voluntary and counts as extra credit, so keep it short.

triage
stakeholder
workflow
constraint
human factors

Saved on this device. Show Mr. Mendoza or add these to your notebook glossary to claim the extra credit.

Teacher-posted resources

Classroom documents for this lesson are posted in Schoology. Open Clever, then Schoology, and find each one by the name shown on its card.

Use during lessonFor: Everyone
BI Activity 1.1.1 Mission: Innovation
worksheet/handoutPosted in Schoology
Open in Schoology

Open this when the class reaches this activity and use it to complete the required lesson artifact.

Placement rationale

Matched Emergency room design and by path:Biomedical-Innovations/Problem-1_Emergency-Room/1.1_Emergency-Room; keywords:er design. Score 138. Visibility: student-schoology (student-facing resource; link through Schoology rather than local path).

Use during lessonFor: Everyone
PLTW BI Activity 1.1.3 Emergency Care Admission Forms
worksheet/handoutPosted in Schoology
Open in Schoology

Open this when the class reaches this activity and use it to complete the required lesson artifact.

Placement rationale

Matched Emergency room design and by path:Biomedical-Innovations/Problem-1_Emergency-Room/1.1_Emergency-Room; keywords:triage, admission. Score 138. Visibility: student-schoology (student-facing resource; link through Schoology rather than local path).

Use during lessonFor: Everyone
PLTW BI Problem 1.1.4 Patient Data Chart Template
worksheet/handoutPosted in Schoology
Open in Schoology

Use this as the classroom resource for Emergency room design and .

Placement rationale

Matched Emergency room design and by path:Biomedical-Innovations/Problem-1_Emergency-Room/1.1_Emergency-Room; keywords:triage, er design. Score 138. Visibility: student-schoology (student-facing resource; link through Schoology rather than local path).

Sign in to Clever with your district Microsoft account to open Schoology or myPLTW. Follow today's posted steps. If myPLTW will not open, use the posted alternative and tell Mr. Mendoza. Turn in your completed work through the Schoology assignment.

Practice: try a question, then check your answer

Claim ceiling for this check: Today's evidence supports a classroom claim about ER inefficiency brief. It cannot prove causation, diagnose a real patient, or justify action outside this room.

Quick self-check · commit, then reveal

Rewrite this weak problem statement to make it usable: 'The waiting room is a mess and people are unhappy.' Add specificity, observability, and a named stakeholder.

How sure are you?

Write an answer and pick a confidence to unlock the key.

Cumulative WebXam review · flash practice

Fast retrieval with instant answers, not the commit-then-reveal check above. Try each from memory first: write what you remember about the earlier units, then check yourself here.

Tap an answer to check it · nothing is recorded or graded
[Review: Orientation: how we learn in Biomedical Innovations] What is the WebXam?
[Review: Orientation: how we learn in Biomedical Innovations] What is the WebXam?
[Review: Launching Biomedical Innovations: safety, your design notebook, and the SDS] In which cabinet should you store rubbing (isopropyl) alcohol?
What is the proper method for maintaining the integrity of a clean room?
Missed class or ready for more?
Where this leads: careers
What to do if you were absent
If YOU are absent

Today is individual work you can do from home: complete the same target above, then submit your ER inefficiency brief.

FOR A GRADE
Open Schoology

Go to Schoology to turn this in. Submit one PDF. Put your first and last name in the document header. Name the file: FirstName LastName - Assignment Title - YYYY-MM-DD.pdf. If you cannot get in, see Mr. Mendoza. Do not skip the work.

If MR. MENDOZA is absent

Class still runs. Complete the online activity above (it's self-guided). Need the concept taught without a teacher? Use this authoritative explainer:

CDC Emergency Department Data
How this is graded
For: CER: ER inefficiency brief: specific bottleneck observation, stakeholder harm linked to the map, and a one-sentence design problem statement.
  • Complete
    Every required part of the artifact is present, nothing left blank.
  • Accurate
    The science and the data are correct and match the evidence.
  • Scientific reasoning
    You explain your claim with evidence and reasoning (CER), not just an answer.
  • Professional communication
    Clear, organized, labeled, and written the way a clinician or scientist would.
  • Submitted
    Go to Schoology to turn this in. Submit one PDF. Put your first and last name in the document header. Name the file: FirstName LastName - Assignment Title - YYYY-MM-DD.pdf. If you cannot get in, see Mr. Mendoza. Do not skip the work.