The Values Integration Protocol

The Problem

You did the work. You ran the DNA Stress Test, mined real stories, defined Observable Behaviors, mapped the Near Enemies. You have a values document that's honest — archaeologically honest, not aspirationally honest.

And nothing changed.

The same people get hired because they "felt like a good fit." The same high performer bulldozes every meeting and nobody says a word because she closed $400K last quarter. The same annual review cycle asks about KPIs, mentions "culture" in one throwaway question, and moves on.

Values are hallucinations until they have consequences. Your team doesn't read the poster. They watch who you hire, who you promote, and — most tellingly — who you fire. The enforcement loop is where values stop being philosophy and start being culture. This protocol is Phase V of the Values Discovery process: the part where it gets real or dies.

Who This Is For

Founders and leadership teams who have already defined their values (through the Values Discovery Protocol or equivalent) and are ready to wire them into the three decisions that actually shape culture: who gets in, how they're coached, and who gets shown the door.

What You'll Need

• Time commitment: 1–2 weeks to build the hiring interview guide, scorecard template, and exit criteria. Then it's ongoing — this becomes operating rhythm, not a one-off project.
• Prerequisites: A completed values architecture — Core Values with Observable Behaviors and Near Enemy definitions. If you haven't done that work, start with the Values Discovery Protocol. You can't enforce what you haven't defined.
• Tools: Your existing interview process (you'll be adding a Values Interview stage). A simple quarterly scorecard — spreadsheet, Notion, whatever your team already uses. Written exit criteria that your leadership team has agreed to before you need them.

The Protocol

The Core Philosophy: Consequences, Not Declarations

Every company has two cultures. The one on the website and the one people experience on Tuesday afternoon when the pressure is on. The gap between those two cultures is measured by a single variable: what happens when someone violates a value and nothing changes?

The moment you tolerate a breach, you've communicated the real hierarchy. Revenue over respect. Output over ownership. Sales numbers over standards. Your team decoded that message in seconds. It will take you months to undo it.

This protocol closes the gap through three levers. Each one operates at a different timescale, but they reinforce each other. Miss one and the other two weaken.

Lever 1 — The Hiring Protocol (The Gatekeeper)

Goal: Stop hiring for "Culture Fit" and start hiring for Values Alignment.

Culture Fit is a dressed-up way of saying "people we'd like to grab a beer with." It selects for similarity — same background, same communication style, same blind spots. Values Alignment is different. It selects for behavior under pressure, regardless of whether you'd enjoy the person at a barbecue.

Step 1: Separate the Values Interview from the Technical Interview.

Technical screens measure skill. Values interviews measure character. They require different questions, different interviewers, and different scoring. Combining them guarantees the technical assessment swallows the values assessment — because technical ability is easier to measure and harder to argue about.

Assign a dedicated Values Interviewer. This person's only job in the process is to assess alignment with your Core Values. They don't care about coding ability, domain expertise, or sales track record.

Step 2: Build the Behavioral Interview Guide.

You cannot ask "Are you resilient?" They will say yes. Everyone says yes. You need evidence of past behavior — not hypothetical promises.

For each Core Value, write two prompts:

The Alignment Prompt: Asks for a specific story demonstrating the Observable Behavior.

Example (for the value Ownership): "Tell me about a time you saw a problem that wasn't your job to fix, but you fixed it anyway. Walk me through what happened."

The Near Enemy Check: Asks for a specific story where the candidate encountered the shadow side of the value.

Example (for the value Speed): "Our value is Speed, but we've learned the near enemy of speed is Recklessness — moving so fast you break things that matter. Tell me about a time you moved too fast and something went wrong. What did you learn?"

The Near Enemy prompt is the sharper diagnostic. Anyone can tell a heroic story about ownership. The candidate who can articulate a time they tipped into the shadow side — and caught themselves — has a level of self-awareness you can't train.

Step 3: Score on Evidence.

Pass: A specific, verifiable story that matches your Observable Behavior definition. Named dates, named people, named outcomes. You could call the reference and confirm it.

Fail: A generic answer ("I'm just someone who cares about quality"), a hypothetical ("If that happened, I would..."), or a story that actually describes the Near Enemy while the candidate presents it as the value.

That last one — the candidate who tells a Near Enemy story believing it's a value story — is the most dangerous miss. A perfectionist who describes grinding a project to a halt will frame it as "high standards." A people-pleaser who describes avoiding conflict will frame it as "empathy." Your Near Enemy definitions are the decoder ring.

Lever 2 — The Management Protocol (The Scorecard)

Goal: Move values from the annual performance review to daily coaching.

Annual reviews are autopsies. By the time you're discussing a values issue twelve months after it started, the behavior is calcified and the resentment is mutual. The scorecard moves values assessment into the quarterly rhythm where it can actually change behavior.

Step 1: Build the Values Scorecard.

Every team member gets rated quarterly on each Core Value, separate from their KPI review. The question isn't "Did they hit their number?" It's "How did they hit their number?"

Use your Observable Behaviors as the rubric:

• Green Flag behaviors observed regularly — the value is alive in their daily work.
• Neutral — no signal either way. The value hasn't been tested or you don't have data.
• Near Enemy behaviors observed. The shadow side is showing up.

Step 2: Assign the Growth Edge.

This is the single most powerful move in the scorecard. Don't try to fix someone's entire personality. Pick ONE value where the gap between their current behavior and the Observable Behavior is biggest. That's their Growth Edge for the quarter.

The conversation sounds like this:

"Sarah, your technical output is strong. But your Growth Edge this quarter is Collaboration. In the last two sprints, you shipped features without looping in design review — and when Dev challenged your architecture choice in last week's retro, the conversation shut down fast. That's the Near Enemy: Silencing Others. This quarter, we're measuring you on one specific thing: inviting debate before decisions ship."

Notice what happened. The feedback isn't personal. It's tied to a value both parties already agreed matters. It names the Observable Behavior (inviting debate), names the Near Enemy (Silencing Others), and gives a timeframe (this quarter). There's no ambiguity about what "better" looks like.

Step 3: Normalize the Rhythm.

When values feedback happens quarterly — and only quarterly — it feels like a judgment event. When it happens weekly in standups, 1:1s, and retros, it becomes vocabulary. The goal is a team where someone can say "That felt like the Near Enemy of Speed" in a planning meeting and everyone knows what it means, nobody gets defensive, and the conversation moves forward.

The scorecard creates the structure. Repetition creates the culture.

Lever 3 — The Exit Protocol (The Ultimate Validation)

Goal: Protect culture at all costs. Specifically, at the cost of revenue.

Here is the rule: fire on values breaches faster than you fire on competence issues.

A competence gap is a skill deficit. Skills can be coached. You send someone to a course, pair them with a mentor, give them reps. A reasonable person with a competence gap and the right support will improve. That's a training problem.

A values gap is a character misalignment. The person who violates your Core Value isn't missing a skill. They disagree with the standard — or they agree with it verbally and override it under pressure. That is not a training problem. That is a fit problem. And fit problems do not resolve with more coaching.

The "Brilliant Jerk" Test.

You know who they are. Top of the leaderboard. Violates Respect in every meeting. Talks over people. Takes credit. Dismisses dissent. And you keep them because the revenue number is hard to argue with.

Here's what the team sees: the values are real for everyone except the people who make us money. That's not a culture. That's a protection racket.

The Protocol:

1. First breach — Direct feedback. Name the value, name the Observable Behavior they violated, name the Near Enemy they're operating from. Use the Effective Feedback Protocol. Be explicit that this is a values conversation, not a performance conversation.

2. Second breach — Formal warning with a deadline. "This is the second time [behavior] has shown up. Our value of [X] is non-negotiable. You have [timeframe] to demonstrate the Observable Behavior consistently. If the pattern continues, we'll part ways."

3. Third breach — Exit. No negotiation. No "but they just closed a huge deal." The deal doesn't matter. The signal to the team does.

The Narrative.

When someone exits for a values breach, be honest with the team — without being cruel. You don't need to share private details. You do need to name the category: "This was a values misalignment, not a performance issue." That single sentence tells everyone in the room that the poster on the wall has teeth.

The first time you fire a high earner to protect a core value, something shifts. People stop rolling their eyes at the values document. The skeptics — the ones who assumed it was all theatre — recalibrate. That one decision communicates more about your culture than a hundred all-hands speeches.

What You'll Find

The hiring lever produces results fastest, but not in the way you'd expect. Most teams discover they've been running interviews that select for confidence and verbal fluency — not values. The candidate who tells the best story wins, regardless of whether the story matches the Observable Behavior. Once you install the Near Enemy check, a different kind of candidate rises: the one who can describe failing, catching the shadow side, and correcting. That candidate won't wow the room. They'll build your culture.

The scorecard surfaces a harder truth. You'll find at least one person on the team — usually someone everyone likes — who is living in the Near Enemy of a core value and has been rewarded for it. The empathetic manager who lowers standards. The "high standards" lead who paralyzes the team with perfectionism. The scorecard makes that pattern visible for the first time, and the first Growth Edge conversation with that person will be uncomfortable. Do it anyway. They deserve the chance to close the gap before it becomes a fit conversation.

The exit lever is where founders stall. Knowing the rule intellectually ("fire on values faster than competence") and executing it when the person in question generates 30% of your pipeline are different experiences entirely. You'll negotiate with yourself. You'll find reasons to give a fourth chance. What breaks the cycle is remembering that every week you delay, you're teaching everyone else that the value has a price tag — and the price is whatever that person bills.

Adaptations

Pre-revenue startup, no team yet. Build Lever 1 before your first hire and skip Levers 2 and 3 for now. Write the Behavioral Interview Guide using your own DNA Stress Test stories as the baseline — the behaviors you sacrificed for are the ones you should be screening for. When you write the job post, describe the Near Enemies explicitly. "We value Speed — but not Recklessness" will repel the wrong candidates faster than any list of perks.

Remote and async teams. The scorecard matters more here, not less. Without hallway conversations and body language, values breaches go undetected longer. Build the Growth Edge check into your async 1:1 cadence (written, every two weeks). Ask the question directly in the doc: "Where did you see the Near Enemy show up in your work this sprint?" Make self-reporting part of the culture. In a remote team, the person most likely to catch a values drift is the person doing it.

Co-founder relationship. All three levers apply, but the power dynamics are different. You can't "fire" a co-founder the way you fire an employee — the legal, financial, and emotional stakes are orders of magnitude higher. The scorecard becomes your early warning system. Run it on each other, quarterly, with radical honesty. If a values gap opens between co-founders and doesn't close within two quarters, that's a conversation for the boardroom and possibly a mediator. Don't wait for a crisis to discover you've been operating from different value sets for two years.

Acquired team or post-merger integration. Don't impose your values on day one. Run Phase 1 of the Values Discovery Protocol with the acquired team first — mine their actual culture before declaring what it should be. Then overlay the three levers gradually: hiring first (you control new hires immediately), scorecard second (after the first quarter together), exit last (only after the values have been clearly communicated and the team has had time to adapt). Forcing the exit lever before the team has internalized the values is punishment without due process.

Where This Came From

This protocol synthesizes the enforcement side of three bodies of work. Patrick Lencioni's The Advantage makes the case that organizational health — not strategy, not technology — is the greatest competitive advantage, and that health starts with behavioral clarity from leadership. Jim Collins' Built to Last documents companies that preserved core ideology across decades, not by being flexible about values but by being fanatical about them — "preserve the core, stimulate progress." The behavioral interviewing methodology comes from Geoff Smart's Who, which demonstrated that structured, evidence-based interviewing dramatically outperforms gut-feel hiring. The Near Enemy integration throughout all three levers is the original contribution — the recognition that values don't just fail through violation, they fail through distortion. The team member who embodies the shadow version of your value is harder to identify and more culturally corrosive than the one who openly breaks the rule.

Related Protocols

• The Values Discovery Protocol — Phases 1 through 4, where Core Values are mined, defined, stress-tested, and crafted. This protocol (Phase 5) assumes that work is done.
• The Near Enemies — The full framework for identifying the shadow side of every value. Required reading before building the Behavioral Interview Guide or the Growth Edge scorecard.
• The A-Player Scorecard Protocol — The performance measurement system that pairs with the Values Scorecard. KPIs measure output. The Values Scorecard measures how the output was achieved. You need both.
• The Effective Feedback Protocol — The four-step script for delivering values feedback in Lever 2 (Scorecard) and Lever 3 (Exit). Use it every time — the structure prevents the conversation from sliding into personal attack.