How many users to talk to as part of discovery?
It's not about the number.

Minimum is the amount willing to talk to you in the ballpark timespan that you have. Depends on your assessment and your manager's appetite for discovery (could come out to be 1-3 interviews).

1/3

B2B product managers get lots of feature requests from customer-facing teams. We try to get as much of the "why" behind the request

I see it as a micro-opportunity for me to coach CSMs, Sales & Support reps. This way, over time, the quality of feedback will improve

A thread 🧵

PM's role in decision-making per Kevin Weil, OpenAI CPO. Via @lennysan.bsky.social

Decisions don't have to come from PM. PM should guide the room toward quality decision

Reminds me of @moskov.goodventures.org Asana cofounder: Prep meetings with “What questions do we want to answer?”, and not goals

Product management is such a misunderstood role. Mainly because it’s unique per company.
But a lot of the "it's unique per company" is actually "it's unique per founder".

A blog post about resentment and empathy towards leadership.

www.guypeled.com/p/resentment...

Product managers watching users engaging with their feature-rich but usability-poor product

This is great advice for new hires. It's even better advice for candidates.
You'd want to be perceived as a fast learner. Best indication for that is the level of granularity of your questions during the interview.

Below is from this excellent article:
review.firstround.com/the-indispen...

Many Product Managers still work as if their job is to make decisions.

No.

Your job is ensuring decision quality and that a decision is made.
Your job is to extract the best decision out of the room.

Making a decision yourself is last resort to prevent death by committee.