Existed First
The landscape was mapped
before the event proved it.
In 2022–23, working with Hackney's Economic Development team through UCL's Institute for Global Prosperity, the analysis produced a Wardley Map of the entire London Borough of Hackney technology landscape — anchored to the User, charted from Genesis to Commodity. The map was not built to predict a ransomware attack. It was built to answer a different question: where is this organisation's intelligence, and why can't it move?
The map showed two distinct component systems operating in parallel — one for LBH internally, one for external tech ventures and partnerships — with IT and HR appearing twice, each being rebuilt independently. AI sitting in the Custom-Built phase, showing early signs of moving toward Product. A red arrow pointing right on the Technology axis, annotated simply: the direction of travel.
The annotation read: "New technology evolves and gets standardised. Two different component systems are mapped — for LBH and for external tech ventures." What it meant: the borough was paying to solve problems that had already been solved. Everywhere except inside itself.
When the 2020 Pysa ransomware attack encrypted 440,000 files and paralysed every service the borough ran — housing, benefits, planning, social care — it did not reveal a new problem. It revealed the exact vulnerability the map had already named. Centralised intelligence. No distribution. No flow. A single point of failure that a criminal gang could reach with commodity tools.
The question was not how to harden the vault. The map said: stop building vaults.
The original Wardley Map — London Borough of Hackney
A Wardley Map visualises the components of a system, and how evolved they are. It's a strategic tool for understanding where things are, where they're heading, and what that means for decision-making.
Reconstructed from the UCL Institute for Global Prosperity research, 2022–23. User-anchored. Components plotted from Genesis to Commodity. The prediction line — Technology evolving toward industrialisation — was drawn before AI reached commodity. It was an observation of where things were heading. Events confirmed it.
↗ Prediction line — drawn 2022–23
Three conditions.
All named before the event.
The UCL research brief asked the right questions: how does innovation already existing in the borough get supported rather than overridden by top-down approaches? How does data get systemised, processed and exchanged between departments to drive bottom-up, unbiased solutions? The Wardley Map answered them. The answers were uncomfortable.
Intelligence that flows
cannot be encrypted.
The architecture was not a response to the attack. It was the answer to the map. Four layers, designed to move intelligence through the organisation in real time — from resident need, through cross-departmental context, through machine-readable specification, to autonomous action.
Outcome
Architectural sovereignty.
The map becomes the platform.
The distinction between tech-based innovation and digital transformation — the central question of the UCL research — resolved into something simpler: innovation without architecture is noise. Transformation is what happens when the organisation's intelligence is made to flow.
Hackney had the ambition. It had the people. It had — as I saw working inside the Economic Development team — extraordinary institutional knowledge about its residents, its communities, the real shape of inequality in one of London's most complex boroughs. What it lacked was a layer that made that knowledge actionable, in real time, without depending on any one person holding it in their head.
The organisations that understand what happened in Hackney will build architecture before the event. The ones that don't will learn the same lesson at the same cost.
The Wardley Map drawn in 2022–23 showed AI in Custom-Built, moving toward Product. That prediction has now resolved. AI is commodity infrastructure. The question is no longer whether to use it. It is whether the intelligence architecture exists to make it act on what the organisation actually knows — and intends.
The map was drawn before the question was fully understood. That is what systems thinking is for.
The lesson is not
about Hackney.
Every organisation working on complex, real-world problems — green economy transition, social care coordination, urban planning under pressure — has the same structural condition. Rich institutional knowledge. No architecture to make it flow.
The data exists. The policy intent exists. The people doing the hardest work are brilliant. The missing layer is always the same: a system that can read what the organisation knows and turn it into real-time action without re-explaining itself from scratch every time.
That layer is buildable. It is diagnosable before the event that makes it obvious. The audit exists precisely to find it — before the cost of not having it becomes undeniable.
Now draw your map.
The Context Architecture Audit maps where your organisation's intelligence is stored rather than flowing, siloed rather than distributed, improvised rather than specified.