How Core Values Actually Work in a Company
Most companies write core values like they're decorating an office lobby. They pick words that sound good and hang them on the wall. The ones that actually stick are different. They become useful when someone has to make an uncomfortable decision and the values are the thing they reach for. I worked with a mid-size SaaS company last year trying to build their value system from scratch. We went through three rounds of workshops before anything looked real. The breakthrough came when we stopped asking what values they admired and started asking what they'd actually sacrifice money to protect. That shift changed everything about the output.
Defining What Core Values Actually Are
Core values are the non-negotiable principles that guide decision-making across an organization. They're not goals. They're not missions. They're the things the company will not compromise on, even when it costs revenue or slows down delivery. If a value can be safely ignored during a tight deadline without anyone noticing, it's not a core value. It's a nice sentiment. The standard mistake is writing values that are too vague to be useful. "Integrity" means nothing on its own. "We disclose cost overruns to clients within 24 hours, even when it hurts our margins" means something specific. The second version is a behavior you can observe and enforce. The first version is wallpaper. Another mistake is having too many. Anything over eight values starts to lose its edge. People can't remember eight abstract principles under pressure. They remember three or four, and those four should be the ones that actually matter most.
How to Build Values That Survive Contact With Reality
Start by collecting stories. Ask employees at every level to describe a moment where they had to choose between something valuable and something profitable. Not a hypothetical. A real moment. I collected forty-seven of these from a company with roughly two hundred people across four offices, and after the third round, the patterns were obvious. Five themes kept showing up regardless of department or seniority. Those five became the foundation. Next, convert each theme into a behavioral statement. This is where most people stall because they don't know how to be specific without being narrow. The trick is to describe the action, not the intention. Instead of "we treat customers fairly," write "we respond to support tickets within four business hours, and if a resolution requires more than twenty-four hours, we send a progress update before the customer has to ask." I learned this distinction the hard way. Early in my career, I wrote a values document for a logistics company that read like a mission statement collection. The CEO looked at it and said nobody would ever reference it during an actual crisis. Fair point. We rewrote it three weeks later with concrete behavioral anchors, and six months after that, two managers referenced those anchors during a dispute over whether to honor a shipping commitment that would have cut into profit by twelve percent. They honored the commitment. The values document was the thing they cited.
Get the Full Details
Practical Examples Of Core Values In Action
Here are some real examples from companies I've seen work with, written in the behavioral format rather than the poster format: Transparency: All pricing is published on the website before a customer speaks to anyone. No custom quotes for standard products. If a feature isn't listed, it doesn't exist yet, and the sales team says that out loud. Ownership: When something breaks, the person who discovers it owns the fix until it's resolved, regardless of which team the issue falls under. Handoffs are documented in a public tracker, not handled through private messages.
Craft: Code reviews require at least one reviewer from outside the immediate team. Shipping work that your reviewer wouldn't be proud of in their own portfolio is treated as a performance issue, not a speed issue. Respect: Meeting invites include an agenda and expected outcome. Meetings without agendas can be declined without explanation. Late arrivals to scheduled calls are noted and addressed in the next team retro, not in the moment. Growth: Every employee receives a quarterly learning budget of at least two hundred dollars and two days of paid time off for professional development. Managers track completion, not just allocation.
Notice the pattern. Each one describes observable behavior. You can see whether someone followed it or didn't. That's the difference between a value and a slogan.
The Hard Part: When Values Conflict
This is where most frameworks break down. Two values will contradict each other under real conditions. Transparency might demand you share bad news early. Respect might suggest giving your team space to fix things before escalating. Ownership might mean you soldier through a problem alone. Craft might mean you admit you can't solve it properly and bring someone else in. Without explicit guidance on which value wins in which situation, you get inconsistency. Different managers make different calls. Employees get confused about what's actually expected. The values document becomes irrelevant because it never helped with the hard decisions. The workaround I use is what I call conflict mapping. After drafting the initial values, take the top five and run through every possible pairwise combination. Ask: if Value A and Value B collide, which one takes priority? Write the answer down. This produces a decision hierarchy that people can actually use.
For example, one client had a conflict between Growth and Craft. Their growth value encouraged rapid experimentation. Their craft value demanded thorough testing. The conflict mapping exercise revealed that in customer-facing product changes, Craft always wins. In internal tooling and experimental features, Growth takes priority. This wasn't intuitive at first. It took two hours of debate in a room full of people who actually worked on the product to land there. But once documented, it eliminated dozens of smaller debates that would have happened anyway.
A Downside Most People Don't Talk About
Core values documents age poorly. The ones written in a retreat and locked away get stale within eighteen months. The organizational context shifts, new hires bring different assumptions, and the original wording starts to feel disconnected from how work actually gets done. I've seen this happen repeatedly. The fix is a quarterly review cycle. Thirty minutes per quarter. Look at the behavioral statements and ask: are we still following these? Which ones feel irrelevant? Which new situations have emerged that aren't covered? Update the document. This keeps it alive. A values document that gets revised annually is still more useful than one that was perfect five years ago and hasn't been touched since. There's also a limitation worth acknowledging. Core values don't fix leadership behavior. If the people running the company regularly violate the stated values, the document becomes cynical decoration. Employees notice immediately. They notice more than they let on. One company I consulted for had a value called "Collaboration" but their promotion process rewarded individual contributors exclusively. Nobody was fooled. The values were technically well-written. They were also completely decoupled from reality.
If you're building a values system and your compensation structure, promotion criteria, and hiring practices don't align with what you've written down, either fix the alignment or skip the exercise. A half-hearted values document is worse than no values document at all, because it signals that leadership doesn't mean what it says. The best values systems I've encountered share one trait: they're referenced in actual meetings. Not in onboarding presentations. In real decisions. When a project gets scoped, someone asks which values apply. When a hire is evaluated, the values are the rubric. That's the bar. Everything else is just formatting.
