"Collaboration" Is Bullshit
This provocative piece boldly claims that "collaboration" as an organizational ideology is often counterproductive, arguing that true progress stems from individual ownership and the focused efforts of small, high-agency teams. It strikes a nerve with many who feel modern corporate "collaboration" often leads to diffused responsibility and endless, unproductive meetings. The article and its strong stance ignited a lively debate among developers about team dynamics, effective work structures, and the pitfalls of process for process's sake.
The Lowdown
The article, titled "Collaboration" Is Bullshit, gained significant attention on Hacker News, though its full content was largely inaccessible due to a security verification page. Based on extensive discussion in the comments, the piece provocatively challenged the modern corporate emphasis on collaboration. It argued that true productivity and high-quality work are achieved through individual ownership and the focused efforts of small, high-agency teams, rather than through enforced, ideological 'collaboration'. The author's core arguments, as inferred from the commentary, included:
- "Collaboration-as-ideology" has made ownership and responsibility feel antisocial, despite ownership being crucial for task completion.
- Complex and high-quality work is typically performed by individuals or very small groups with clear authority and accountability.
- The "collaboration industry" is criticized for obscuring this reality.
- The piece apparently drew an analogy, later debated, between unproductive team members and the reported historical observation that a large percentage of soldiers did not fire their weapons in combat.
Ultimately, the author appears to advocate for structures that empower individuals and small teams with clear responsibilities, suggesting that current collaboration trends often mask organizational inefficiencies and a lack of tangible output.
The Gossip
Corporate Collaboration: Conundrums and Criticisms
Many commenters resonate with the author's critique, distinguishing between genuine, effective collaboration as a support mechanism and its perversion into an ideology that stifles individual ownership. They frequently observe that corporations often misapply "collaboration" to mask deeper organizational dysfunctions, leading to excessive meetings and diffused responsibility rather than productivity. Anecdotes highlight frustrating experiences with imposed Agile frameworks, "visibility theater" from management, and incompetent colleagues who dilute accountability.
Debunking the Dissenting Doers and Distributing the Work
A significant portion of the discussion focuses on the article's apparent use of the WWII soldier analogy, specifically regarding the claim that 80% refused to fire their weapons. Commenters quickly debunk this, providing academic sources and detailed historical context, noting training improvements that changed combat firing rates. This leads to a broader discussion on the "20% do all the work" phenomenon (e.g., Price's Law), with some arguing it's a symptom of organizational failure to structure teams effectively, leading to communication overload, rather than an inherent flaw in the 80%.
Teamwork's Tenacity and Practical Trade-offs
While acknowledging the frustrations of poorly implemented "collaboration," many commenters argue strongly for the necessity and benefits of genuine teamwork for complex projects. They contend that large-scale achievements like the Linux kernel or space programs require coordinated efforts beyond individual contributions. The discussion highlights the trade-offs between individual ownership and collaborative resilience (e.g., against personnel turnover) and the importance of well-managed teams, clear communication, and defined problem-solving for successful project delivery.