From Waterfall to Hive: A Twelve‑Step Journey to Agility

In meeting rooms, the slides are beautiful. There is a strategy, a roadmap, and perhaps even a “target operating model”. On the walls, you might see words like “agility”, “customer‑centricity”, “innovation”. On the floor, the reality is different. Frontline staff are waiting for “simple” tasks from above. Middle managers are translating strategy into PowerPoint. A few people at the top are trying to hold the whole picture in their heads and feel increasingly alone.

For many years, I walked into such organisations as a coach. I arrived with tools, frameworks, and good intentions, and I quickly noticed something: the same patterns kept appearing, regardless of industry or country. The names were different – project, programme, agile release train, tribe – but the underlying models were strikingly similar. Some people thought; other people executed. In between, there were relays. The whole company served the tip of the iceberg.

To make sense of this, I began sketching what I saw. I drew how information actually flowed, who talked to whom, who never met customers, who carried risk, and who owned decisions. This became ORPO (Operational Business Review) – a snapshot, a Polaroid of your organisation for those of my generation. When you watch this snapshot carefully, you see where strategy bends, where messages get filtered, and where people lose sight of why they are doing what they do.

At some point, I realised that I was not looking at thousands of unique situations but at a limited set of recurring stereotypes. During my experiments, I identified twelve organisational stereotypes – eight tactical and operational, four managerial – that made it possible to say: “This is the model you are in, and these are the models that could realistically be next.” In other words, these stereotypes help you discover your acceptable level of agility, your Requisite Agility, instead of chasing a generic ideal.

This book is built around those twelve steps. It starts with the Unknown, where alignment is absent and “team” is mostly a slogan. It passes through familiar stops: the project manager as new hero, the dedicated project team, Proto‑Agile, Proto‑Scrum, Old Scrum, and the first mature Scrum teams. It continues towards company‑wide agility and ends with an agile organisation designed as a hive and its swarms – a platform with simple rules where self‑organisation, accountability, and resilience become a new routine.