Values are decisions: How to operationalize organizational values

Most organizations have values.

They’re on the website. They show up in recruiting materials and onboarding decks. Maybe they’re painted six feet tall on a conference room wall.

And then Monday morning happens.

A client asks for something the team doesn’t believe is right. A manager has to deal with a high performer who is making everyone around them miserable. A deadline gets tight and quality starts slipping. Revenue is down, budgets need to be cut, and suddenly all those things the organization says it cares about are competing for oxygen.

This is where values get interesting. Because agreeing with a value is easy. Most people are willing to get behind integrity, curiosity, excellence, collaboration and treating people well.

The harder question is whether any of those beliefs change what happens next.

A value that never influences a decision is mostly a sentiment. And organizations need more from their values than that.

There’s nothing inherently wrong with words like innovative, collaborative, honest or customer-focused. The problem is how often the work stops at choosing the words.

“Be collaborative” sounds good. It also leaves quite a bit open to interpretation. Does collaboration mean everyone gets a vote? Seeking input before making a decision? Sharing information freely across departments? Making it safe for a junior employee to challenge a senior leader?

And what happens when collaboration slows something down? Now we’re getting somewhere.

Once an organization identifies a value, we think the next question should be:

What does believing this require of us?

If curiosity is a value, perhaps people are expected to ask questions before defending their position. Research gets actual time in the schedule instead of becoming the first thing sacrificed when a project gets tight. Leaders have to tolerate the occasional inconvenient question instead of rewarding certainty for certainty’s sake.

If courage is a value, employees need some room to say, “I think we’re making the wrong call.” That has consequences for leadership. You can’t ask people to be courageous and then make disagreement professionally dangerous.

Now the value is doing something. A useful progression is:

Value → Belief → Behavior → Decision

The word is the starting point. The decision is where you find out whether anyone meant it.

Within our Center Platform work, we think about organizations through three connected areas: Identity, Operating Culture and Expression.

Values live in Identity because they answer a fundamental question: What do we believe strongly enough to build around?

But Identity cannot sit off by itself as a collection of noble ideas. It has to shape Operating Culture: how people work together, how authority functions, what gets rewarded, how conflict gets handled, how quality is defined, and what people are trusted to decide.

And it eventually becomes visible through Expression: what the organization says, makes, promises and puts into the world.

That connection is a big part of why we developed the Center Platform in the first place. Organizations are often trying to solve problems in one area that actually originate somewhere else.

A brand team sees inconsistent messaging and tries to fix the messaging. Leadership sees an employee engagement problem and launches a culture initiative. Customers are having inconsistent experiences, so someone starts mapping the customer journey.

Any one of those responses might help. But sometimes the inconsistency is simply traveling downstream. People are making different choices because they are working from different ideas about who the organization is, what matters most and how things are supposed to work.

A stronger Center gives them something shared to work from. Not a script. A common logic.

One of the fastest ways to find out whether a value is useful is to stop discussing it under ideal conditions.

Say an organization values both excellence and responsiveness. A major client asks for a significant change the day before a deadline.

Great. What does the organization believe now?

Does responsiveness mean the team says yes and works until 2 a.m.? Does excellence mean the deadline moves? Can the team reduce scope? Who gets to make that decision? What if the client refuses the compromise? At what point does taking care of the client become taking advantage of the team?

The tension is the useful part.

Try it elsewhere. What does the value mean when you’re choosing between two job candidates? When someone is up for promotion? When your biggest rainmaker routinely violates the values? When a lucrative potential client is a terrible fit? When honoring a commitment costs more than expected? When two people strongly disagree and both have reasonable arguments?

You don’t really learn much about an organization’s values when everyone agrees and business is good. Look at the tradeoffs.

Values become real at the point where they cost you something.

This is where values have to get into the machinery of the organization: hiring, onboarding, performance, leadership expectations, recognition, client selection, planning, policies and everyday decisions about who gets heard, who gets trusted and what gets rewarded.

The goal isn’t to stamp the values onto every process until employees start developing an allergic reaction to the word integrity. It’s to find the places where shared beliefs could improve judgment.

Hiring is an obvious one. Beyond assessing whether someone can do the job, what behaviors suggest they can succeed in this organization?

During onboarding, skip the ceremonial reading of the values page. Give people situations. Talk about the uncomfortable calls the organization has made and why.

Performance conversations are especially revealing. If someone consistently hits every number while damaging trust, burning through colleagues or treating customers poorly, what happens?

Because whatever happens next is the value.

The same goes for policies and processes. Organizations regularly ask people to behave one way while their systems quietly demand another.

“Take ownership,” followed by six layers of approval.

“Experiment,” as long as the experiment works.

“Collaborate,” but hit your individual metrics first.

“People first,” right up until the spreadsheet gets nervous.

Nobody needs a workshop to decode those contradictions. People learn very quickly what an organization actually values. They watch what gets rewarded, what gets tolerated, what gets funded and what leadership protects when pressure arrives.

That accumulation of decisions is the culture.

This is where the separation between “brand work” and “culture work” becomes especially unhelpful.

Customers experience the decisions your organization makes. Employees make many of those decisions. Those employees are operating inside systems shaped by leadership.

So when a brand promises one thing while the organization rewards something else, eventually the gap becomes visible.

A company can build a beautiful brand around extraordinary service. If frontline employees are given impossible volume targets, customers will experience the targets.

A business can position itself as innovative while employees learn that unfamiliar ideas take three times as much effort to get approved. An organization can talk about being human-centered while its best people quietly burn themselves out because overextension has become a proxy for commitment.

The external brand does not get to overrule the internal business.

Which is why we believe brand belongs closer to the center of the organization than it usually gets placed. Brand isn’t the layer you add once the business decisions are finished. It is one of the ways those decisions become visible.

Employees are very good at spotting the difference between a stated belief and an operating one. Usually because they have to live inside the difference.

If transparency matters, people pay attention to what leadership does when the news is bad. If innovation matters, they remember what happened to the last person whose thoughtful experiment failed. If people matter, they notice whether a brilliant jerk keeps getting promoted. If quality matters, they watch what happens when protecting it threatens a deadline or a margin.

These moments carry more weight than another internal campaign ever could. And they’re especially important because leadership behavior gives everyone else information about how to interpret the values.

What gets protected? What gets challenged? What are we willing to be uncomfortable about? Where will we hold the line?

Leadership answers those questions whether it intends to or not.

If your values make every decision obvious, they probably aren’t describing a real organization. Real organizations contain competing goods.

Move quickly and do excellent work. Take care of people and hold them accountable. Be courageous and be responsible. Serve the customer and protect the health of the business.

There will be situations where you cannot maximize everything at once. Pretending otherwise creates vague values because vague values never have to confront a tradeoff.

Operationalizing them means talking about the tension. Which belief takes precedence here? Why? Does the context change the answer? Who has the authority to make the call?

The goal is not perfect consistency. It’s coherence.

That distinction matters. Consistency can become rigid. Coherence gives people room to respond to the situation while still making choices that belong to the same organization.

That’s what a Center should do.

There’s another reason values need more definition than a word and a nice sentence underneath it. Most strengths become liabilities when they’re overused.

Excellence can become perfectionism. Speed can become recklessness. Collaboration can become consensus paralysis. Empathy can make accountability harder. Innovation can turn into endless reinvention. Loyalty can keep an organization attached to people, products or practices it has outgrown.

So part of operationalizing a value is defining its healthy expression.

If excellence matters, when is the work excellent enough to move? If collaboration matters, which decisions need input and which decisions simply need an owner? If empathy matters, what does compassionate accountability look like?

This level of definition can feel less inspiring than writing the original values. It is also considerably more useful.

This may be the most important reason to operationalize values at all.

In a small founder-led organization, a surprising amount of the Center can live inside one person. People know how the founder thinks. They ask questions. They watch what she approves, rejects, changes and gets excited about. Over time, they learn the unwritten rules.

Then the organization grows.

More people make more decisions. Leaders get farther from the work. New employees arrive without years of accumulated context. Teams form their own habits. What once felt obvious starts getting interpreted five different ways.

You can respond by adding more approvals, more rules, more meetings and more oversight. Or you can make more of the organization’s underlying logic visible and usable.

A strong center helps distribute good judgment.

Someone can encounter a situation the CEO never anticipated and still make a decision that feels right for the organization. A manager can explain why a choice makes sense here. Two teams can solve a problem differently without drifting into two different versions of the company.

An employee can say, “I don’t think this is how we do things here,” and have something more substantial behind that statement than personal preference.

That is what organizational values can help create when we stop treating them as language and start treating them as infrastructure for decision-making.

If you like the way we think and want to talk, please contact us.