⌘ The Architecture Reference

Path elevator · The Architect's Path · Beginner

The Architect's Many Roles

No single archetype defines a good architect — the master planner, gardener, guide, and glue are all partial truths, and seniority rests on three legs: skill, impact, and leadership.

Path elevator Beginner ⏱ 4 min read Complete

🎬 Analogy

Famous building architects are recognizable from afar — Meier’s white boxes, Gehry’s crooked forms, Hadid’s fabric-like shapes. Every chief IT architect likewise has a personal style. There is no single mold; “architect” (Greek architekton) means master builder — someone who builds, not merely someone who draws pictures.

Hohpe uses movie characters to argue that no single archetype defines a good architect. Most carry several personas at once, switching as the situation demands.

Four personas, four lessons

graph TD
A["The Architect"]
A --> MP["Master Planner<br/>(The Matrix)"]
A --> G["Gardener<br/>(Edward Scissorhands)"]
A --> GU["Guide<br/>(tour guide)"]
A --> GL["Superglue<br/>(catalyst / matchmaker)"]
MP -.->|"seductive but fails"| W["decides on distorted facts"]
G -.->|"prunes, balances"| ECO["living ecosystem"]
GU -.->|"leads by influence"| INF["architecture without architects"]
GL -.->|"holds it together"| HOLD["architecture + detail + business + people"]
  • The Master Planner (The Matrix). The all-knowing, all-controlling Architect — seductive but flawed. Humans decide only on the facts known to them, and the top architect’s facts are distorted as they pass up the floors. Avoid the fantasy of the supreme decider.
  • The Gardener (Edward Scissorhands). Large-scale IT is a garden that evolves on its own — and weeds grow fastest. The architect trims, prunes, and establishes balance, planting for the plants’ needs. “Top-down governance with weed killer” usually does more harm than good.
  • The Guide. A tour guide who has walked the path many times, tells a good story, steers gently toward what matters and away from risk, and rides along instead of just handing over a map. This is Erik Dörnenburg’s “architecture without architects” — leadership by influence.
  • The Superglue. Job postings ask for superheroes; what enterprises actually need is superglue — an architect who holds architecture, technical detail, business needs, and people together, like a catalyst or matchmaker who understands what each part being glued is made of.

🔑 Key insight

Most good architects combine stereotypes: “periodic gluing, gardening, guiding, impressing, and a little bit of all-knowing now and then can make for a pretty good architect.”

Standing on three legs

Seniority rests on a three-legged stool — remove any leg and it wobbles:

  • Skill — knowledge and the ability to apply it. “Knowledge is like a drawer chest full of tools. Skill is knowing when to open which drawer.” Certifications mostly test knowledge.
  • Impact — how well that skill benefits the company: added revenue, reduced cost, faster time-to-market, the ability to absorb late requirements. “Architects who don’t make an impact don’t have a place in a for-profit business.”
  • Leadership — advancing the practice: mentoring, publishing, speaking, teaching.
graph TD
SK["Skill"] --> SEN["Balanced seniority"]
IM["Impact"] --> SEN
LE["Leadership"] --> SEN
SK -.->|"without impact"| F1["Perpetual student"]
IM -.->|"without leadership"| F2["Plateaued architect"]
LE -.->|"without prior impact"| F3["Ivory tower"]

⚠️ A chair can't stand on two legs

Each missing leg has a failure mode. Skill without impact = the perpetual student. Impact without leadership = the plateaued architect who hits a glass ceiling. Leadership without prior impact = the ivory-tower resident preaching outdated methods (maximize logic in stored procedures; run nightly batch in a 24/7 world).

The virtuous cycle

The three legs feed each other in a cycle that repeats with every technology wave — relational to NoSQL, on-prem to cloud — each loop faster and deeper. First you learn how, later why. The key move is to scale horizontally: ten well-mentored juniors out-deliver one ever-smarter senior, who is otherwise just a single point of failure. Mentoring also sharpens the mentor’s own thinking and earns reverse-mentoring on new technology.

💡 Architect as destination, not stepping stone

Treat “architect” like “software engineer” — a destination role decoupled from seniority. At digital companies the engineering ladder reaches SVP level. The goal is to keep architecting, not to graduate out of it.

See also

When to use it — and when not

✅ Reach for it when

  • When defining or hiring for an architect role and tempted to write a 'superhero' job description.
  • When deciding whether to govern top-down or cultivate change by influence.
  • When assessing your own growth as an architect across skill, impact, and leadership.

⛔ Think twice when

  • When a problem genuinely needs a single decisive owner rather than a connector or gardener.
  • When 'top-down governance with weed killer' is being used to crush healthy local evolution.
  • When you would use the architect title as 'engineered deception' and forget your technical roots.
path-elevatorThe Architect Elevator

The architect's job is to ride between the penthouse (business strategy) and the engine room (where software is built), translating in both directions and keeping the floors in sync.

path-elevatorArchitecting for Change and Options

The rate of change is the real driver of architecture — architects 'live in the first derivative' and create value by selling options: deferring decisions until uncertainty resolves.

path-elevatorCommunicating with the Organization

Architects close the gap between technical knowledge and decision makers by building a ramp not a cliff, asking the right questions, and treating the organization itself as a system to be understood.

Check your understanding

Score: 0 / 4

1. Which role model does Hohpe warn is seductive but dangerous?

The master planner fails because humans decide only on facts known to them, and in a large enterprise the top architect relies on presentations distorted as they pass through the floors.

2. What are the three legs an architect's seniority stands on?

Like a three-legged stool, removing any one leaves the architect unbalanced: skill without impact is a perpetual student; impact without leadership plateaus; leadership without prior impact becomes an ivory tower.

3. What does 'architecture without architects' (the Guide role) emphasize?

The Guide is a tour guide who knows the terrain, tells a good story, gently steers away from risk, and rides along rather than just handing over a map.

4. Why does Hohpe say architects should 'scale horizontally, not vertically'?

Getting smarter alone makes you a bottleneck; multiplying capability through mentoring spreads impact and feeds the virtuous cycle of skill, impact, and leadership.

Comments

Sign in with GitHub to join the discussion.