[bgdnpn]

I've worked as a PM for a few startups and scale-ups and can confirm that sometimes one of our responsibilities is to slow down the release speed. Why? Because, after (and even before) the customer base passes a certain threshold in size and complexity, there are many more hidden variables in the "what and how to build" equation.

This being said, as a PM (or at least as the specific "story writing and prioritizing" sub-category of PMs known as a Product Owner) you sometimes have the feeling that you're adding complexity and overhead to the process without actually contributing much. I guess this is true mostly when you're new to the company and have a long way to becoming an integral part of the product development machine.

In addition, I have to agree with this line taken from another comment: "Growth stage developers are a different breed than scale stage developers. As a company reaches scale, things generally need to get more formal and experts take favour over generalists."