If it ain't broke, don't fix it
When considering changes to working systems
Understanding the Rule
Don't make unnecessary changes to systems or processes that are functioning well. Change for change's sake often introduces new problems without providing real benefits.
What Happens When You Break It
Unnecessary changes waste resources, introduce new bugs, disrupt workflows, confuse users, damage morale, and risk breaking functional systems.
Benefits of Following This Rule
Preserving working systems maintains stability, focuses resources on real problems, avoids unnecessary risk, respects proven solutions, and prevents self-inflicted problems.