I recently started a series on software development and the role of the Product Manager. If you haven’t already done so, it might be a good idea to read Part 1 (Overview) before continuing. In this post I’d like to write about the first step in the development process, namely Product Requirements, and the various sources of input that go into deciding what to build and how to improve your product.
As I started writing I realized the topic is just too big for one post, so I’m going to split it up into a few different posts:
- Part 2 (this post) will be about user needs as an input to product requirements.
- Part 3 will be about business needs and technology needs as inputs to product requirements.
- Part 4 will be about the PM’s role in the Product Requirements phase.
Even though the focus here is not on what kind of product/service your company should develop and sell, I do want to briefly mention product/market fit, because it is probably the most important aspect to figure out to be a successful business. No one talks about this better than Marc Andreesen, so I wanted to quote from one of his (now deleted) blog posts:
The quality of a startup’s product can be defined as how impressive the product is to one customer or user who actually uses it: How easy is the product to use? How feature rich is it? How fast is it? How extensible is it? How polished is it? How many (or rather, how few) bugs does it have?
The size of a startup’s market is the the number, and growth rate, of those customers or users for that product.
The only thing that matters is getting to product/market fit. Product/market fit means being in a good market with a product that can satisfy that market.
With product/market fit figured out (no easy task), and a workable product to start with, it’s time to get serious about building and improving the product — and that’s the stage where this post starts. At the heart of a good product roadmap stands a Product Manager that is able to strike a balance between user needs, business needs, and technology needs. So let’s look at each of those in detail, starting with user needs.
(more…)