image (C) Tauntaunwampa
I was talking earlier this week with a new product manager on my team. It was our 1:1 and we were discussing his latest project. It’s the first big product area that this PM has taken on and it’s very important for our next release, so we were using our conversation to make sure everything was on-track. I was peppering him with questions after he shared his update:
“How do you feel the project is going?”
“What challenges have you hit working with your feature team?”
“Is the spec ready for review?”
“Okay, can you show me the diagram for the main use case that you’re stuck on?”
“What about this part of the lookup, can we also double-back with the phone number?”
“I just thought of these two uses cases, have you considered them?”
“What’s left between now and the spec review?”
Later that same day I was in a feature team meeting discussing the status of a new product offering. The lead developer was sharing his detailed update, which included a few specific areas that had risk and ambiguity.
“Why did you choose that implementation path?”
“Will this scale if we 10x the amount of users in a year?”
“Is there a faster way to do it?”
“What if we added more resources?”
“What are the biggest remaining risks?”
Folks who have worked with me before know that I love to ask questions. A lot of questions. 🙂 The questions I asked during the 1:1 with my PM (and their resulting answers) helped me quickly understand the status of the project and where he was blocked. It also set the stage for the type of information I’d want to hear in the next update I get about the project. He and I then spent a few minutes talking about questions, curiosity, and why they’re both so important for Product Managers to be effective in their careers.
Awesome Product Managers have an unrelenting sense of curiosity. They’re equally curious about the latest competitive apps, their own project statuses, industry news, how a piece of backend technology works, the reason a bug occurred, or why a partner team is late on delivering. A great PM should use precision questioning to drill into every conversation and problem to understand what is really going on and what they can do to move things forward. This can reveal gaps in use cases, technical knowledge, or even a partnership agreement that need to be addressed.
Checking for curiosity is critically important when evaluating a PM for a role on your team. Many parts of my PM interview process, from the “What’s your favorite app?” question all the way through the product design case study, are used to see how curious the candidate is. Do they start out the case study by immediately jumping into a solution on the whiteboard based on something they know, or do they open with a set of questions back to me to help understand what they don’t know.
Ultimately your use of precision questioning as a PM must be balanced with the amount of investigation and discovery you do on your own. You will also gain a lot of experience over time simply from being in more and more product cycles.
The simplest way I can frame this advice? Don’t wait if you’re curious about why something is. Get curious and ask the question.