On the same note, maintaining a product for 13 years, I keep thinking about, what I call, "docs-driven development"[0]. The idea is to have a minimal set of co

On the same note, maintaining a product for 13 years, I keep thinking about, what I call, "docs-driven development"[0]. The idea is to have a minimal set of core features that allow you to achieve complex tasks (might be tedious at the start to do so), but document those ways to achieve the tasks using the current set of features. If a certain workflow is being used enough (e.g. Photoshop: remove background from an image using the Lasso Tool), replace the tutorial in the docs with an actual new feature that simplifies this workflow (e.g. include an algorithm/AI to automatically remove the background from an image in one click). The advantage of this is that customers are still able to achieve what they need (using your guidance/tutorial), but in the long-term you improve the product and make your customer's life easier if you start providing one-click automations/better UIs for the most common use-cases. [0]: https://uxwizz.com/blog/docs-driven-development https://uxwizz.com/blog/docs-driven-development