Reviewing Peers

Source: photobucket inc.No, not actually reviewing your peers. I am suggesting peer reviews of your work. Ugh… I know the stink of requirement reviews with development is all over the office, but I am not thinking requirement reviews.

I am suggesting reviews of your problem statements with your peers. Specifically the other product management types you work with. I know, you are the only product manager in the company. This is a great excuse to have a sit down with the head of marketing or an executive. At this point, I am trying to stay away from the people who will build the solution.

This doesn’t have to be a formal review with an official sign-off process. You are looking to validate a few things including that you have a well defined problem statement that is devoid of solution, within your market segments, measurable, observable and answers all questions.

Since the problem statement is technically your first official analysis of the idea (no matter who or how it was sourced.. err.. sensed), you want the extra eyes to validate whether it warrants further processing. This is a great gating factor to help save some R&D cycles by filtering out requirements that are ill-defined or out of scope for your target market. If the problem smells, it’ll never get to the requirement stage.

For what it is worth, this totally works for features and roadmaps too.

Image Source: photobucket inc.

If you enjoyed this post, please leave a comment or subscribe to the feed to receive future updates. You can also follow me on Twitter. Tell other people about this post.

Related Posts:

  • The Top Product Management Blogs 2012
  • One Good Release
  • Product Management Is...