Agility is not a vibe

I was watching a webinar lineup go up about how to make smarter twists and turns in a customer-facing business. Good speakers, decent topic. But I noticed how often the language of agility has slipped into being a soft synonym for change-fluency, as if the goal were to be the kind of leader who is comfortable saying the words 'pivot' and 'adapt' on stage.

Agility is a property of the system, not the leader

A leader who personally enjoys change is not the same thing as an agile organisation. I have worked with brilliant, change-loving executives whose companies turned like oil tankers because the actual machinery underneath them was rigid. The leader was nimble. The system was not. The system always wins that argument in the end.

Real agility lives in places that are not glamorous to talk about on stage. It lives in how quickly your finance team can re-forecast. It lives in whether your legal team is set up to read a new contract template in days rather than weeks. It lives in whether your engineering pipelines can ship a meaningful change to a real customer in hours, with the safety nets to roll it back if you have to.

A test I use

When someone tells me their organisation is agile, I ask a small question: how long does it take, end-to-end, to change a price for a product? Not the technical change. The full path from "we have decided" to "the customer sees the new price". Most large companies, when they answer honestly, find a number that horrifies them. The horror is useful. It is the start of an actual programme of work.

The conferences will keep using the word 'agility' as a vibe. That is fine. But inside our own organisations we owe each other a harder definition. Otherwise we end up with a generation of leaders who know how to talk about adaptation and a generation of systems that cannot adapt.

What I would tell a peer who has just been handed an "agility transformation"

Pick three concrete journeys. Pricing. Onboarding. Incident response. Map the end-to-end clock time on each one. Cut it in half. Do not tell anyone you are running a transformation. Just produce the new clock times and let the rest of the organisation reverse-engineer how you got there. That is how change actually moves through a large company.