Occasional writing on technical leadership, architecture, and governance.
An architecture review is often misunderstood as a documentation exercise. Someone arrives, reads the architecture documents, comments on whether they look reasonable, and leaves a report behind. This is not an architecture review. This is reading. A genuine architecture review examines what the organisation actually has — which is almost never what the architecture documents …
An organisation without a roadmap is not undirected. It is directed by whatever is shouting loudest at any given moment. The strategic vacuum does not feel like a vacuum from the inside. There is plenty of activity. Decisions are being made. Projects are being funded. Vendors are being selected. The organisation appears to be moving. …
It usually starts with a brief like this. “I just want a website. Nothing fancy. A few pages, a contact form, something that looks professional. A thousand pounds, give or take.” The website gets built. It does what was asked. For a while, this is enough. Then the business grows. The escalation Year one. The …
Most architectural conversations start with the platform. Which CRM, which CMS, which ERP. The data model emerges from whichever platform was selected — shaped by its assumptions, its category structures, its custom field conventions. This is backwards. The data is the durable asset. The platforms are replaceable. An organisation that lets the platform choose its …
The observation is not original. It is widely attributed to Deming, though the precise origin is disputed. The point survives the attribution: if an organisation consistently produces the same operational failure, the cause is rarely the individual at the point of failure. It is the system that made that failure inevitable. Recurring problems are structural. …
Most organisations confuse three things: policy, compliance, and governance. Policy is what you wrote down. Compliance is what you can prove. Governance is what actually happens when nobody is checking, on a normal Tuesday, in the middle of a busy quarter, when the team is under deadline pressure and the person who originally read the …
Integrations look like technical projects. Two systems, an API, some mapping, a sync schedule. The work is engineering. The deliverable is a connection. This framing is wrong, and the consequences are visible in every organisation that has built integrations without first answering a different set of questions. Who owns this entity? Who is allowed to …
The report is due. The manager is waiting. In the corner of the office, someone is four hours into a VLOOKUP, trying to reconcile two versions of the same data that have never quite agreed with each other. This scene is not a one-off. It repeats itself, in the same organisation, on the same schedule, …
Jurisdiction is not an administrative label. It is a set of live obligations that attach to an entity, travel with its data, and do not pause because the parent company is headquartered somewhere else. Most technology decisions made by international firms with EU operations are made without a clear understanding of this. The results are …
A car imported from the United Kingdom, purchased during EU membership. The manufacturer’s nagivation system asks for a country. Greece is on the list. Turkey is on the list. Cyprus — a full EU member state — is not. The system maps it to the Middle East. Nobody made that decision maliciously. Cyprus simply was …