[wokwokwok]

> And an increasing number of features inevitably begin to bog down what a company can do going forward

This is a common misconception.

It may happen to be true, but it does not have to be true.

What prevents rapid delivery is constraints, and naive, stupid or incompetent implementation (or requirements) for features that add more constraints.

Adding features in a way that aligns with existing constraints, or breaks existing constraints doesn’t have to be slow; just careful.

What kills software is “nothing can ever change once it’s in production”; ie. once a feature is live, it becomes a hard constraint that can never be altered or removed or changed because of user expectations.

It’s not the number of features; it’s the immobility and panic caused by the prospect of anything ever changing, which prevents you changing anything, except very very slowly.