Most content on influence in senior technical work treats it as a skill. Something learnable. The ability to read a room, frame a technical position in the language of the person receiving it, time an intervention correctly, manage the dynamics of a difficult conversation. These capabilities are real and they are necessary. The architect who…
Two editions of this newsletter have laid the groundwork for a conversation that has not yet been named directly. Edition 12 argued that going AI-first requires more than deploying a tool into an existing process. It requires understanding the process, redrawing it around AI, and being honest about which human steps survive that redraw and…
Large organisations divide accountability deliberately. Risk sits here. Product sits there. Delivery sits somewhere else. Architecture somewhere else again. Each function has a reporting line, a governance obligation, a definition of what good looks like from its own position. That division is the rational response to scale, complexity, and the control requirements that accumulate in…
Everything written about senior architecture work is written after the fact. The strategy succeeded. The strategy stranded. The transformation landed. The transformation failed. The lessons get drawn from a position where the outcome is settled and the writer can see the arc cleanly. That distance is what makes the reflection possible. It is also what…
Most RAG deployments work in the demonstration. A question goes in. The right answer comes back. The room is impressed. The programme gets the green light. Then it goes to production. Real users. Real questions. Questions the demonstration never asked. And the system that looked entirely capable in a controlled environment starts behaving in ways…
The clearest signal that a high-performing team is operating beyond the organisation’s capacity to use them is not dramatic. There is no single moment where the gap becomes visible. It is a slow accumulation. Decisions that should be straightforward take months. Work that was produced to a high standard sits unused. Recommendations that were right…
Edition 12 of The Architect’s Mundane. This edition examines why enterprise AI adoption has stalled at the tool deployment stage and what AI-first process redesign actually requires. Why the Tool Alone Does Not Transform Most large organisations have Copilot. It is the default starting point for enterprise AI adoption, rolled out broadly across functions, available…
How Decisions Get Made and How Long They Last Large organisations do not wake up one morning and decide to pursue a strategy. Someone decides. And that someone is almost always brought in, elevated, or empowered specifically to solve a problem that shareholders have identified as urgent. The sequence is familiar. A gap surfaces. Competitive…
Edition 5 of this newsletter looked outward. Twenty five years of technology paradigm shifts, from mainframe to AI, and what it felt like to live through them as a practitioner. That was an external arc. The world changing and the work changing with it. Edition 10 looks inward. This is a personal reflection. Not a…
The API Legacy There was a moment, roughly a decade ago, when APIs were the answer to everything. Large organisations were facing a genuine crisis. Mobile had arrived. Digital channels were multiplying. The legacy estate, mainframes, MQ bridges, batch processes, point-to-point integrations, was never designed to be consumed by an app on someone’s phone. APIs…