Building Team Culture
Solo builders who are hiring or co-founding use this Lenny-guest research digest to set decision rights, feedback norms, and diversity habits before team friction costs shipping speed.
Overview
Building Team Culture is an agent skill most often used in Operate (also Validate, Build) that surfaces Lenny Podcast guest insights so solo builders can design team norms, decision rights, and feedback habits before cul
Install
npx skills add https://github.com/refoundai/lenny-skills --skill building-team-cultureWhat is this skill?
- 212 mentions across 138 Lenny podcast guests distilled into actionable culture tactics
- Co-founder playbook: complementary domains, clear decision rights, attack the problem not the person
- Diversity framed as business speed—teams that mirror users reduce external research loops
- Regular relationship check-ins to separate personal dynamics from product conflict
- Quotable guest insights with timestamps for deeper listening
- 138 guests
Adoption & trust: 1.3k installs on skills.sh; 1k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You are adding co-founders or early hires but lack a concise, battle-tested playbook for decision rights, conflict, and diversity that fits a tiny team.
Who is it for?
First hires, co-founder agreements, and weekly leadership rituals when you want podcast-grade culture tactics without reading hundreds of episodes.
Skip if: Solo builders with no plans to collaborate who only need coding or growth skills—skip until people are in the loop.
When should I use this skill?
You are hiring, co-founding, or stabilizing team dynamics and want condensed Lenny guest culture tactics.
What do I get? / Deliverables
You leave with guest-backed tactics and check-in rituals you can paste into a team handbook or founder agreement and revisit as you iterate the working relationship.
- Culture insight summaries with tactical bullet lists
- Timestamped quotes for deeper podcast follow-up
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Culture systems matter most once you are running a product with other humans—operate is the canonical shelf for sustained team execution, even though insights apply earlier when you first add collaborators. Iterate fits ongoing refinement of how you work together (check-ins, conflict norms, hiring bar) rather than one-off launch events.
Where it fits
Compare co-founder skill sets and assign decision rights before you commit to building together.
Draft team norms for feedback and domain ownership before the second engineer merges code daily.
Run a quarterly ritual using guest tactics on respectful interpretation and relationship check-ins.
How it compares
Use as a curated research digest instead of random leadership blog posts or generic HR templates with no operator context.
Common Questions / FAQ
Who is building-team-culture for?
Indie founders and small-team leads who want Lenny-style operator advice on partnerships, feedback, and diversity without manually mining the archive.
When should I use building-team-culture?
During Validate when scoping a co-founder fit, in Build when defining roles for early engineers, and in Operate when instituting check-ins and conflict norms as the team grows.
Is building-team-culture safe to install?
It is narrative research content—review the Security Audits panel on this page before installing any skill from the same repo and treat excerpts as editorial input, not legal HR advice.
SKILL.md
READMESKILL.md - Building Team Culture
# Building Team Culture - All Guest Insights *138 guests, 212 mentions* --- ## Ada Chen Rekhi *Ada Chen Rekhi* > "We had a very, very good set of complimentary domains and skillsets, so we had really clear decision making rights... the ability to be really truth seeking and take the most respectful interpretation when you're giving feedback to focus on trying to get to a smart good outcome that benefits the business." **Insight:** Successful high-stakes partnerships (like co-founders) require clear domain separation and a commitment to 'most respectful interpretation' during conflict. **Tactical advice:** - Establish clear decision-making rights based on complementary skill sets. - Attack the problem, not the person, during constructive conflict. - Schedule regular check-ins to explicitly discuss how the working relationship is affecting personal dynamics. *Timestamp: 01:09:08* ## Adriel Frederick *Adriel Frederick* > "You got to have your teams look like the world, it just makes you so much faster. It's not perfect... But it helps a lot. To your second point about diversity and how to foster it... When you recognize that you get business value from it, then it all of a sudden becomes something that you look out for and you take care of." **Insight:** Diversity is a business efficiency driver that allows teams to internalize global user perspectives and make faster product decisions without constant external research. **Tactical advice:** - Recruit teams that reflect the global diversity of your user base to speed up decision-making. - Focus on retention of diverse talent by creating an environment that rewards their unique cultural perspectives. *Timestamp: 00:16:51* ## Alexander Embiricos *Alexander Embiricos* > "OpenAI is truly, truly bottoms up... because we don't exactly know what capabilities will even come up soon and we don't know what's going to work technically... it's much more important for us to be very humble and learn a lot more empirically and just try things quickly. And the org is set up in that way to be incredibly bottoms up." **Insight:** In high-uncertainty technology environments, a bottoms-up, empirical culture is more effective than rigid top-down planning. **Tactical advice:** - Hire for high individual drive and autonomy to support a bottoms-up structure - Prioritize quick empirical learning over long-term roadmaps when technical capabilities are evolving rapidly *Timestamp: 00:08:45* ## Adam Grenier *Adam Grenier* > "If you are managing a team and you want to sharpen the skills, make it a team goal, or have accountability and just say, "Hey guys, I know that I've been pushing back on things lately. I want to really try to embrace and grow off of ideas better, hold me accountable, call me out and be like, 'Adam, "Yes, and..." this please.'"" **Insight:** Building a culture of openness requires leaders to be public about their own development goals and give the team permission to hold them accountable. **Tactical advice:** - Publicly state your intention to improve specific soft skills to your team - Give team members explicit permission to call out when you fall back into old habits *Timestamp: 00:12:32* ## Alisa Cohn *Alisa Cohn* > "They're trying now to be the leader who everyone loves, but what really needs to happen very often is, we need to drive towards results... High engagement workforce is great. I think what that comes from is winning culture, which means we're set up for success. We've got the structure for success, we have the culture for success, everyone understands their role, they know the impact of their role." **Insight:** A healthy culture is built on results and clarity, not just employee happiness or perks. **Tactical advice:** - Prioritize driving results over being liked - Codify culture around how work gets done (e.g., 'measure twice, cut once') rather than social rituals - Ensure every employee understands the impact of their specific role *Time