Industry Insights
2020: When the Playbook Stopped Working
In January 2020, I wrote about the gap between transformation rhetoric and delivery reality. I didn’t expect the universe to provide such a dramatic case study within two months.
COVID-19 didn’t just disrupt business operations. It dismantled the assumptions that most delivery methodologies were built on. Overnight, every engagement went remote. Discovery workshops moved to Teams calls. Whiteboard sessions became shared documents that nobody edited simultaneously. The hallway conversations that quietly resolved ambiguity — gone.
Waterfall Hit the Wall First
The first casualty was traditional gated delivery. Gate reviews depend on getting senior stakeholders in a room, walking them through a document, and getting a decision. When that room became a video call with fifteen muted participants, half of whom were dealing with a child in the background, the gate review became a formality. Decisions weren’t made. They were deferred. Programmes stalled — not because the work couldn’t continue, but because the governance model assumed physical presence.
Organisations that relied on heavyweight documentation fared no better. The analysts who produced those hundred-page requirements specs needed access to subject matter experts — people who were now drowning in their own operational crises. Discovery slowed to a crawl.
Agile Struggled Too
Here’s what surprised me: agile teams didn’t automatically thrive. The agile manifesto values individuals and interactions over processes and tools — but when interactions were reduced to a grid of muted cameras, the model lost its engine.
Stand-ups became status reports. Sprint demos played to silence. The informal, continuous feedback that makes agile work — overhearing a conversation, catching someone at their desk, sensing the energy in a room — none of it translated to remote. Teams that relied on osmotic communication found themselves isolated and misaligned.
Retrospectives surfaced the symptoms but couldn’t fix the root cause. You can’t iterate your way out of a communication vacuum.
What Actually Worked
The organisations that adapted fastest weren’t the ones with the best agile maturity scores. They were the ones with the clearest analysis upfront. When I looked at which programmes maintained momentum through the spring and summer of 2020, a pattern emerged: the teams that had invested in structured, concise problem definition before entering delivery were the ones that kept moving.
Less rework. Fewer misunderstandings. Developers who understood not just what to build but why — which meant they could make sensible decisions autonomously when they couldn’t get a quick answer from a product owner.
The teams that had skimped on analysis — the ones relying on “we’ll figure it out in the sprint” — were the ones sending confused Slack messages at midnight, building features that solved last quarter’s problem, and burning through budget on rework.
Transformation Got Real
There was a silver lining. COVID turned digital transformation from a PowerPoint aspiration into a survival imperative. Organisations that had been “considering” cloud migration did it in weeks. Customer portals that were on a two-year roadmap launched in months. The urgency was real, and it cut through years of institutional inertia.
But the speed also exposed the cracks. Fast delivery without clear analysis produced solutions that worked but didn’t quite fit. Systems that were deployed under pressure became the technical debt of 2021.
2020 taught me something I’d suspected but couldn’t prove: the methodology debate — agile versus waterfall — was the wrong argument. The real differentiator was the quality of thinking that happened before anyone started building. Get that right, and the delivery approach almost doesn’t matter. Get it wrong, and no framework can save you.