The Architect Elevator

Ride between the penthouse and the engine room: connect business strategy with technical reality.

The architect's value is riding between strategy and technical reality, not staying on one floor.

To an executive

Strategy often fails in translation as it passes down many layers. An architect who understands both leadership and the people building things keeps decisions realistic and stops costly misunderstandings.

To an engineer

Spend regular time with leadership and explain technical constraints in their terms. Carry strategy back down as concrete consequences for your systems, rather than just relaying messages.

The idea

Gregor Hohpe describes large organisations as tall buildings. Executives in the penthouse set strategy, engineers in the engine room build systems, and many floors of management sit in between. Information gets distorted on every floor.

The architect's unique value is riding the elevator: understanding the engine room well enough to be credible, and speaking the penthouse's language well enough to influence strategy. Architects who stay on one floor lose either relevance or credibility.

Hohpe warns against the opposite failure too: an architect who rides up and down but only relays messages has become a lift attendant, not an architect.

Why it works

Strategy fails in translation. Executives decide in terms of markets, cost and risk; engineers decide in terms of services, data and deployments. Someone has to carry meaning between the two without losing it on the way.

Credibility comes from the engine room. Leaders trust technical advice from people who demonstrably know how today's systems are built and run. Regular visits keep that knowledge current.

Influence comes from the penthouse. Many technical problems are really decisions about funding, priorities or organisation. They can only be fixed by people who set those, so the architect has to be heard at the top.

Where it applies

Strategy announcements, such as cloud-first or platform programmes, where the technical consequences are not yet understood.
Large organisations with deep hierarchies, where status reports are filtered on the way up.
Investment decisions, where an engine-room fact changes the business case.
Incident and delivery problems whose root cause is an organisational choice.

How to apply

Spend deliberate time at both ends: pair with engineers, read real code and incident reports, and sit in leadership forums.
Translate, do not relay. Turn engine-room facts into business consequences, and strategy into concrete technical options.
Look for divergence between what the penthouse believes is happening and what the engine room is actually doing.
Shape the decision, not just the message: bring options and trade-offs, and recommend one.

Example scenario

Leadership announced a cloud-first strategy expecting cost savings. An architect who rode down to the engine room found teams lifting virtual machines unchanged into the cloud, which was raising costs rather than cutting them.

Riding back up, the architect reframed the goal as speed and resilience rather than savings, and showed which savings would only come with automation and managed services. Funding shifted to those, and the programme's targets were rewritten to match what it could actually deliver.

Questions to ask

When did I last spend real time in the engine room, with code, pipelines or incidents?
Does the penthouse understand the technical consequences of the strategy it just announced?
Which floor between here and the engineers is distorting this message?

When not to use it

Small organisations with few layers, where engineers and leaders already talk directly.
Purely technical decisions with no strategic consequence, which the team should own without an architect in the middle.

How it misleads you

Becoming a messenger. The elevator is for connecting and shaping decisions, not relaying status reports between floors. The opposite trap is never leaving one floor: an architect who lives in the penthouse drifts out of date, and one who lives in the engine room never changes the decisions that matter.