Hands-on vs. Ivory Tower Enterprise Architecture: A Gandalf vs. Saruman Analogy

Why the best enterprise architects walk the road with the Fellowship, and the worst ones disappear into the tower.

Picture two architects.

The first sits in a glass-walled office on the 18th floor. His TOGAF certifications hang behind him. His ArchiMate models are immaculate, color-coded, and traceable to corporate strategy on three different axes. Business stakeholders rarely meet him; when they do, they leave the room more confused than when they entered. His diagrams are admired. They are also, quietly, ignored.

The second one you'll find in a workshop room with sticky notes peeling off the wall, sketching a flow on a whiteboard for a product owner who's about to launch. She speaks TOGAF and ArchiMate fluently, but only with other architects. With everyone else, she draws boxes and arrows. Her models are messier. Her decisions stick.

In organisations, architects are often described as strategic problem-solvers: the people who turn complexity into order and align IT, data, and governance with business objectives. Because of that mix of abstraction and authority, they're frequently compared to wizards.

But not all wizards are alike. And the difference between the hands-on enterprise architect, deep in business processes and mentoring teams, and the "ivory tower" architect, perfecting frameworks at a distance, is the difference between Middle-earth's two most famous wizards: Gandalf and Saruman.

Both are powerful. Both are learned. Only one of them is in the field when it matters.

1. The Tower vs. The Trail

This humorous 2x2 comparison image uses Gandalf from The Lord of the Rings to contrast two approaches to enterprise architecture.
Top-left: “Rigor of the TOGAF Method” shows Gandalf in an ivory tower holding a crystal ball — “Static Ivory Tower Architecture”.
Top-right: “Detachment from the Field” depicts Gandalf overlooking a vast battlefield — “Massive gap between strategy and execution”.
Bottom-left: “Dynamic Graphs & Boldo 360° Explorer” presents Gandalf as “The Field Architect” with interactive network graphs and a 360° explorer tool — “The Immediate Visual Bridge”.
Bottom-right: “Field Actionability” shows a smiling Gandalf — “Living, adopted, agile architecture”.

Hands-on Enterprise Architects speak TOGAF and ArchiMate with other architects, but use the business language and simple sketches with the rest of the organisation.

Saruman lives in Orthanc, a tower of black stone, sealed against the outside world. From there he studies, theorises, and issues decrees. He is, by every formal measure, the head of his order. He is also catastrophically out of touch.

Ivory tower architects play the same role. They excel at strategic design and frameworks like TOGAF or Zachman, defining principles and enterprise-level models that capture the organisation's systems, capabilities, and processes. The artefacts are often brilliant. But the architect operates at a distance from the teams that have to execute, making decisions on theoretical grounds without continuous contact with implementers or end-users. The result is a familiar gap: a beautiful target architecture that the rest of the organisation politely works around.

Hands-on architects, like Gandalf, are out on the road. They guide and mentor teams through complex challenges. They translate: TOGAF and ArchiMate among peers, plain business language and napkin sketches with everyone else. They don't just define the architecture. They continuously engage with the people who live inside it. They sit in product workshops. They walk the warehouse floor. They learn what the CFO actually means by "we need agility."

This grounded approach produces architecture that teams adopt rather than tolerate, bridging the gap between high-level strategy and the messy realities of execution.

Lesson learnt: Strategic thinking is necessary but insufficient. Architecture that isn't grounded in collaboration becomes a museum piece: admired, untouched, and ultimately irrelevant.

2. The Palantír Problem

Humorous 2x2 meme using Gandalf to compare two types of enterprise architects.
Top-left: “Ivory Tower Architecture: Perfect Theory” — Gandalf in a dark tower with network diagrams and a crystal ball, caption: “His artifacts are superb, but far from the Community.”
Top-right: “Back from the Field (The Script Crashes at 2AM)” — Epic battle with a Balrog representing SAP S/4HANA migration and NIS2 compliance nightmare.
Bottom-left: “Field Architect: Rejoin the Community” — Gandalf holding a network cable like a sword and Ethernet cable like a whip, “A network cable as a sword and a Boldo 360° vision for the rest.”
Bottom-right: “The Commitment That Takes It to the Next Level” — Gandalf fighting the Balrog with a glowing server, caption: “Knowing how to design the architecture is one thing. Making it actually work all the way through is another.”

Enterprise Architecture must evolve in line with technological advances, business needs, and team feedback. A model written once is a model already aging.

Saruman's downfall begins with a single object: the palantír, a seeing-stone he believes will give him perfect knowledge of the world. He stares into it. He stops listening to anyone else. He becomes convinced that what he sees is the whole truth.

Ivory tower architects have palantírs too. They're called the reference architecture from three years ago. They're called the EA repository nobody updates. They're called the framework I learned in my certification and have never questioned since.

Architects who rely too heavily on established frameworks can drift into a rigid, static practice. Their designs are based on best practices, and that's the trap. Best practices age. Once a model is signed off, the temptation is to defend it rather than revise it. The organisation moves on. The architecture doesn't. Within eighteen months, the target state and the real state are strangers to each other.

In contrast, hands-on architects treat enterprise architecture as a living system (see the Continuous Architecture manifesto). They revisit decisions on a cadence. They run field workshops. They invite feedback from IT and business units alike, knowing that the most valuable signal usually comes from whoever is closest to the pain. They borrow from solution architecture practices: fitness functions to monitor whether the architecture still does what it was designed to do (a topic that deserves its own article).

Gandalf gathers knowledge from hobbits, elves, men, dwarves, and the librarians of Minas Tirith. He revises his understanding constantly. Saruman, certain he already knows, looks into a stone and sees only what the stone shows him.

Lesson learnt: The architect's job isn't to produce the right answer once. It's to keep producing the right answer as the question changes.

3. Joining the Fellowship

Hands-on architects don't define the architecture and walk away; they stay engaged throughout the journey, helping to solve problems as they arise.

When the moment comes to actually do something about Sauron, Saruman stays in his tower. Gandalf joins the Fellowship.

That single choice is the analogy in a sentence.

Ivory tower architects focus on high-level design and hand execution to project managers and delivery teams. They may sit on steering committees and review milestones, but they're not in the room when the migration script fails at 2 a.m. or the integration partner pushes back on the chosen pattern. This separation looks efficient on paper. In practice, it means the architect rarely sees their assumptions tested, and is therefore rarely in a position to correct them. When a transformation hits the inevitable wall (ERP migration, cloud re-platforming, AI scaling, data governance), the people closest to the design are the furthest from the problem.

Hands-on architects take ownership of the architecture's impact. They show up for the Balrogs: the SAP S/4HANA migration nobody wants to lead, the data governance initiative that's been stalled for two years, the cybersecurity programme that touches every business unit, the AI deployment that needs to scale without becoming a compliance disaster. They don't just sign off; they stay engaged, adjust the design as reality reveals itself, and accept that an architecture only counts if it survives contact with execution.

Gandalf falls with the Balrog. He also gets back up, wiser, sharper, and, as we'll see, considerably more powerful.

Lesson learnt: Architecture decisions don't end at the diagram. The architect who follows them into execution is the only one who can refine them when reality pushes back.

Are You Becoming Saruman? A Quick Diagnostic

If three or more of these feel uncomfortably familiar, the tower is closing in:

• The last time a business stakeholder voluntarily walked into your office was over a quarter ago.
• Your reference architecture hasn't been materially updated in the past 12 months.
• You can name the latest TOGAF version but not the top three pain points of your largest business unit.
• When projects go wrong, you're informed in a steering committee, never in the war room.
• You have an opinion about every framework and a working relationship with very few delivery teams.
• The word "pragmatic" makes you slightly suspicious.

None of this makes anyone a bad architect. It makes them a distant one. The fix is geographical before it is intellectual: get out of the tower.

Conclusion: Be More Gandalf, Less Saruman

Here's the part of the story worth remembering. Gandalf doesn't start as Gandalf the White. He starts as Gandalf the Grey, wandering, listening, getting his cloak dirty. It's only because he walks the road, falls with the Balrog, and comes back changed that he is elevated. Engagement is what upgrades him.

Saruman, meanwhile, declares himself Saruman of Many Colours. He gives himself the promotion. And he loses everything.

That, in the end, is the choice every enterprise architect makes, not once but every quarter. You can be the architect who is technically correct and operationally invisible. Or you can be the architect who is in the room, in the field, in the work, and whose decisions shape what actually happens.

Enterprise architects play a pivotal role in guiding organisations through digital transformation and aligning IT with business strategy. Both the ivory tower and the hands-on architect bring valuable expertise. But the architect who collaborates, learns continuously, and owns the outcome is the one whose architecture survives.

Be more Gandalf, less Saruman. Get out of the tower. Walk the road. Join the Fellowship.

And what about Boldo?

Even Gandalf had a staff. We build one for enterprise architects and IT leaders, helping you understand, model, anticipate, and communicate impacts within seconds, so the time you spend in the tower shrinks and the time you spend in the field grows.

Identify, explore, and communicate impacts within seconds.

Tags: Enterprise Architecture · TOGAF · Transformational Leaders · Digital Transformation · Chief Information Officer