Habitat 67 — stacked concrete cubes rearranged into homes

PRACTICE 02 — TRANSFORMATION

Change that survives contact with Monday morning.

DORA, NIS2, operational resilience — delivered as a better way of working, not another binder for the shelf.

THE PROBLEM

0

PAGES OF POLICY HAVE EVER
STOPPED AN ATTACK ON THEIR
OWN. PEOPLE AND HABITS DO.

Why most transformation programmes stall.

The pattern is familiar. A regulation lands, a programme is stood up, a big firm arrives with a maturity model — and a year later you own a few hundred pages nobody reads and a set of controls people quietly work around.

DORA and NIS2 aren't document requests. They ask whether your firm actually behaves differently under stress — and that's a question about your operating model, not your paperwork.

Crumpled tracing paper — the retired template

Most of it ends up here anyway.

HOW A PROGRAMME RUNS

WEEKS 0–6

Diagnose

We map how security actually works day to day, not how the documents say it does. You get an honest picture of the gaps, in priority order.

WEEKS 6–10

Decide

Operating model, controls and priorities agreed with your executives. The change has owners before it has milestones.

WEEKS 10–26

Deliver

We work inside your teams — retiring controls nobody can explain, building fewer and sharper ones, and testing them until they hold.

FROM WEEK 26

Hand over

Capability moves across to your people, cadence by cadence. What still works a year later is the point.

WHERE WE'RE USUALLY CALLED IN

RELATED

We'd rather leave you a better firm than a thicker binder.

Start a conversation