Read the system as it is
Observe the operating reality, not only the policy, organogram or presentation.
Approach
Read reality. Clarify authority. Design control. Test pressure.
The method keeps institutional analysis connected to decisions, dependencies, evidence and implementation.
Clarify authority and constraints
Identify who can decide, who can prevent, who bears consequence and which dependencies matter.
Map exposure and failure
Trace how operational, political, financial, technological and behavioural risks travel.
Design the architecture
Establish governance, controls, information flows, escalation and accountability.
Test it under pressure
Create an operating model that remains intelligible when conditions change.
Start with the system, not the label
Mandates rarely respect practice boundaries. Governance, finance, technology, regulation, logistics and human behaviour often meet in the same decision.
Separate fact, assumption, inference and recommendation
Traceability is part of the method. The evidence base, analytical judgement, uncertainty and recommended action should not be presented as if they were the same thing.
Design for use under pressure
An architecture is useful when boards, management, regulators and operators can understand who acts, with which information, under what threshold and what happens when conditions change.