The main function of a PM is what’s the need that the product is meeting and how do we meet the need. Both ‘what’ and ‘how’ are important and one cannot have a successful product with either without the other. Once we have a product, the next important goal is to frame the value exchange between the business and the customer (according to Melissa Perry).
PM roles can vary according to the growth stage of the company.
### Large companies:
- Make mock ups
- Talk with users
- Check in with contractors
### Midsized companies:
- Make mock ups for designers
- Talk with users directly
- Check in with contractors
Large Companies:
- Planning meetings with specialized teams like designers, engineers etc.
- Negotiating with C-Corp about delays, feature changes.
- Using data from logs more than talking to end customers. It is still important to talk with customers but often PMs talk with fewer end customers at large companies.
What is a typical workflow of PMs?
Communicate: Clearly communicate product vision, needs, and bring clarity by removing ambiguity.
Trust: Trust in your team’s ability and intention to do good work but set consistent progress check-ins. If you don’t trust in your team, there’s a hiring problem and try to fix that.
Delegate: Empower others to do good work. Distribute work.
Monitor: Monitor to give ideas but don’t micromanage or be patronizing.
Feedback: Give charitable and constructive feedback in good faith.
Adjust: Based on learning, do the next iteration better than the last.
Question for the Author:
Would you recommend joining a large company or a small startup for a new PM?
