June 25, 2026
Trust issues, but make it corporate
Shall We Play a Coordination Game?
When the safety team and builders stop fighting, everyone might finally keep the harvest
TLDR: The article argues that workplace safety teams should help companies move faster and smarter, not just block decisions. Commenters loved the idea but fought over the real culprit: bad teamwork, or bosses rewarding speed and blaming everyone else when things break.
A thoughtful essay about workplace trust somehow turned into a full-on comments-section therapy session about one of tech’s oldest feuds: the people trying to keep systems safe versus the people trying to ship things fast. The writer’s big idea is simple enough for non-experts: safety at work shouldn’t exist just to say “no.” It should help the company actually get things done. In this case, that means the safety team and the software-building team need to cooperate instead of treating each other like rival kingdoms in a bad marriage.
And wow, readers had feelings. The loudest camp basically yelled, “Finally, someone said it: safety that blocks everything is useless!” Another faction fired right back that this is sweet in theory, but in real life one side gets blamed when things go wrong while the other gets rewarded for moving fast — so of course trust collapses. That sparked the juiciest argument: is this a teamwork problem, or a management problem wearing a teamwork costume?
The jokes were flying too. Commenters compared the relationship to divorced parents, airport security, and two farmers refusing to share a fence until both crops die. Others joked that every office game theory post eventually becomes “Prisoner’s Dilemma, but make it quarterly planning.” The vibe was half serious strategy talk, half group roast, with many readers agreeing on one painfully relatable truth: if teams don’t share goals, they’ll keep acting surprised when everyone loses together.
Key Points
- •The article argues that security should be treated as a product with a defined organizational purpose rather than pursued for its own sake.
- •It presents security as a business enabler and links its purpose in technology organizations to supporting software delivery performance.
- •The article identifies the relationship between security and DevOps as commonly described in the industry as strained or adversarial.
- •It uses behavioral economics, cooperation games, and moral hazard as frameworks for understanding barriers to cooperation between security and DevOps.
- •The article explains game theory concepts including cooperative versus non-cooperative games, zero-sum versus non-zero-sum outcomes, and perfect versus imperfect and complete versus incomplete information.