Playbook
IntermediateFounderCEOHR

Designing Culture Intentionally: From Posters on the Wall to Operating Behaviors

Every company has a culture. Most are accidents. This is how to design culture as an operating system — values that behave like rules, rituals that ship behavior, and decision rights that survive scale — drawing on Edgar Schein, Brian Chesky, Patty McCord, Reed Hastings and Daniel Coyle.

18 min read Updated 2026-05-17

Culture is not the words on the wall, the perks in the kitchen or the way the office is decorated. Culture is the set of behaviors that get rewarded, tolerated and punished — and the unwritten beliefs underneath them. Every company has one. The question is whether yours is designed or inherited.

What culture actually is

Culture is what happens when no one is watching.
Often attributed to Brian Chesky / Airbnb leadership memos

Edgar Schein, the MIT scholar who effectively founded the field of organizational culture, defined it as 'a pattern of shared basic assumptions that the group learned as it solved its problems'. The operative word is solved — culture is the residue of how you actually handle problems, not what you say you would.

Schein's three levels

Schein's model of culture
  1. 1
    Artifacts
    Visible — office, dress, stories, language, rituals. Easy to see, easy to misinterpret.
  2. 2
    Espoused values
    What the company says it believes — values posters, manifestos. Often aspirational, sometimes a lie.
  3. 3
    Underlying assumptions
    Unconscious, taken-for-granted beliefs. The hardest to change and where culture actually lives.
The gap test

If your espoused values and underlying assumptions don't match, employees default to the assumptions. Posting 'we value candor' while punishing candor in practice teaches people to lie politely.

Values that behave like rules

Patrick Lencioni's classic HBR essay 'Make Your Values Mean Something' argued that values fail when they're generic ('integrity', 'teamwork') or aspirational without consequence. The Netflix culture deck, Bridgewater's Principles and Amazon's Leadership Principles share a property: they discriminate. They give you criteria to say no to behavior — including from senior people.

The test of a real value
  1. 1
    Discriminating
    It rules out plausible alternatives. 'We hire smart people' rules out nobody. 'We hire only people who would be in the top 10% at our most demanding competitor' rules out most.
  2. 2
    Costly
    Living it costs something. If it costs nothing, it's marketing.
  3. 3
    Specific to action
    Translates into a concrete behavior, hiring criterion, or firing criterion.
  4. 4
    Tested at the edges
    Survives a hard case — losing a customer, firing a star, killing a project — without bending.
Bad vs. good values (paraphrased from public sources)
GenericDiscriminating
IntegrityWe say what's true even when it costs us a deal (Bridgewater: 'Pain + Reflection = Progress')
Customer focusWe will refund any unhappy customer in 60 seconds without manager approval (Zappos)
InnovationWe disagree and commit — speak up in the room, support the decision after (Amazon LP)
High performanceAdequate performance gets a generous severance package (Netflix)

Rituals: where culture ships

Daniel Coyle's research in The Culture Code identified that high-performing cultures are not values-statement organizations — they are ritual-rich. Rituals are how abstract values become muscle memory across thousands of people.

  • Onboarding rituals — Airbnb's '4-day onboarding' includes a tour of the values, host stories, and a personal welcome from a founder.
  • Decision rituals — Amazon's 6-page memo + silent read at the start of meetings encodes 'narrative over slides'.
  • Feedback rituals — Bridgewater's recorded meetings + dot-collector force radical transparency in real time.
  • Recognition rituals — Pixar's daily dailies normalize public, blameless critique of work in progress.
  • Conflict rituals — Netflix's '4A feedback' (Aim to assist, Actionable, Appreciate, Accept or discard) gives a script for disagreement.
  • Closing rituals — Atlassian's quarterly demo days celebrate shipped work across the company.
Three rituals every company needs

(1) A weekly ritual that connects work to mission. (2) A monthly ritual that celebrates outcomes, not effort. (3) A quarterly ritual that publicly closes the loop on what worked and what didn't.

Decision rights and behavior

Reed Hastings argues in No Rules Rules that culture is not just values — it is who gets to decide what, and what happens when they're wrong. Vague decision rights produce political behavior; clear ones produce courage.

RAPID / DACI for decisions
  1. 1
    Driver / Recommend
    Owns the proposal and moves it forward.
  2. 2
    Approve
    Has formal sign-off. Should be ONE person, not a committee.
  3. 3
    Consult / Input
    Provides expert input before the decision is made.
  4. 4
    Inform
    Notified after the decision, not blocking it.
If everyone has to agree, no one is in charge

Consensus-by-default is the most common cultural failure mode in fast-growing companies. Every decision needs a single accountable approver. Disagree-and-commit is a cultural muscle, not a policy.

What changes at every scale break

Culture at scale — what breaks first
HeadcountWhat breaksWhat to add
1–15Founder is the culture; everyone interviews everyoneWrite down 5 values you actually hire by
15–50Lunch table no longer fits; tribal knowledge fragmentsWritten onboarding, weekly all-hands, decision rights
50–150 (Dunbar)You no longer know everyone's name; politics startManager training, calibration, internal comms function
150–500Sub-cultures form; one company starts feeling like fourLeadership offsites, cross-team rituals, refresh values with data
500+Brand and culture decouple unless actively bridgedCulture survey + behavior audit; executive role models on stage

Cases: Netflix, Airbnb, Stripe, Bridgewater

  • Netflix — built culture around 'Freedom and Responsibility', removed expense, vacation and approval policies, paid top of market, fired adequate performers. Result: low process drag, high accountability, polarising for newcomers.
  • Airbnb — Chesky doubled down on 'belong anywhere' and held interviews himself well past Series C; founders set the cultural floor.
  • Stripe — internal 'Engineering culture doc' and 'Writing is thinking' principle; documentation is treated as a first-class product.
  • Bridgewater — radical transparency taken to an extreme few survive; instructive as a counter-example as much as a model.

Warning signs you're losing it

  • New hires can't articulate the values without checking a doc.
  • The same difficult conversations keep getting kicked upstairs.
  • Process growth outpaces revenue growth two quarters in a row.
  • Regrettable attrition is concentrated in your top performers.
  • Skip-level meetings reveal completely different perceptions of the company.
  • Internal language drifts toward 'they' — the company becomes 'them', not 'us'.

The intentional-culture playbook

  1. Audit — interview 12 people across levels. Write down what they describe (assumptions level), not what they cite.
  2. Edit values — rewrite to be discriminating, costly and specific. Cut anything you wouldn't fire over.
  3. Codify rituals — pick 3–5 weekly/monthly/quarterly rituals that ship those values into behavior.
  4. Map decisions — top 10 recurring decisions with a single approver per. Publish.
  5. Hire / fire on it — interview rubrics map to values. Exit interviews ask which values were lived and which weren't.
  6. Measure — annual culture survey + behavior audit. Track the gap.

References

Written by Pawan Joshi. Sources cited inline. Last updated 2026-05-17.