Skip to main content

Product Management is like Therapy

"Uncovering psychotherapy emphasizes facilitating clients' insight into the roots of their difficulties."

Imagine you're a psychotherapist. Patients comes to you complaining that they are unhappy. You don't just ask them what's wrong. You probe into their backgrounds, their situations, and why what they describe makes them unhappy.

In product management, we do much the same thing. We interview prospective customers to understand their backgrounds, situations, and problems they face. We listen, but we are not passive. To get to the root problems that our product can help solve, we have to ask the right questions and not stop at what a prospect initially says is the problem. By the end of an interview, the prospect should have greater insight into her own situation.

Comments

Sean Murphy said…
I worry that this framing puts you in a "one up" mind set instead of peer to peer. If you are not getting questions from the prospect it's not a conversation it's an interrogation.
Roger L. Cauvin said…
Thanks for the comment, Sean.

Engaging a prospect by playing a role akin to a therapist is an acknowledgment that the prospect is the expert on their situation and challenges, not you. Central to prospect interviews is that you are not the expert.

Just as good psychotherapy is not an interrogation, neither is a prospect interview. Questions are facilitative, not interrogative. The best session is one in which the therapist or the product manager effectively empowers the "subject" to share her wealth of knowledge that only she has.

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