Culture isn’t subjective.It's only been invisible.

You can’t design a culture you can’t diagnose.

Most leaders can feel culture. They know when a team is working, when something feels off, or when a new leader has somehow changed the room. They can walk into two departments inside the same company and immediately sense that the rules are different.

What’s harder is explaining exactly what they’re noticing.

So we reach for words like good, toxic, collaborative, innovative, or high-performing. Those words describe the experience of a culture, but they don’t tell us what’s producing it. And without knowing what’s underneath, changing culture becomes a lot of trial and error.

That’s why organizations so often borrow practices from companies they admire. They adopt someone else’s meeting cadence, incentive structure, leadership model, or values and expect similar results. Sometimes it works. Sometimes the exact same practice creates resistance, confusion, or behavior nobody intended.

The practice wasn’t necessarily wrong - it was just designed for a different system.

Culture is infrastructure. It determines what gets rewarded, which information gets trusted, how authority works, how conflict is managed, and what counts as a good decision when the answer isn’t obvious.

Once you can identify that structure, culture stops being something you can only feel. It’s something you can diagnose.

There is no such thing as the “best” culture.

Once you stop treating culture as a vibe, something else becomes clear: there isn’t one ideal version of it.

Different cultures are built to solve different problems. One may reward speed and individual initiative, while another prioritizes consistency and collective agreement. One may treat direct conflict as useful information; another may protect cohesion because stability is what allows the system to perform.

None of those approaches is inherently better. They’re optimized for different things. That’s why a leadership practice that transforms one organization can destabilize another. And why someone who thrives inside one company can struggle inside another despite being equally talented, experienced, and motivated.

The first question isn’t whether your culture is good or bad. It’s: what system are you actually running?

Nine recognizable decision systems.

Relationality identifies nine distinct Culture Types - nine recognizable decision systems with different assumptions about what matters, what creates value, and how people should act when priorities compete.

Think of it like an operating system. Windows and macOS are built around different assumptions about how the system should work. Neither is inherently better, but those differences shape what each system does well, what works naturally within it, and where friction is likely to emerge. Neither system is the problem. Friction appears when something designed for one is expected to work inside the other.

Culture works the same way.

You’ve been looking at the Culture Map the whole time.

The Relationality logo isn’t just a logo. It’s a map.

The three primary colors - Yellow, Blue, and Red - represent three foundational culture patterns. As those patterns combine, they create distinct Culture Types, each with its own decision logic, strengths, and predictable sources of friction.

The arrangement matters just as much as the colors. The nine types are positioned in relationship to one another, so the same map that identifies a culture also shows where compatibility is likely to come naturally - and where more translation may be required.

Compatibility isn’t another layer of the model. It’s visible in the relationship between the types.

That’s what makes the Culture Map more than a classification system. It doesn’t just name cultures. It shows how they relate.

Yellow

Yellow
Blue-Yellow
Red-Yellow
Yellow-Blue
Blue
Red-Blue
Yellow-Red
Blue-Red
Red

Blue

Yellow
Blue-Yellow
Red-Yellow
Yellow-Blue
Blue
Red-Blue
Yellow-Red
Blue-Red
Red

Red

Yellow
Blue-Yellow
Red-Yellow
Yellow-Blue
Blue
Red-Blue
Yellow-Red
Blue-Red
Red

Knowing your Culture Type is only the beginning.

Two organizations can share the same Culture Type and feel completely different to work inside.

One may be thriving. The other may be struggling with turnover, mistrust, or decisions that repeatedly stall. The underlying operating system can be the same while the way that system is functioning looks very different.

That’s why identifying the type isn’t enough.

A diagnosis has to go deeper. It has to tell us what the culture is built to optimize, where authority actually comes from, what earns influence, how information moves, which behaviors get rewarded, and what happens when the system is under pressure. Most importantly, it has to evaluate those things in the context of that specific Culture Type.

A behavior that signals dysfunction in one culture may be completely healthy in another. Direct confrontation might strengthen one system and destabilize another. Consensus might create trust in one environment and gridlock in the next.

That’s why culture health isn’t measured against one universal standard. Each of the 9 Culture Types has its own spectrum of expected behavior from high-functioning to dysfunctional - and diagnosis shows us where the organization is functioning within that range.

The question isn’t: Does this look like a good culture? Instead it’s: Is this a healthy version of the culture you’re actually running?

To diagnose culture, you need to see two things.

You need to understand what the system is built to do and how that system is actually behaving. That’s the distinction between MAP and PRISM.

MAP reveals the engine.
It identifies the underlying structure driving the culture: how it creates value, what gives people cultural permission to act, and what ultimately determines power and influence.

PRISM reveals the behavior.
It looks at the observable signals that tell us how that system is functioning in practice: what gets rewarded, how information moves, which rules actually govern behavior, what failure looks like, and what all of those patterns produce on the ground.

Together, these eight dimensions give us a standardized way to examine something that otherwise feels subjective.

MAP

structure / 03
M

Modus Operandi

The culture’s primary driver and mechanism of creating value.

A

Authority

What determines whether someone has cultural permission to act.

P

Power

What creates influence and status inside the system.

PRISM

behavior / 05
P

Performance Failure

What it looks like when a particular culture becomes dysfunctional.

R

Reward Mechanism

Behaviors the culture reinforces and elevates.

I

Information Flow

How truth, knowledge, and influence move through the organization.

S

System Rules

The formal and informal rules governing behavior.

M

Manifestation

What the culture feels like on the ground when all of the above are in motion.

Two organizations can share the same Culture Type and function completely differently.

One may be healthy and high-performing while another struggles with mistrust, friction, or behaviors that undermine the system from within.

Together, MAP and PRISM let us separate something organizations often confuse: Culture Type from culture health. Those are different diagnoses. And they require different interventions.

A healthy culture can still work against the strategy.

Culture diagnosis becomes especially useful when you put it next to what the organization is trying to accomplish.

A culture can be healthy, cohesive, and high-functioning while still reinforcing behaviors that make a particular strategy harder to execute. A culture that rewards certainty may hesitate when the strategy requires experimentation. One that prizes individual ownership may struggle when success suddenly depends on coordination across teams.

That doesn’t make the culture wrong. It tells you where execution is likely to get difficult.

Because strategy doesn’t execute itself. Eventually, every strategic priority becomes a series of decisions: what gets funded, what gets delayed, which risks are acceptable, whose input matters, what gets rewarded, and what people do when priorities compete. Those decisions happen inside the culture you already have.

That’s why diagnosis matters. MAP shows what the culture is built to optimize. PRISM shows how those underlying priorities are actually showing up across the organization. Put that beside the strategy, and you can see where the system naturally supports what you’re asking people to do - and where it may quietly pull them in another direction.

Now you can be intentional about what happens next. You can protect the parts of the culture that give the organization its strength, address what isn’t functioning well, and change the conditions that are getting in the way of execution.

Strategy sets the direction.

But whether the organization actually moves in that direction depends on thousands of decisions made when leadership isn't in the room. Culture is the invisible system shaping those decisions.

Strategy is the plan.Culture is whether it happens.

Ready to see what you’ve been missing?

Knowing you made the right executive hire. One major conflict resolved. One strategic decision made faster. For many organizations, that’s enough to pay for the investment many times over.