3 ms·
The pacemaker example doesn't resonate with me. Its a very well-posed problem - don't let the patient die. You don't have to be user to understand how to make t
by thecleaner 8y ago
The pacemaker example doesn't resonate with me. Its a very well-posed problem - don't let the patient die. You don't have to be user to understand how to make things better. For things like personal computing its a bit different. Problems are very ill-posed and often the question is what to make. In the second category its better to start with a map of the future and refine it with user feedback. However often users don't know what they want and then you need folks like Jobs.
- redshirtrob 8y agoPerhaps I should have quoted the specific point I was responding to: > You have to be a user of your own product to really make it good. That doesn't say anything about product or market. It's a very general statement that I happen to find rather dangerous in terms of hiring/employment practices. I tossed out pacemakers as a very obvious counter-example. I could come up with plenty of others--some from my own work experience. I did try to couch the comment a bit. I do think there's value in being a user of your own product. I do not think it's a necessary precondition though. And treating it as such unnecessarily constrains the candidate pool. That's the point I was trying to make.
- batteryhorse 8y agoIt's like being a chef but not wanting to eat the food you cook. For example, a lot of people want their salmon cooked extremely well done, when you as the chef, think this is wrong, but this is what the customer wants, so you do it anyway, but you no longer care about it.