We scan new podcasts and send you the top 5 insights daily.
The "brains in jars" mental model treats developers as isolated, interchangeable units, ignoring collaboration and social dynamics. This simplistic view leads to burnout, low productivity, and an inability to solve complex problems because it devalues essential work like mentoring and learning out loud.
Classifying people into critical "barrels" and dispensable "ammunition" is a dehumanizing relic of Taylorism. Instead of sorting talent, leaders should remove systemic obstacles that prevent more people from developing into end-to-end drivers.
Building a team is a complex system that changes with every interaction; it can't be solved with fixed instructions. Unlike a complicated but predictable task like building a Ferrari, leading a team requires constant experimentation, sensing, and responding to an ever-evolving dynamic.
Focusing on individual performance metrics can be counterproductive. As seen in the "super chicken" experiment, top individual performers often succeed by suppressing others. This lowers team collaboration and harms long-term group output, which can be up to 160% more productive than a group of siloed high-achievers.
Companies fail at collaboration due to behavioral issues, not a shortage of good ideas. When teams operate in silos, believing "I know better," and are not open to challenging themselves or embracing "crazy ideas," progress stalls. Breaking down these habitual, protective behaviors is essential for creating a fluid and truly innovative environment.
Leaders who always have the right answer often create an environment where others feel devalued and excluded. The blocker's real cost is not the accuracy of their ideas, but the damage done to team connection and collaborative decision-making, which prevents the team from arriving at the best solutions together.
Critical thinking is a team culture, not just an individual skill. When a leader stops demonstrating and demanding rigorous thought, they don't just stunt their own growth. They create an environment where the entire team's ability to avoid expensive mistakes atrophies.
Many leaders who suppress team intelligence don't do so maliciously. Well-intentioned behaviors like being an 'idea fountain' or a 'rescuer' can inadvertently signal a lack of trust and capability, diminishing others' contributions and getting less than half of their team's available intelligence.
Better products are a byproduct of a better team environment. A leader's primary job is not to work on the product, but to cultivate the people and the system they work in—improving their thinking, decision-making, and collaboration.
A leader's role is to teach their team, not just provide answers. Even if you can build a solution faster (like an AI agent), doing it for your team deprives them of a critical learning opportunity. The best approach is demonstrating what's possible, then empowering them to build it themselves.
Leaders default to adding more—more features, more goals, more meetings. This 'addition bias' creates friction and exhausts teams, leading one employee to say she only has 'scraps of myself for my family.' The solution is for leaders to act as 'editors-in-chief,' relentlessly subtracting tasks and complexity.