I am familiar with a particular small business. They have this loop:
1. Product and Engineering cooperatively develop a project, scope milestones, cut tickets, do agile, eng writes the code and iteratively works with product to incorporate feedback and it's a grand ole time
2. They get about 80% done with implementation (so they're about 90% if the way through the entire project, impl is usually about half the time)
3. The owner takes note of the project and examines more closely. They profess their opinions all over it, sowing madness and scope creep, freaking out the junior ICs and new hires, and further exasperating the seniors and old hands
4. They scramble, cut other scope that isn't in the Eye of Sauron, do some late nights and cut a bunch of corners, write some shit code here and there, then push it over the finish line a little late and a lot of stressed
5. They have a retro in which they excoriate the evils of scope creep and extol the virtues of sync meetings and exec reviews and more process layers and stamps.
6. Owner doesn't participate in any of the additional process because they don't have time, naturally.
7. A project nears about 80% completion, the owner takes notice, and...
It's really a beautiful cycle. At various points, sometimes someone will notice all the layers of scar tissue, uh I mean process, aren't actually helping, so they cut a bunch of them out. Much rejoicing. Then the next project gets about 80% done, and...
Yeah. Whatcha gonna do? It's the only thing about the company that isn't going to change.