Company Culture & Values Documentation

Purpose

This recipe produces a complete culture documentation package — 3-7 core values with definitions, behavioral examples, anti-values, and decision-making principles — ready to embed in hiring scorecards, performance reviews, and onboarding. The output transforms implicit cultural norms into an explicit, actionable handbook that guides how the team makes decisions when founders are not in the room. [src4] Based on methodologies proven at Netflix, GitLab, Stripe, and documented by Horowitz, this approach treats culture as observable behavior rather than aspirational slogans.

Prerequisites

• Founding team commitment — 2-3 hours of focused workshop time from all co-founders or leadership team
• Mission/vision statement — even a rough draft provides the foundation values must align with
• Team behavioral observations — notes on how decisions are actually made today (Slack history, meeting recordings, decision logs)
• Collaborative document platform — Notion, Google Docs, Confluence, or Git-based wiki
• Minimum 4 weeks of operating history — cannot document culture that does not yet exist

Constraints

• Values must describe actual behavior, not aspirations — Horowitz defines culture as "how your company makes decisions when you're not there" [src4]
• Limit to 3-7 core values — recall drops sharply beyond 7; GitLab uses 6 (CREDIT) [src2]
• Every value must include an anti-value to prevent weaponization [src1]
• Decision-making principles must specify WHO decides, not just HOW [src6]
• Values must be embedded in at least one operational system within 30 days [src5]

Tool Selection Decision

Which path?
├── Company stage = pre-launch (founders only)
│   └── PATH A: Founder Workshop — lightweight, 1-page output
├── Company stage = early-stage (2-15) AND no existing docs
│   └── PATH B: Full Build — workshop + team input + handbook
├── Company stage = early-stage/growth AND has informal norms
│   └── PATH C: Codify Existing — extract patterns + formalize
└── Company stage = growth/scaling AND needs refresh
    └── PATH D: Refresh & Extend — survey + workshop + update

Execution Flow

Step 1: Gather Founder Input

Duration: 2-3 hours · Tool: Whiteboard or shared document

Each founder independently answers five questions before the group session: describe 3 moments when the team was at its best, 2 moments of cultural friction, what behavior would cause a firing (Horowitz test), a company whose culture they admire and why, and what this company should never become. Then discuss as a group. Look for convergence — themes mentioned by multiple founders are likely real values.

Verify: 4-6 behavioral themes identified with founder agreement · If failed: If founders disagree fundamentally, resolve co-founder alignment first.

Step 2: Identify Existing Behavioral Patterns

Duration: 3-5 hours async · Tool: Slack/email search, decision logs

Mine existing behavior: review the last 20 significant decisions, search for praise and conflict patterns, review hiring decisions for values fit/misfit. For teams of 5+, survey each person on "how things really work here." Map findings to founder themes. Real values show alignment between intent and behavior. [src2]

Verify: Each theme has 2+ behavioral examples from actual history · If failed: Flag themes without evidence as aspirational.

Step 3: Draft Values with Anti-Values

Duration: 2-3 hours · Tool: Collaborative document

For each value (3-7 total), create: a memorable name, 1-2 sentence definition, 3+ observable behaviors ("what this looks like"), 2+ anti-values ("what this does NOT mean"), and a decision test ("when faced with X, we choose Y over Z"). Anti-values are critical — without them, values get weaponized. [src4]

Verify: Non-founders can correctly identify which scenarios align with each value · If failed: Value is too abstract; rewrite as a behavior.

Step 4: Create Decision-Making Principles

Duration: 1-2 hours · Tool: Same document

Document: decision authority framework (who decides what), values hierarchy for conflicts (which value wins when two collide), and communication defaults (public vs. private, written vs. verbal, disagreement protocol). Stripe’s "Users first" outranks "Move with urgency" — never ship something harmful to hit a deadline. [src3]

Verify: A new hire could correctly resolve 3/4 decision scenarios · If failed: Add specific scenario examples.

Step 5: Build Behavioral Norms

Duration: 1-2 hours · Tool: Same document

Translate values into daily defaults: meeting norms, communication norms, feedback norms (Netflix 4A model: Aim to Assist, Actionable, Appreciate, Accept or Discard), conflict norms, work-life norms, and quality norms. Keep each to 1-2 sentences. [src1]

Verify: Every norm maps to at least one value · If failed: Norms contradicting values indicate aspirational values; update values to match reality.

Step 6: Publish and Embed in Operational Systems

Duration: 1-2 weeks · Tool: HR/people platform, ATS, review tool

Publishing is 10% of the work; embedding is 90%. Embed in: hiring (values-based interview questions), onboarding (first-week culture session + 30-day check-in), performance reviews (values as evaluation dimensions), and recognition (channel for calling out values-aligned behavior). Schedule quarterly review for the first year. [src5]

Verify: Hiring rubric updated within first week · If failed: If embedding delayed beyond 30 days, values will not take hold.

Output Schema

{
  "output_type": "culture_documentation_package",
  "format": "Markdown documents",
  "documents": [
    {"name": "culture-values-handbook", "type": "primary", "required": true},
    {"name": "hiring-rubric-values", "type": "integration", "required": true},
    {"name": "performance-review-template", "type": "integration", "required": false},
    {"name": "onboarding-culture-session", "type": "integration", "required": false}
  ],
  "primary_document_structure": {
    "values_per_document": "3-7",
    "anti_values_per_value": "2-3",
    "behavioral_examples_per_value": "3-5"
  }
}

Quality Benchmarks

If below minimum: Re-run Step 1 with broader founder input. If values lack behavioral examples, the company may need more operating history first.

Error Handling

Cost Breakdown

Anti-Patterns

Wrong: Copying another company's values wholesale

Adopting Netflix's values verbatim for a 5-person seed-stage startup. Their culture of high performance with significant HR infrastructure does not translate without that context. [src1]

Correct: Study frameworks, then discover your own

Use Netflix, GitLab, and Stripe as structural inspiration but derive actual values from your team's behavioral patterns in Step 2.

Wrong: Publishing values without anti-values

Writing "We value transparency" without boundaries leads to sharing confidential data, delivering harsh criticism, or bypassing managers publicly. [src4]

Correct: Every value gets a "what this does NOT mean" section

Pair each value with explicit anti-values that prevent misinterpretation and weaponization.

Wrong: Treating culture documentation as a one-time project

Publishing values during an offsite and never revisiting. GitLab updates their values page continuously as a living document. [src2]

Correct: Schedule quarterly reviews and track behavioral drift

Review values quarterly. Track whether hiring, promotions, and terminations are consistent with documented values.

When This Matters

Use when founders or leadership need to move culture from implicit understanding to explicit documentation. Most critical at 5-15 employees (before founders can no longer onboard everyone personally) and again at 40-60 employees (before sub-cultures form). McKinsey research shows cultural friction causes up to 26% of startup failures. [src6]