The Metric That Ate the System
Why the systems we build to prevent failure become the systems that guarantee it — and why the fastest organizations have the fewest failures
The onboarding took three and a half months.
Nobody thought that was a problem. The product was a mid-market SaaS platform with several hundred enterprise accounts, but the implementation looked more like a consulting engagement. Hundreds of configuration fields. Custom JSON editing. Bespoke HTML templates for every client. A sales engineer could hand a customer practically anything they asked for — a UI layout that matched their brand guidelines, a workflow that mirrored their internal process, a data model shaped to their specific edge case. Customers loved it. They got exactly what they wanted. Each one felt like the product had been built for them alone.
The flexibility was the pitch. It was also the thing that was quietly converting a software business into a professional services firm. Every bespoke configuration added hours to onboarding. Every custom template required an engineer who understood that specific customer’s setup. Renewals required annual configuration updates that consumed weeks of the customer’s time, weeks of the team’s time, tested against a setup so customized that no two deployments looked alike. The product could do anything. Getting it to do the specific thing a customer needed took longer every year.
Our team built the replacement. Opinionated where the old system was open-ended. Fewer configuration fields. Sensible defaults. A product that behaved like a product. The tradeoff was obvious: some customers would lose the exact UI tweak they’d requested two years ago. Some workflows would standardize where they’d previously bent. The new system could onboard a customer in weeks instead of months.
The legacy teams refused to touch it. They had existing customers on annual update cycles that already required weeks of careful work. Switching those customers to the new platform meant some customization wouldn’t carry over. A button in the wrong shade. A dashboard panel in a different order. The teams were measured on retention. They could see the risk of a customer calling to complain about a missing feature. They could not see the cost of a customer losing weeks of their year to a configuration update that existed only because the system was too bespoke to update efficiently. One risk had a number. The other was invisible.
The measurement system was working exactly as designed. It just couldn’t see what it was protecting, or what that protection was costing.