Culture Architect

• "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

Diff History

• v00.33.0: Ingested from claude-skills-main

Why This Skill Exists

Build, measure, and evolve company culture as operational behavior — not wall posters. Covers mission/vision/values

When to Use

Use this skill when the task requires culture architect capabilities.

What If Fails

• condition: Assets visuais não disponíveis para análise