The Signal
Every business carries old promises that nobody would approve again if they had to make the call today. A package created to close one deal. A report built for one customer. A product option that solved a launch problem two years ago. A policy that made sense when the team was half the size.
Those decisions rarely look expensive at the moment of creation. They become expensive later, when the business has to preserve them through every hire, handoff, pricing change, support ticket, product update, and sales conversation.
Why this matters now
Growth usually rewards addition. More segments. More plans. More workflows. More exceptions for good customers. More internal metrics because one leader wanted better visibility during a specific quarter. Each addition feels like responsiveness. The bill shows up as operational drag.
That drag does not always appear as a clean line item. It hides inside slower onboarding, longer sales calls, confused customers, brittle product releases, messy fulfillment, and managers who spend half their week explaining why the system works the way it does. The business starts paying rent on complexity that has stopped earning.
This is not an argument for stripping a business down until every customer gets the same thing. Some complexity is the business. Custom service levels, expert judgment, flexible fulfillment, and product depth can be the reason customers stay. The question is whether each piece still protects revenue, improves the experience, or helps the team make better decisions.
The mistake to avoid
The mistake is treating subtraction like a simplicity campaign. That turns a useful operating discipline into a slogan. Operators hear "reduce complexity" and cut visible choice while leaving the internal mess untouched. The offer menu gets shorter, but the team still maintains twelve exception paths behind the scenes.
Retirement has to apply to the whole operating model. Customer options count. So do reports, approval rules, handoff steps, onboarding docs, service promises, product toggles, and old workarounds that became normal because nobody wanted to reopen the decision.
What earns renewal
Useful complexity has proof. Customers use it. Sales can explain it without a side conversation. Support can resolve issues without hunting for tribal knowledge. Product can change adjacent parts of the system without breaking it. Finance can see the margin effect. Leadership can name the owner.
Weak complexity has a different smell. Nobody knows who asked for it. Usage is assumed because removal feels risky. The team keeps it because someone might need it. Customers do not mention it unless it breaks. New hires need a long explanation before they can operate around it.
The removal test should be practical, not philosophical. If you turned this off for 30 days, who would notice? What revenue would be at risk? What customer promise would fail? What internal decision would get worse? If the answer is vague, the complexity is living on inertia.
The first move
Choose one surface where the sprawl is visible. Do not audit the whole company. Start with offers, features, policies, reports, fulfillment rules, or service levels. Write down every active element in that area, then force each one to renew its contract with the business.
The move this week
By Friday, tag each element as protect, simplify, retire, or test. Protect the parts that clearly differentiate the business or defend revenue. Simplify the parts with value but too much handling cost. Retire the parts with no owner and no evidence. Test the scary ones by removing them from one segment, one package, or one workflow before you touch the rest of the system.
Complexity is not bad by default. But if it keeps asking the team for time, attention, training, support, and margin, it should have to earn renewal like anything else.