I should probably start with a confession that will immediately disqualify me from being objective about Ted Lasso. I have a Believe tattoo. Not only that, but worked into it are the words “Be curious, not judgmental.” So when I hear people in the Agile community complain that Ted Lasso quotes have become overused, I am probably not their target audience. I have taken two of the most overused ideas from the show and permanently attached them to my body. I don't merely tolerate the cliché. I apparently decided to become a walking version of it.
And yet, the eye-rolling has always fascinated me. Not everyone in Agile does it, of course, but I have heard enough consultants dismiss Ted Lasso because the lessons are too neat, the quotes are overused, and—perhaps my favorite criticism—the whole thing is scripted. Which is fair. Ted Lasso is a fictional television show. The writers know where the dart is going before Ted throws it. But this criticism gets a little harder for me to take seriously when it comes from a profession that has spent decades telling some variation of the story where a frustrated software team grabs an electric power tool and starts dismantling the cubicle walls separating them from each other.
You know the story. Someone realizes the physical layout is preventing collaboration. Permission either takes too long or never comes. So out comes the power tool. Cubicle walls start coming apart. Management is horrified. The team is liberated. Collaboration improves. Somewhere, presumably, an Agile consultant sheds a single tear.
I have heard enough versions of this story that I no longer know whether there was one legendary cubicle demolition that became Agile folklore or whether software developers spent the early 2000s roaming corporate America with cordless drills.
Either way, maybe storytelling isn't actually the problem.
Agile Has Always Run on Stories
The cubicle story works for exactly the same reason the dart scene works. Nobody really cares about the power tool. The point is what it represents: a team recognizing that the environment around them is getting in the way of how they need to work and deciding to change it. A messy organizational lesson becomes something physical, visual, and memorable. You can tell someone for twenty minutes about organizational silos and communication barriers, or you can tell them about the day the developers took a drill to the cubicles.
Agile has always taught this way. There are stories about Toyota factories and assembly lines. Stories about managers who finally learned to get out of the way. Stories about organizations that stopped estimating, stopped having meetings, or started writing everything on index cards. These stories survive because stories are useful. They compress complicated ideas into something we can remember. A transformation that actually involved organizational politics, budgets, personalities, technology, incentives, failures, and years of work becomes a moment when somebody picked up a power tool. Reality gets simplified so the lesson becomes visible.
That's not a criticism. That's teaching. Which makes the eye-rolling at Ted Lasso particularly strange, because the show is doing exactly what Agile coaches have been trying to do for decades: taking abstract ideas about how people work together and making them understandable through stories. Except Ted Lasso has a considerably larger audience.
And nobody had to pay for the certification.
The Coach Who Doesn't Have the Answers
The joke at the center of Ted Lasso has always been that Ted is spectacularly unqualified for his job. He arrives in England knowing almost nothing about soccer. He doesn't understand the rules, the terminology, the traditions, or even how a league table works. We tend to associate leadership with expertise, and expertise with having answers. Leaders are supposed to walk into the room knowing what everyone should do next. Ted does something much more useful: he asks.
He surrounds himself with people who know things he doesn't. He listens to Beard. He learns from Roy. He discovers that the quiet kit man has ideas worth hearing. He changes his mind, experiments, gets things wrong and adjusts. Most importantly, he isn't threatened when someone else has the better answer. His authority doesn't depend on being the smartest person in the room, which allows the room to become smarter than he is. Agile has been trying to teach this lesson forever. The leader's job isn't to dictate every solution. Create the conditions in which the people closest to the work can solve the problem. Give them context. Remove obstacles. Ask questions. Then trust them enough to act.
Ted just makes it more entertaining.
The Team Is the Unit That Matters
But perhaps the most Agile thing about Ted Lasso isn't Ted at all. It's Richmond. Professional sports naturally creates heroes. The star scores the goal. The superstar gets the contract and their face on the billboard. Software organizations aren't immune to this instinct. We have our rock-star developers, our 10x engineers, the architect who understands the system nobody else dares touch. Individual brilliance is seductive because individual brilliance is easy to see. Teams are harder.
Again and again, Ted Lasso pulls our attention away from the individual and toward the system around them. Jamie Tartt can be enormously talented and still make Richmond worse. Roy Kent can be a legend and still have to learn that the team cannot remain organized around who he used to be. Nate can see things other people miss, but individual intelligence separated from trust and belonging can only carry a team so far. Even Ted's leadership is ultimately measured not by how much the team needs him, but by what the team becomes capable of doing together. That's a profoundly Agile idea: the team is the unit that matters.
A great engineering organization cannot depend on one heroic developer saving every release. If one person has to be in every architectural conversation, approve every important decision, or swoop in whenever production breaks, you haven't discovered your MVP. You've discovered a constraint. Sustainable performance comes from teams that share context, challenge one another, cover one another's weaknesses, and become collectively capable of solving problems none of them could solve alone. Richmond becomes better when Jamie stops needing every play to end with Jamie. The transformation isn't that he becomes less talented. It's that his talent becomes more valuable when it belongs to the team.
We spend an enormous amount of energy trying to identify the best individual engineers. We build career ladders around individual contribution and celebrate the person who solved the impossible production problem at two in the morning. But Agile, at its best, has always challenged some of that thinking. The question isn't whether you have brilliant people. The question is whether their brilliance makes everyone around them better. Ted understands that without ever putting “cross-functional team dynamics” on a slide.
Psychological Safety Without the Slide
The phrase “psychological safety” has become so common in corporate life that it risks becoming another piece of management wallpaper. We put it on slides. We measure it in engagement surveys. We tell leaders they need to create it. Then someone makes a mistake in production and half the organization starts looking for the name attached to the pull request. Ted rarely explains psychological safety. He creates it.
People around him are allowed to be unfinished. They can admit fear, fail publicly, disagree with him, be angry, or ask for help. And when those moments happen, Ted's first instinct is usually curiosity rather than judgment. Yes, I know. There it is. “Be curious, not judgmental.” The quote has been used so often that merely putting it on a presentation probably causes an Agile coach somewhere to involuntarily roll their eyes. It has been quoted, misquoted, printed on mugs, and turned into exactly the kind of corporate inspiration that eventually makes people allergic to the underlying thought. But overuse doesn't make an idea wrong.
Curiosity before judgment remains one of the most useful behaviors a leader can practice. When a deployment fails, you can ask who screwed up or you can ask what allowed the failure to happen. When a team misses a commitment, you can decide they aren't performing or try to understand what changed. When someone makes a decision you don't understand, you can assume incompetence or get curious about the information they had when they made it. We built entire practices around this: blameless postmortems, retrospectives, Five Whys, root-cause analysis, inspect and adapt.
Ted got a dartboard.
Maybe Scripted Is the Point
Which brings me back to the criticism that started me thinking about all of this: it's scripted. Of course it is. The writers can arrange the conflict so the lesson lands. Rebecca, Roy, Jamie, Nate, Keeley, and the rest of Richmond encounter situations conveniently suited to exploring leadership, trust, ego, failure, forgiveness, and change. That's what stories do.
And Agile does it too. We take complicated transformations and turn them into stories with a beginning, a revelation, and an ending. We tell the Toyota story. We tell the Spotify story. We tell the story about the team that became autonomous once the manager stopped telling them what to do. We tell the story about the wall. Not because we're lying, but because we're teaching. Fiction simply admits what it is doing.
A good story creates a safe little laboratory for human behavior. It lets us watch someone get leadership wrong, see the consequences, and then try something different. It compresses years of organizational learning into thirty minutes on a couch. If an Agile consultant tells a room full of people that teams perform better when individuals feel safe enough to challenge authority, everyone nods. When Ted Lasso shows us what that actually looks like, millions of people feel it.
I'm not sure the consultant has the stronger teaching method.
Agile Escaped the Conference Room
This is why I think some of the Agile world's eye-rolling at Ted Lasso has the whole thing backwards. If you've heard “be curious, not judgmental” at six conferences and twelve retrospectives, you're allowed to be tired of hearing it. If someone puts a goldfish on the opening slide of another leadership workshop, you're allowed a small internal groan. If you've spent twenty years working in Agile, some of what Ted teaches is going to seem painfully obvious. But that's our problem, not Ted's.
Most people aren't Agile consultants. The person sitting at home watching Ted Lasso might be a teacher, a nurse, a restaurant manager, a parent, a software engineer, or someone leading a team for the first time. They don't care that you've heard the quote before or which framework deserves credit. They care that the story helped them understand something. And perhaps we've become so accustomed to Agile as an industry that we've forgotten this was supposed to be the goal.
Agile wasn't supposed to win because everyone eventually learned Agile vocabulary. It was supposed to win because the ideas changed how people worked. Teams over heroes. Curiosity over blame. Learning over pretending we already know. Adaptation over blindly following the plan. Leaders creating environments where people can solve problems rather than prescribing every solution. Those ideas escaped the conference room. That's a good thing.
Millions of people who have never read the Agile Manifesto now understand that the person closest to the work might have the best answer, that leaders don't have to be the smartest people in the room, and that great teams need enough trust to fail and learn together. They may never call any of that Agile. They don't need to.
When an idea becomes so widely understood that people no longer need the experts' vocabulary to explain it, the experts shouldn't be annoyed. They should declare victory.
Believe
As Ted Lasso reaches its season finale, there will inevitably be another wave of quotes. There will be BELIEVE signs. There will be goldfish. Someone will post the dart scene. Someone else will roll their eyes. I'll probably enjoy all of it. Again, I have the tattoo. There's no point pretending I'm above this.
But beneath the sentimentality and the quotes that have been repeated a few too many times, Ted Lasso accomplished something worth recognizing. It took ideas about teams, leadership, trust, failure, curiosity, adaptation, and human potential that entire professional disciplines have struggled to explain and made them accessible to millions of people. No transformation roadmap. No maturity assessment. No framework. No certification.
Ted Lasso is teaching people to be curious before they judge. To make failure safe enough to learn from. To put the team ahead of the individual. To listen to the person who might know something they don't. To change when the evidence tells them they're wrong. And, eventually, to build a team strong enough that it doesn't need them standing in the middle of it. If those ideas sound familiar, they should. Agile has been trying to teach them for decades.
Ted Lasso just figured out how to get people to watch.
And he did it for free.