The Values Discovery Protocol

The Problem

You have values. They're on a slide somewhere, maybe a wall poster. Nobody can recite them, and they've never cost you a dollar. The moment a high performer violates one and nothing happens, your team learns the real culture: whatever we tolerate. You don't have a values problem. You have an enforcement problem — and it started because you never mined the values from reality in the first place.

Who This Is For

Founders or leadership teams ready to define culture by what they'll sacrifice for — not what sounds good in a pitch deck.

What You'll Need

• Time commitment: 2-4 weeks for the full Standard Track (two sessions plus a one-week stress test). The Fast Track compresses to 48 hours if you're in crisis.
• Prerequisites: At least one specific story where you lost money, fired someone, or took a painful hit to protect a principle. If you can't name one, you're not ready — you don't have values yet, just preferences.
• Tools: Recording capability for internal meetings (Track B). A third-party observer if you're running Track A. A simple document for your "Mirror Document" and Near Enemy definitions.

The Protocol

The Core Philosophy: Anti-Fragility

Resilience is "bouncing back." Anti-fragility is the ability to learn from chaos and get stronger because of it. To be anti-fragile, a team must stop making decisions from Fear & Anger (Reactive) and start making them from a place that is Centered & Aligned.

Values are not "words on a wall." They are the specific behaviors we default to when it costs us money to do so.

The Operating Standard: "The Room is for Decisions"

• The Rule: We never start from a blank page in the room.
• Pre-Work: Participants complete "shitty first drafts" (15-min limit) before the session.
• The Session: We debate and decide. We do not write.
• Post-Work: We test the output in the real world.

Phase 1: The Mining (Data Gathering)

Goal: Capture the actual culture, not the aspirational one.

Step 1: The Anchor — "The DNA Stress Test" (Founders Only)

This is the most critical step. Values are revealed by what we sacrifice.

The Prompt: Founders must identify 3 specific moments where they:

• Lost money to protect a principle.
• Fired a high-performer because of a behavioral breach.
• Took a painful short-term hit for a long-term belief.

The Insight: The themes connecting these three stories are your actual non-negotiable values.

Step 2: The Observation (Choose Your Track)

You cannot read the label from inside the bottle. You need an objective view.

Track A: The "Pro" Audit (Ideal for Scale-ups)

• Action: A third-party observer shadows the team for 1–2 weeks (Stand-ups, Whips, Slack).
• Output: A detailed "Field Report" of unwritten rules and hidden friction.

Track B: The "Light" Audit (Ideal for Startups/Budget-Conscious)

• Action: The Founder records 3 internal meetings (1 All-Hands, 1 Leadership, 1 Project Review).
• The Review: The Founder watches the recordings with the volume OFF for 5 minutes (to see body language/engagement), then with volume ON to catch interruptions and tone.
• Output: A simple 1-page "Mirror Document" listing 3 behaviors to keep and 3 to fix.

Phase 2: The Definition (The Architecture)

Goal: Turn abstract concepts into coachable actions.

The Hierarchy of Clarity:

• The Value: The headline (e.g., Ownership).
• The Principle: The rule we live by (e.g., "We don't audit the problem; we own the solution.").
• The Observable Behavior: The specific action we can see.
  • The Video Camera Test: If we filmed the office, would we see this happening?

Phase 3: The Distinctions (The Shadow Side)

Goal: Prevent the value from becoming toxic.

The "Near Enemy" Concept: Every virtue has a shadow side — a behavior that looks like the value but actually destroys the culture.

• Value: Empathy.

  • The Near Enemy: Sympathy (or Ruinous Empathy).
  • The Difference: Empathy is "I understand your pain, and I know you can fix this." Sympathy is "I understand your pain, let me lower the standard for you."

• Value: High Standards.

  • The Near Enemy: Perfectionism.
  • The Difference: Standards drive excellence. Perfectionism drives paralysis.

Phase 4: The Craft (The Timeline)

Goal: Resonance and Memorability.

Standard Track (Deep Work)

• Session A: Review raw data, debate drafts, define Near Enemies.
• Stress Test: 1 Week. Leaders must use the draft values in at least 3 decisions.
• Session B: Review the "Stress Test" data. Finalize language.

Fast Track (Crisis/High-Velocity)

• Session: One 4-Hour Intensive.
• Stress Test: 48 Hours. "Go try to break these values."
• Finalization: 30-minute sign-off call.

Phase 5: The Integration (The Enforcement Loop)

Goal: Making it Real. Values are hallucinations until they have consequences.

1. The Gatekeeper (Hiring)

We do not hire for "Culture Fit" (which usually means "people like us"). We hire for "Values Alignment."

Protocol: Every interview must include one specific question per Core Value.

• Example for "Ownership": "Tell me about a time you fixed a problem that wasn't your job."

2. The Scorecard (Quarterly Accountability)

Every employee has a scorecard.

The Growth Edge: Identify ONE specific Value/Principle the employee needs to master this quarter.

• The Coaching: "We are not criticizing your personality; we are coaching the agreement we made on this value."

3. The Exit (The Ultimate Validation)

If a high performer violates a core value and stays, the value is dead.

Protocol: We fire on values breaches faster than we fire on performance issues.

The Narrative: When someone leaves, we are explicit (without being cruel) if it was a values mismatch. This signals to the team that the values are real.

What You'll Find

Two things hit founders hardest in this protocol. First, the DNA Stress Test usually produces only one or two genuine stories — meaning most of what you thought were "values" were actually aspirations you'd never been tested on. That's the gap between your poster and your culture. Second, the Near Enemy work changes how you see your best people. The overperformer who's "just really passionate" might be running on perfectionism. The manager who's "so empathetic" might be lowering the bar for everyone. The distinction between a value and its shadow is where culture actually lives.

Adaptations

Solo founder, no team yet: Run Phases 1-3 before your first hire. You won't have the observation data (Track A or B), but the DNA Stress Test and Near Enemy definitions will give you a hiring filter that's worth more than any job description. When you write the job post, describe the Near Enemies explicitly — it repels the wrong candidates faster than listing the values themselves.

Existing team, values already defined but dead: Skip Phase 1. Go straight to Phase 3 (Near Enemies) and Phase 5 (Enforcement). Your values probably aren't wrong — they're just unenforced. The first time you fire someone for a values breach, the rest of the team will know the game has changed.

Where This Came From

This protocol was built from watching the same failure pattern across dozens of founding teams. The founders who struggled had values that were aspirational — things they wished were true. The founders who built real cultures had values that were archaeological — dug out of specific moments where they'd already paid the price. The Near Enemy concept comes from Buddhist psychology (every virtue has a "near enemy" that mimics it), adapted here because the most dangerous cultural failures aren't obvious violations. They're the shadow versions of your best intentions. The "shitty first draft" operating standard borrows from Anne Lamott's writing philosophy, repurposed for the boardroom.

Related Protocols

• The Herb Brooks Protocol — The hiring and team-building playbook that sits on top of these values. Once you've defined what you stand for, this protocol shows you how to select and onboard people who actually live it.
• The Zero-State Protocol — When values conflicts trigger reactive decision-making, this clears the emotional charge so you can enforce standards from clarity instead of anger.
• The Decision Architecture — Values tell you what matters. This protocol tells you how to make the hard call when two values collide — which they will.