Visualizing end product is not always possible, that does not mean you shouldn't start..!!

So happens many times with individual developers / freelancers and sometimes even with companies / clients / businesses that -

•          I have an idea in mind and it would be very useful if I implement it / create a portal / an app / a product about it, but I don’t know what all it should contain.
•          I/We have been thinking about this idea for quite a long time, however I/We cannot finalize what all functionalities I/We should include so that it becomes a complete solution.
•          We have had many meetings to brainstorm on that but we couldn’t come to conclusion about how we should go about that until we have all the pieces to put together.
•          Etc etc.

In my opinion, even if you have broad level idea of what problem your app / portal / product should solve and some basic functionalities, you should just draft them and start working on it instead of going on planning / brainstorming about it. Till the time you complete what you have drafted, new ideas about the functionalities / requirements do pop-up in mind. And even if you are not able to think of what more to add, you can just release this version to your internal team / colleagues / friends and take feedback from them, that surely does help you think more and to better your product.

Better yet, if the users are going to use that no matter what, have your own plan / pipeline of requirements to implement however simultaneously release the basic version of app / portal / product and incorporate end users’ feedbacks as well in the subsequent releases. This way you get 2 benefits – you get actual feedback from end users and incorporating that ensures usability, and creation of loyal user base.

Sure this approach as well does not guarantee a success, but it is worth taking chances than to keep thinking/discussing and never start.

Journey of thousand miles starts with a single step..!!