Culture Architect

Culture Architect

Culture is what you DO, not what you SAY. This skill builds culture as an operational system — observable behaviors, measurable health, and rituals that scale.

Keywords

culture, company culture, values, mission, vision, culture code, cultural rituals, culture health, values-to-behaviors, founder culture, culture debt, value-washing, culture assessment, culture survey, Netflix culture deck, HubSpot culture code, psychological safety, culture scaling

Core Principle

Culture = (What you reward) + (What you tolerate) + (What you celebrate)

If your values say "transparency" but you punish bearers of bad news — your real value is "optics." Culture is not aspirational. It's descriptive. The work is closing the gap between stated and actual.

Frameworks

1. Mission / Vision / Values Workshop

Run this conversationally, not as a corporate offsite. Three questions:

Mission — Why do we exist (beyond making money)?

• "What would be lost if we disappeared tomorrow?"
• Mission is present-tense. "We reduce preventable falls in elderly care." Not "to be the leading..."

Vision — What does winning look like in 5–10 years?

• Specific enough to be wrong. "Every care home in Europe uses our system" beats "be the market leader."

Values — What behaviors do we actually model?

• Start with what you observe, not what sounds good. "What did our last great hire do that nobody asked them to?"
• Keep to 3–5. More than 5 and none of them mean anything.

2. Values → Behaviors Translation

This is the work. Every value needs behavioral anchors or it's decoration.

Workshop exercise: Write your value. Then ask "How would a new hire know we actually live this on day 30?" If you can't answer concretely, it's not a value — it's an aspiration.

3. Culture Code Creation

A culture code is a public document that describes how you operate. It should scare off the wrong people and attract the right ones.

Structure: 1. Who we are (mission + context) 2. Who thrives here (specific behaviors, not adjectives) 3. Who doesn't thrive here (honest — this is the useful part) 4. How we make decisions 5. How we communicate 6. How we grow people 7. What we expect of leaders

See templates/culture-code-template.md for a complete template.

Anti-patterns to avoid:

• "We're a family" — families don't fire each other for performance
• Listing only positive traits — the "who doesn't thrive here" section is what makes it credible
• Making it aspirational instead of descriptive

4. Culture Health Assessment

Run quarterly. 8–12 questions. Anonymous. See references/culture-playbook.md for survey design.

Core areas to measure: 1. Psychological safety — "Can I raise a concern without fear?" 2. Clarity — "Do I know how my work connects to company goals?" 3. Fairness — "Are decisions made consistently and transparently?" 4. Growth — "Am I learning and being challenged here?" 5. Trust in leadership — "Do I believe what leadership tells me?"

Score interpretation:

5. Cultural Rituals by Stage

Rituals are the delivery mechanism for culture. What works at 10 people breaks at 100.

Seed stage (< 15 people)

• Weekly all-hands (30 min): company update + one win + one learning
• Monthly retrospective: what's working, what's not — no hierarchy
• "Default to transparency": share everything unless there's a specific reason not to

Early growth (15–50 people)

• Quarterly culture survey: first formal check-in
• Recognition ritual: explicit, public, tied to values (not just results)
• Onboarding buddy program: cultural transmission now requires intentional effort
• Leadership office hours: founders stay accessible as layers appear

Scaling (50–200 people)

• Culture committee (peer-driven, not HR): 4–6 people rotating quarterly
• Values-based performance review: culture fit is measured, not assumed
• Manager training: culture now lives or dies in team leads
• Department all-hands + company all-hands separate

Large (200+ people)

• Culture as strategy: explicit annual culture plan with owner and KPIs
• Internal NPS for culture ("Would you recommend this company to a friend?")
• Subculture management: engineering culture ≠ sales culture — both must align to company core

6. Culture Anti-Patterns

Value-washing: Listing values you don't practice. Symptom: employees roll their eyes during values discussions.

• Fix: Run a values audit. Ask "What did the last person who got promoted demonstrate?" If it doesn't match your values, your real values are different.

Culture debt: Accumulating cultural compromises over time. "We'll address the toxic star performer later." Later compounds.

• Fix: Act on culture violations faster than you think necessary. One tolerated bad behavior destroys what ten good behaviors build.

Founder culture trap: Culture stays frozen at founding team's personality. New hires assimilate or leave.

• Fix: Explicitly evolve values as you scale. What worked at 10 people (move fast, ask forgiveness) may be destructive at 100 (we need process).

Culture by osmosis: Assuming culture transmits naturally. It did at 10 people. It doesn't at 50.

• Fix: Make culture intentional. Document it. Teach it. Measure it. Reward it explicitly.

Culture Integration with C-Suite

Key Questions a Culture Architect Asks

• "Can you name the last person we fired for culture reasons? What did they do?"
• "What behavior got your last promoted employee promoted? Is that in your values?"
• "What would a new hire observe on day 1 that tells them what's really valued here?"
• "What do we tolerate that we shouldn't? Who knows and does nothing?"
• "How does a team lead in Berlin know what the culture is in Madrid?"

Red Flags

• Values posted on the wall, never referenced in reviews or decisions
• Star performers protected from cultural standards
• Leaders who "don't have time" for culture rituals
• New hires feeling the culture is "different than advertised"
• No mechanism to raise cultural concerns safely
• Culture survey results never shared with the team

Detailed References

• references/culture-playbook.md — Netflix analysis, survey design, ritual examples, M&A playbook
• templates/culture-code-template.md — Culture code document template

Culture Playbook

Reference frameworks for building, measuring, and evolving company culture.

---

1. Netflix Culture Deck — What Works, What Doesn't

Reed Hastings published this in 2009. 125 slides. 20M+ views. It changed how tech companies think about culture.

What works

"Adequate performance gets a generous severance" — This is the sentence that made HR professionals uncomfortable. It's also why Netflix has high performers. If you keep B-players, A-players leave.

Context, not control — Instead of rules and approvals, Netflix provides context (strategy, goals, constraints) and expects people to make good decisions. This only works if you actually hire people who can.

"Freedom and responsibility" as a pair — You can't have one without the other. Freedom without responsibility is chaos. Responsibility without freedom is bureaucracy.

Publicly stated values actually describe behavior — The deck is descriptive, not aspirational. It says "here's what we actually do." That's rare and valuable.

What doesn't work (or doesn't transfer)

"We are not a family" — Works at Netflix, lands badly in many cultures (especially European). The principle underneath it is valid: performance matters. The framing is optional.

"Keeper test" — "Would I fight to keep this person?" Powerful tool, but managers need coaching to use it well. Without context, it becomes paranoia-inducing.

No vacation policy — Works when managers model healthy vacation use. Doesn't work when culture implicitly punishes taking time off. The policy is neutral; the culture around it determines the outcome.

Radical transparency on compensation — Netflix publishes pay bands. This works in high-trust, high-fairness environments. In environments with existing pay inequities, it creates problems before it fixes them.

Key lesson

The Netflix culture deck works because it's honest about tradeoffs. Your culture code should be equally honest. "We move fast, which sometimes means decisions get revisited" is more credible than "we move fast AND we get it right the first time."

---

2. Values-to-Behaviors Mapping Framework

Values without behavioral anchors are intentions. Behavioral anchors make values operational.

The mapping process

Step 1: List your stated values Don't curate. Write down everything on the values list, however it's currently stated.

Step 2: For each value, find three real examples "Describe a time in the last 6 months when someone exemplified [value]." If you can't find three examples, the value isn't real.

Step 3: Extract the observable behavior From the examples, identify the specific action. Not the feeling, not the intention — the action.

Step 4: Write the behavioral anchor Format: "[Subject] does [specific action] in [specific context]."

Step 5: Find the counter-example For each value, identify a behavior that violates it. This is what you don't tolerate. Format: "[Subject] does NOT [specific opposite action] even when [temptation/pressure]."

Example mapping: "Customer Obsession"

Common mapping mistakes

Too vague: "We put customers first" — this doesn't change behavior. Too broad: "We care about quality in everything we do" — can't be measured or violated. Too personal: "We're passionate" — describes emotion, not action. Too aspirational: "We strive to deliver world-class..." — "strive" lets you off the hook.

---

3. Culture Survey Design — 8-12 Questions That Reveal Truth

Most culture surveys are useless because they measure satisfaction, not health. Satisfaction can be high in a dysfunctional culture ("I like my team, my boss, my pay" ≠ healthy culture).

Survey design principles

1. Anonymous, always. If it's not anonymous, people answer what they think you want to hear. 2. Short enough to complete honestly. 8–12 questions max. 15 minutes max. 3. Likert + open text. "On a scale of 1–5" captures signal. "Why did you give that score?" captures insight. 4. Action-linked. Never run a survey unless you're prepared to share results and act on them. 5. Consistent questions over time. You want trend data, not one-off snapshots.

The 10-question core survey

Follow-up open text questions (pick 2–3)

• "What's the one thing leadership could do differently that would most improve the culture?"
• "What do we tolerate that we shouldn't?"
• "What should we protect as we grow that we're at risk of losing?"
• "What's the gap between what we say we value and what we actually do?"

Analyzing results

eNPS (question 10): Score = % Promoters (9–10) minus % Detractors (1–6). Healthy: > 20. Great: > 40.

Questions 1 and 3 (psychological safety): If below 70%, you have a leadership problem, not a culture problem. Fix the manager first.

Question 7 (accountability): This is the most honest question. Cultures that fail to hold underperformers accountable destroy high-performer retention.

Biggest drop between surveys: This is your fire. Don't average it away.

---

4. Cultural Ritual Examples by Company Stage

Seed (< 15 people)

Weekly "Wins and Learnings" (15 min, Fridays)

• Each person shares one win (however small) and one learning (failure, insight, mistake)
• No slides. No prep. Just talking.
• Purpose: normalizes imperfection, builds psychological safety early

"Open book" financials

• Share revenue, burn, runway with the whole team monthly
• Builds owners, not employees
• Requires trust that people won't misuse the data

"Postmortem as celebration"

• When something goes wrong, celebrate the post-mortem publicly
• "We learned X, here's how we'll do it differently"
• Prevents a blame culture from forming early

Early growth (15–50 people)

Monthly "Founder's Letter"

• CEO writes an unfiltered update: what we're winning, what's hard, what's changed
• Not polished. Not PR. Real.
• Distributed internally before it goes external

Values spotlight in team meetings

• One agenda item: "Who exemplified [value] this week? What did they do?"
• Takes 3 minutes. Trains the muscle for values-linked recognition.

New hire "30-day truth sessions"

• At day 30, every new hire meets with a senior leader (not their manager) and answers: "What surprised you? What's different from what you expected? What would you fix?"
• Captures culture signal while the new hire's eyes are still fresh

Scaling (50–200 people)

Quarterly culture review

• Culture committee reviews survey results, names top issues, proposes 2–3 concrete actions
• Results shared with all-hands within 2 weeks of survey close
• 30-day action accountability check-in

Manager calibration on culture fit

• Quarterly: managers share one team member who exemplifies culture, one who struggles
• Group discussion on patterns, not individuals
• Identifies culture outliers early before they become retention or performance crises

"Culture at the edges" audit

• Review last 10 performance issues, 10 terminations, 10 promotions
• Ask: "Is the pattern consistent with our stated values?"
• This is the reality check. The data doesn't lie.

Large (200+ people)

Subculture alignment mapping

• Each department articulates its micro-culture
• Cross-reference with company core values
• Identify deviations: healthy variation vs. value violation

Culture ambassador program

• Peer-nominated, rotating, not HR
• Run culture rituals, surface issues, connect remote/distributed teams
• Budget: small (recognition, team events), influence: large

---

5. How to Evolve Culture Without Losing Identity

Culture must evolve as you scale. The mistake is either: (a) refusing to evolve, preserving founder culture that doesn't scale, or (b) evolving so fast that original identity is lost.

The evolution framework

Preserve: Core values that define who you are. These should be stable across stages. If "move fast" is core, it doesn't go away — but its expression changes.

Adapt: Behaviors that worked at one stage but need updating. "Move fast" at 10 people = decide same day. At 200 people = decide within 1 week with the right people in the room.

Add: New behaviors required at the new scale. "Documentation culture" wasn't needed at 10. It's essential at 100.

Retire: Behaviors that actively hurt at scale. "Ask forgiveness, not permission" works at seed. Creates coordination chaos at Series B.

The evolution process

1. Annual values review (not a rewrite — an audit) 2. Ask: "Which of our current behaviors are we proud of? Which embarrass us?" 3. Identify behaviors to add/adapt/retire 4. Communicate the evolution explicitly: "Here's what's changing and why" 5. Update the culture code, onboarding, and performance criteria

Communication of culture change

Never let culture evolution look like hypocrisy. Proactively name it: "We used to make all decisions quickly at the team level. As we've grown, that's created coordination problems. Here's how we're updating that: [new behavior]. The underlying value — speed — hasn't changed. How we deliver it has."

---

6. Handling Culture Clashes in M&A or Rapid Hiring

M&A culture integration

Before signing:

• Culture due diligence is as important as financial DD
• Questions to answer: How do they make decisions? What gets people fired? What gets them promoted? What do they celebrate?
• Red flag: "We have a great culture" with no supporting evidence

First 90 days:

• Don't impose culture; conduct a bilateral audit
• Identify: what do they do that we should adopt? What do we do that they should adopt? What conflicts must be resolved?
• Assign an integration lead on each side. Give them actual authority.

Failure mode: Assuming acquisition = cultural absorption. The target's culture doesn't disappear. It goes underground and resurfaces as dysfunction.

Rapid hiring culture dilution

When a company doubles in headcount in 12 months, culture dilution is near-certain. Prevention:

1. Codify before you scale. Document the culture before the surge, not after. 2. Onboarding is cultural transmission. Not just process, not just paperwork — immersion in how decisions get made, what's celebrated, what's not tolerated. 3. Hire for culture adds, not fits. "Fit" means homogeneity. "Add" means the person brings a perspective or behavior that strengthens the culture without violating core values. 4. Manager density matters. If you're adding 10 ICs and 0 managers, the new people have nobody to transmit culture to them. Hire managers ahead of the curve. 5. Culture buddy system. Pair new hires with culture exemplars for the first 60 days.

[Company Name] Culture Code

This document describes how we work, what we value, and what it's like to be here. It's meant to be honest — which means it will attract some people and repel others. Both outcomes are correct.

---

Who We Are

[2–3 sentences: what you do, who you serve, what would be lost if you disappeared.]

Our mission: [One sentence. Present tense. Specific enough to be wrong.]

Our vision: [Where we'll be in 5–10 years. Specific enough to debate.]

---

What We Value

Values are behaviors, not adjectives. Each one has a "this is what it looks like" and a "this is what it doesn't look like."

[Value 1]

What this means: [Behavioral anchor — what someone does when they live this value]

What this doesn't mean: [The misconception or violation to guard against]

Example: [A real story of this value in action at your company]

---

[Value 2]

What this means: [Behavioral anchor]

What this doesn't mean: [The misconception or violation]

Example: [Real story]

---

[Value 3]

What this means: [Behavioral anchor]

What this doesn't mean: [The misconception or violation]

Example: [Real story]

---

(Repeat for each value. 3–5 total. Never more than 5.)

---

Who Thrives Here

These are specific, observable behaviors — not personality traits or adjectives.

• You raise problems early, not after they've grown. You don't complain privately and stay silent publicly.
• You own decisions even when the outcome isn't what you expected.
• You say "I don't know" instead of bluffing. Then you find out.
• You give direct feedback to the person who needs to hear it, not to everyone else.
• You make things better, not just done. You notice what's broken and fix it even when it's not your job.
• [Add 2–3 specific to your company]

---

Who Doesn't Thrive Here

This is the most useful section. Read it carefully.

• People who need clear instructions before taking action. We provide context; you figure out the path.
• People who optimize for credit over outcomes. We care what got done, not who gets the headline.
• People who treat bad news as a liability. Here, hiding problems is the problem.
• People who need consensus before every decision. We move faster than that.
• [Add 2–3 specific to your company — be honest]

---

How We Make Decisions

Decision types:

• Reversible, small scope: Make it yourself. Don't ask. Tell us what you decided.
• Reversible, larger scope: Tell relevant people, move forward unless you hear an objection within 24 hours.
• Irreversible or high-stakes: Bring the right people into the room. Write it down. Decide together.

Default: Bias toward action. A good decision made fast beats a perfect decision made slow.

Who decides: The person closest to the problem, with the most context. Not the most senior person in the room.

---

How We Communicate

Default to async. Most things don't need a meeting. If it can be written, write it.

Meetings that happen: [List your recurring meetings and what they're for]

Meetings that don't happen: Status updates (use tools), information sharing (write a doc), decisions that one person could make.

How we give feedback: Direct, specific, timely. "That report was late and incomplete" not "you should think about your time management." We give feedback to help, not to vent.

How we share bad news: Within 24 hours of knowing. To the person who needs to know. Not softened to the point of unclear.

---

How We Grow People

We invest in people who invest in themselves. We provide [budget, learning days, access — be specific]. We don't require you to use them.

Promotions: Based on impact already demonstrated, not time served. You're promoted when you're already doing the job you want.

Performance feedback: [How often, what format, who delivers it]

When things aren't working: We have direct conversations early. We don't let problems simmer for quarterly reviews.

---

What We Expect of Leaders

Leaders here are multipliers, not heroes. Your job is to make your team better.

• You share context, not just instructions. Your team should be able to make decisions you'd make when you're not there.
• You give credit visibly and take accountability privately.
• You have hard conversations before they become unavoidable.
• You model the culture. If you don't live the values, neither will your team.
• You develop people, including ones who will outgrow their role here.

---

The Fine Print

This document is descriptive, not aspirational. It describes how we operate today, with the intent to keep improving.

We update this annually. When the update happens, we'll tell you what changed and why.

Last updated: [Date] | Version: [X.X]