The Architecture of Understanding
Enterprise architecture should not only connect systems. It should help people form a clearer shared understanding of what the business is seeing.
Signature ideas
These are the ideas I keep returning to in my writing: not as slogans, but as working lenses for understanding enterprise systems, AI and the responsibilities that appear when technology begins to influence decisions.
Enterprise systems. Artificial intelligence. Decision-making. Wisdom.
The idea map
Enterprise architecture should not only connect systems. It should help people form a clearer shared understanding of what the business is seeing.
When AI recommends or acts, the organisation needs a visible record of evidence, permission, escalation and consequence.
Data lineage asks where a value came from. Authority lineage asks who allowed that value, model or recommendation to influence reality.
Read access is not recommendation authority. Recommendation authority is not approval authority. Approval authority is not execution authority.
The goal is not simply faster reports. It is better judgment at the point where people, systems and consequences meet.
Some of the hardest questions about AI are not about outputs alone, but about what can and cannot be known from the outside.
Technology can process, predict and recommend. Meaning, responsibility and wisdom still need a human home.
Start here
AI authority
How leaders must redesign enterprise architecture for the era of algorithmic delegation.
Read the essay →Workflow governance
Why enterprise AI cannot be treated as a side experiment once it starts shaping daily decisions.
Read the essay →Decision intelligence
What changed across twenty-five years of data systems — and what did not.
Read the essay →The thread beneath the work
This page is a living map. As the writing grows, the ideas will become clearer, sharper and more useful.