Every business has at least one process that survives purely on inertia, nobody remembers exactly why it exists, but changing it feels riskier than keeping it, so it stays. That inertia has a real, ongoing cost, it's just invisible because nothing about it looks urgent.
Why legacy process is so hard to spot
A new, obviously broken process gets noticed immediately, it's new, it's visible, it's easy to compare against "how we used to do it." A legacy process that's slowly become wrong has no such comparison point, it's just always been there, so it reads as normal rather than as a cost.
The question that surfaces it
For any recurring process, ask: if we were designing this from scratch today, knowing what we know now, would we build it this way. If the honest answer is no, that's a legacy process being carried forward on habit alone, not on merit.
A common pattern worth checking for specifically
A step that exists because of a tool or a person that's no longer part of the business. The tool got replaced two years ago, but the manual workaround built around its limitations never got removed. The person who needed that extra approval step left the company, the step stayed anyway, because removing a step feels riskier than keeping an unnecessary one.
Why this is worth auditing on a schedule
Legacy process doesn't announce itself for review, it has to be actively looked for, because by definition nothing about it is currently causing an obvious fire. Left unchecked, it just accumulates, quietly, as a permanent tax on every year going forward.
What to actually do about it
Pick one process a quarter, the oldest one, and run the from-scratch question against it deliberately. Most businesses find at least one step that's been costing real time for a reason nobody can fully articulate anymore.