A team surfaces its real organizational values by looking at what the business has already proven, not by writing aspirational statements on a whiteboard. Real values live in the decisions that got made under pressure, in the behaviors the organization consistently rewarded, and in the stories people tell about why they stayed. The organizational values discovery process that actually works starts with evidence, not intention. You ask the room what’s already true before you ask what you want to be true. That sequence changes everything, because the values that hold under pressure were already present in the organization before anyone wrote them down.
Why Aspirational Values Don’t Stick
Most companies go through a values exercise the same way. The leadership team gets into a room, usually off-site, usually with a facilitator who has a prepared template. Someone puts a list of words on a flip chart. Integrity. Innovation. Excellence. Teamwork. The group debates which ones feel right, which ones sound like the company, which ones they’d be comfortable printing on the wall. By Friday afternoon, they have five values and a commitment to cascade them to the team the following week.
Six months later, nobody can name them. And the reason isn’t that the leadership team was careless or that the facilitator did a poor job. The reason is that the values were invented in a room with the select few, rather than discovered by the diverse many in the organization. They described what the team hoped the culture would become, not what it had already produced. When employees encounter those values on a poster and they don’t recognize them in how decisions get made on a Tuesday afternoon, the values lose credibility immediately. Cynicism is fast. Trust is slow.
The other problem with aspirational values (that aren’t lived already), is that they’re fragile. When the business faces a hard decision, a truly hard one involving real trade-offs between money, people, and principle, aspirational values provide no guidance. Nobody knows which one wins. Real values, the ones that were already operating in the organization before anyone named them, provide actual direction because the organization has already demonstrated how it uses them.
Values From the Inside Out: What the Process Actually Looks Like
A values from inside out process works backward from evidence. Instead of asking what we want to stand for, you ask: when has this organization been at its best? What made that possible? What did the people involved do that they’d do again? What did leadership protect when it would have been easier to compromise?
Those questions surface something real. The team starts pulling stories, specific ones, with names and situations and outcomes. A time the company absorbed a financial hit rather than cut corners on a client deliverable. A manager who stayed late to help a new hire through a difficult week, not because it was in the job description, but because it’s what people do here. A decision to walk away from a contract because the client’s values didn’t align with how the team wanted to work.
Those stories aren’t illustrations of values. They are the values, made visible. The discovery process is about naming what the stories are already proving. When you read those stories back to the room and ask “what does this say about who we actually are,” the answers come quickly and with conviction, because the evidence is sitting right there. Nobody has to argue for them. Nobody has to be convinced. The organization already lived them. You’re just putting language to something that was already operating.
This is the core of Appreciative Inquiry applied to values work. You start from the positive core of the organization, the moments when it was operating at its highest, and you build from that foundation rather than from a gap analysis of what’s currently broken or missing. The result is a set of values that the whole team can see themselves in, because the whole team contributed to the evidence that produced them.
Who Needs to Be in the Room
The values discovery process breaks down when it’s limited to the leadership team. This is one of the most common mistakes companies make. They treat values as a strategic asset to be designed by senior leadership and communicated downward. But if only the top five people in the organization shaped the values, those values will reflect the experience of the top five people. That’s a narrow slice of where the real organizational culture lives.
The people closest to the work, the ones who interact with customers daily, who solve operational problems in real time, who onboard new colleagues and show them how things actually get done, carry enormous amounts of institutional knowledge about what the organization actually values in practice. When they’re excluded from the process, you lose access to that evidence. And when they’re excluded from the process, they’re also excluded from ownership of the outcome. Values that were handed to them feel like a mandate. Values they helped surface feel like a description of themselves.
A properly structured values discovery session includes voices from multiple levels of the organization. It doesn’t require consensus on every word. It requires broad participation in the evidence-gathering phase so that when the language gets finalized, it reflects something the whole organization recognizes as true. The leadership team still makes the final decisions about how the values are articulated and how they’re integrated into operating rhythms. But the raw material comes from everyone.
From Discovery to Decision Architecture
Values only function as a management tool when they’re integrated into the decisions the organization makes regularly. This is where most companies stall after a values exercise. They do the work, land on language they’re proud of, communicate it to the team, and then proceed to make decisions the same way they always did. Within a year, the values are decorative. They’re on the website. They’re not in the operating rhythm.
For values to actually work, they need to be embedded in the conversations where decisions happen. That means they show up in hiring and in how the organization decides who fits and who doesn’t. They show up in performance conversations and in how leaders give feedback. They show up in how escalations get resolved and which criteria get applied when there’s a trade-off to make. If the values don’t appear in those moments, they’re not operating values. They’re communication assets.
This is where the AiMS approach differs structurally from a traditional off-site values exercise. AiMS doesn’t treat values as a deliverable that comes out of a planning session. It treats values as an operating input that needs to be present in the rhythms, the conversations, and the decision architecture of the business. When a manager is coaching a team member, the values should be the frame for that conversation. When the leadership team is evaluating a strategic option, the values should be part of the criteria. The system holds that standard consistently, not just when someone remembers to invoke it.
What Happens to the Stories After the Session
One of the least-discussed costs of traditional values exercises is what happens to the source material. Teams spend a half-day or a full day surfacing the stories, the memories, the evidence of who the organization has been at its best. That material is rich. It represents years of accumulated institutional memory about what the culture has actually produced. And in most cases, it gets summarized into five bullet points and then disappears.
The stories that generated those values are the most compelling onboarding material a company can have. They’re the clearest explanation of culture that any new hire could receive, because they’re specific and real rather than abstract and aspirational. A new manager joining the team and reading three pages of actual stories from inside the organization will understand the culture faster and more accurately than one who reads a values poster. The culture is legible in the stories in a way it can never be in the language alone.
When AiMS runs a values discovery process, the outputs don’t stop at the values statement. The stories that surfaced the values get captured and stored in the organization’s institutional memory. They become part of the knowledge layer that supports onboarding, leadership development, and decision-making over time. The organization doesn’t just have values. It has the evidence behind the values, and that evidence compounds as more stories get added to it. The culture becomes readable and reproducible rather than dependent on whoever happens to carry it in their head this year.
The Test of Real Values
There’s a straightforward test for whether an organization’s values are real or aspirational. Look at the last three hard decisions the leadership team made, situations where there was a genuine trade-off and where doing the right thing by one value cost something by another standard. If the organization’s stated values can explain why those decisions went the way they did, the values are operational. If the decisions were made on entirely different grounds and the values were never part of the conversation, the values are decorative.
Most leadership teams, when they apply that test honestly, find that their organization has a set of operating values that are different from the stated ones. The real values are legible in the patterns of decisions, in what leadership protects when things get hard, in what behaviors actually get rewarded. The job of a genuine values discovery process is to make those operating values visible, name them clearly, and then decide consciously which ones the organization wants to keep and which ones it wants to change.
That last part matters. Discovery isn’t just affirmation. Sometimes the process surfaces values that the leadership team doesn’t like seeing. Patterns of protecting internal comfort over client outcomes. A tendency to avoid hard conversations in ways that harm accountability. A reward structure that inadvertently values individual performance over team cohesion. A good values discovery process doesn’t paper over those findings. It uses them as the starting point for a real conversation about the organization the leadership team actually wants to build.
Frequently Asked Questions
How do you surface organizational values from inside the team instead of just writing them in a leadership session?
The process starts by collecting specific stories from people across the organization, not just the leadership team, about moments when the company was operating at its best. Those stories are examined for patterns: what behaviors appeared repeatedly, what trade-offs the organization made consistently, what it protected when things got hard. The values that emerge from that evidence are the ones the organization already holds. You’re naming them, not inventing them, and because the team contributed the evidence, the result reflects something everyone can recognize as true.
Why do most company values end up feeling generic or meaningless?
Most values exercises start from the wrong question. Asking what we want to stand for produces aspirational language that sounds right in the room and means nothing in the field. The values that hold meaning are the ones extracted from evidence, from how the organization has already behaved, decided, and operated under real pressure. Generic values are usually a sign that the process was designed around language rather than around the culture that already exists.
How often should an organization revisit its values?
Values don’t need to be redesigned on a schedule, but they do need to be tested against the organization’s real decisions periodically. If the leadership team can’t point to specific decisions in the past six months where the values shaped an outcome, that’s a signal the values have drifted into decoration. A lighter review once a year, asking whether the stories that justified the values are still being replicated, is usually enough to keep them operationally current.
Can an organization change its values if the discovery process surfaces ones it doesn’t like?
Yes, but the sequence matters. First, you have to be honest about what the current operating values actually are, even the ones that are uncomfortable to name. Then you can make a deliberate choice about which ones to keep, which to challenge, and what new behaviors the organization wants to build into its culture going forward. Skipping the honest assessment and going straight to the desired values produces the same aspirational problem the organization was trying to solve in the first place.
What’s the difference between culture and values in this context?
Values are the principles the organization uses to make decisions. Culture is the pattern of behaviors that those values produce over time. Values shape culture, but they only do so if they’re embedded in the operating rhythms where decisions actually happen. You can have excellent stated values and a dysfunctional culture if the values exist only in communication materials rather than in the conversation architecture of the business.
If your leadership team is ready to stop guessing at your organizational values and start building them from what the organization has already proven, AiMS is designed to run that process and keep it alive long after the session ends. Book a demo to see how the values discovery process works inside the AiMS platform and what it looks like when the outputs are embedded in your operating rhythm rather than filed away after the off-site.