--- # === IDENTITY === id: business/startup-operations/company-culture-values-documentation/2026 canonical_question: "How do I articulate company culture — methodology for values, behavioral norms, decision-making principles?" aliases: - "Company culture documentation methodology 2026" - "Startup values and behavioral norms guide" - "Decision-making principles framework for startups" entity_type: execution_recipe domain: business > startup-operations > company-culture-values-documentation region: global jurisdiction: global temporal_scope: 2025-2026 # === VERIFICATION === last_verified: 2026-03-12 confidence: 0.87 version: 1.0 first_published: 2026-03-12 # === TEMPORAL VALIDITY === temporal_validity: status: evolving last_breaking_change: "GitLab updated CREDIT values framework and handbook structure in 2025; Netflix revised culture memo with inclusion emphasis" next_review: 2026-09-08 change_sensitivity: high # === CONSTRAINTS === constraints: - "Values must reflect actual behavior, not aspirational wishes — document what is, then adjust toward what should be" - "Limit to 3-7 core values — more dilutes meaning and recall" - "Every value must include an anti-value (what it does NOT mean) to prevent misinterpretation" - "Founding team must participate directly — culture cannot be delegated to HR at early stage" - "Values must be embedded in hiring rubrics and performance reviews within 30 days of publication or they decay into wall art" # === SKIP CONDITIONS === skip_this_unit_if: - condition: "Company has 200+ employees and needs a culture transformation program" use_instead: "business/transformation/culture-transformation/2026" - condition: "User only needs a mission/vision statement, not full culture documentation" use_instead: "business/brand-strategy/brand-strategy-development-playbook/2026" - condition: "User needs employer branding content, not internal culture documentation" use_instead: "Search knowledgelib.io for employer branding content — no dedicated unit yet" # === AGENT HINTS === inputs_needed: - key: company_stage question: "What is the company's current stage?" type: choice options: ["pre-launch (founders only)", "early-stage (2-15 people)", "growth (15-50 people)", "scaling (50-200 people)"] - key: existing_documentation question: "Does the company have any existing values or culture documentation?" type: choice options: ["none — starting from scratch", "informal/unwritten norms exist", "have values but need refresh", "have full documentation that needs updating"] - key: documentation_format question: "What format should the culture documentation take?" type: choice options: ["internal handbook (Notion/Confluence)", "public handbook (GitLab-style)", "culture deck (Netflix-style)", "lightweight one-pager"] - key: budget_for_tools question: "What's the tool/platform budget?" type: choice options: ["free tier only", "up to $50/month", "up to $200/month", "no limit"] # === EXECUTION METADATA === execution: required_inputs: - name: "Founder/leadership team availability" source: "internal — founding team" format: "2-3 hours of focused workshop time" - name: "Employee behavioral observations" source: "internal — existing team interactions, Slack messages, decision logs" format: "notes and anecdotes" outputs: - name: "Culture values document" format: "document (Notion page, Google Doc, or Markdown handbook)" description: "3-7 core values with definitions, behavioral examples, anti-values, and decision-making principles" - name: "Hiring rubric integration" format: "scorecard template" description: "Interview evaluation criteria mapped to each value with behavioral indicators" - name: "Performance review framework" format: "review template" description: "Values-aligned evaluation criteria for quarterly or semi-annual reviews" tools_required: - name: "Collaborative document platform" purpose: "Drafting, editing, and publishing the culture document" tier: "free" cost: "$0" alternatives: ["Notion", "Google Docs", "Confluence", "GitHub/GitLab wiki"] - name: "Survey tool (optional)" purpose: "Gathering behavioral pattern input from team members" tier: "free" cost: "$0" alternatives: ["Google Forms", "Typeform free tier", "Notion form"] credentials_needed: - service: "Collaborative document platform" type: "account access" where_to_get: "https://notion.so or https://docs.google.com" free_tier_limits: "Unlimited for this use case" estimated_duration: "2-4 weeks from kickoff to published document; 6-8 hours of active work" estimated_cost: "$0 (free tools) to $500 (if using external facilitator or Culture Amp survey)" # === DISTRIBUTION === canonical_source: "https://knowledgelib.io/business/startup-operations/company-culture-values-documentation/2026" suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-12)" # === RELATED UNITS === related_kos: depends_on: - id: "business/brand-strategy/brand-strategy-development-playbook/2026" label: "Brand strategy playbook whose Step 2 defines mission, vision and core values with statement templates and quality bars" related_to: - id: "business/startup-hiring/remote-team-setup-guide/2026" label: "Remote team culture and setup — async-first norms, virtual culture rituals, time zone overlap, tooling for distributed teams" alternative_to: - id: "business/transformation/culture-transformation/2026" label: "Culture transformation program — diagnostics, phased interventions and measurement over 18-36 months" # === SOURCES === sources: - id: src1 title: "Netflix Culture — Jobs" author: Netflix url: https://jobs.netflix.com/culture type: company_handbook published: 2024-06-01 reliability: authoritative - id: src2 title: "GitLab Values" author: GitLab url: https://handbook.gitlab.com/handbook/values/ type: company_handbook published: 2025-01-15 reliability: authoritative - id: src3 title: "Stripe's Operating Principles" author: Stripe url: https://stripe.com/jobs/culture type: company_handbook published: 2025-01-01 reliability: authoritative - id: src4 title: "What You Do Is Who You Are" author: Ben Horowitz url: https://a16z.com/books/what-you-do-is-who-you-are/ type: book published: 2019-10-29 reliability: authoritative - id: src5 title: "How Lattice Defined Its Authentic and Meaningful Company Values" author: Lattice url: https://lattice.com/articles/how-lattice-defined-authentic-and-meaningful-company-values type: industry_guide published: 2024-03-01 reliability: reliable - id: src6 title: "Culture matters when building new businesses" author: McKinsey & Company url: https://www.mckinsey.com/capabilities/business-building/our-insights/when-building-new-businesses-culture-matters type: research published: 2024-09-01 reliability: authoritative --- # 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, what gets celebrated, what creates friction (Slack history, meeting recordings, decision logs) - [ ] **Collaborative document platform** — Notion, Google Docs, Confluence, or a Git-based wiki - [ ] **Minimum 4 weeks of operating history** — cannot document culture that does not yet exist; need observable patterns ## 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 — research shows recall drops sharply beyond 7 items; GitLab uses 6 (CREDIT) [src2] - Every value must include an anti-value — Netflix pairs each principle with what it does NOT mean to prevent weaponization [src1] - Decision-making principles must specify WHO decides, not just HOW — ambiguity here is the #1 source of cultural friction [src6] - Values must be embedded in at least one operational system (hiring, reviews, or promotions) within 30 days or they become decorative [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 ``` | Path | Approach | Time Investment | Tools | Output Quality | |------|----------|----------------|-------|---------------| | A: Founder Workshop | Co-founder alignment session | 3-4 hours | Google Docs | Good — captures intent but untested | | B: Full Build | Workshop + team input rounds | 2-3 weeks | Notion + survey tool | Excellent — validated by team | | C: Codify Existing | Pattern extraction + formalization | 1-2 weeks | Notion + Slack analysis | Excellent — grounded in reality | | D: Refresh & Extend | Survey + workshop + revision | 3-4 weeks | Culture Amp/Lattice + Notion | Excellent — data-driven update | ## Execution Flow ### Step 1: Gather Founder Input **Duration**: 2-3 hours (single session or two 90-minute sessions) **Tool**: Whiteboard (Miro/FigJam) or shared document Each founder independently answers these questions before the group session: 1. **Describe 3 moments when the team was at its best.** What behaviors made those moments work? 2. **Describe 2 moments of cultural friction.** What behaviors caused the problem? 3. **When you fire someone, what behavior will be the reason?** (Horowitz test) [src4] 4. **Name a company whose culture you admire. Why?** Be specific about behaviors, not vibes. 5. **What should this company NEVER become?** Describe the anti-culture. Then discuss as a group. Look for convergence — themes mentioned by multiple founders are likely real values. Themes mentioned by only one founder are preferences, not values. **Verify**: At least 4-6 behavioral themes identified with agreement from all founders. **If failed**: If founders disagree fundamentally, this is a co-founder alignment problem. Resolve disagreements before proceeding — documenting contradictory values is worse than having none. ### Step 2: Identify Existing Behavioral Patterns **Duration**: 3-5 hours of async analysis **Tool**: Slack/email search, meeting recordings, decision logs Mine existing behavior for evidence that values are already lived (or violated): 1. **Review the last 20 significant decisions.** How were they made? Who decided? Was consensus required? 2. **Search Slack/email for praise patterns.** What gets celebrated? What language do people use? 3. **Search for conflict patterns.** What triggers disagreements? How are they resolved? 4. **Review hiring decisions.** Who was hired despite skill gaps (values fit)? Who was rejected despite strong skills (values misfit)? 5. **If team is 5+ people**: Send a brief survey asking each person to describe "how things really work here" in their own words. Compare answers. Map findings to the founder themes from Step 1. Real values are ones where founder intent AND team behavior already align. Aspirational values are ones where there is a gap. **Verify**: Each theme from Step 1 has at least 2 behavioral examples from the team's actual history. **If failed**: If a theme has zero behavioral evidence, flag it as aspirational and move it to a "working toward" section rather than claiming it as a current value. ### Step 3: Draft Values with Anti-Values **Duration**: 2-3 hours **Tool**: Collaborative document For each value (aim for 3-7), create a structured entry: ```markdown ## Value: [Name — make it memorable and specific to your company] **Definition**: [1-2 sentences — what this means in practice] **What this looks like**: - [Observable behavior 1 — specific enough to evaluate] - [Observable behavior 2] - [Observable behavior 3] **What this does NOT mean (anti-value)**: - [Misinterpretation 1 that must be explicitly rejected] - [Misinterpretation 2] **Decision test**: When faced with [specific tension], we choose [this] over [that]. ``` Naming guidance from proven frameworks: - **Netflix** uses plain language: "Judgment," "Selflessness," "Courage" [src1] - **Stripe** uses action phrases: "Move with urgency and focus," "Collaborate egolessly" [src3] - **GitLab** uses an acronym (CREDIT) for recall: Collaboration, Results, Efficiency, DIB, Iteration, Transparency [src2] - **Lattice** uses distinctive phrases: "Ship, Shipmate, Self" [src5] Anti-values are critical. Without them, "Move fast" becomes "Skip quality checks." "Be transparent" becomes "Share confidential information." "Be direct" becomes "Be cruel." [src4] **Verify**: Each value has at least 3 behavioral examples and 2 anti-values. Non-founders can read the document and correctly identify which of two scenarios aligns with each value. **If failed**: If a value cannot be illustrated with concrete examples, it is too abstract. Rewrite it as a behavior, not a noun. ### Step 4: Create Decision-Making Principles **Duration**: 1-2 hours **Tool**: Same collaborative document Decision-making principles answer: "When values conflict, which wins?" and "Who gets to decide?" Document these elements: 1. **Decision authority framework**: Specify who decides what at each level. - Reversible decisions: person closest to the problem decides (inform, don't ask) - Irreversible decisions: require [specific approval — e.g., "two co-founders" or "team lead + one peer"] - Hiring/firing: always requires [specified authority] 2. **Values hierarchy for conflicts**: When two values collide, which takes precedence? - Example (Stripe): "Users first" outranks "Move with urgency" — never ship something that harms users to hit a deadline [src3] - Example (Netflix): "People over process" outranks efficiency — keep the team excellent even if it slows you down [src1] 3. **Communication defaults**: How does information flow? - Default to public (GitLab model) vs. default to private with explicit sharing [src2] - Written decisions vs. verbal decisions — specify which is the source of truth - Disagreement protocol: disagree openly, commit after decision, revisit with data **Verify**: A new hire reading only this section could correctly resolve 3 out of 4 realistic decision scenarios without asking a manager. **If failed**: The principles are too abstract. Add specific scenario examples. ### Step 5: Build Behavioral Norms **Duration**: 1-2 hours **Tool**: Same collaborative document Behavioral norms translate values into daily operational defaults. These are the "how we work" specifics: 1. **Meeting norms**: How are meetings run? Who attends? Required prep? Decision recording? 2. **Communication norms**: Response time expectations, async vs. sync defaults, tool preferences 3. **Feedback norms**: How is feedback given? (Netflix: 4A model — Aim to Assist, Actionable, Appreciate, Accept or Discard) [src1] 4. **Conflict norms**: How are disagreements handled? Escalation path? 5. **Work-life norms**: Availability expectations, time-off policies, after-hours communication 6. **Quality norms**: What is "good enough" to ship? Who signs off? Keep each norm to 1-2 sentences. If it needs a paragraph, it is a policy, not a norm. **Verify**: Every norm maps back to at least one value. Orphan norms (not connected to a value) should be cut or the value set should be expanded. **If failed**: If norms contradict values, the values are aspirational and the norms are real. Update the values to match reality. ### Step 6: Publish and Embed in Operational Systems **Duration**: 1-2 weeks for full embedding **Tool**: HR/people platform, ATS, review tool Publishing the document is 10% of the work. Embedding it in systems is the other 90%. 1. **Publish the culture document**: Make it accessible to all employees. Consider making it public (GitLab model — attracts aligned candidates, repels misaligned ones). [src2] 2. **Embed in hiring**: - Add values-based questions to interview scorecards (1-2 questions per value) - Train interviewers to evaluate behavioral evidence, not self-reported alignment - Include culture document in candidate information packet 3. **Embed in onboarding**: - First-week session: walk through values with real examples from company history - Assign a "culture buddy" who models the values - 30-day check-in: ask new hire to identify one example of each value they observed 4. **Embed in performance reviews**: - Add values as evaluation dimensions (equal weight to skill-based criteria) - Require specific behavioral examples for each rating, not just a score - Tie promotion criteria explicitly to values demonstration 5. **Embed in recognition**: - Create a channel or ritual for calling out values-aligned behavior - Reference the specific value when recognizing someone 6. **Schedule quarterly review**: Values are a living document. Review quarterly for the first year, then semi-annually. [src2] **Output files**: - `culture-values-handbook.md` — Complete culture document with values, anti-values, decision principles, and behavioral norms - `hiring-rubric-values.md` — Interview scorecard template with values-mapped questions - `performance-review-template.md` — Review framework with values as evaluation dimensions - `onboarding-culture-session.md` — First-week culture walkthrough outline **Verify**: All four documents are complete and internally consistent. At least one operational system (hiring scorecard) is updated within the first week. **If failed**: If operational embedding is delayed beyond 30 days, values will not take hold. Prioritize hiring rubric integration as the minimum viable embedding. ## Output Schema ```json { "output_type": "culture_documentation_package", "format": "Markdown documents", "documents": [ {"name": "culture-values-handbook", "type": "primary", "description": "Core values, anti-values, decision principles, behavioral norms", "required": true}, {"name": "hiring-rubric-values", "type": "integration", "description": "Interview scorecard with values-based evaluation criteria", "required": true}, {"name": "performance-review-template", "type": "integration", "description": "Review framework with values as assessment dimensions", "required": false}, {"name": "onboarding-culture-session", "type": "integration", "description": "First-week culture walkthrough outline", "required": false} ], "primary_document_structure": { "sections": ["mission_alignment", "core_values", "anti_values", "decision_making_principles", "behavioral_norms", "operational_embedding"], "values_per_document": "3-7", "anti_values_per_value": "2-3", "behavioral_examples_per_value": "3-5" } } ``` ## Quality Benchmarks | Quality Metric | Minimum Acceptable | Good | Excellent | |---------------|-------------------|------|-----------| | Number of core values | 3 | 4-5 | 5-7 with clear hierarchy | | Anti-values per value | 1 | 2 | 3+ with scenario examples | | Behavioral examples per value | 2 | 3-4 | 5+ from real company history | | Decision principle specificity | Generic guidance | Role-specific authority | Scenario-tested with team | | Operational embedding touchpoints | 1 (hiring) | 2 (hiring + reviews) | 4+ (hiring, reviews, onboarding, recognition) | | Team validation | Founders only | Founders + 2-3 team members | Full team input with survey | **If below minimum**: Re-run Step 1 with broader founder input. If values lack behavioral examples, the company may be too early — wait until the team has 4+ weeks of working together before attempting documentation. ## Error Handling | Error | Likely Cause | Recovery Action | |-------|-------------|----------------| | Founders cannot agree on values | Fundamental co-founder misalignment | Pause culture documentation. Facilitate a co-founder alignment session first. If values diverge on 3+ dimensions, flag as a startup risk. | | Values are too generic ("integrity," "excellence") | Skipped the anti-values and behavioral examples step | Re-run Step 3. Apply the Horowitz test: "Would any company disagree with this value?" If no, it is not distinctive. [src4] | | Team ignores published values | Values not embedded in systems (Step 6 skipped) | Immediately integrate into hiring rubric (minimum viable embedding). Schedule values-based recognition in next all-hands. | | Values contradict actual behavior | Documented aspirations instead of reality | Re-run Step 2 with honest behavioral analysis. Document what IS, then create a separate "working toward" section for gaps. | | New hires don't understand values | Onboarding embedding missing or too abstract | Add concrete scenario-based examples. Create a "Values in Action" library of real stories. | | Values become weaponized ("Be direct" = "Be cruel") | Missing anti-values | Add explicit anti-values for every core value. Update hiring rubric to screen for this misinterpretation. | ## Cost Breakdown | Component | Free Tier | Paid Tier | At Scale | |-----------|-----------|-----------|----------| | Workshop facilitation | Founder-led ($0) | External facilitator ($500-2000) | Culture consultancy ($5000-15000) | | Documentation platform | Google Docs / Notion free ($0) | Notion team ($8/user/mo) | Confluence ($6/user/mo) | | Employee survey (Path D) | Google Forms ($0) | Culture Amp ($5/user/mo) | Lattice ($11/user/mo) | | Hiring integration | Manual scorecard ($0) | ATS with scorecards ($50-200/mo) | Greenhouse/Lever ($300+/mo) | | **Total for typical startup (10 people)** | **$0** | **$500-1000 one-time** | **$2000-5000** | ## Anti-Patterns ### Wrong: Copying another company's values wholesale Adopting Netflix's values verbatim for a 5-person seed-stage startup. Netflix's culture of "adequate performance gets a generous severance" works with 13,000 employees and significant HR infrastructure. Without that context, it creates fear rather than excellence. [src1] ### Correct: Study frameworks, then discover your own Use Netflix, GitLab, and Stripe as structural inspiration (how they format, what they include) but derive the actual values from your own team's behavioral patterns in Step 2. ### Wrong: Publishing values without anti-values Writing "We value transparency" without specifying boundaries. Result: an employee shares salary data publicly, another shares a client's confidential roadmap in an all-hands, a third reads "transparency" as license to deliver harsh criticism without empathy. ### Correct: Every value gets a "what this does NOT mean" section "We value transparency" paired with "This does NOT mean: sharing confidential client information, delivering feedback without empathy, or bypassing someone's manager to escalate publicly." [src4] ### Wrong: Treating culture documentation as a one-time project Writing values during an offsite, publishing them on the wiki, and never revisiting. GitLab updates their handbook values page continuously — it is a living document with a visible edit history. [src2] ### Correct: Schedule quarterly reviews and track behavioral drift Set a calendar reminder to review values quarterly. Track whether hiring decisions, promotions, and terminations are consistent with documented values. Update the document when the company's reality evolves. ## 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 the founders can no longer onboard everyone personally) and again at 40-60 employees (before sub-cultures form in departments). McKinsey research shows cultural friction causes up to 26% of startup failures — making this a survival exercise, not a nice-to-have. [src6] ## Related Units - [Mission & Vision Statement](/business/startup-planning/mission-vision-statement/2026) - [Interview Scorecard Design](/business/startup-hiring/interview-scorecard-design/2026) - [Performance Review Framework](/business/startup-operations/performance-review-framework/2026) - [Remote Team Culture](/business/startup-operations/remote-team-culture/2026) - [Onboarding Process Design](/business/startup-operations/onboarding-process-design/2026)