Team & Organization 15 guests | 33 insights

Building High-Performing Team Culture

Establish a culture of ownership, transparency, and intensity to drive long-term product success.

Includes our free 8-email course on making your product team AI-native. Unsubscribe anytime.

The Guide

5 key steps synthesized from 15 experts.

1

Audit and Articulate Cultural DNA

Analyze the founder's personality and the team's natural strengths to identify inherent cultural traits. Use these insights to codify values that are honest and applicable, ensuring each value includes a clear trade-off that guides behavior during conflict. Avoid aspirational statements that do not reflect the reality of how the team actually operates.

Featured guest perspectives
"I think really defining that in your values, and values aren't values unless there's an actual trade-off. And so we had things like optimize for the long-term. There's a clear trade-off when we optimize for the long-term, you probably give up short-term revenue."
— Patrick Campbell
"80% of the culture of a company is literally defined by the personality of the founder. Our job as operators or as leaders is to help articulate the culture that they're creating."
— Molly Graham
2

Establish Transparency and High Context

Replace centralized command structures with shared transparency by providing every team member with full access to business financials and strategic data. Use 'Context, No Control' as a guiding principle, where leadership provides the 'why' and the 'what' but empowers teams to decide the 'how.' This shifts the culture from seeking approval to acting with autonomy.

Featured guest perspectives
"We really have an approach of very radical transparency about everything. Before we went public, we actually shared every bit of information with our employees. Instead of demoralizing people, I think that this is something that gives them a sense of deep partnership."
— Daniel Lereya
"The number one thing is context, no control. That's the reason why we're always encouraging people to see themselves as a business owner."
— Ray Cao
3

Foster Safety and Vulnerability

Model vulnerability by openly admitting mistakes and sharing personal stories that move beyond surface-level professionalism. Implement 'BB Time' or similar segments in meetings where team members share what is currently difficult. Create low-stakes spaces for sharing early-stage, 'rough' work to normalize failure as part of the creative process.

Featured guest perspectives
"So we divided the team into these smaller groups for peer feedback groups and the idea is that they meet every two weeks or so, somebody brings something that's in a pretty rough draft that they want to get reviewed and then everyone's expected to give feedback. And because we've got people in there who are different leadership levels, it's a really good opportunity to model the kind of feedback that's helpful and the culture there is one of everyone lifting that person up to make their work stronger."
— Megan Cook
"“After years of research, Google discovered the secret weapon to building a great team was creating a sense of psychological safety.” — Inc"
— Lenny Rachitsky
4

Institutionalize Rituals and Shared Identity

Design unique team rituals, such as 'Kudos Boards' or 'Life Story Fridays,' that prioritize emotional connection over task management. Encourage the creation of internal memes, nicknames, and quirks to foster the extreme camaraderie needed for complex projects. Ensure remote teams maintain connection through regular in-person offsites that combine collaborative work with social play.

Featured guest perspectives
"We have this ritual called Kudos Boards inside of FigJam, where everyone will shower each other with love and just kind call out their teammates for what they've done over the last week or so."
— Mihika Kapoor
"Culture isn’t just a nice-to-have—it’s a cheat code for momentum, creativity, and execution. A product’s success depends on a team culture so strong it feels borderline religious."
— Lenny Rachitsky
"One of the other things we do is we get everyone together just like every six months. So all of the product managers get together in the same place and the idea is to have a bit of an onsite. Now we start off with just doing something fun because everybody... As you might know, Atlassian is a remote organization, so everybody works remote all the time."
— Megan Cook
5

Drive Intensity and Accountability

Actively fight the natural dilution of intensity by reminding the team that comfort is often a sign of stagnation. Shift the focus from performative hours to high-quality output and shipping velocity as the core solutions to business problems. Hold leaders accountable for maintaining these standards, prioritizing results over individual popularity.

Featured guest perspectives
"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. This employee continuing to not really do a great job at their job, you don't want to push them because you don't want to upset them. You don't want to give them difficult feedback, so you're just going to keep hoping it works out. Ultimately, that leads to the demise of your company."
— Alisa Cohn
"If you want to be in the 99th percentile in terms of outcomes, it's going to be really difficult. You got to sort of remind people that if they ever find themselves in the comfort zone at work, they are definitely making a mistake. It's supposed to be really fricking exhausting."
— Matt MacInnis
"At Ramp, our culture is velocity. It shapes every process and team ritual. It’s how we develop our people. It’s our solution to nearly every problem."
— Lenny Rachitsky

Get this guide as an AI skill for Claude Code

Includes our free 8-email course on making your product team AI-native. Unsubscribe anytime.

Install This Skill

Add this skill to Claude Code, Cursor, or any AI coding assistant that supports Agent Skills.

Quick Install (Recommended)

Install this skill directly using npx:

npx skills add RefoundAI/lenny-skills --skill team-culture

Or install all 76 skills:

npx skills add RefoundAI/lenny-skills
View on GitHub →
Manual Installation
1

Download the skill

Download Skill (.zip)
2

Add to your project

Create a folder in your project root and add the skill file:

.claude/skills/team-culture/SKILL.md
3

Start using it

Claude will automatically detect and use the skill when relevant. You can also invoke it directly:

Help me with building high-performing team culture

Guest Perspectives

Deep dive into what 14 podcast guests shared about building high-performing team culture.

Alisa Cohn 1 quote
Listen to episode →
"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. This employee continuing to not really do a great job at their job, you don't want to push them because you don't want to upset them. You don't want to give them difficult feedback, so you're just going to keep hoping it works out. Ultimately, that leads to the demise of your company."
Tactical:
  • Shift your leadership priority from being liked to driving results and ensuring the long-term survival of the company.
  • Stop avoiding difficult feedback in the hope that performance issues will resolve themselves without intervention.
  • Identify the personal fears or weights you are attaching to difficult conversations to understand why you are avoiding them.
View all skills from Alisa Cohn →
Daniel Lereya 1 quote
Listen to episode →
"We really have an approach of very radical transparency about everything. Before we went public, we actually shared every bit of information with our employees. Instead of demoralizing people, I think that this is something that gives them a sense of deep partnership."
Tactical:
  • Share core business financials and challenges openly with all employees to build a sense of ownership.
  • Distribute decision-making context across the entire company instead of relying on a few centralized 'brains.'
  • Leverage transparency to engage the collective intelligence of the organization during difficult transitions.
View all skills from Daniel Lereya →
Jag Duggal 1 quote
Listen to episode →
"When there are hard decisions to be made, we bias in favor of the customer. The customer's love, will they want to tell their friends, and neighbors, and family about it? And so I think that's the heart of it."
Tactical:
  • Establish 'fanatical customer love' as the primary organizational value.
  • Bias decision-making in favor of the user's emotional experience over short-term gains.
  • Identify and solve a deep, emotionally-held pain point in the market that incumbents ignore.
View all skills from Jag Duggal →
Jason Shah 1 quote
Listen to episode →
"So, in my opinion, I think that the only way to maintain moral is to make progress. I think that no speech, no sort of extrinsic motivators like we're going to give everybody some free crypto to keep motivated about it or something like that really works. I think people get really excited when they see progress."
Tactical:
  • Focus the team on making visible product progress every day.
  • Avoid relying on extrinsic motivators to boost spirits during market cycles.
  • Prioritize shipping features and meeting customer needs even when metrics are down.
View all skills from Jason Shah →
Jeremy Henrickson 1 quote
Listen to episode →
"I think that's the other, maybe the key point here that everyone is exposed senior leadership, yes, we have a management structure because you have to, but that management structure does not interfere with the ability of anyone anywhere in the organization to look at what's actually happening. And that happens very directly."
Tactical:
  • Remove management barriers that prevent senior leadership from looking directly at what is happening at the ground level.
  • Increase the tempo of reviews by having leaders comment directly on the latest designs and progress.
  • Use one-page views of new initiatives to trigger immediate decisions to build.
View all skills from Jeremy Henrickson →
Jess Lachs 1 quote
Listen to episode →
"Yes, you are a data scientist, but your goal is to figure out what's happening. And if that means that you're going to pick up the phone and call customers, then that is what you're going to do to roll up your sleeves."
Tactical:
  • Encourage data professionals to do 'whatever it takes' to solve a problem, even if it falls outside their typical job description.
  • Incorporate direct customer feedback and operational experience into data deep dives to build empathy and context.
  • Reward team members who investigate the 'why' behind the numbers through manual or non-technical exploration.
View all skills from Jess Lachs →
Katie Dill 1 quote
Listen to episode →
"Regardless of each individual saying, what was very clear was that the missing piece, the theme that was across all of that, is that I hadn't earned their trust. So whether how right or how wrong what I was doing was, is the key piece is that I wasn't bringing the team along with me."
Tactical:
  • Listen to harsh feedback interventions silently and without defense to truly hear the team's perspective.
  • Identify the underlying emotional theme of feedback—such as a lack of trust—rather than getting bogged down in individual technical complaints.
  • Shift from inflicting change on people to involving them in the process by listening to their individual motivations first.
View all skills from Katie Dill →
Laura Modi 2 quotes
Listen to episode →
"The most obvious kind of cliched one is culture. It is bread and butter to everything you do, from the people you hire to how you build the right mindset to just keeping the energy. I mean, energy at Airbnb was the currency. It was like, unless you didn't have that energy, nothing was happening."
Tactical:
  • Incorporate personal check-ins into professional meetings to build trust.
  • Focus on maintaining high team energy as a core operational metric.
  • Foster deep personal relationships cross-functionally to create a 'second family' work culture.
"I now reflect back on just how powerful our storytelling was at Airbnb to get people pumped up. I mean, even for some of the smallest features that we would build, Lenny, they would kick off with the most powerful storytelling. I mean, we were changing lives."
Tactical:
  • Kick off projects with a narrative about the human impact of the work.
  • Connect routine technical tasks to a larger vision of changing users' lives.
  • Ensure storytelling is felt throughout the entire organization, not just at the leadership level.
View all skills from Laura Modi →
Matt MacInnis 2 quotes
Listen to episode →
"If you want to be in the 99th percentile in terms of outcomes, it's going to be really difficult. You got to sort of remind people that if they ever find themselves in the comfort zone at work, they are definitely making a mistake. It's supposed to be really fricking exhausting."
Tactical:
  • Remind the team that staying in the comfort zone is a mistake.
  • Explain that exhaustion and high pressure are necessary precursors to 99th-percentile outcomes.
  • Leverage periods of high company growth as the justification to ask for the team's maximum effort.
"Teams will always optimize for local comfort over company outcomes. The purest form of ambition and most intense source of energy in the business is the founder CEO. Every next concentric circle of management beyond the founder CEO has the potential to be an order of magnitude drop off in intensity."
Tactical:
  • Actively preserve intensity at every level of the management hierarchy to prevent drop-offs.
  • Identify and correct teams that prioritize local convenience over broader company goals.
  • Maintain a "red line" engine speed for the collective team to ensure competitors cannot find gaps to exploit.
View all skills from Matt MacInnis →
Megan Cook 3 quotes
Listen to episode →
"So we divided the team into these smaller groups for peer feedback groups and the idea is that they meet every two weeks or so, somebody brings something that's in a pretty rough draft that they want to get reviewed and then everyone's expected to give feedback. And because we've got people in there who are different leadership levels, it's a really good opportunity to model the kind of feedback that's helpful and the culture there is one of everyone lifting that person up to make their work stronger."
Tactical:
  • Split large product teams into small groups that meet every two weeks for peer feedback.
  • Normalize sharing early-stage, rough drafts to catch direction issues before significant work is wasted.
  • Have senior leaders model vulnerability by receiving and giving feedback alongside junior members.
"One of the other things we do is we get everyone together just like every six months. So all of the product managers get together in the same place and the idea is to have a bit of an onsite. Now we start off with just doing something fun because everybody... As you might know, Atlassian is a remote organization, so everybody works remote all the time."
Tactical:
  • Bring remote team members together for in-person onsites every six months.
  • Begin team gatherings with social "play" or fun activities to help people build rapport and warm up.
  • Use face-to-face time for workshops where team members teach each other different elements of their craft.
"I think often when there's difficult conversations, or those conflicts come up, you can put them off until they become much bigger. Or if somebody is conflict adverse, they can try to avoid having it at all. But by having a specific slot of time in your week for something like that, then you're sort of in that mindset."
Tactical:
  • Schedule a recurring 30-minute weekly meeting, such as a "Fight Club," for product, engineering, and design leads.
  • Address disagreements early to prevent small frictions from escalating into major organizational blockers.
  • Enter conflict-resolution meetings with the explicit mindset of solving hard, shared problems together.
View all skills from Megan Cook →
Mihika Kapoor 1 quote
Listen to episode →
"We have this ritual called Kudos Boards inside of FigJam, where everyone will shower each other with love and just kind call out their teammates for what they've done over the last week or so."
Tactical:
  • Implement 'Kudos Boards' where team members publicly celebrate each other's weekly contributions.
  • Utilize internal hackathons to provide the 'breathing space' needed to be wildly ambitious.
  • Shift meetings from one-way presentations to democratic sessions where everyone contributes via sticky notes or comments.
View all skills from Mihika Kapoor →
Molly Graham 1 quote
Listen to episode →
"80% of the culture of a company is literally defined by the personality of the founder. Our job as operators or as leaders is to help articulate the culture that they're creating."
Tactical:
  • Analyze the founder's natural strengths and weaknesses to identify the company's inherent cultural traits.
  • Focus cultural initiatives on articulating and documenting the values the founder already lives.
  • Act as a translator for the founder's personality to help new hires navigate the organization's unique environment.
View all skills from Molly Graham →
Patrick Campbell 1 quote
Listen to episode →
"I think really defining that in your values, and values aren't values unless there's an actual trade-off. And so we had things like optimize for the long-term. There's a clear trade-off when we optimize for the long-term, you probably give up short-term revenue."
Tactical:
  • Identify a clear trade-off for every core value you define.
  • Codify specific behavioral expectations, such as the 'most charitable interpretation' of conflict.
  • Defend your values by helping those who cannot adapt to the company's behavioral standards find other jobs.
View all skills from Patrick Campbell →
Ray Cao 1 quote
Listen to episode →
"The number one thing is context, no control. That's the reason why we're always encouraging people to see themselves as a business owner."
Tactical:
  • Provide teams with full transparency and data context so they can make decisions without needing specific top-down instructions.
  • Encourage a 'Day One' startup mentality to ensure the organization remains hungry for growth as it scales.
  • Empower individuals to see the 'full picture' across departments to solve complex organizational puzzles.
View all skills from Ray Cao →