Most major implementations are designed and delivered by people who are very good at the technology and much less close to the operational reality of the business. The requirements were gathered. The configuration was built to those requirements. The training was delivered. The project was closed. But requirements gathered from a distance never fully capture how a business actually works. They miss the workarounds people have developed over years. The informal processes nobody documented because they've always just been how things are done. The political realities that determine which parts of a new system people will actually adopt — and which they'll route around the moment nobody is watching. The implementation delivered the system that was specified. What it couldn't deliver was adoption by a business it never actually understood deeply enough to serve. This is why post-implementation remediation is almost always possible. The platform usually isn't wrong — it's misconfigured, under-adopted, or disconnected from how the business actually operates. Those are solvable problems. They don't require starting again, replacing the platform, or going back to the vendor that created the problem in the first place.