building-team-culture
This skill helps users develop and strengthen team culture by drawing on frameworks from 138 product leaders at companies ranging from startups to Google and Airbnb. Use it when articulating team values, establishing psychological safety, onboarding new team members, managing cultural transitions, or creating decision-making norms for distributed teams. The skill emphasizes articulating existing culture rather than creating new values, designing culture as a decentralized decision guide for when leadership isn't present, and using coaching-based approaches to develop people and reinforce cultural attributes through lived examples.
git clone --depth 1 https://github.com/RefoundAI/lenny-skills /tmp/building-team-culture && cp -r /tmp/building-team-culture/skills/building-team-culture ~/.claude/skills/building-team-cultureSKILL.md
# Building Team Culture Help the user build and sustain high-performing team culture using frameworks from 138 product leaders who have shaped cultures at companies from startups to Google and Airbnb. ## How to Help When the user asks for help with team culture: 1. **Understand the context** - Ask about team size, stage, remote vs in-person, and what triggered the culture question 2. **Diagnose the current state** - Identify whether the issue is definition, communication, or enforcement of culture 3. **Focus on articulation over creation** - Help them describe what's already working rather than inventing new values 4. **Design for decentralized decisions** - Ensure culture can guide behavior when leadership isn't present ## Core Principles ### Articulate, don't create Dharmesh Shah: "Culture actually already exists... what I'm really trying to do is kind of describe the culture that's there. It's not creating culture, it's articulating the culture." Document the attributes of people who make others happy and successful. ### Culture is for when the boss isn't around Chip Conley: "Culture is what happens around here when the boss is not around. The more distributed a company, the more culture is important." Use culture as a decentralized decision-making guide, especially for remote teams. ### Replace management with coaching Cam Adams: "We don't really have managers, but everyone at Canva has a coach. They're constantly working with you to look at your skills, but also when it might be time to move on to the next level." Coaches focus on skill development and career trajectory, not task oversight. ### Earn trust before inflicting change Katie Dill: "It can be hard to bring feedback forward like that. So it was an extremely valuable learning experience. I took from that to then immediately shift how I was operating." Prioritize listening over "coming in swinging" when joining a new team. ### Challenge sacred cows to cure stagnation Kayvon Beykpour: "We wanted to change the lack of ambition, the lack of creativity, the lack of customers feeling that the product had changed at all." Identify and challenge cultural artifacts that prevent product evolution. ### Use culture as a talent magnet Chip Conley: Culture attracts the right people and repels the wrong ones. Prioritize in-person gatherings for remote teams to reinforce cultural cues that can't be transmitted digitally. ### Make culture a living document Dharmesh Shah: Create a "Culture Code" that acts as an operating system for the company. Update it as you learn what actually works versus what sounds good. ### Psychological safety enables feedback Katie Dill: Building trust through active listening and empathy is the foundation for organizational change. Teams won't give honest feedback if they don't feel safe. ## Questions to Help Users - "What behaviors do you see in your highest performers that you wish everyone exhibited?" - "When has someone made a decision you disagreed with but couldn't fault their reasoning?" - "What happens when someone fails publicly on your team?" - "How do new hires learn 'how things work around here'?" - "What decision would be made differently if you weren't in the room?" ## Common Mistakes to Flag - **Inventing aspirational values** - Culture documents should describe what already works, not what you wish were true - **Values without behaviors** - "We value innovation" is meaningless without specific examples of what that looks like in practice - **Over-engineering for small teams** - Startups need shared understanding, not formal culture playbooks - **Ignoring the distributed challenge** - Remote teams need explicit cultural transmission that co-located teams get implicitly - **Leadership-culture mismatch** - Functional orgs require active leadership tiebreaking; if the CEO is hands-off, culture can't fill the gap ## Deep Dive For all 212 insights from 138 guests, see `references/guest-insights.md` ## Related Skills - Writing Job Descriptions - Conducting Interviews - Evaluating Candidates - Onboarding New Hires
Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality.
Help users define AI product strategy. Use when someone is building an AI product, deciding where to apply AI in their product, planning an AI roadmap, evaluating build vs buy for AI capabilities, or figuring out how to integrate AI into existing products.
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.
Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.
Help users build effective AI applications. Use when someone is building with LLMs, writing prompts, designing AI features, implementing RAG, creating agents, running evals, or trying to improve AI output quality.