We love to release early and release often. It makes us and our users happy. But, we sometimes fall into the trap of doing some things so quickly that in hindsight it would have been better off not to release the feature at all. In the race to keep up, thinking about getting the new features out the door seems so tempting, but, if not planned properly, can compromise on the user experience of your overall product - not to mention having grumpy users that might leave!
There is absolutely no point in releasing a feature for the sake of a release and to maintain a track record - if it is not done yet!
Get it working nicely and let the new feature fit well with exiting features within your app. Creating a loose-ended feature that you will improve upon over time is no excuse for just throwing something online and then worrying about the user experience later.
It is ok if this development takes a bit more time. I am not saying you need to get it perfect, but you need to ‘manage’ the user experience part of it really well. Will the user use it and keep using it? Are you solving a real need for the feautre in your app? Is it building upon something that you don’t have currently? Will it help users save time? In the case of DeskAway, the question we often ask is if it will help people work smarter and collaborate effectively?
Recently, we were debating on how we would integrate the Google Docs functionality within a DeskAway project - it is extremely useful (we use Google Docs a lot) when you can access your Google Docs within your projects and even share comments with your team. Everything is so neatly organized. Logically, Google Docs would fit well within DeskAway’s Docs section. Should we have it separate (like another drop-down for gDocs) and run it parallel with our existing Docs functionality? This would definitely be easier to program in and we won’t have to worry about dabbling a lot within the current Docs code. In the name of ‘release fast, release often’, we mocked it up and realized that it is going to be a pain in the $%# for the user to not only navigate an additional menu item but he/she will have to go to 2 seperate pages to see Docs created within DeskAway and Docs created/attached via Google. Definitely not a practical solution when you think about ease of use and the overal workflow of a typical user. We scraped this idea and went ahead with re-engineering our code for the Docs section to also include Google Docs - a little more time consuming but worth it! When complete, this will present the user a one-page summary of all his/her docs - and the Google ones will be labeled with a nice Google Docs icon.
We could have released with the original idea and gotten feedback on how to improve - but we are here to not waste our user’s time. We rather give you something that is functional than something that seems functional but won’t add to the over experience of collaborating in a team.
So, stay tuned untile we release this new feature very soon