Collaboration Sucks

PostHog says skip the meetings and just ship—cue comment chaos

TLDR: PostHog argues meetings slow teams and says one “driver” should ship first and ask for feedback later. Comments erupted: some want tiny decision circles, others insist collaboration is a skill, with warnings about manager flybys—making this a big culture clash over speed versus quality.

PostHog dropped a bomb with “Collaboration Sucks,” arguing teams move faster when a single driver makes the call, ships the thing, and asks for feedback later. Fewer meetings, fewer “let’s discuss” Slack messages, more shipping—got it. But the community? Absolutely split down the middle, and the drama is delicious.

On Team Less Talk, ssalmon74 pitched “Gravitational Pull,” a tiny trio of decision-makers called the “Quantum Sync Circle,” declaring “everyone else is noise.” Fans called it the anti-meeting cleanse. Meanwhile, the opposition rolled in: bryzaguy said bad collaboration isn’t a reason to ditch it—it’s a skill, like a team sport. Cue the meme wave: “Globetrotters vs Lakers” got spammed as folks argued showy solo plays vs real team wins. mcdow went full woodworking wisdom: “Measure twice, cut once”—translation, communicate before you code.

Then came the office politics: john_moscow reminded everyone that companies don’t love lone wolves running the show, and throwaway713 roasted managers who say “it’s your call,” then swoop in later to second-guess. The crowd clowned PostHog’s count of 175 “let’s discuss” in Slack, turning it into a running gag. Whether you’re pro-speed or pro-meeting, the battle lines are set—and the comment section is on fire. Read the post at PostHog for the full sparkly ✨collaboration✨ villain arc.

Key Points

  • The article argues that excessive collaboration slows execution and reduces shipping velocity.
  • PostHog emphasizes a “driver” model with high individual ownership and minimal coordination.
  • Observed behaviors include broad, non-specific feedback requests and frequent “let’s discuss” defaults (175 mentions in Slack).
  • Recommended practices: prioritize shipping via pull requests, limit participants, assign a clear driver, and request targeted feedback.
  • Feedback is encouraged after shipping to inform subsequent iterations rather than pre-release reviews.

Hottest takes

"Everyone else is noise." — ssalmon74
"If your collaboration sucks IMHO you haven’t done enough." — bryzaguy
"Measure(communicate) twice, cut(build) once." — mcdow
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.