build-team-culture

name	Build Team Culture
description	Surface and articulate your team's actual culture rather than inventing aspirational values. What it does: transforms observed behaviors, meeting patterns, and peer feedback into documented cultural norms. When to use it: during onboarding refreshes, after team scaling events, when leadership senses a culture gap, or when preparing for new hires. Trigger on: culture, values, beliefs, team identity, distributed teams, trust, onboarding, culture mismatch, sacred cows.
dependencies	[]
connectors	[{"name":"Slack","reason":"Analyzes conversation tone, norms, and informal rituals; identifies what people actually prioritize"},{"name":"Google Calendar","reason":"Maps team rhythm—meeting types, frequency, who convenes—as behavioral culture signals"},{"name":"Notion","reason":"Captures documented practices, informal handbooks, and emerging team standards"},{"name":"GitHub","reason":"Reveals code review culture, commit cadence, and collaboration norms"},{"name":"Google Drive","reason":"Surfaces shared documents, templates, and decision frameworks that shape behavior"}]
author	Harmony
version	1.0.0
icon	sparkles
cover
screenshots	[]
category	Operations

Purpose

Culture isn't a mission statement on the wall—it's what happens when the boss isn't around. This skill surfaces the actual culture your team lives, reflects it back to them, and helps you articulate it so new hires, leaders, and remote employees can embody it.

Rather than inventing aspirational values that contradict how your team actually operates, Build Team Culture excavates existing norms from meeting data, transcripts, Slack patterns, and peer observations. It then structures those insights into a living document that names your sacred practices, psychological safety norms, and decision-making culture.

The skill is especially critical for distributed teams, where culture isn't absorbed by osmosis, and for leadership teams that may have drifted from their stated values. It's also your defence against the most common culture mistake: leadership imposing values that the team doesn't practice.

When to Use

• After scaling events: New team members join and you realize your informal culture hasn't been made explicit; align on what's actually valued before it dilutes.
• Distributed team onboarding: Remote hires can't absorb culture through hallway conversations; you need documented norms and rituals.
• Leadership transition: New exec or manager arrives; surface how decisions are made, how feedback flows, and what "good" looks like on this team.
• Culture mismatch signals: You hear "that's not how we do things here" in different ways; reveals hidden norms that need naming or challenging.
• Preparing for a funding event or acquisition: Investors and new leadership want to understand (and potentially shift) your team dynamics.
• Recovering from trust breach: After conflict or misalignment, document the psychological safety norms you're rebuilding.
• Quarterly culture audit: Revisit as team evolves; culture is a living document, not a poster.

Instructions

1. Schedule a culture listening session (60–90 min, leadership + 3–5 senior individual contributors).

   • Frame as "articulating who we are, not who we think we should be."
   • Prepare leaders: this may surface unflattering truths; listen without defending.

2. Map behavioral patterns from available sources.

   • If Slack is connected: what types of messages get reactions? What topics get amplified? What tone dominates?
   • If calendar is connected: what meetings are sacred? Who convenes decisions? What's the ratio of sync to async?
   • If GitHub/code is available: what's the pace of merges? How thorough are reviews? What do code comments reveal about values?