Hello Future Leaders,
Every issue takes one thing that quietly goes wrong between managers and their teams, shows it happening through a real story, and leaves you with something to try this week.
Today it's the moment something breaks in front of your team, and everyone turns to look at you. You'll leave with a fifteen-second breathing reset and a four-line script for the first thing you say.
10:14 on launch morning
The payments page went red at 10:14.
Olivia's team had been building the new checkout for nine weeks. Seven of them were crowded into a meeting room with a big screen, a tray of pastries nobody had touched, and a dashboard that had looked fine at 10:13.
Olivia stood up so fast her chair hit the wall. "Are you kidding me? We tested this. We tested this three times."
She shut her laptop hard enough that people winced.
Then the room went quiet. Two engineers started fixing two different things without telling each other. Rehan, who'd spotted a config error in the logs at 10:16, kept it to himself for half an hour. Later, he admitted he hadn't wanted to be the one who'd missed it.
The fix took four minutes once someone finally said it out loud. The outage lasted 47.
What the room was actually doing
Every person in that room was watching Olivia's face. The dashboard could wait.
When something goes wrong at work, your team takes its cue from the most senior face in the room. It happens in seconds, mostly without anyone deciding to do it. Olivia's panic was reasonable (nine weeks of work, a public launch, her name on it). But the room caught the panic and lost the thinking.
Researchers have watched this happen. In a 2005 experiment, Thomas Sy, Stéphane Côté and Richard Saavedra put leaders in either a good or a bad mood before they led a group task. Team members picked up the leader's mood. And groups led by someone in a bad mood coordinated worse with each other, even though they put in more effort.
More effort, worse coordination. That's a pretty good description of 10:16 to 11:01 in Olivia's meeting room.
Calm is something you do
Here's something that might take Olivia and you, yourself a while to accept. She'd always described herself as "intense," the way you'd describe your eye colour. Something you're born with, fixed for life.
Watch a steady manager closely during a bad hour and you see something else. Calm under pressure turns out to be a short sequence of moves, and moves can be practised. Steady managers still feel the jolt when the page goes red. They've just rehearsed what comes in the next ninety seconds, often without noticing they've rehearsed it.
Olivia found that out the slightly embarrassing way. The week after launch, she booked a meeting room for twenty minutes and asked Rehan to read fake alerts off his laptop: checkout's down, search is timing out, and the CEO's on the phone. Each time, she stood up, let out one long breath, and said the first thing that came to mind.
Her first three answers were terrible. One was just a sigh. By the ninth, she'd found an opening line that came out on its own: "Okay. Here's what we know." Rehan called it the strangest meeting he'd ever sat in and then admitted it was the first time he'd felt fine telling her something had broken.
What to do Monday
Two things, both small enough to practice on a normal day.
Start with the breath. Stanford researchers tested five minutes a day of "cyclic sighing" against mindfulness meditation for a month.
Cyclic sighing (two short inhales through the nose, then a long, slow exhale through the mouth) improved mood more and slowed people's breathing at rest. In the moment, two or three of those sighs take about fifteen seconds. Nobody will notice.
Then the words. Write this somewhere you'll see it and fill it in out loud:
- What we know: …
- Still unknown: …
- Who's on what: …
- Next update: [a specific time]
It sounds almost too simple. That's the point. When your heart rate is up, you won't come up with anything clever, but you can read four lines you've already practiced.
Where this goes wrong
The common mistake is faking it. Saying "It's fine, it's fine" through your teeth while your neck goes red.
People can tell. Your face, your posture, and your typing speed all give you away, and a calm voice over obvious panic just teaches the team that you won't tell them the truth when it matters.
So be honest about the feeling and steady about the plan. "This is bad, and I'm annoyed. Here's what we're doing." That's calm. It doesn't require you to pretend you aren't rattled.
The other trap is saving the script for big emergencies. You'll never remember it then. Use it when the printer jams before a client meeting, when someone's late with a deck. Small stakes are where you get the reps.
One thing this week
Pick one minor annoyance this week and run the whole thing on purpose: two sighs, then the four lines, out loud, even if it's just to one colleague.
Three weeks after launch day, Olivia's team had a smaller outage on a Thursday afternoon. Olivia's coffee went everywhere when the alert pinged. She said a word we won't print, took a breath, and then said, "Okay. Search is down. Don't know why. Rehan, logs. Sam, status page. Update at 3:30."
Rehan found the problem at 3:22. He said it the second he saw it.
Feedback
| How was your experience with Future Leader today? |
|
|
|
|
Subscribe to participate in polls.
If you have specific feedback or anything interesting you’d like to share, please let us know by replying to this email.
600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246
Unsubscribe · Preferences