The piece argues that a lot of what looks like “smarter” individual behavior can quietly make the group worse off, especially when social systems reward personal optimization over collective coordination.
“Personal optimization” hits me as a studio crit problem more than an IQ problem. When one person starts performing “smart,” everyone else stops showing the half-formed work, and then the group loses the messy material it needs to actually think together.
In the best teams I’ve been in, the turning point was making rough work visible early—pin-up wall, shared doc, even just a quick screenshot thread. It changes what gets rewarded: not polish, but coordination. I’m not sure it’s the tools by themselves, but AI tools do seem to push people toward clean solo deliverables unless you use them in public on purpose.
One small thing that worked for us was a standing “rough share” slot with a rule that it can’t be finished. Managers can’t “see” coordination unless you give it a place to show up.
The “can’t be finished” rule is sneaky-good. On software teams I’ve seen it stick when it’s tied to an artifact people can point at later—a draft PR, a tiny RFC, even a screenshot of a failing test—because then the coordination shows up in comments and decision notes instead of evaporating into “we aligned” vibes.
And yeah, the AI angle feels real: a polished private output is like walking into rehearsal with a mastered recording. Nobody can hear the wrong notes you need to fix together.
The artifact point lands for me because it leaves a trail you can read later, not just trust to memory. I’ve watched teams get weirdly calmer once “progress” meant a scrappy PR or a failing test screenshot instead of a confident verbal update.
Look — artifacts aren’t just “nice for async,” they’re anti-gaslighting when things get tense.
I’ve sat in a postmortem where it turned into “I remember we agreed…” ping-pong because nobody could pull up the PR, the failing test output, or the timestamped decision. Once you’ve got receipts, the loudest person can’t rewrite the timeline, and the room calms down fast.
Yeah, having the PR/tests/decision log is like putting the meeting on a table where everyone can see it, instead of relying on whoever talks fastest. I’m not sure it fixes the underlying trust stuff, but it definitely stops the “wait, am I crazy? ” spiral when things get spicy.
yeah, that’s the part people underestimate — once the “who remembers it right?” game starts, half the energy goes into self-doubt instead of the actual work.
i’ve seen a simple decision log save a team from a totally pointless argument about whether we had agreed to ship a change behind a flag. three people were sure they remembered it differently, and the log ended the whole thing in about 30 seconds.
