There are valid use cases and then there is the overkill. As a product manager, you must be aware of when you are crossing the line. If not, you are made aware. If you have handled the difficult developer (now come on guys, don't you all go nodding on me), you will be able to appreciate the supposedly overdone use cases or their close cousins some product managers are likely to have heard in their lifetime:
1. The ECG machine will not monitor heart rates below 20 beats per minute. The performance deterioration far outweighs the probability of the use case.
2. Air traffic controllers will be able to monitor only up to 20 flights an hour. This is not Heathrow!
3. Bank balances will be stored only till the hundredth decimal place. Who really cares about the chump change?
4. Pages of the eBook will not be reproduced in exact order. What is this? Six sigma? Its a book, for Christ sakes!
5. There will be no search feature for this fledgling e-commerce site. What is this? Amazon?
I empathise with the developers. If you let us product managers dictate all the requirements, no system would ever work. Let those who do the 'real work' decide. They know their stuff.



