2 ms·
I didn’t mean that you should only hire candidates who are existing users of your product. Haven’t you ever had moments, while using something, where you encou
by Razengan 8y ago
I didn’t mean that you should only hire candidates who are existing users of your product.
Haven’t you ever had moments, while using something, where you encountered some stupid behavior that made you go, “Do the people who make this thing ever use it themselves??”
This is related to the concept of qualia [0], and sentiments like “Be the change you want to see in the world.” or “Necessity is the mother of invention.”
Yes: someone without a heart condition will not be able to fully appreciate all the nuances of a pacemaker.
Of course that’s not to say they can’t contribute to the development and production of pacemakers. That’d be absurd.
But unless the thing you make is actually used by you, you will only [need to] perform within the specifications of your job, get paid and get out.
You won’t be able to identify any deficiencies that aren’t immediately obvious, and unless user feedback impacts your profits, you may see no reason to improve something. It’ll be /r/NotMyJob.
But if you’re an active user of your own product, you’ll have a much higher chance of noticing annoyances and shortcommings and fix them before waiting for user feedback to bubble up through the corporate chain to influence a change in the product.
[0] https://en.wikipedia.org/wiki/Qualia https://en.wikipedia.org/wiki/Qualia