Writers hear this all the time: cut the sentence you love most if it doesn't serve the story. Salesforce Orgs need the same discipline.
Most Orgs weren't built badly. They were built for the requirements and deadlines people had at the time. Years later, that Flow from 2021 may no longer be needed. The Apex trigger solved a problem that no longer exists. The Permission Set structure made sense before three reorgs and two acquisitions.
Removing those things feels personal. Even for me. We remember the effort it took to build something, not the cost of keeping it around after its purpose is gone. That's sunk cost thinking: the time already spent building it feels like a reason to keep it, when it should have no bearing on whether it stays.
That's why internal cleanup stalls. The question quietly shifts from "What still creates value?" to "Should we really delete something we worked so hard on?"
An unused Field is just an unused Field. An obsolete Flow is simply obsolete. The only question that matters: does this still earn its place in the Org?
Thanks for the input, Joy Shutters Helbing.
Book a free 60-minute Salesforce Technical Debt Audit: a score for Usability and Build Quality, and your top cleanup priorities.