Toyota Lets Anyone Pull the Cord. Your Clinic Can, Too.
Five everyday ways to let anyone flag a small problem early, and to make sure help comes before the patient moves on.
What you’ll take away
- The problem
- A small problem passed forward grows into rework later, and people often stay quiet when flagging it feels risky or nobody is free to help.
- What to remember
- A flag works when two things are true: anyone may raise it, and someone comes to help settle it where it started.
- What to do differently
- Agree on what counts, give everyone one way to flag it, name who answers each session, and settle it before the patient moves to the next step.
A small problem passed along doesn’t stay small. A missing site photo. A specimen jar that doesn’t match its requisition. When the schedule is tight, the easy move is to keep things moving and let someone downstream sort it out. Then the problem ambushes the dermatologist in the exam room, or turns up days later on a pathology report, and the fix means redoing work that was built on top of it. Flagging it early feels risky when you aren’t sure it counts, and pointless when nobody is free to help. People speak up early when two things are true: they’re allowed to, and someone comes. Toyota builds both into the way it makes cars.
The team member says: “That bolt won’t seat.”
Notice. A bolt won’t seat at her station. Passed along, the next steps would build right over it.
The team member says: “Pulling the cord. I need a hand.”
The team leader says: “Right here. Show me.”
Signal brings help. Her pull lights her station on the board, and the team leader comes straight there to help.
The team member says: “Now we can build on it.”
The team leader says: “Seated. Good catch.”
Resolve at the source. Fixed within the station’s time, production carries on. If not, the line pauses right there until it is.
On a Toyota assembly line, anyone who spots a problem can pull a cord. Toyota names in advance what counts: a quality problem, an equipment problem or work falling behind. A pull lights up a signboard, the andon, so the team can call the person in charge.1, 2 Toyota calls the idea jidoka, loosely “automation with a human touch”: stop when something is wrong, make it visible, and fix it before it moves on.1
The pull is a call for help, not an emergency brake. Toyota’s UK magazine describes how it works at the company’s Burnaston plant. A pull lights that station’s number on the board, with a chime and a flashing light, and the team leader comes straight there to help.2 Each station has a set window, its process time. If the problem is fixed inside that window, production carries on and the line doesn’t stop. If not, the line pauses until the problem is solved, and a second pull restarts it.2 Either way, the problem doesn’t travel on.
Stopping can look expensive. Toyota’s UK magazine admits that stopping a line “seems like a costly measure,” in time and in productivity.2 The company’s answer is that sorting problems out where they occur keeps a defective part from “finding its way into a finished vehicle,” and that clearly flagging each problem builds quality in, keeps it from coming back and, in the long run, saves time.1, 2
Pulling is only half the move. The other half is the team leader who shows up. A flag with nobody on the other end is just decoration.2 The cord is the visible part. The promise behind it is what matters: if you pull, someone comes.
Principles of Excellence
- Anyone can raise the signal. On the line, the person who spots the problem is the one who pulls the cord.1, 2
- What counts is agreed in advance. Toyota names the triggers: a quality problem, an equipment problem or a work delay. Nobody has to decide alone, in the moment, whether it’s big enough.1
- The signal brings help to the spot. A pull lights that station on the board and brings the team leader straight there. A flag with nobody on the other end is just decoration.2
- Fix it in time, or pause right there. Fixed within the station’s process time, production carries on. If not, the line pauses until the problem is solved, so it doesn’t ride on to the next step.2
- Each pull teaches. Toyota says making each problem visible lets it build quality in and keep the same problem from coming back.1
5 Exceptional Practices for your Clinic
- Agree in advance what counts as a flag. With your medical director and practice manager, pick a short list: a missing biopsy-site photo, a specimen jar that doesn’t match its requisition, a medication list that doesn’t match the chart, or a new or changing spot mentioned at checkout. Then nobody has to decide alone whether it’s worth raising.
- Give everyone one way to raise it, right away. Use one plain phrase, such as “I’m flagging a site photo,” said the same way by everyone, from the newest MA to the physician. When anyone says it, the next step waits.
- Name who answers, every session. One dermatologist or PA takes clinical questions, and the lead MA takes flow. Whoever raises a flag knows exactly who is coming. Anything urgent still goes straight to the clinician.
- When the site photo is missing at rooming. The MA rooming a patient for a planned procedure finds three look-alike healed biopsy sites and no photo marking the intended one. The tray stays sealed, and the MA calls the referring office for the photo with the site marked. The dermatologist checks it against the referral and with the patient before anything is opened. If the site can’t be confirmed, the team pauses rather than guesses. It may still mean a wait; it never means a guess.
- Thank every flag, and learn from the tally. A flag that turns out to be nothing still counts as a good catch. Keep a paper tally with no patient identifiers and look at it at the next huddle. Zero flags isn’t a win yet: ask whether there were no cases, missed cases, an unclear trigger, or people hesitating to speak up.
Explore the Evidence Further
Explore the Evidence Further. All 5 sources, with methods, findings and clinic applications
Five sources, grouped by kind of evidence: Toyota’s own accounts, a hospital that adapted the idea, and research on speaking up. Each row gives the design and its main caution, the key finding, why it matters and a way to apply it. Study names link to the original sources, and the full references close this section. None of these sources tested a cord or a flag in a dermatology clinic, so every application is our proposal, not a tested intervention.
The Toyota practice: company accounts
| Study or source | Setting, design and sample | Key finding | Why it matters | How to Apply It to Your Derm Clinic |
|---|---|---|---|---|
| Toyota, “Toyota Production System”1 | Company account: Toyota’s own undated description of its production system. It reports no outcome data. | When something is abnormal, a quality problem, an equipment problem or a work delay, the machine stops itself or the operator pulls a stop cord, and a board lights up so workers can call the person in charge. Toyota calls this jidoka and says it keeps defective products from flowing on and stops problems from recurring. | It names what counts in advance and pairs the signal with a call for help. | Proposed: agree in advance which problems count as a flag in your clinic, so nobody has to judge alone. |
| Toyota UK Magazine, “TMUK’s 25 Objects – 19: Andon Cord”2 | Company account, one plant: Toyota Manufacturing UK’s magazine on its Burnaston plant (2017, updated 2024). No data on how often the cord is pulled, how long the line stops, or quality. | A pull lights that station’s number on a board, with a chime and a flashing light, and the team leader gives immediate assistance there. Fixed within the station’s process time, production continues; if not, the line pauses until the problem is resolved, and a second pull restarts it. Stopping “seems like a costly measure,” the magazine says, but it keeps a defective part from “finding its way into a finished vehicle.” | It shows the cord is a call for help with a clear rule for when work pauses, not a switch that halts everything. | Proposed: name who answers a flag each session, and agree that the patient doesn’t move to the next step until the flag is settled. |
Health care: a hospital alert system modeled on Toyota
| Study or source | Setting, design and sample | Key finding | Why it matters | How to Apply It to Your Derm Clinic |
|---|---|---|---|---|
| Furman and Caplan, “Applying the Toyota Production System: using a patient safety alert system to reduce error”3 | Single-hospital report: Virginia Mason Medical Center, Seattle, 2002 to 2006, written by the hospital about itself, with no comparison group. It counts alerts, not harm, and not the number of people reporting. | Any employee who saw a risk to a patient was expected to stop and call a Patient Safety Alert. Alerts rose from an average of 3 a month in 2002 to 285 a month in 2006. Most were processed within 24 hours and resolved within 2 to 3 weeks. | A hospital paired an alert any employee could call with quick processing. More reports does not prove fewer patients were hurt. | Proposed: pair your flag with a named responder and a quick answer, and review the tally at the next huddle. |
Research on speaking up and psychological safety
| Study or source | Setting, design and sample | Key finding | Why it matters | How to Apply It to Your Derm Clinic |
|---|---|---|---|---|
| Kane and colleagues, “Defining speaking up in the healthcare system: a systematic review”4 | Systematic review of definitions: A review of how health care research defines speaking up. It proposes a definition and reports no effect data. | Research on speaking up in health care has focused on the speaker and neglected the listener. | A flag needs someone on the other end. Plan the response as carefully as the signal. | Proposed: name the person who answers before you ask anyone to speak up. |
| Edmondson, “Psychological safety and learning behavior in work teams”5 | Field study, one company: Work teams in one manufacturing company, measured at one point in time. Not health care, and not about a cord. | Defines team psychological safety as “a shared belief held by members of a team that the team is safe for interpersonal risk taking.” | It names the permission half: whether people believe it is safe to speak up. | Proposed: thank every flag, including the ones that turn out to be nothing, so raising one never feels like a risk. |
Across all five sources:
- None tested a cord or a flag in a dermatology clinic.
- Toyota’s accounts describe its own system; they give no independent defect, time or cost data, and the Burnaston rule describes one plant.
- The hospital report counts alerts, not patient harm, and has no comparison group.
- The speaking-up and psychological-safety sources define ideas; they did not test cord systems.
Principles of Excellence: related evidence from other settings
The main text explains Toyota’s practice in plain English. These sources describe it, or study related ideas elsewhere; none measured Toyota’s results.
| Point in the brief | Related evidence |
|---|---|
| Anyone can raise the signal. | Toyota’s own descriptions (company accounts).1, 2 Psychological safety, the shared belief that a team is safe for interpersonal risk taking (field study, one manufacturing company).5 |
| What counts is agreed in advance. | Toyota names the triggers (company account).1 |
| The signal brings help to the spot. | Burnaston’s account (company account, one plant).2 Research on speaking up has neglected the listener (systematic review of definitions).4 A hospital paired staff alerts with quick processing; it counted reports, not harm (single-hospital report).3 |
| Fix it in time, or pause right there. | The process-time rule at one plant (company account).2 |
| Each pull teaches. | Toyota’s own description, with no independent data (company account).1 |
Our clinic suggestions: proposed, not tested
The five practices and today’s action are our suggestions for a dermatology practice, not a tested program.
| Suggestion | What it draws on |
|---|---|
| Agree what counts: a short list of flags, picked by the medical director and practice manager. | Toyota names its triggers in advance (company account).1 |
| One way to raise it: one plain phrase, used by everyone, and the next step waits. | Anyone on the line may pull the cord (company accounts).1, 2 Psychological safety (field study).5 |
| Name who answers: a clinician for clinical questions and the lead MA for flow; urgent concerns go straight to the clinician. | The team leader answers every pull (company account, one plant).2 Research on speaking up has neglected the listener (review of definitions).4 |
| A missing site photo at rooming: keep the tray sealed, call the referring office, confirm with the referral and the patient, and pause rather than guess. | In the plant Toyota UK describes, an unresolved problem pauses the line before it moves on (company account).2 The clinic scene is an illustration, not a documented case. |
| Thank every flag and learn from the tally: a flag that turns out to be nothing still counts; zero flags means ask why. | A hospital alert system with quick processing; it counted reports, not harm (single-hospital report).3 Toyota says flagging each problem helps keep it from coming back (company account).1 |
| One action today: one problem, one flag, one person who answers, for one week. | No study tested this one-week trial; it applies the same pattern. |
Sources
- Toyota Motor Corporation. “Toyota Production System.” Toyota global website, undated page. global.toyota
- Biddle A. “TMUK’s 25 Objects – 19: Andon Cord.” Toyota UK Magazine, 11 December 2017 (updated 9 September 2024). mag.toyota.co.uk
- Furman C, Caplan R. Applying the Toyota Production System: using a patient safety alert system to reduce error. Jt Comm J Qual Patient Saf. 2007;33(7):376–386. PubMed
- Kane J, Munn L, Kane SF, Srulovici E. Defining speaking up in the healthcare system: a systematic review. J Gen Intern Med. 2023;38(15):3406–3413. PubMed · PMC
- Edmondson A. Psychological safety and learning behavior in work teams. Administrative Science Quarterly. 1999;44:350–383. web.mit.edu