refoundai/team-culture
Help users design and maintain a high-performing culture by balancing radical transparency, psychological safety, and a relentless focus on customer delight.
npx skills add https://github.com/RefoundAI/lenny-skills --skill team-culture
Establish a culture of ownership, transparency, and intensity to drive long-term product success.
Help the user with building high-performing team culture using insights from 26 guests and posts across Lenny's Podcast and Newsletter.
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. 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."
High-performing leaders must prioritize organizational results and performance standards over the desire to be liked by every individual. Avoiding difficult feedback to preserve popularity ultimately jeopardizes the long-term survival of the company.
Daniel Lereya: "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."
Sharing core business financials and strategy creates a sense of deep partnership between leadership and employees. When everyone has full context, they are empowered to solve problems independently as owners.
Jag Duggal: "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."
High-growth cultures are fueled by a commitment to customer delight that outweighs short-term operational compromises. Leaders should bias decision-making in favor of the user emotional experience over local convenience.
Megan Cook: "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."
To move fast, teams need low-stakes environments where they can share rough, early-stage work. Normalizing the presentation of 'unfinished' drafts helps catch directional errors early and builds collective confidence.
Matt MacInnis: "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."
Top-tier success requires a culture that views staying in the comfort zone as a strategic mistake. Exhaustion and high pressure are often necessary precursors to 99th-percentile progress.
Patrick Campbell: "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."
Authentic values must involve clear trade-offs where one positive behavior is prioritized over another. This makes the values useful for decision-making rather than just being decorative plaques.
See references/artifacts.md for the full list with details.
For all 47 sourced insights from 26 guests, see references/guest-insights.md
Take refoundai/team-culture from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.