The Organisational Resilience Lattice — a systemic methodology for weaving resilience into the fabric of the enterprise.

Strategy is the set of explicit choices about where to compete, how to win, and what the enterprise will refuse to do. In the Lattice, strategy is judged not by the document but by whether operating decisions visibly defer to it.

TODO: describe the typical failure pattern — strategy decks that never translate into operating principles, leaving middle managers to invent priorities week by week.

TODO: describe what good looks like — every quarterly plan, hiring decision, and capital allocation traceable to a named strategic choice.

Governance is the architecture of decisions: who decides, who is consulted, who escalates, and where oversight ends and management begins.

TODO: describe the typical failure pattern — boards drawn into operating decisions, executives drawn into board-level oversight, and escalation paths that route around the people who should decide.

TODO: describe what good looks like — documented decision rights, predictable cadence, and a clear distinction between the chair's domain and the CEO's.

People covers role design, capability, incentives, and the observable leadership behaviours that determine whether the operating model functions or fragments under pressure.

TODO: describe the typical failure pattern — ambiguous roles, incentives that reward output not outcome, and leadership behaviour that contradicts the stated operating model.

TODO: describe what good looks like — role-clear teams, incentives aligned to the KPI tree, and leadership behaviour visibly modelling the change.

Process is the end-to-end flow of value, governed by controls and managed with BPM discipline. The Lattice scores process not on diagrams but on adherence and adaptability under stress.

TODO: describe the typical failure pattern — process maps that exist only in audit binders, with operational reality run on tribal knowledge and workarounds.

TODO: describe what good looks like — process owners with authority, controls embedded in the workflow, and measurable cycle-time improvement.

Change capability is the institutional muscle for converting design into adoption. It spans organisational change management, communications, training, and benefits realisation.

TODO: describe the typical failure pattern — change treated as a launch event, communications mistaken for adoption, and benefits realisation orphaned after go-live.

TODO: describe what good looks like — change capability embedded in line management, adoption tracked alongside delivery, and benefits owned by the business not the programme.

Technology in the Lattice is judged as an enabler of the operating model, not as a portfolio of its own. Architecture, data, and tooling are scored on the fit they offer to the strategy and process strands.

TODO: describe the typical failure pattern — technology roadmaps disconnected from operating-model design, data fragmented across silos, and tooling that automates the wrong process.

TODO: describe what good looks like — an architecture that flexes with the operating model, trusted data feeding governance, and tooling that removes friction from the value flow.