Notes
Occasional notes on technology leadership: architecture, governance, operating models, and AI in IT operations. New notes appear here first.
Governance as decision enablement
Why good governance removes ambiguity instead of adding process, and how to build decision paths people actually use.
Build to run
Why new technology needs an operating model before it needs a roadmap, and what a clean handover into regular operations looks like.
Platform ownership
Integrating new platform services into an existing infrastructure organization: roles, responsibilities, and operating models without parallel structures.
Standardization before individualization
Complexity as the real cost driver in IT, and how to make exceptions deliberate rather than accidental.
AI in IT operations, soberly
Automation, knowledge access, operational relief: what works today and what to leave alone.
Target pictures people actually use
Why most target architectures die in slide decks, and what turns one into a navigation instrument instead of a poster.
Shadow IT is feedback
When users route around official IT, that is data, not disobedience: a review of your paved road, written in effort.
The org chart is an architecture diagram
Conway's law for leaders: system boundaries follow communication structures, so designing the organization is designing the landscape.
After the last big upgrade
Evergreen operations: what continuous updating changes about budgets, testing, and ownership when no next migration project is coming.