Business agility starts to ail when teams under economic pressure fall back into old patterns of control and micromanagement. Two schemes from emergency medical services help with the diagnosis: AMPLE looks at the history, the “medication” given so far and where energy was invested most recently, while ABCDE checks whether people can speak freely, the rhythm of work, decision paths and the protected space for agile working. Recovery takes patience and targeted single measures, not more layers of methods.
Key Takeaways
- Companies in crisis fall back into old control patterns almost automatically, because agile working never became part of their DNA and was only imposed on them.
- The ABCDE scheme from emergency medical services maps directly onto ailing agility: airway, breathing, circulation, disability and environment as the order of priority for the diagnosis.
- Introducing too many agile measures at once makes it impossible to see what works and how measures interact, just like a doctor who gives every medication at the same time.
- In many teams the word “agility” alone triggers resistance, which is why the same concepts get repackaged under new names like New Work or learning organization.
Business Agility Isn’t Dying, but It Can Get Sick
Agility as a way of working isn’t going away. What’s wobbling in many companies is how it’s put into practice at work and how people talk about it. That is the real state of business agility today: the principle holds, the implementation struggles.
The idea behind agile working is older than the Agile Manifesto of 2001. Lean has agile elements built in, and even early large-scale projects came close to cross-functional teams working in iterations. So when people talk about the death of agility, they rarely mean the principle. They usually mean whatever was rolled out under the agile label in one particular company.
That’s where a different question pays off: is agility ailing in a team, or did it never become part of how the team works? The answer decides whether reviving it makes sense or whether another approach fits better.
Why Companies Fall Back into Old Patterns
When things get tense, companies reach for familiar patterns. Once money gets tight and doubts grow about years of agile initiatives, the organization switches into survival mode.
In that mode, the same thing happens as with people under pressure: you act the way you always have. For managers, that often means more control and micromanagement. “Let’s do it the way we did back then, when it worked” becomes a reflex.
That reflex shows that agile working never became part of the company’s DNA. Where agility is truly anchored, the question of falling back doesn’t even come up.
Some Companies Can’t Work Any Other Way
In some companies, agile working is so natural that they can’t even put a name to it. Born-digital companies and large cloud providers react to the question of how they became agile with a blank look: “How else would we work?”
These companies have never worked differently. Agility is part of how they survive, which is why there’s no origin story behind it. They’ll keep working in an agile way because it’s built into their structure.
Where an agile way of working hasn’t taken root on its own, there’s a reason. Agile work is often out of step with everything else in the organization: the rules of the game, the structures and the mentality don’t fit together. Two worlds collide. When things get critical, something that was pushed in with a lot of force is hard to hold on to.
When Agile Working Fits, and When It Doesn’t
Not every retreat from agile practices is a failure. Many companies rolled out agility everywhere with a grand gesture because it was popular. Today, organizations are more deliberate and ask where agile ways of working are really needed.
In some industries, classic, tightly managed project management is the better choice. People acting in critical situations don’t work in an agile way. In emergency medical services, clear schemes, rules and protocols give staff the confidence to stay able to act.
The lesson: clear rules aren’t the opposite of good work. In some contexts, they’re what makes it possible. So don’t ask whether agility is good or bad. Ask where in your organization it’s the right approach at all.
The AMPLE Scheme: A Diagnosis Before You Intervene
Before you intervene in an organization, you need a picture of its condition. The AMPLE scheme from emergency medical services gives you a structure for that. Each letter stands for a question you ask about the situation.
- A for allergies: Is the organization allergic to something? For many, the word “agile” itself is the trigger. Then the same thing gets repackaged under new names: effective working, learning organization, New Work.
- M for medication: What was administered most recently? A Spotify model, OKRs, five agile coaches: the latest measures reveal a lot about the treatment so far.
- P for past history: Has the company been in crisis for years anyway? Was there a major break in the past?
- L for last meal: Who is still putting energy into it? If a lot of effort recently went into new methods, the team will throw up at the next suggestion.
- E for events: What specific event led to the current situation? A workshop, a change of CEO, after which nobody talks about agility anymore.
The last-meal image goes a long way. A doctor won’t give medication to someone who just ate a big plate of pasta. In the same way, trying to introduce five more methods fails when a team is still digesting OKRs and everything else. “How are we supposed to digest all this?” is the most honest reaction.
Assessing the Acute Situation with ABCDE
For more serious cases, the ABCDE scheme from trauma care is the better tool. It sorts problems by priority: the first problem you find gets treated right away before you move on.
| Letter | In Emergency Medicine | Applied to the Team |
|---|---|---|
| A (Airway) | Is the airway clear? | Can people still talk, complain and speak their mind in the retro? |
| B (Breathing) | Is the person breathing steadily? | Is there still an agile rhythm, iteration and flow, or only bottlenecks? |
| C (Circulation) | Is circulation stable? | Do the communication paths work? Who decides, and who has which authority? |
| D (Disability) | Where is the fracture, the bleeding? | Which values, behaviors or methods are blocking things? |
| E (Environment) | What is the environment like? | Does the company still maintain the protected space for agile working? |
The order isn’t arbitrary. If something is stuck in the windpipe and the airway is blocked, there’s no point looking any further. For a team, that means: if people can’t talk openly anymore, any discussion about methods comes second.
The E often reveals the real cause. Agile working functions inside a single team with its own protected space, but not at scale. Then the problem lies in the environment: the other teams, the company’s attitude, a protected space nobody maintains anymore.
Why Removing Methods Often Works Better Than Adding New Ones
The most common mistake when agility is ailing is the reflex to add something. Someone comes back from a conference and wants to introduce OKRs or more retros, and everyone rolls their eyes because they can’t even cope with the methods they already have.
Sometimes reduction is the better therapy. Fewer meetings, shorter meetings, one method removed instead of one added. In that simplicity, a team can breathe again.
There’s a scientific principle behind this: change one thing and keep everything else constant, and you can observe the effect. If you keep piling on new things, you never know what worked or which interactions came into play. That’s the same reason a doctor doesn’t give all medications at once.
“One measure after the other, with plenty of time and rehab. Recovery takes time.”
(Miriam Sasse)
Recovery Takes Patience, Not a Deadline
Damaged agility rarely gets fixed in a week. If you injure your shoulder, it may take a year before you have full mobility again. A badly injured way of working needs time on the same scale.
This is often where management fails, expecting everything to be running again by next week. That pressure gets in the way of recovery. Give the process time, take one measure after the other and plan a real rehab phase.
The metaphors from emergency medicine create the distance you need. They help you look at the situation calmly instead of getting swept up in it. And in many cases, an organization that seemed to have stopped breathing is bouncing around the playground again shortly afterwards. Small, targeted steps can save more than it looks like in the acute moment.
Frequently Asked Questions
Is Agility Over When Companies Scale Back Their Agile Initiatives?
No. What’s faltering is the concrete implementation in the workplace and the discourse around it, not the principle itself. The idea predates the 2001 Agile Manifesto: Lean incorporates agile elements, and early large-scale projects were similar to cross-functional teams using iterative work. Those who speak of the death of agility usually mean what was rolled out under that label in a specific company.
How can you tell if agile work is truly embedded in an organization?
A good test is to ask about the company’s founding story. Born-digital companies and large cloud service providers react to this with confusion: “How else could it be?” They’ve never worked any other way; agility is part of their survival mechanisms. Where, on the other hand, the agile work style has never taken root on its own, the rules, structures, and mindset don’t align. In critical situations, the imposed framework then falls apart.
Do clear rules and guidelines contradict good work?
No. In some contexts, they’re a prerequisite for it. Those who act in critical situations don’t work in an agile way: In emergency medical services, fixed protocols, rules, and guidelines give employees the confidence to remain capable of taking action. The meaningful question, therefore, is not whether agility is good or bad, but rather where within an organization it is actually the appropriate approach.
What should be clarified before intervening in an organization?
A snapshot of the current state before the first measure is taken. The AMPLE scheme provides five questions for this: What does the organization react negatively to, what measures were most recently implemented, has the company been in crisis for years anyway, who is still putting energy into it, and what specific event led to the current situation? The most recent interventions reveal a lot about how the situation has been handled so far.
Why does the word “agile” meet with resistance in some teams?
Because the term itself has become a trigger, regardless of its meaning. In such cases, the same concepts are repackaged under different names: effective work, learning organization, New Work. Anyone who ignores this aversion and continues to use the old vocabulary loses the discussion on the matter before it even begins.
Which problem should be addressed first when multiple issues are causing friction in a team?
The ABCDE framework assigns priority to issues, and the first problem identified is addressed immediately. At the very top is the “airway”: Are people still allowed to talk, complain, and voice their opinions in the retrospective? Only then do rhythm and flow, communication and decision-making processes, obstructive values, and finally the environment follow. If a team is no longer allowed to speak openly, any discussion of methodology is secondary.
Does introducing additional agile methods help when the workflow stalls?
Usually not. The most common mistake is the reflex to pile on even more, while the team is already struggling with the existing methods. Simplification often works better: fewer meetings, shorter meetings, removing one method instead of adding one. If you keep everything else constant and change just one thing, you can actually observe the effect.
How long does it take for a damaged way of working to recover?
Significantly longer than a week. Think of it like an injured shoulder: it can take up to a year before it regains full range of motion. The same applies to a severely damaged work process. If management expects quick results, that pressure actually hinders recovery. It makes sense to implement one measure at a time and plan for a rehabilitation phase.
