Saeed Khan writes,
In my effort to build products with limited resources, I often spend time justifying the need for features. Market facts provide quantification for the requirements and usage scenarios put them in context. But too often, I still face the usual questions from the engineers over each requirement:
- Is this feature critical for this release?
- How many customers have asked for it?
- Are there any workarounds?
- Would we lose deals if we didn't have it?
And my least favorite:
- Of all of these features, if you could have only one, which one would you choose?
Why they persist in asking this question, I don't know. It's like asking, "Of all of the doors on the house, if you could only have one, which one would you choose?"
Read about A house with no front door.
Why the Desktop Is Dying
Business 2.0 :: Working Tech :: Why the Desktop Is Dying: "What does it mean when a website delivers this kind of function better and faster than a desktop application? It means the desktop as we know it today is doomed. Screens may get larger, but the boxes attached to them will shrink. The Mac Mini is just the beginning."
What impact, if any, do web-based applications with massive storage and instantaneous search (such as Gmail) have on your product strategy?
Posted on January 31, 2005 at 08:35 PM in Industry News & Commentary | Permalink | Comments (0) | TrackBack (0)