Earlier quoted context omitted.
I don't know. From what I've seen, a lot software gets built by a small group of people. It becomes wildly popular and the is maintained by a behemoth churning out minor features at a snails pace while everyone frets about the even the smallest product changes. It's easy to experiment and build when your product is small and few people use it. When you're bringing in real money and most of the Fortune 500 is using yo…
Well, yeah, because the risk/reward of the decision making changes, purely in terms of dollars/second for an outage, never-mind legal and reputation risk.
In a product as old as Google docs, they honestly have all the important features that most people actually care about already. You can save. You can track changes. You can set up custom styles. Or embed images. You can edit docs collaboratively. Or programmatically via their api. Documents look the same on basically everyone’s computer. And they can be in shared folders for teams.
At some point every product runs out of high value, visible features to add that anyone cares about. This isn’t a failure mode. It’s the opposite. This is the final state that most successful software should aspire to reach.
I have a lot more respect for teams that understand this, and let their products find their UX steady state. Fastmail. Git. Vim. WhatsApp. And yes, Google docs.