← ClaudeAtlas

shirky-principlelisted

Apply the Shirky Principle when analyzing why legacy systems persist, why incumbents resist disruptive solutions, why organizations seem to make self-defeating decisions, or why a tool or institution appears to be prolonging the problem it was meant to solve. Trigger on phrases like "why do they keep the old system running?", "this tool is creating the problem it's supposed to fix", "why won't they just adopt the better solution?", "why does this bureaucracy exist?", or any situation where an institution's incentives seem misaligned with its stated purpose.
The-Artificer-of-Ciphers-LLC/skills-from-the-artificer · ★ 2 · DevOps & Infrastructure · score 73
Install: claude install-skill The-Artificer-of-Ciphers-LLC/skills-from-the-artificer
# Shirky Principle > "Institutions will try to preserve the problem to which they are the solution." > — Clay Shirky, 2010 ## The core idea Organizations — companies, government agencies, industry groups, software tools — are built to solve a problem. Over time, their continued existence depends on the problem continuing to exist. This creates a perverse incentive: the institution has structural reasons to resist, undermine, or slow the permanent resolution of the very problem it was founded to address. This isn't always conscious or malicious. It's often structural: the people in an institution have careers, salaries, and identities tied to the institution's continued relevance. ## Examples in software and tech **Legacy vendors:** A company selling expensive middleware solutions has every incentive to argue that cloud-native alternatives "aren't mature enough," "lack enterprise features," or "present security risks" — even as those alternatives become clearly superior. Killing the problem kills the business. **Security compliance organizations:** A compliance framework that provides checklists and certifications has incentives to ensure compliance remains complex and requires annual renewal. Simple, automatically verified security would undermine the certification industry. **Internal tools teams:** An internal developer tools team whose purpose was to manage a painful deployment process has subtle incentives to resist adopting off-the-shelf solutions that would elim