Pull the values page off ten Fortune 500 websites and you’ll find the same five or six words to a varying degree: integrity, respect, innovation, excellence, teamwork, accountability. Researchers who’ve studied this at scale find the overlap isn’t a coincidence, it’s closer to a template. Values statements across large companies converge on a narrow set of safe, broadly worded terms, which means the words themselves stopped differentiating anything years ago.

That wouldn’t matter if the words still did their job inside the friendly confines of the building. Mostly, they don’t. A company can post “integrity” on every wall and still have two VPs who define it completely differently when they are called to act on it. One reads integrity as never overpromising to a client. The other reads it as always backing your team publicly, even when they’re wrong. Both are defensible. Neither was ever tested against the other, because nobody had openly questioned the working definition.

There’s a term from rhetorical theory for exactly this problem: the ideograph. Rhetorician Michael Calvin McGee described ideographs as culturally loaded words — liberty, equality, ownership — that a group treats as settled and shared even though nobody agreed on what they meant. Presidential rhetoric scholar Vanessa Beasley uses “liberty” as her example: two people can swear allegiance to the word and hold incompatible definitions of it, and neither one notices until the definitions collide. Swap “liberty” for “excellence” and you have the exact mechanism behind a stalled values initiative at a Fortune 500 company. The word feels shared but was never tested.

Why Values Statements Alone Don’t Change Performance

The research on whether espoused values predict organizational performance is more sobering than most leadership books let on. Multiple studies looking at the relationship between stated corporate values and financial outcomes find a weak or inconsistent link — companies with beautifully written values statements perform no better, on average, than companies without them. What separates high performers isn’t the presence of a values page. It’s whether those values show up consistently in how decisions get made, especially the hard ones where a value and a shortcut point in different directions.

That distinction means wordsmithing a values statement is a start, and the true work is in building a structure that forces a leadership team to define what a value means in a specific decision, before the decision gets made, not after someone gets asked to explain it in a postmortem.

Where The Definition Gets Built

This is the exact gap DLP’s MEET framework is built to close. MEET — Map, Evaluate, Experiment, Turn into action — is a facilitation structure for the meetings where vague language usually gets nodded through uncontested. The Map phase is where an ideograph gets tested: every person writes their view in silence before anyone talks, which means “we value ownership” gets replaced on the wall with what each individual thinks “ownership” requires in this specific decision. Silent, individual contribution exists precisely to prevent the loudest voice, or the most senior title, from becoming the default definition everyone else defers to.

The Evaluate phase does the second half of the work. Once the room’s real definitions are visible, dot voting against a specific criterion — not a debate about whose definition is right — surfaces which interpretation the group wants to act on. That’s a materially different outcome than a values workshop that ends in applause and no shared definition. One produces a decision. The other produces a slide that gets referenced for a year and never once changes a call anyone makes under pressure.

What This Looks Like In Practice

A leadership team is deciding whether to walk away from a client who’s profitable but exhausting to work with. Someone says, “this isn’t who we are — it violates our values.” Which value, specifically, does keeping this client violate? Does it violate “excellence,” because the account consumes disproportionate resources for the return? Does it violate “respect,” because the client treats the team poorly? Those are two different decisions with two different owners and two different next steps — and a team that stops at “our values” instead of naming which value, and what it requires here, will make the call based on whoever argued loudest in the room.

Run that same decision through five minutes of silent writing and a Map phase, and the ambiguity surfaces before the decision does, not after it’s already been made and someone must defend it.

Picture it on the wall. Six people write their own definition of “integrity” on sticky notes, in silence, before anyone talks. One writes “never overpromise to a client.” Another writes “always disclose bad news early, even when it costs us the deal.” A third writes something closer to loyalty — “back your team publicly, even when they’re wrong in the room.” None of those are incompatible in the abstract. They become incompatible fast the moment a real decision requires picking one over another, which is exactly why the wall matters more than the word. A team that sees all six notes clustered together, in view, at the same time, can have the actual conversation — which version of integrity governs this specific call — instead of discovering the gap three weeks later when two people acted on two different definitions and neither one was wrong according to their own sticky note.

That’s the difference between a values statement and a mapped value. The statement lives on a wall as decoration. The map lives on a wall as evidence, and evidence is what a leadership team can argue with.

The words on the values page were never the problem. The problem is that most organizations spend their energy writing the words and almost none of it building the structure that forces a shared definition when the words get tested.