Declaring Agile by Fiat

Cyclic Disruption: A Series on Technology and Human Nature

The Situation

It was the early 2000s, I was working at a large financial institution. Although the headiness of the “dot com” frenzy had died down somewhat, there was still a heavy focus on driving rapid technology change (do more, do it faster, maintain quality).  To support that, senior executives had decided it was time to “get modern.” Word spread quickly: leadership was going to announce a major shift in how projects were run.

The day of the rollout, we packed into a windowless conference room that smelled of dry coffee and the faint chemical bite of whiteboard markers. A projector hummed in the corner, throwing slides onto a screen with the kind of blue-gradient template that was standard issue back then. At the top of the deck, in bold letters, was the headline: Becoming Agile.

The announcement was short and absolute: “We’re Agile now.”

By the next week, the signs of change were everywhere. Project managers were rechristened as Scrum Masters. Daily stand-ups were scheduled in meeting rooms that had never seen anyone standing. Whiteboards were lined with sticky notes in bright columns labeled To Do, In Progress, Done. New consultants paced the hallways explaining what a sprint was supposed to look like.

On the surface, it looked like transformation, a fresh vocabulary with new tools. The energy of progress was heralded by management.

But to those of us actually building systems — writing code and pushing projects forward — it felt incredibly hollow. The requirements were still written months in advance (poorly), budgets were still locked for the year, and the same executives who had declared us Agile still wanted the comfort of Gantt charts and milestone decks.

One of the developers in my group summed it up during a stand-up when he leaned over and whispered: “This is just waterfall with more work.”

The Reality on the Ground

That line stuck with me, because he was right. We were going through the motions of Agile without changing the way we actually worked. The ceremonies were there, the language was there, but the culture remained untouched.

Leadership wanted the outcomes that Agile promised — speed, adaptability, collaboration — but they wanted it without giving up the predictability of traditional project management. They wanted sprint boards and annual budgets, retrospectives and five-year roadmaps, and daily stand-ups PLUS all the historical artifacts.

It was Agile as theater, by decree.

The intent wasn’t bad. The bank needed to modernize, to keep pace with younger, faster firms, but declaring transformation by fiat created the illusion of progress without the substance. It let leaders check the box of modernization while leaving the harder, slower work of cultural change untouched.

The Pattern Repeats

I’ve seen this rhythm enough times to recognize it. New approaches arrive full of promise. Leaders seize on them quickly, often too quickly, declaring change before the foundations are in place. The forms appear first — the meetings, the posters, the new vocabulary — but the substance lags.

This wasn’t unique to Agile. A decade earlier I had seen it with Executive Information Systems, where dashboards were unveiled to executives who still wanted binders. A decade later, I would see it with cloud computing, where firms proclaimed their cloud strategies while insisting no sensitive data could leave the data center.

The pattern is familiar: declarations move faster than the actual work of change.

A Familiar Reflex

It’s a reflex born of pressure. Leaders want to reassure employees, investors, regulators, and themselves that they are not standing still, so they reach for certainty in the form of bold declarations.

History offers plenty of examples. Factories in the early 20th century replaced their steam engines with electric motors but kept their floor plans organized as if steam were still driving the belts. The machinery had changed, but the workflow remained Victorian. The real transformation didn’t come until factories reorganized themselves around assembly lines and automation.

Declaring change before it takes root provides a sense of momentum, but it also delays the harder work of realignment. We rename the process and convince ourselves that we’ve changed it, but the form is not the function.

Why This Matters Now

I look back on the Agile push of the 2000s as a turning point — proof that declaring progress and achieving it are rarely the same thing.

Every new wave of technology tempts organizations to declare victory before the work is done., to believe that renaming the process is the same as changing it. Credibility, once lost, is hard to win back. When teams see that leadership declarations aren’t matched with action, trust erodes. The next attempt at transformation becomes that much harder.

With today’s tools, the stakes are higher. Intelligent systems promise to reshape operations and decision-making, but none of that will matter if organizations repeat the same mistake — assuming that declaring transformation is the same as living it.

Your Next Encounter

Declarations have value. They signal intent and create a shared language for where an organization wants to go. But they aren’t the shift itself.

I’ve seen this in every major wave of change I’ve lived through — from the first neural nets I worked on in the 1980s, to Agile in the 2000s, to the early battles over cloud adoption. The announcement always comes first. The real change arrives later, often more quietly, in the way people actually decide, work, and measure progress.

Those moments are easy to miss because they don’t arrive with a headline or a rollout meeting. They show up in small choices: how a team solves a problem when the old rules no longer apply, how a leader responds when the plan falls apart, what gets valued when the metrics shift.

That’s where transformation is won or lost. Announcements set direction. Living into them — in those day-to-day decisions — is what makes the difference.

Previous Post: The Fear We Forget

Next in this series: “Cloudy with a Chance of Disruption” — Why even obvious progress meets disbelief before it meets adoption.

About this series: Cyclic Disruption explores patterns in how humans adapt to transformative technology, drawn from four decades of experience in development, consulting, and leadership. Each essay connects a past moment to today’s dilemmas — showing what we can learn when we stop treating our own creations as strangers.