Quote:
Originally Posted by whpalmer4
So picture this: you are in Omni's conference room with the rest of the OmniFocus product team, and the topic of the meeting is to decide a rough outline of what is going to be in OmniFocus 3. One team member summarizes the top 10 feature requests. There is a request for X, which has 150 votes. There is a request for Y, which has 250 votes, even though all of the votes are more recent than many of the votes for X, because Y relates to a feature that wasn't even in the product when some of the requests for X arrived. You've only got resources to do X OR Y, not both. Everyone agrees that both are things that would improve the product comparably. Why wouldn't you do the one that more people have felt strongly enough about to request, even if the other one had been around longer? What does it matter that something might have been the top request at some point in the past, if it is no longer?
|
So, old-timer feature requests U, V & W all have 100 votes each. They are small but significant to those who want them. Those three combined will take up the same programming time as feature Y.
Which gets done? U, V & W ... or Y?