Ken Norton is well-known in the product management scene, and this slide deck summarizes nearly everything there is to know about software product management. A must-read for every new product manager and also for most PM veterans.
When you have a new product management job, what are your tasks in your first couple of weeks? Study the product, architecture, speak to developer, sales and support, have a look at the roadmap…
The guys at HipChat add a task that they consider even more important: Speak to users. They say: ”
Your job as a PM is to find the right problems – then work with your team to solve them.” So to understand the problems, speaking to users is a better way than studying the product’s architecture.
Last week I shared a post on how to hire a good Product Manager. But there are not only product managers in a good team (and developers, by the way), but a designer is usually also part of the team. You may also call the UX expert, UI specialist, or the like. But there needs to be someone who turns the product manager’s mockups into real UI.
Bokardo has a post on How to hire a good designer.
- Always be building relationships.
- Portfolio, portfolio, portfolio.
- Can they tell a story?
- Are they designers all the time?
- Know what motivates designers.
- Understand their current pain.
- Have them hang with the team.
- Do design exercises.
- Reach out yourself.
- Trust your team.
- Can they critique/take criticism?
Read the details in Bokardo’s post.
When planning a new feature or improvement, one should break it down to the very tasks and jobs that are to be performed by the feature. In other words, one should ask:
- Why will I need this feature?
- What would I like to achieve with this feature?
An example of such an analysis is made on self-driving cars: Exactly what jobs will self-driving cars satisfy?