More often than not, part of the issue is the real needs begin to be discovered after the first version ships. When possible I always encourage creating a firs

More often than not, part of the issue is the real needs begin to be discovered after the first version ships. When possible I always encourage creating a first version disposable of a working prototype that is disposable. Maybe it's built in a low/no-code tech to minimize any emotional attachment to throwing it away. It's also important to remember that especially in the beginning, software is a vehicle for learning and experiments on what's needed. If it's too unstructured, or too structured, it can introduce constraints that limit the ability to learn and solve the problems wherever they are ultimately discovered.