Key Skills
Arjun tells Meera the edition-tag feature will take six weeks, not the two she had hoped for. How she responds in the next ten minutes draws on nearly every skill the job needs.
The rule
A PM works with four tools: questions, numbers, priorities and words.
- Questions: curiosity and empathy. Asking "why?" until you reach the real cause, and wanting to understand how users actually live. Strong PMs are more interested in the problem than in their own ideas.
- Numbers: data literacy. Reading a chart without being fooled by it, knowing the difference between 30 complaints and 30% of users, and doing quick rough maths.
- Priorities: judgement. Weighing value against effort and risk, making trade-offs with incomplete information, and saying "no" or "not yet" kindly and clearly.
- Words: communication. Writing short, clear documents, listening more than talking, and explaining one decision to an engineer, a founder and a student in the words each of them needs.
Two supporting skills hold these up. Technical fluency: a PM does not write production code but understands enough (what an API is, why some changes are slow and risky) to discuss trade-offs honestly. Influence: because nobody reports to the PM, these four tools are how they win agreement.
None of these is a talent you are born with. Each one grows with deliberate practice: write a one-page summary every week, check one number before voicing every opinion, and ask one more "why" than feels comfortable.
The shortcut
In any tricky moment, run the tools in order: ask, count, choose, tell.
Ask
Meera asks Arjun which part takes the time. Matching exact editions needs each book's ISBN data. Matching course codes alone needs only the college's book list.
The trap is jumping straight to choose or tell. Without ask and count, a PM either argues for the original plan or quietly accepts six weeks, and misses the smaller win hiding inside the problem.
Drills
Answer fast — trust the rule.
Twelve complaints arrived this week. Before calling it a crisis, Meera checks how many sales happened in total. Which tool is she using?
Does ReShelf's PM need to write production code?
The team can build only one of three good ideas this month. Choosing between them most directly tests which tool?
Why is influence a core PM skill?
Remember
- Four tools: questions, numbers, priorities and words, held up by technical fluency and influence.
- Shortcut: ask, count, choose, tell, in that order.
- Trap: choosing or announcing before you have asked and counted.