I interviewed a candidate for a Product Manager position the other day. I like to ask a really simple question at the start of a PM interview: “What is your main responsibility as a Product Manager?”
The answer I got from this candidate was one that I’ve heard many times before:
“My primary responsibility as a PM is to translate business needs into technical requirements”.
This is a terrible answer. Translating requirements from one language to another is not your job. That reminds me of this:
As a PM, your job isn’t to understand and translate requirements. It’s to understand customer needs. What problems does the customer have, and what product can you build to solve those problems significantly better than how they are being solved today?
Collecting requirements from everyone and boiling them down to the lowest common denominator is not your job. Your job is an act of understanding and creation: understanding your customer’s problems, and creating a solution that is so much better than their current solution that they are willing to pay you (with money or their attention) to use it.