Image without description
  • Jacco Meijer
  • |
  • Jan 5, 2026

Four architects and why we need all of them

What sounds like a casual observation is actually a structural truth: architecture isn’t about personalities, but about competing stances your organisation cannot afford to miss.

— Senior enterprise architect

"I see four kinds of architects. The one in the tower, the one fixing everything, the one guarding the gate and the one building bridges."

The quote

The quoted architect did not reference any formal model. The quote was informal and exactly as spoken.

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 and this is what we know as the Competing Values Framework (CVF).

Each architect archetype from the quote aligns with a distinct CVF stance: a structural orientation toward work and decision-making rather than 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 stand out:

  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: an actual gap, not a preference, 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 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. They can become a single point of failure disguised as a hero or 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 and 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 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 when alignment becomes the destination instead of 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 which helps explain the behaviour.

CVF QuadrantOrientationArchetype
Open SystemsFlexibility + ExternalTower
Rational GoalControl + ExternalFix-It
Internal ProcessControl + InternalGatekeeper
Human RelationsFlexibility + InternalBridge Builder

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 revealing. The Fix-It is the most context-dependent stance and the hardest to institutionalise. Organisations know they need one when something breaks but are less sure what to do with one when nothing breaks. 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 masters one stance while neglecting others is not strong in any area and therefore 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 no one 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 shows something the quote does not: 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 and it is most visible in the moments when the stances pull against each other.

The tension in practice

The tension is real. 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 and the Bridge Builder is managing the stakeholder reality that vision has to survive. Both sides of each conflict are valid, which makes it difficult.

What the CVF makes visible is that most experienced architects are already navigating this intuitively without naming it. 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. That informal fluency often holds an architecture function together and develops the hard way. The architects who build genuine range across stances have usually watched 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.

Quinn called this 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. The framework does not shortcut that development. But it can make the learning more deliberate.

From intuitive to deliberate

The senior architect who offered the original quote almost certainly knew exactly what the quote was mapping. The CVF was not absent from that conversation, it was just not named. Four clean observations, no jargon, no framework in sight. The theory was silent, the insight was clear. That is the Bridge Builder's move but it is also the mark of someone who has genuinely internalised all four stances.

That internalisation changes two things. It 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.

And it changes how you read yourself. Most architects know which stance they reach for under pressure. The question is whether they can recognise the moment a different one is needed.

You only leave the framework out when you no longer need to show it.

Image without description
  • Jacco Meijer
  • |
  • Feb 2, 2026

Four architects and the limits of personality

Why legal, empirical and behavioural limits keep personality tools and role frameworks apart


References

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

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

Links verified at time of publication. Some sources require registration or institutional access.


Other posts

Image without description
  • Jacco Meijer
  • |
  • Mar 23, 2026

  1. What we do is not the same as how we do it

Six failure modes that follow when that distinction collapses. A diagnostic instrument for architects who need to know not just what went wrong but which mismatch drove it.

Image without description
  • Jacco Meijer
  • |
  • Mar 16, 2026

  1. Having a capability and being able to exercise it are not the same thing

Formal capability is not real capability. A conditions layer for testing whether a capability holds in the environment it must actually operate in.

Image without description
  • Jacco Meijer
  • |
  • Mar 9, 2026

  1. Capability is not confused. It is occupied

Most capability work fails before it starts because it does not ask which type of claim it is making. A diagnostic language for enterprise and security architects.

Image without description
  • Jacco Meijer
  • |
  • Feb 2, 2026

Four architects and the limits of personality

Why legal, empirical and behavioural limits keep personality tools and role frameworks apart

Image without description
  • Jacco Meijer
  • |
  • Oct 22, 2025

What cyber security mistakes do organizations still make?

A brief check on how the AI response for this question compares to real life experience.

Image without description
  • Jacco Meijer
  • |
  • Oct 19, 2025

Risk analysis for software development

By systematically identifying and assessing potential risks, teams can reduce uncertainty and prevent costly issues.

Image without description
  • Jacco Meijer
  • |
  • Oct 18, 2025

Security controls for software development

Exploring how security controls protect and improve every stage of the DevSecOps workflow.

Image without description
  • Jacco Meijer
  • |
  • Oct 17, 2025

Software development security

On risk assessments, security controls and the complexity of securing the Software Development Lifecycle (SDLC)

Image without description
  • Jacco Meijer
  • |
  • Oct 14, 2025

Canonical controls with Enterprise Risk and Security Management

How to use the SCF canonical control objectives with ERSM in Archimate

Image without description
  • Jacco Meijer
  • |
  • Oct 7, 2025

ISO 27000, ISA 62443, NIS2, BIO, NIST CSF and NIST SP 800-53

How to align the steadily increasing number of cyber security frameworks, standards and regulations?

Image without description
  • Jacco Meijer
  • |
  • Aug 15, 2025

Asset security

Information asset identification and classification from a security perspective

Image without description
  • Jacco Meijer
  • |
  • Aug 8, 2025

Data security

Data identification, data roles and data classification from a security perspective

Image without description
  • Jacco Meijer
  • |
  • Jul 25, 2025

Threat modeling, security frameworks and Enterprise Architecture

Combining ISO 27001, NIST CSF and threat modeling with Enterprise Architecture strengthens all elements

Image without description
  • Jacco Meijer
  • |
  • Jul 18, 2025

Threat modeling as part of a risk framework

Threat modeling in the context of ISO 27001 and NIST CSF

Image without description
  • Jacco Meijer
  • |
  • Jul 11, 2025

Cyber security risk frameworks

Managing cyber security risk with ISO 27001 and NIST CSF

Image without description
  • Jacco Meijer
  • |
  • Jun 27, 2025

NIST CSF Tiers for cyber security risk governance and management

NIST CSF 2.0 contains useful tiers for Capability Maturity Modeling in Enterprise Architecture

Image without description
  • Jacco Meijer
  • |
  • Jun 20, 2025

Archimate risk assessment elements

A few simple specializations for working with risk assessments in Archimate

Image without description
  • Jacco Meijer
  • |
  • Jun 13, 2025

Security principles in Enterprise Architecture

Adding security principles to Enterprise Architecture for NIST CSF and ISO 27001

Image without description
  • Jacco Meijer
  • |
  • Jun 6, 2025

Combining ISO 27001 and NIST CSF

How to use ISO 27001 and NIST Cyber Security Framework together

Image without description
  • Jacco Meijer
  • |
  • May 1, 2025

CISSP certification and Enterprise Architecture

How do the CISSP certification domains relate to Enterprise Architecture and the ArchiMate layers?

Image without description
  • Jacco Meijer
  • |
  • Apr 23, 2025

Architect roles in the ArchiMate context

An ArchiMate model that maps architect roles to the ArchiMate framework layers.

Image without description
  • Jacco Meijer
  • |
  • Mar 18, 2025

Visualizing IT Architecture in three languages, UML, C4 and ArchiMate

What are the differences and what are these languages most used for?

Image without description
  • Jacco Meijer
  • |
  • Feb 18, 2025

OAuth 2.0 and OpenID Connect Sequence Diagrams

Technical specs can be hard to read. While still highly technical, the UML Sequence Diagrams provided in this blog are a lot easier to understand.

Image without description
  • Jacco Meijer
  • |
  • Jan 9, 2025

OWASP and CISSP

OWASP recommendations from the independent information security certification CISSP.

Image without description
  • Jacco Meijer
  • |
  • Mar 21, 2024

UI Library with MDX documentation

Using the simple Render JSX plugin for Esbuild this post shows how to setup a simple UI library.

Image without description
  • Jacco Meijer
  • |
  • Mar 20, 2024

Render JSX plugin for Esbuild

Transform Esbuild generated JSX bundles to HTML pages.

Image without description
  • Jacco Meijer
  • |
  • Mar 19, 2024

Esbuild as a static site generator for MDX

Static site generators gain popularity. This blog is about using Esbuild as a static site generator for MDX.

Image without description
  • Jacco Meijer
  • |
  • Mar 18, 2024

11ty and Github pages

Simplifying the Contentful-Gatsby-Netlfy trio.

Image without description
  • Jacco Meijer
  • |
  • Jun 30, 2022

NPM7 and @npmcli/arborist

@npmcli/arborist is a powerful library that handles the new NPM 7 workspaces. This blog is about a simple make tool that uses the library.

Image without description
  • Jacco Meijer
  • |
  • May 12, 2022

Comparing React app, Nextjs and Gatsby

A new React project starts with a React toolchain. Main tools in the chains are SSR, React server components and GraphQL.

Image without description
  • Jacco Meijer
  • |
  • May 10, 2022

Versioning strategy for NPM modules

It is important to be able to bump the version of a NPM package without side effects.

Image without description
  • Jacco Meijer
  • |
  • Apr 12, 2022

React component themes and CSS variables

Creating React components with flexible themes by using CSS variables.

Image without description
  • Jacco Meijer
  • |
  • Mar 21, 2022

Content modeling with variants

The efficiency of a variant field in a content model.

Image without description
  • Jacco Meijer
  • |
  • Mar 12, 2022

Documentation

Documenting a software project is challenging. Here's a few simple guidelines that help a team writing clear documentation.

Image without description
  • Jacco Meijer
  • |
  • Mar 11, 2022

Javascript history

In 1986 David Ungar and Randall B. Smith developed Self at Xerox PARC. Inspired by Java, Scheme and Self Brendan Eich created Javascript in 1995.

Image without description
  • Jacco Meijer
  • |
  • Mar 10, 2022

On Javascript transpilers, bundlers and modules

There's Javascript transpilers, modules, bundles and bundlers. This is a brief overview of all of these.

Image without description
  • Jacco Meijer
  • |
  • Feb 11, 2022

Agile Scrum

The Agile Scrum framework is flexible enough to be used in many different ways. Here's one way of working.

Image without description
  • Jacco Meijer
  • |
  • Jan 20, 2022

What happened to Wheelroom?

Founded in 2018. Started to fly in 2020 and abandoned in 2021. What happened?

Image without description
  • Jacco Meijer
  • |
  • Jan 19, 2022

Contentful, Netlify and Gatsby four years later

What did we learn from using Contentful for four years?

Image without description
  • Jacco Meijer
  • |
  • Jan 18, 2022

Typescript interface for React UI components

How to define an interface for React UI components that prevents breaking changes.

Image without description
  • Jacco Meijer
  • |
  • Jan 17, 2022

Naming React components

What's in a name? A clear naming strategy helps developers communicate. Most devs rather spend time writing component code than wasting time on a good component name.