I read a great point expressed in the book Agile Product Management With Scrum the other day dealing with Google News. Google was about to release the very first version of Google News and was trying to determine which of two features was more important:
1. Filter the news by Date
2. Filter the news by Location
Now we have all come to that critical crossroads just before release where we have to choose A or B (or even C). As we know, Google doesn't exactly have "limited reach". When they release something, people notice, and it's a lot of people (billions?). Needless to say, they performed a great move that we can all learn from... don't choose and just release without the feature!
This may sound crazy for such a huge firm with global reach, but it was the perfect solution. Shortly after the release of Google News the feedback came rolling in. The results?
1. 300 user requests for filtering by Date
2. 3 user requests for filtering by Location
If Google can do this, you can too. Just make sure you have a plan in place to capture the feedback quickly post release so that you can build the enhancements users are clamoring for! Hopefully they are asking for A or B, or else you have a new problem on your hands. Also, be sure your team has the resources to accommodate the new requirements! Time and again I've seen a solid release fall victim to lack of resources just when momentum is picking up!
I always try to tell my users on first release that even Google News, Gmail, etc. was not perfect upon first release! With constant two way communication and the setting of expectations you will keep the users happy and keep the product rolling successfully.
How do you handle the choice between A or B before release? Please comment below!