building-team-culture

Building Team Culture

Scope

Covers

• Diagnosing the current culture (strengths, gaps, “sacred cows”, and where psychological safety breaks)
• Articulating culture as an operating system (principles → behaviors → decision rules)
• Defining team norms (communication, meetings, decisions, feedback, conflict)
• Designing a lightweight rituals/cadence map that reinforces the culture
• Planning rollout + reinforcement (coaching model, hiring/onboarding hooks, measurement)

When to use

• “Create a culture code / values and behaviors for my team.”
• “Our team norms are unclear—write decision-making + communication norms.”
• “Psychological safety is low—propose concrete practices and rituals to fix it.”
• “We’re scaling fast—help us preserve what works and change what doesn’t.”
• “I’m a new leader—help me listen first and then evolve the culture.”

When NOT to use

• You need to design team meeting cadence, rituals, or operating systems (use team-rituals — this skill defines culture principles and norms, not the specific meeting structure)
• You need engineering-specific practices like code review norms, on-call culture, or incident response culture (use engineering-culture)
• You need a full org restructure, reporting lines, or span-of-control redesign (use organizational-design)
• You need to improve your 1:1 practice or manager-report relationship (use running-effective-1-1s)
• You need an HR/legal investigation, harassment response, or policy/compliance guidance (involve HR/legal)
• You need to design a full org restructure, comp bands, or performance management system
• You need to run user/customer research (use conducting-user-interviews) or design a full survey instrument (use designing-surveys)

Inputs

Minimum required

• Team context: function, size, seniority mix, reporting line, stage (startup/scale/enterprise)
• Working model: remote/hybrid/in-office; time zones; any planned org changes
• Current symptoms with 2–5 examples (e.g., slow decisions, blame, low ownership, stagnation)
• Desired outcomes: what should be more true in 4–12 weeks?
• Constraints: timeline, leadership support, meeting/time budget, “non-negotiables”
• Existing artifacts (if any): values, handbook, onboarding, meeting cadences, principles
• Confidentiality constraints (avoid names/PII; use anonymized examples)