By Stuart Dee
Over the years I have bought many books on architecture and, as you invariably find, they tend to fall into one of two camps. Either they are heavy on technology, or they are weighted towards frameworks. Titles that promise practical guidance often deliver dense theoretical models, lengthy methodology descriptions, and abstract principles that feel far removed from the reality of a working architect’s week. What they rarely address is the human side of the role: how to navigate a difficult stakeholder conversation, how to influence a decision you have no formal authority over, or how to explain a complex technical risk to a board that simply wants to know whether the project will deliver on time and on budget. There was nothing that spoke to the practical, day-to-day work that architects have to learn the hard way, through experience, through mistakes, and through the gradual realisation that technical excellence alone will only take you so far.
Architects today face a quiet paradox. We are hired for our technical expertise, yet the moments that define our careers rarely hinge on technology alone. The ability to influence without authority, to translate complexity into decisions, and to build trust across organisational boundaries is what separates architects who progress from those who plateau. Those who recognise this early adapt their focus. Those who don’t often find themselves sidelined despite deep expertise. In a world where delivery is accelerating and AI is reshaping the boundaries of what can be automated, the traditional image of the architect; isolated, document-driven, and advisory is no longer fit for purpose. As organisations embrace agility and continuous delivery, architects must shift from being the authors of static artefacts to becoming strategic enablers of outcomes.
The Governance Trap
Governance has long suffered from a reputation problem. In agile environments it is frequently seen as the thing that slows everything down, the layer of process that exists to say no. Yet the architects who thrive in fast-moving organisations have reframed governance entirely, shifting it from a subjective checkpoint into a mechanism that gives teams more freedom, not less. The difference is not the process itself; it is the decisions you choose to elevate. Governance becomes powerful when it clarifies boundaries, accelerates alignment, and removes ambiguity. When it does that, teams stop seeing it as oversight and start seeing it as support.
Three Shifts That Change How Architects Are Perceived
To make this tangible, here are three small behavioural changes that immediately alter how architects are seen across an organisation.
The first is to start with the outcome, not the explanation. Architects often lead with context, history, and detail. Stakeholders want clarity. Opening with the outcome you need; the decision, the direction, or the constraint reframes you as someone who accelerates progress rather than adds to the noise.
The second is to use governance as guardrails, not gates. A handful of clear, non-negotiable principles gives teams the confidence to move quickly without constant review. It is a lightweight approach, but it transforms governance from a blocker into an enabler and repositions the architect as a partner in delivery.
The third is to frame risks in a way that moves work forward. Pairing every risk with a next step that preserves momentum signals partnership rather than policing. The goal is not to present problems but to motivate action and that distinction earns trust faster than almost anything else.
These are small examples, but they illustrate a broader truth: the modern architect’s impact comes less from technical depth and more from how effectively they shape decisions.
The Skills Nobody Taught You
Technical careers rarely prepare architects for the moments that matter most, influencing a room, structuring an argument, or adjusting your communication style to the audience in front of you. These skills are learnable, but they are rarely taught, and they increasingly define the trajectory of an architect’s career. The challenge is that most practitioners do not realise they need them until they are already in the room and struggling.
Artificial intelligence adds another dimension to this. It is already automating parts of the role that once required significant time and expertise. For some, this feels like a threat. For others, it is the most significant opportunity the profession has seen in a generation. Which side of that line you end up on will depend less on your technical knowledge and more on where you choose to invest in yourself.
The Manifesto Behind the Book
At the heart of Practical IT Architecture is a short, sharp manifesto, a set of principles that capture what modern architecture actually requires. It is not a framework, and it is not a methodology. It is a mindset shift. The themes touched on in this article are a starting point, but the manifesto itself goes deeper: how architects create clarity, how they earn trust, how they make decisions visible, and how they enable delivery without becoming bottlenecks. It is the backbone of the book, and the reason many readers describe it as the thing they wished they had ten years ago.
Practical IT Architecture: A Concise Guide to Effective Practice by Stuart Dee is available now through Amazon Books. Further information is available on the book’s website.