Be a Goldfish

Welcome to the new series, Lessons From a Fictional Football Club. What happens to an organization the moment its strongest personality walks out the door? This series turns to Ted Lasso as an unlikely case study, treating it as a structural experiment in what actually holds an organization together under pressure, versus what was just one person's charisma wearing a disguise. Across this series, I'll pull leadership lessons from specific scenes, ground them in research where it exists, and close with structural reads through the Loadmap framework, all in service of one question worth asking about your own team: when you leave the room, what keeps running?

Early in the first season, the show stages a training session that anyone who's ever been new at a job will recognize from the inside. In this instance, a young defender keeps getting beaten by the team's star, who celebrates each win by mocking him in front of the squad. Watch the kid through the whole drill and you can see the real problem: every mistake costs him a few seconds of replaying it in his head, and those few seconds are exactly the window the next mistake needs. He has the skill. He's just still playing the previous ball.

The coach jogs over mid-session and asks him a question that has nothing to do with football: what's the happiest animal on earth? A goldfish, the coach tells him, because it's got a ten second memory. Then the whole instruction, three words long: "Be a goldfish."

The kid's next play is better. Not in a movie-magic way. He just gets his attention back.

Give failure a ten second memory.

The spiral that young defender was in has a boring clinical name: rumination. The sequence runs like this. An error grabs your attention. Attention replays it. The replay takes up the same limited attention your next action needs, so the next action suffers, which produces a fresh error and an even richer replay to run. The psychologist Susan Nolen-Hoeksema spent a career documenting what rumination actually does: it feels like useful thinking while it's happening, and it performs like paralysis, leaving you in a worse mood and measurably worse at solving the very problem you're chewing on.

And the obvious fix runs backward. Telling yourself not to think about the mistake backfires, and the psychologist Daniel Wegner proved it with his famous white bear experiments: the harder you try to keep a thought out, the more often it comes back, because some part of your mind has to keep checking for the thing it's supposed to be ignoring. (Try, right now, not to think about your last bad meeting. Chances are good you’ll see the problem.)

What the goldfish does instead is scheduling. I know this sounds like denial with better branding. But the mistake doesn't get erased. It gets reviewed later, in calmer times, when reviewing it can actually change something. It just doesn't get to play the next ball. Basketball has used the same practice under a different name for decades: Duke's teams were drilled on the phrase "next play" for precisely this reason, because the few seconds after a mistake are where good teams leak points.

There's a second mechanism in the scene, and it's the one that earns the goldfish a place in this series. The phrase spreads. Within a season, players are saying it to each other without the coach in the room. That's worth staring at, because it's how culture actually moves: a short phrase anyone can carry, attached to a practice that visibly works, passed sideways from player to player rather than handed down from the top. The values poster arrives later, if at all, and matters about as much as you'd expect.

The practice, small enough to start tomorrow. Build a ten second reset for your own mistakes: exhale and say the phrase, then turn to the next concrete action. Borrow the goldfish or pick words your team won't laugh at, though if your team laughs at people that's a different post. Then schedule the review for later and actually hold it. The goldfish only stays honest if the mistake has an appointment. Run it for one week, on every mistake, and keep both halves of the bargain: the fast forgetting and the scheduled review.

This blog is called The Load, and this is where I start paying that off. Load is the word I use, borrowed from Loadmap, the framework I do my thinking in, for the pressure your way of working has to carry in the live moment. The match. The launch. The customer who's already angry when they call. Whatever your version of match day is, that's where load arrives, and what happens there is the visible surface of everything underneath.

The goldfish is interesting because of where it operates: the exact point where load meets behavior. It fixes nothing upstream of that moment, and it doesn't pretend to: why the team keeps producing mistakes in the first place, and why the star gets away with mocking the rookie, are questions about how the club is run, and they get their own posts later in the series. A ten second reset absorbs the bump. It doesn't repave the road. Both jobs matter, but only one of them can be done in the next ten seconds, and a lot of leadership advice fails exactly here, selling the bump-absorber as if it could also repave the road.

So here's this week’s question: when someone on your team drops something in front of everyone, what do the next ten seconds actually look like? If you don't know, watch this week. If you don't like the answer, you know where the series is headed.

The Load is unofficial analysis and commentary. It is not affiliated with, sponsored by, or endorsed by Apple, Warner Bros., or anyone connected with the television series Ted Lasso. Loadmap is the framework used in the structural reads; Stokefire is its first authorized provider. 

Get The Load directly in your inbox