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 from 5 people to 500.

## 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, psychological safety, culture scaling, engagement, eNPS, remote culture, hybrid culture, culture clash, employer brand, onboarding culture, performance culture, recognition

---

## 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 is descriptive. The work is closing the gap between stated and actual.

---

## Clarify First

Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:

- [ ] **Which deliverable is needed** (values + behaviors, culture code, health survey, ritual calendar, culture-debt audit, or M&A integration) — each has its own template
- [ ] **Company stage and headcount** — rituals and transmission mechanisms that work at 15 people break at 150; the ritual matrix is stage-keyed
- [ ] **What is actually rewarded, tolerated, and celebrated today** — culture is descriptive, not aspirational; without the honest current state you produce wall-poster platitudes
- [ ] **Work model** (in-person, remote, hybrid) — determines which operating principles and meeting rules apply

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

---

## Culture Diagnostic Decision Tree

```
START: "How is our culture?"
  |
  v
[Run the Values Audit]
  Ask: "What did the last person who got promoted demonstrate?"
  |
  +-- Answer matches stated values --> Values are real. Check transmission.
  |     |
  |     v
  |   [Can a 30-day employee describe the culture accurately?]
  |     +-- YES --> Culture is operational. Maintain and evolve.
  |     +-- NO  --> Transmission gap. Fix onboarding and rituals.
  |
  +-- Answer differs from stated values --> Values are performative.
        |
        v
      [Do leaders model the real (non-stated) values?]
        +-- YES --> Rewrite values to match reality, then iterate.
        +-- NO  --> Deeper problem: no coherent culture exists. Build from scratch.
```

---

## Framework 1: Mission / Vision / Values Workshop

### Mission (Why We Exist)

| Element | Test | Example |
|---------|------|---------|
| Present-tense | Is it about what we do now, not what we aspire to? | "We reduce preventable falls in elderly care" |
| Specific | Could a competitor claim the exact same thing? If yes, too generic. | Not "We make the world better" |
| Meaningful | Would something be lost if we disappeared? | Answer must be concrete |

### Vision (What Winning Looks Like)

| Quality | Bad | Good |
|---------|-----|------|
| Specificity | "Be the market leader" | "Every care home in Europe uses our system by 2030" |
| Falsifiability | "Transform healthcare" | "Reduce fall-related injuries by 50% in partner facilities" |
| Timeline | No date | 5-10 year horizon with milestones |

### Values (What We Actually Do)

| Rule | Explanation |
|------|-------------|
| 3-5 values maximum | More than 5 and none are memorable |
| Derived from observation | "What did our best hire do that nobody asked?" |
| Each has behavioral anchors | Specific enough to judge against |
| Include the tension | Good values have a cost ("Speed" means "we accept some risk") |

---

## Framework 2: Values-to-Behaviors Translation

This is the work that makes values operational. Every value needs concrete behavioral anchors.

| Value | Vague Version | Behavioral Anchor | How You'd Observe It |
|-------|---------------|-------------------|---------------------|
| Transparency | "We're open and honest" | "We share bad news within 24 hours, including to our manager" | Bad news travels fast, no surprises |
| Ownership | "We take responsibility" | "We don't hand off problems -- we own until resolved, even across team boundaries" | No orphaned issues |
| Speed | "We move fast" | "Decisions under $5K happen at team level, same day" | Low decision latency |
| Quality | "We don't cut corners" | "We stop the line before shipping something we're not proud of" | Teams delay launches for quality |
| Customer-first | "Customers are our priority" | "Any team member can escalate a customer issue to leadership, bypassing normal channels" | Escalation is celebrated, not punished |

### Translation Workshop (90 minutes)

```
For each value:
  Step 1: State the value in 2-3 words
  Step 2: Ask "How would a new hire know we live this on day 30?"
  Step 3: Write 3 observable behaviors that prove this value
  Step 4: Write 3 behaviors that violate this value
  Step 5: Ask "What does this value cost us? What's the trade-off?"
  Step 6: If no trade-off exists, it's not a value -- it's a platitude

Output: Value card with behaviors, violations, and trade-offs
```

---

## Framework 3: Culture Code Creation

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

### Culture Code Structure

| Section | Purpose | Key Question |
|---------|---------|-------------|
| 1. Who We Are | Mission, context, stage | "Why does this company exist?" |
| 2. Who Thrives Here | Specific behaviors, not adjectives | "What does success look like day-to-day?" |
| 3. Who Doesn't Thrive Here | Honest misfit description | "When have we made a bad hire? What was the pattern?" |
| 4. How We Make Decisions | Decision rights, speed expectations | "Who can decide what, and how fast?" |
| 5. How We Communicate | Channels, cadence, expectations | "What can I expect in response time a