Teams often hurt more than help; productivity drops when groups grow beyond five, roles blur, and social dynamics dominate, so keep teams tiny, focus on A-players, and inject a healthy contrarian to avoid groupthink.
The article argues that most of the loss in team productivity comes from assembling groups that aren't needed. Research shows a five-person ceiling before overhead explodes, and even small teams waste time on emails, meetings, and logistics instead of actual work. The author urges leaders to ask the unasked question: do we really need a team, and if we do, keep it as small as possible.
Hackman's 60/30/10 rule underpins the rest of the advice: 60 percent of success is who you put on the team, 30 percent is clear role assignment, and only 10 percent is leadership. The piece stresses hiring or promoting A-players, clarifying responsibilities, and accepting that most teams will never hit the ideal composition. It also warns that the average worker's output can drop 40 percent once they become part of a group.
Interaction matters as much as talent. Studies cited show high-performing teams have roughly five positive interactions for every negative one, and the weakest link determines overall trust. The author flips conventional wisdom by recommending a deliberately disagreeable team member - not a jerk, but someone who will challenge consensus and keep ideas from going stale.
Leadership is framed as creating an environment of safety, vulnerability, and purpose. Safety means everyone gets a chance to speak and feel heard; vulnerability encourages honest admission of mistakes, a practice even Navy SEALs use after missions; purpose ties the team to a clear story of who they are and what they stand for. These three pillars let the team function with less friction and more momentum.
The final takeaway is practical: question the need for a team, keep it tiny, fill it with high performers, assign clear roles, tolerate a contrarian voice, and as a leader, nurture safety, openness, and a shared purpose. Applying these steps can turn a bureaucratic assemblage into a high-output, motivated unit that actually enjoys working together.
Check out the full stdlib collection for more frameworks, templates, and guides to accelerate your technical leadership journey.