Can One Architect Really Do It All?
Can One Architect Really Do It All?
On paper, the idea is appealing.
Yes, there are highly experienced architects who can span Solution Architecture, Technical Architecture, and even Enterprise Architecture. For the organisation, it sounds like a bargain, one architect instead of several costly roles. For the architect, it’s a chance to showcase depth, breadth, and flexibility. A multi-skilled architect feels like an always-employed architect.
So what’s not to like?
Quite a lot, once you step into the real world…
Single capacity
 Any reasonably sized initiative demands serious time and attention. Even the fastest, most capable architects eventually hit a wall. Sustained overload leads not to heroics, but to burnout, and quality suffers long before exhaustion is visible.
Single validation
 A core purpose of architecture is independent validation. When one architect designs and approves their own work, they’re effectively marking their own homework. The result is fewer challenges, weaker decisions, and missed risks.
Single experience
 No matter how seasoned an architect is, they bring only one set of experiences and perspectives. Architecture thrives on debate, challenge, and shared learning. No single person can cover every technology, domain, or emerging pattern—research alone can’t replace lived experience.
Single risk
 Concentrating enterprise knowledge in one individual is a major organisational risk. Documentation helps, but it never captures the full, undocumented understanding that lives in an architect’s head. When that person leaves, the gap is immediate and painful.
Career dead end
For the architect, there’s nowhere to grow and no succession path. The role becomes a trap, valuable, indispensable, and difficult to leave. 'Golden handcuffs' don’t make for healthy careers.
The idea of “one architect who does it all” sounds compelling until it’s tested against reality. With real experience applied, it quickly falls apart.
Much of this thinking stems from confusion about what architecture actually is and what architects truly do. Without that understanding, decisions get made that sound efficient and logical, but fail when exposed to the complexity of the real world.
What are your thoughts, and are they based on experience or theory?
hashtagPracticalEA. Visit PracticalEA.com
