Seems like you had that flash of brilliance in the shower years ago. That revolutionary product that everyone would love so much they would buy two. You spent time and money…maybe even have a mock-up or prototype, but it feels like you are stuck.
If things are not going well, it’s time to step back and ask yourself some important questions (hopefully not for the very first time). Don’t throw the baby out with the bathwater just yet…….but let’s go back to the basics and revisit the foundation of what you’re doing, adjusting course as needed.
-What problem is your product intended to solve?
-Are you consistent in the guidance of those hired to help?
-Do you have a sufficient understanding of the development process?
Are you clear about the problem your product is trying to solve for your customer? Do you know who your customers will be and how you will find them?
If these questions stump you. Stop immediately and go back to the drawing board. The first thing you should always have is a written product definition that answers these basic questions. They serve as your road map. Without a road map……it is no wonder you are feeling a little lost.
Are you consistent in the guidance you give to those hired to help?
Now you have your road map as an anchor. Are you bouncing around changing your mind or adding things to the requirements. Change is a normal part of the process, but the more you change things the more tasks are redone and the whole process takes longer and costs more.
If you feel unsettled about where you are going and others are involved (especially when you are paying them hourly) step back and consider the end result you want until it feels pretty solid update your spec and begin again. Changing things on the fly can get very expensive.
Do you have a good understanding of the development process?
Have you heard the saying ‘Everything is easy when you are not the one doing it?’ It is common to under estimate and under appreciate the time it takes to to do things that you do not know how to do.
This is why I am a big fan of starting with your simplest ideas first. The bigger the complexity and challenge, the bigger the development budget needs to be. A simple first product will not seem simple, yet is the better learning experience which you can then apply to your future complex products.
The better educated you are the better questions you ask, the more money and time you are likely to save. Do everything that you possibly can yourself…..including the best possible preparation for those that you hire to help you.