I used to think leadership meant having all the answers and holding the reins. I believed a good manager stayed close to the work, checked it often, and stepped in whenever something went sideways.

Then I watched teams that others had written off outgrow me. I had given them the direction and stepped back, mostly because I ran out of hours in the day. They kept moving. They got better. And they did it without me hovering. That experience changed how I read the word agile.

The Word Got Loud and the Meaning Got Quiet

Agile shows up everywhere now. Sprint boards, stand-ups, retrospectives, velocity charts. Whole calendars fill with ceremonies that carry the name. When a term gets thrown around this much, I go back to a simple habit. I ask what problem it was invented to solve, then I judge everything against that. Agile started as a response to frustration. Teams spent months planning work in detail, only to deliver something the customer no longer needed. The plan was perfect, and the result was wrong. The fix was to keep changing how a group works as it learns. Deliver something small, look at it, adjust, deliver again. The willingness to keep changing was the whole point.

A Named Method Is a Tool, Never an Identity

Somewhere along the way, the tools became the identity. People started measuring teams by whether they ran the rituals correctly. I stay careful here. A named methodology is a set of tools in a bigger bag. It is never the work itself. 💡 A team can run every ceremony on schedule and still be rigid. The ceremonies were only ever a container. The harder thing for leaders inside them is to release control and let people own the work. This matters because most of what gets counted as agile resolves to a checkbox. Did the stand-up happen? Did the board update? Did the retro get scheduled? Anything you can observe, document, or simply claim becomes gameable. You tick the box, and the reality it was supposed to point to disappears.

Follow the Discomfort to the Real Objection

When I bring this up, some leaders call it soft. They say teams need structure, oversight, someone accountable at the top. I have learned to follow that discomfort to what sits underneath it. The objection is rarely about structure. It is about control, and the fear of giving it up. Trusting people to move before you know they will is uncomfortable. I have felt it. I took over an environment thick with top-down habits and chose to loosen my grip on it. Every instinct told me to check the work more, not less. The discomfort was the signal that something was happening.

Ask Who Grows Inside the Arrangement

Here is the question I use now to judge whether a way of working actually means anything.

Do the people inside this system get more capable over time, and could they carry on without the person at the top?

That single test cuts through most of the theatre. A team drowning in ceremony and relying on a single leader for every decision has not become agile. It has decorated its dependence. A team that keeps getting more capable, more trusted, and more able to own outcomes has the real thing, whatever rituals it happens to run. This shift shows up across industries. Organizations are moving toward self-organizing teams and away from command-and-control structures, a shift the original agile principles outlined decades ago, when they prioritized individuals and interactions over processes and tools.

Judge the Direction of Travel, Not the Snapshot

I prefer to judge a team by whether it can keep changing, rather than the state it happens to be frozen in today. A snapshot tells you where a team stands this week. The direction of travel tells you whether the team is evolving or stuck. Agile lives in that direction. The teams that surprised me were not the most polished. They were the ones learning fastest, adjusting how they worked without waiting for permission, and being trusted more with each cycle. Research on delivery performance backs this pattern. The long-running DORA research found that teams delivering in small, frequent increments detect problems earlier and recover faster, which lines up with everything I saw firsthand.

The Leader's Real Job

I used to lead like a hero. I wanted to be the one who solved the hard thing, the one people came to. Now I try to lead like a healer. My job is to build an environment where people grow, and then to get out of the way enough that they can. That reframe cost me something. It meant giving up the identity I had built around having answers. It meant trusting the process of people developing over the comfort of controlling the outcome. ⚠️ People-first language means nothing when a leader has no intent to honour it. If you say you trust your team and then check their every move, they read the second message and ignore the first.

What Agile Means When You Strip It Down

Agile is a commitment to keep evolving how people work. It becomes real when leaders trade control for trust, and the team grows beyond needing them. The rituals can help. The boards, the cadences, the feedback loops all serve a purpose when they carry the harder thing inside them. On their own, they are furniture. So here is what I would ask you to check in your own team. Look past the calendar of ceremonies. Watch who is growing. Notice how much control still sits at the top. Track whether the direction of travel points toward greater capability and trust, or toward greater dependence. That is the measure that cannot be faked. Everything else is a container waiting for you to put something real inside it.