Skip to main content

What's Wrong with Product Management?

Over at the On Product Management blog, Saeed asks us to complete a brief survey on what the biggest problems are in technology product management.

I answered roughly as follows:

Q1. What do you see as the biggest problems facing the technology product management profession today?
  1. Too much tactical activity in the absence of sound strategy.
  2. The lack at most companies of a skilled interaction designer or user experience professional role.
Q2. What solutions would you suggest to address these problems?
  1. Educate executives about the importance of strategy and how to best determine it.
  2. Hire skilled interaction designers or user experience professionals.
Q3. Which of the following best describes your role/department?
Product Management


Unknown said…
I really enjoy reading your blog. i'm a business analyst and i started this week with a new client. we had a very long JAD session yesterday and i'm having a hard time distinguishing between requirements, objectives, and business rules.

could you clarify the difference between the three in a sentence or two?
Roger L. Cauvin said…
AJ, thanks for reading and for your question.

Depending on the context, an objective is a higher level goal that a business is trying to achieve. The business typically has various problems that are preventing it from achieving those goals.

A requirement is the least stringent condition that must exist to solve or avoid a problem that a prospective or existing customer faces. See this entry for details.

A business rule is something that governs a business' processes. It may give rise to requirements, or requirements may give rise to new or modified business rules. See this entry for more details.
happy said…
Product Management, whats missing is a simplified, agile Product Matrix. If a Product Matrix is single sourced, updated, processed to grow - maybe like a tree. Use trunks, branches and leaves and fruits - as ways of defining a product. Then I believe a lot of amazing, simple, verified group of products can be created, and managed into the new agile markets.

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware