A review added because of a launch gone wrong. A new legal check to guard against possible litigation. Layers accumulate over the years until you're unable to release a new feature for months after it's ready — stuck between reviews, with no clear path out.
— my take
This is one of the scariest things about scaling. Every process you add is a response to a real problem, but nobody goes back to ask whether the problem still exists or whether the fix is proportional. As a founder, I want to build a culture where process is treated like code: reviewed, refactored, and sometimes deleted. The instinct to add a check after every failure is natural — the discipline to remove checks that no longer serve you is what separates fast companies from bureaucratic ones. I keep thinking about Ramp's culture of velocity; they seem to guard against this almost religiously.