Respond

The problem category

The first four chapters gave you time. Time to weigh the decision, read the records, prepare the pitch, plan the negotiation. This chapter takes the time away.

That’s the respond muscle. Something has gone wrong, right now. A customer got sick. The data leaked. Half the staff walked out mid-shift. You don’t have the whole story, and you won’t get it before you have to act. A facilitator runs a clock and drops injects on you, new developments every few minutes: a customer posts online, a reporter calls, the health inspector shows up, the real cause finally surfaces. Each one forces you to re-decide what matters most, right now, with what little you know.

The situation changes under your feet. How you respond as it changes is what’s being tested.

The one big idea

Protect people first, tell the truth fast, control the controllable.

Under pressure, the instinct is to protect the business. Keep the doors open. Stay quiet and hope it blows over. Deny it. Blame the supplier. Every one of those feels safe in the moment, and every one makes the crisis worse. The habit that works runs the opposite way, in a fixed order.

1. Protect people first. If someone might still be getting hurt, stop the harm before you worry about the money or the brand. Even when it costs you right now. Especially then.
2. Tell the truth, fast. A clear, honest word early beats a perfect statement too late. Silence reads as guilt. Spin reads as guilt. Say what you know and what you’re doing.
3. Control the controllable. You can’t undo what already happened. You can decide what you do in the next ten minutes. Put your energy there, not on the past you can’t change.

Every scenario is built so the loud problem, the angry post or the reporter, isn’t the same as the urgent problem, the person who might still be getting hurt. And so the tempting shortcut, staying quiet or blaming someone else, scores worse than the honest, costly, correct move.

How to tackle it

1. Triage: separate the urgent from the loud. The urgent thing is where someone’s being harmed. The loud thing is where someone’s angry or watching. They’re usually not the same thing, and the urgent one wins every time.
2. Protect people first, even at a cost. Pull the product. Clear the area. Send people home. The safe thing before the cheap thing.
3. Decide with incomplete information, and call for help early. You won’t have the full story. Freezing until you do is a decision, and a bad one. Ask for help, an expert, the authorities, sooner than feels comfortable. Calling for help is strength, not weakness.
4. Communicate honestly and fast, to the right audience. Customers, staff, the public, the authorities. Each needs a clear, true message. No denial. No promises you can’t keep.
5. Stay composed and adapt. When a new inject changes the facts, change the plan. Keep your own team coordinated so you’re not tripping over each other while the clock runs.

The traps

• Working the loud problem while the urgent one grows. Answering the angry post while a customer is still in danger is the classic failure.
• Going quiet to protect the brand. Silence doesn’t buy you time. It spends your credibility.
• Denying or over-promising. “There’s no problem” and “this will never happen again” are both lines you’ll have to walk back.
• Freezing, or guessing wildly. Both come from the same place: no method. You have one now.

One tool: the decision log

Under pressure, teams forget what they decided and why. Keep a running log: the time, what you knew, what you decided, and why. It keeps the team honest, it keeps everyone on the same plan, and afterward it’s the clearest record of how you did.

The holding statement

You almost never know the cause in the first 30 seconds. You still have to say something, because silence reads as guilt and a guess reads as guilt too. The holding statement is the honest one-liner that buys you credibility while you still know almost nothing. It does three things and only three: it names what happened, it says what you are doing right now, and it says when you will know more. It never guesses the cause, and it never promises an outcome.

The template:

“Here’s what happened. Here’s what we’re doing right now. Here’s when we’ll know more.”

Fill it with only what is true. “We had a customer report a reaction, we’ve pulled the item and we’re checking every batch, and I’ll have an update within the hour.” That’s it. Notice what it leaves out: why it happened, whose fault it is, and any version of “this will never happen again.”

The holding statement works because it is small and it is true. You can say it before the facts arrive, and you never have to walk it back. When you do know more, you say more. Until then, this holds the line without spending your credibility.

Worked walkthrough: The Propane Scare

Middle of the lunch rush at Sunny’s. The line is long. A cook leans over and says quietly, “I smell gas near the propane tank.” At the same moment a customer near the front is holding up a phone, filming, annoyed the line has stopped, and the event coordinator whose lot Sunny is parked in is walking over to ask about the holdup.

Two problems, and they aren’t the same. The loud problem is the crowd, the phone, the coordinator. The urgent problem is a possible gas leak with people standing a few feet from the tank. Only one of those can hurt someone in the next minute.

Now, inject by inject.

Inject 0, the smell, before you know anything. You don’t yet know if it’s a real leak or a jumpy cook. Doesn’t matter. Protect people first: shut off the gas at the tank, stop cooking, move the customers back from the truck.

Here’s the wrong turn, and it happens in the heat of it. As the smell registers, a teammate says two tempting things at once: “Let me just move the truck to the far end of the lot and keep serving so we don’t lose the rush,” and “I’ll post a quick reply to that video so we don’t look bad.” Both are wrong, for the same reason. You don’t tow a possibly-leaking propane tank across a crowded lot to set up next to a fresh group of people, and you don’t answer the phone, which is loud, while the tank, which is urgent, sits unsecured. The call: tank and people first, phone second, and the truck doesn’t move until it’s safe. Say it out loud so the team stays on one plan.

(Decision log, 12:05. Smell of gas reported. Gas off, cooking stopped, customers moved back 15 feet. Truck stays put. Cause unknown.)

Inject 1, a customer posts. The filming customer puts up “sunnys food truck almost blew up lol.” Now, with people safe, handle the loud problem. Don’t deny it, don’t spin it. Answer honestly and fast: “We smelled gas and shut everything down right away to keep everyone safe while we check it. Thank you for your patience.” The truth, quickly, does the work.

Inject 2, the coordinator wants a reopening time. The coordinator asks, “Can you be back up this afternoon? People are hungry.” The tempting answer is “yes, give me twenty minutes,” because you want to save the day. Don’t promise a time you can’t guarantee. Say what has to be true first: “As soon as the tank is checked and confirmed safe, and not before. I’ll tell you the moment I know.” A promise you might break is worse than an honest “not yet.”

Inject 3, the cause surfaces. You find it: a loose regulator fitting on the tank, a real leak, now shut off. Fixable. It’d be easy, and wrong, to tell the crowd “one of my cooks hooked it up wrong.” Don’t blame a cook in public. Own it: “We found a loose fitting on the propane regulator. It’s being repaired and the tank rechecked. This is on us to fix, and we’re fixing it.”

The final call, reopen or not. Reopen only after the fitting is repaired and the tank is checked and confirmed safe, and say so, out loud to the crowd and in a short post online: “We’re back open. The propane fitting is repaired and the tank has been checked. Thanks for bearing with us, safety first.” You controlled the one thing you could control, the next ten minutes, and told the truth the whole way.

Here’s the decision log, cleaned up.

Time	What you knew	What you decided	Why
12:05	Smell of gas near tank	Gas off, cooking stopped, crowd back, truck stays	Protect people before revenue
12:08	Customer posted a joke video	Honest public reply, no denial	Truth fast beats silence
12:12	Coordinator wants a time	“When the tank is confirmed safe, not before”	No promise you can’t keep
12:20	Loose regulator fitting found	Own it publicly, repair, recheck	Honesty, no scapegoat
12:40	Fitting repaired, tank checked	Reopen and say so plainly	Controlled the controllable

What good looks like

A weak answer:

Shut off the gas and move everyone back from the truck. Then, with the crowd waiting, say nothing online about the video, and tell the coordinator, “It’s probably nothing, just a whiff, we’ll be open again in ten minutes.” Reopen once the smell fades.

This one gets the hardest part right, and that’s what makes it instructive. It protects people first: gas off, crowd back, no arguing with the danger. Most teams that fail this scenario fail right there, and this one passed. Then it comes apart on everything after. Going silent while a video spreads spends the credibility a fast honest word would have bought. “Probably nothing, open in ten minutes” is both a guess and a promise, the kind you have to walk back the moment you find the real leak. And “reopen once the smell fades” reopens on a hope, not a confirmed-safe tank. Right on safety, wrong on truth, timing, and the reopening call.

A strong answer is the sequence above: shut down before you’re sure, secure the truck, tell the truth quickly, refuse the promise you can’t keep, own the cause, and reopen only when it’s genuinely safe.

Crisis challenges are scored on four things: protect people first (safety and the harmed come before revenue and reputation), decisions under pressure (sound, timely calls with incomplete information, and calling for help instead of hiding), communication (honest, fast, the right message to each audience, no denial or over-promising), and composure and adaptation (calm under fire, updating the plan as facts arrive, keeping your team together). There’s no perfect script. Clear priorities and honest, adaptive judgment win, not the fastest talker or the most confident guess.

A second walkthrough: The Dark Truck

Saturday evening at the brewery lot. A summer storm rolls through and the transformer feeding the lot blows. The whole row of stalls goes dark, and so does Sunny’s truck. No griddle, no lights, and no refrigeration. The cold food, the pork, the dairy, the prepped salsas, is sitting in a fridge that is now just an insulated box, warming up. A line of two dozen people is still standing there, hungry and already annoyed about the rain. The coordinator is jogging over to ask what everyone’s asking: are you still serving.

Two problems, and they aren’t the same. The loud problem is the line and the lost Saturday revenue. The urgent problem is that warming food, because serving something that has sat in the danger zone can put people in a clinic. Only one of those can hurt someone.

Now, inject by inject.

Inject 0, the lights go out. You don’t yet know how long the fridge has been off or how warm it is inside. Doesn’t matter yet. Protect people first: stop selling anything that came out of that fridge. Keep the door shut to hold the cold as long as you can. Cooked-to-order off the griddle is dead anyway with no power.

Here’s the wrong turn, and it’s tempting because it’s cash. A cook says two things fast: “The fridge is still kind of cold, let’s just sell through the pork before it turns so we don’t eat the loss,” and “Tell the line we’ll be back up in fifteen.” Both are wrong, same reason. “Kind of cold” is a guess, and you don’t gamble a customer’s night on it. And you can’t promise fifteen minutes on a transformer you don’t control. The call: nothing questionable gets sold, and no reopen time gets promised. Say it out loud so Dylan and Mara are on one plan.

Inject 1, the coordinator asks. She wants to know if you’re serving. Honest holding statement, no spin: “Power’s out, so our fridge is down. We’ve stopped selling the cold items to be safe, and I’ll know more once I’ve checked temperatures. I’m not promising a reopen until I do.” The truth, fast, to the person who needs it.

Inject 2, the line pushes. Someone up front says the food was cold ten minutes ago, just sell it. This is the loud problem leaning on you hard. You don’t argue and you don’t cave: “I hear you, and I’m not comfortable serving food I can’t keep cold safely. I’d rather lose the sale than make anyone sick.”

Inject 3, you’re unsure. You check: the fridge has drifted up past safe and you’re honestly not sure what’s still good. Don’t guess. Call the health department’s guidance line, tell them the times and temps, and do what they say. Calling for help early is the strong move, not the weak one.

The final call, discard and reopen. Guidance is clear: what crossed the line gets tossed. You discard the warmed pork and dairy, a real hit, call it about $180 in food you’re pouring into the bin, and you don’t reopen the cold menu until power’s back and you’ve restocked from safe cold storage. You tell the line plainly and post a short honest note. You controlled the one thing you could.

Time	What you knew	What you decided	Why
6:10	Power out, fridge warming	Stop selling cold items, keep door shut	Protect people before revenue
6:14	Coordinator asking	Honest holding statement, no reopen promise	Truth fast, no promise you can’t keep
6:20	Line pushing to sell it anyway	Hold the line, refuse to serve questionable food	Safe before cheap
6:30	Unsure what’s still safe	Call health guidance, follow it	Call for help early
6:45	Temps past safe, ~$180 of food	Discard it, reopen only when safe	Took the loss, controlled the controllable

Try It: First Ten Minutes

Your turn. The worked answer is in Appendix A.

At Sunny’s, three things happen in quick succession.

• A. A customer calls to say they think last night’s burrito gave their kid an allergic reaction and they’re on the way to a clinic.
• B. A local reporter calls, having seen a comment online, asking “is your food safe?”
• C. You check and find a new batch of tortillas was made in a facility that also handles peanuts, so the “peanut-free” label on your truck is now wrong.

Put A, B, and C in the order you’d act on them, and for each, label it urgent or loud and say your first move.

Work it out, then check Appendix A.

More practice

Four more. Work them on paper, then check Appendix A.

1. The Slip. It’s the lunch rush, and three things hit at once. An older customer slipped on a spill by the serving window and is on the ground, holding their wrist. The line behind them is grumbling, and someone starts filming. And you realize the spill is from your own leaking cooler, which is still dripping onto the walkway. Order the three, label each urgent or loud, and give your first move for each.

2. Rewrite the Statement. A batch of online-order receipts went out showing the wrong customers’ names and addresses. Sunny’s first draft of a public note reads: “There is no real problem here, just a small glitch, and no one’s information was ever at risk. This will never happen again. Please keep ordering!” Name what’s wrong with it, then rewrite it honestly.

3. The Fryer Fire. It’s a busy Saturday and three things land at once. A pan of oil on the griddle catches fire and flames are climbing toward the awning where customers stand. At the same time, Mara says she just burned her hand badly reaching for it and it’s blistering. And a customer near the front is loudly filming the flames and telling the line “this place is a hazard.” Put the three in the order you’d act on, label each urgent or loud, and give your first move for each.

4. The Plastic Post. A customer found a small piece of plastic in their taco and posted a photo. Sunny’s draft public reply reads: “That plastic definitely didn’t come from us, our kitchen is spotless and this is basically impossible. We’ve totally fixed it already and it will absolutely never happen again. Anyway, come grab a taco this weekend, we’ve got a new salsa!” Name what’s wrong with the draft, then rewrite it honestly.

Take it live (optional)

Ready to test this muscle for real? Each of the five programs has a bank of live team challenges, run with a facilitator. You don’t need them to finish the book; the walkthrough and practice above already cover the skill. To show you exactly what one looks like, here is a full Respond scenario, including the hidden cause and the timed injects. Read it, or run it: one team responds while a facilitator works the answer key and the clock. The other four in this bank stay sealed, so they’re fresh when you compete.

A full challenge: The Bad Batch

The setup (what the team gets). It’s 8:00 on a Monday morning, and the Coconut Grove Cafe opens at 9. Over the weekend, three customers called to report severe stomach illness after drinking Friday’s fresh-pressed green juice. One of them, a regular, is in the hospital. A local health reporter has just emailed asking for comment. Your team runs the café. The clock is running, and the story won’t hold still. Decide what to do, in what order, and say it out loud. Keep a decision log, write the statements you’d actually send, and brief your staff as the situation changes.

Facilitator answer key.

The hidden truth (the team learns this only as the injects land). The café’s fresh-pressed juices are unpasteurized, a genuine food-safety risk. Friday’s green juice used a lot of raw spinach that the supplier, Cedar Grove Farms, quietly recalled Monday morning for possible contamination. The illness is real and linked to the café’s product, and more mild complaints are still coming. The cause is findable and fixable, but only if the team preserves the batch instead of throwing it out and cooperates instead of hiding.

The injects, dropped on the clock:

• The report (start). Strong teams’ first move is a safety action: stop selling the fresh-pressed juice and hold the batch, before anything else.
• Social media. A customer posts that their friend is in the hospital, with a photo of the juice, and tags the café. Strong: respond honestly and publicly, don’t delete or argue.
• The health department. They’ve had a report; an inspector is coming this afternoon. Strong: the team already called them, or calls now and cooperates fully.
• The reporter, and more cases. A reporter is at the door, and two more mild complaints arrive. Strong: one calm spokesperson, an honest holding statement, never “no comment.”
• The cause. The recalled Cedar Grove spinach lot surfaces. Strong: pull everything with that lot, fix the process, and resist dumping all the blame on the supplier to dodge responsibility.
• The curveball. A well-meaning employee already told the reporter “the owner said it’s probably nothing.” Strong: correct the record fast and get everyone speaking with one voice.
• The doors. It’s nearly 9:00 and regulars are waiting. Strong: opening is fine only if the suspect juice is pulled and there’s a visible, honest notice and a staff script. Opening as if nothing happened, or panic-closing with no word, both fail.

The model order: stop the harm first (pull the juice, and hold the batch, it’s the evidence that finds the cause), care for the people harmed, call the health department yourself, communicate honestly and fast, find and fix the cause, and keep one voice. The traps that feel safe and score badly: keep selling because “we’re not sure it’s us,” go silent, delete the post, publicly blame the supplier before the facts, over-promise (“this will never happen again”), or throw out the batch and destroy the evidence. Scored on protect people first, decisions under pressure, communication, and composure and adaptation.

The rest of the Respond bank

Four more, sealed for fresh scored play. Triage the urgent from the loud, protect people first even at a cost, communicate honestly and fast, and keep adapting as the facts change.

1. The Breach (customer data is exposed). A duty to notify, and harm you can’t see.
2. The Walkout (staff quit mid-shift, in public). Leadership and talking to your own team, not just the public.
3. The Storm (a disaster shuts you down). Keeping going, and many stakeholders under real loss.
4. The Video (an employee’s misconduct goes viral). Fairness to the accused against a public pile-on.

Going deeper

Real crises involve harm you can’t see, and stakeholders who don’t agree on what to do. The next skills are acting on invisible risk, like a data breach where nobody feels hurt yet, and leading your own people through it, not just managing the public. The bank’s later scenarios add both.