
Building Team Culture
- 1.6k installs
- 1.2k repo stars
- Updated July 16, 2026
- refoundai/lenny-skills
Lenny skill for team culture articulation.
About
The building-team-culture skill helps leaders sustain culture using insights from 138 product leaders. It diagnoses definition, communication, or enforcement gaps, articulating what works instead of inventing aspirational values. Principles include articulate-don't-create, culture guiding decentralized decisions, coaching over management, earning trust before change, challenging sacred cows, and culture as talent magnet. Agents ask about team size, remote context, failure responses, and flag values without behaviors. Use when defining team values, onboarding, navigating cultural change, or building distributed norms with psychological safety enabling honest feedback across startups and large tech companies. Articulate existing culture not aspirational slogans. Culture guides decisions when leadership absent. Coaching over task oversight. Flags values without behaviors. 138 leader insights with hiring-related skills. Lenny skill for team culture articulation. User asks about team culture or psychological safety.
- Articulate existing culture not aspirational slogans.
- Culture guides decisions when leadership absent.
- Coaching over task oversight.
- Flags values without behaviors.
- 138 leader insights with hiring-related skills.
Building Team Culture by the numbers
- 1,555 all-time installs (skills.sh)
- Ranked #362 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
building-team-culture capabilities & compatibility
- Capabilities
- culture diagnosis · remote norms
- Use cases
- planning
npx skills add https://github.com/refoundai/lenny-skills --skill building-team-cultureAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.6k |
|---|---|
| repo stars | ★ 1.2k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 16, 2026 |
| Repository | refoundai/lenny-skills ↗ |
How define culture for distributed teams?
Coach leaders to articulate existing team culture, design decentralized norms, and build psychological safety using Lenny frameworks.
Who is it for?
Leaders defining values or remote norms.
Skip if: Sprint process design.
When should I use this skill?
User asks about team culture or psychological safety.
What you get
Behavior-linked cultural principles.
By the numbers
- Indexes insights from 138 Lenny's Podcast guests
- Contains 212 tagged team-culture mentions across guest entries
Files
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
Related skills
FAQ
Invent new values?
No. Articulate behaviors already working.
Remote importance?
Culture guides decisions when boss is not around.
Related skills?
Job Descriptions, Interviews, Onboarding New Hires.
Is Building Team Culture safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.