Thanks for the insight, this makes a lot of sense. What about when depth adds complexity and over serves some of your users. Is it worth it at the early stage

Thanks for the insight, this makes a lot of sense. What about when depth adds complexity and over serves some of your users. Is it worth it at the early stages of development to spend the time keeping the software simple for those users who don't need the additional functionality but available to those who do? Or do you just leave all functionality in there that's required by all of your known users, train the early adopters who don't need the additional complexity to sift through it and then once your customer base is more representative of your market you worry about simplifying workflow?