Four architects and why we need all of them

The quote

The architect in the quote above did not frame it in terms of any formal model. The quote was informal, uneven and exactly as it was said.

And yet, it maps onto something real.

In 1983, Robert E. Quinn and John Rohrbaugh published research examining the criteria organisations use to define effectiveness. They found that those criteria clustered around two competing dimensions: flexibility versus control and internal versus external orientation. Plotting these dimensions produces four quadrants — what we know as the Competing Values Framework (CVF).

Here, each architect archetype from the quote corresponds to a distinct CVF stance: a structural orientation toward work and decision-making, not a personality type.

The CVF was not built to describe architects. It was built to describe what organisations need to be effective. If the four archetypes map onto the CVF stances cleanly, this has a structural meaning. Three things in particular:

1. The archetypes are not personality quirks: they are structurally distinct orientations that organisations need.
2. No single stance is the right one: the CVF is explicitly about competing values, meaning each quadrant represents a legitimate way of operating.
3. The absence of any one stance is a risk: not a preference, an actual gap — even if that gap is not immediately visible.

Let's see if this hypothesis holds.

The four stances in practice

Tower

This architect thinks in systems and horizons. Their comfort with abstraction sets them apart — and that distance is precisely what makes them valuable. They are the person in the roadmap discussion who keeps pulling the conversation back to a question nobody else thought to ask.

The failure mode is familiar: the gap becomes too wide to cross and the vision too detached to guide decisions. Without this stance, however, technology decisions accumulate like debt — each one reasonable in isolation, collectively ruinous.

Fix-It

This architect shows up when something is genuinely broken. They diagnose, they solve, they have earned trust by delivering under pressure. They are the person who is already on a call before anyone has thought to ask who should lead the incident.

The failure mode is that they become indispensable in ways that are not scalable — a single point of failure disguised as a hero — or worse, a source of instability others must work around. But architects who have never felt the weight of a production incident struggle to earn the respect of those who have. Operational credibility is real.

Gatekeeper

This architect holds the line on standards, security posture, compliance obligations and architectural coherence. They are the person in the design review who asks the question that makes the room go quiet — and is usually right to ask it.

They are often cast as the villain — the reason a promising initiative stalled. They are also, sometimes, the reason the organisation did not make a catastrophic mistake.

The failure mode is not saying no. It is saying no without a path forward — or without fully understanding what is being blocked.

Bridge Builder

This architect translates fluently between the CISO, the product team and the infrastructure engineers. They are the person who has had three separate conversations before the meeting starts, which is why the meeting actually reaches a decision.

They create the conditions for alignment that would not otherwise exist.

The failure mode is that alignment becomes the destination rather than the means — progress slows while agreement improves. The capability itself is foundational: architectures that are technically correct but politically orphaned do not get built.

Plotting the stances

The Competing Values Framework plots these orientations across two dimensions: flexibility versus control and internal versus external focus. Each stance occupies a distinct quadrant — and the quadrant helps explain the behaviour.

Each archetype represents a dominant orientation, not an exclusive one — in practice, architects often operate across adjacent quadrants.

The Tower is externally oriented because the focus is on exploring systems and possibilities beyond the organisation's current state — sensing and shaping what comes next. Flexible because that thinking resists being pinned down to a single solution.

The Fix-It maps to the Rational Goal quadrant: control oriented and externally focused in the CVF sense of being driven by outcomes and results rather than internal process or relationships. The Fix-It's north star is delivery — closing the gap between the current broken state and a working one. That orientation toward concrete, measurable results is what the external axis captures, even when the work itself happens deep inside internal systems. Of the four, this is the mapping that sits closest to a quadrant boundary — the Fix-It can shade toward Internal Process when the work is primarily about restoring order rather than delivering outcomes. That ambiguity is itself revealing: the Fix-It is the most context-dependent stance. It is also, for that reason, the hardest to institutionalise. Organisations know they need one when something breaks. They are less sure what to do with one when nothing has — which is precisely when the stance is most at risk of being crowded out.

The Gatekeeper is internally oriented because the focus is on process, standards and coherence. Control oriented because holding that line requires structure and predictability.

The Bridge Builder is internally oriented because the focus is on the people and relationships within the organisation. Flexible because navigating those relationships requires adaptability over structure.

What this tells us

The mapping holds. Each of the three points in the opening hypothesis is supported by the quadrant structure.

These are not personality quirks. The CVF did not emerge from studying individual architects; it emerged from studying what makes organisations effective. That the four archetypes map so neatly onto it shows that each stance is a legitimate and necessary mode of operation. Individuals may have a default stance, but the stances themselves are structural, not optional.

No single stance is the right one. Each quadrant in the CVF carries equal weight. The framework was designed around the insight that organisations need all four orientations to operate effectively. An architecture function that has mastered one stance while neglecting the others is not strong in a single area — it is incomplete.

The absence of any one stance is a risk. Without a Tower, technology decisions accumulate without direction. Without a Fix-It, operational credibility erodes. Without a Gatekeeper, the line nobody wanted to hold gets crossed. Without a Bridge Builder, technically correct architectures fail to get implemented. The organisation suffers whenever any stance is missing, regardless of how talented individual architects may be.

The mapping also reveals something the original quote does not: that these stances are not evenly distributed in most organisations. The Tower and the Bridge Builder tend to be undervalued in environments that reward delivery and compliance — precisely the environments where architecture functions most often operate. The Gatekeeper is structurally incentivised by risk and audit culture. The Fix-It is structurally incentivised by incidents and deadlines. The result is that the two control-oriented stances tend to crowd out the two flexibility-oriented ones — not because organisations choose this, but because the reward structures quietly select for it. That is the gap worth watching.

On first reading, it is a sharp observation. On closer reading, it is a precise description of a system that organisational theory has been mapping for forty years.

Do the stances compete?

The tension is real. In high-pressure moments the stances pull in different directions. The Fix-It wants to move fast during an incident — the Gatekeeper wants to move carefully. The Tower arrives at a roadmap discussion with a vision — the Bridge Builder is managing the stakeholder reality that vision has to survive. Both sides of each conflict are right. That is precisely what makes it hard.

That tension deserves to be sat with. It does not resolve cleanly and the instinct to smooth it over too quickly is itself a failure mode — usually the Bridge Builder's.

And yet. In practice, most architects move between these stances more than they realise. The Gatekeeper who unblocks a stalled initiative by finding a path forward. The Fix-It who slows down long enough to bring the team with them. The Tower who rolls up their sleeves when something breaks. The Bridge Builder who, having built the coalition, holds the line on what the architecture actually needs. The system works because people are already doing this — intuitively, without naming it. That informal fluency is often what holds an architecture function together.

Under pressure, even experienced architects can retreat to their dominant stance. That is the natural response — and the moment when fluency matters most. The most capable architects have learned to stay curious about the other stances, even when the situation is drawing them toward just one. They hold the Gatekeeper's caution and the Tower's vision in the same conversation, knowing when to hold the line and when to move.

So the answer is not that the stances compete. It is that they are in tension — and that tension, managed well, is the point. Fluency is not about suppressing your default stance; it is about knowing when it is serving the situation and when it is not. That distinction is harder than it sounds. Under pressure, the dominant stance feels like clarity — it is only in hindsight that it becomes visible as a retreat. The architects who develop genuine fluency tend to have had the experience of watching their default stance fail: the Tower whose vision was ignored, the Fix-It who solved the wrong problem, the Gatekeeper who blocked something they later wished had been built, the Bridge Builder whose consensus collapsed the moment it met reality. Failure across stances is, paradoxically, what builds the range. The framework does not shortcut that — but it can make the learning more deliberate.

Naming the stance

These stances are predictable responses to real organisational pressures. Naming them changes how you read a room. The Gatekeeper is not being obstructive — they are operating from a different horizon. The Fix-It is not ignoring the relationship — they are managing something the Bridge Builder cannot see from where they are standing. The stance explains the behaviour. Without a name for it, that explanation is not available.

Most architectural conflict is not disagreement about solutions. It is disagreement about which stance the moment requires. The cost of not naming that is friction that looks personal but is not.

In practice, this means a few concrete things. Before a difficult conversation, it is worth asking which stance the other person is likely operating from — not to predict their argument, but to understand their horizon. A Gatekeeper raising an objection is not the same problem as a Bridge Builder raising the same objection; the response that works for one will often fail for the other. It also means being honest about your own default. Most architects know which stance they reach for under pressure. The question is whether they can recognise the moment when a different one is needed — and whether they have practised it enough to reach for it deliberately rather than accidentally.

That points to something more fundamental than self-awareness. The most effective architects are not simply aware of the stances — they have learned to move between them deliberately. Quinn, whose research underpins the CVF, called it behavioural complexity — the ability to enact multiple, even competing roles in response to what the situation requires. His research found that the most effective people are not those who have mastered one quadrant, but those who can move fluidly between all four. Gregor Hohpe, in The Software Architect Elevator, described something adjacent: the architect's job as connecting the engine room, where systems are built and maintained, to the penthouse, where business strategy is defined. The elevator moves vertically. The argument here is lateral — but the underlying capacity is the same. Knowing where you are, recognising where the situation needs you to be and being able to move.

Most experienced architects arrive at this intuitively, without a name for it. That is what this framework offers — not a new capability, but a language for what practitioners already have.

References

Quinn, R. E., & Rohrbaugh, J. (1983). A spatial model of effectiveness criteria: Towards a competing values approach to organizational analysis. Management Science, 29(3), 363–377.

Quinn, R. E. (1988). Beyond Rational Management: Mastering the Paradoxes and Competing Demands of High Performance. Jossey-Bass.

Hohpe, G. (2020). The Software Architect Elevator. O'Reilly Media.