Skip to main content

Focus Groups

Previously, I wrote that effective product managers actively go to the market to obtain information rather than relying on industry experience, feedback from support calls, or feedback from sales. Many executives don't seem to appreciate the value of go-to-market approaches, with one exception: focus groups.

Due to media attention to the concept of focus groups - whether in the context of product marketing or politics - much of the population is familiar with the notion. So the first idea that may pop into your head as an executive when you need market feedback is to conduct a focus group. Unfortunately, focus groups, while sometimes a useful tool, are often not a particularly effective active means of gaining an understanding your market.

The main problem with focus groups is that they don't give the facilitator the opportunity to probe deeply into the customers' situations and problems. Not all customers have the same perspective and background, so you would have to probe each customer individually to understand them. A focus group is not the appropriate setting for probing each individual's personal situation.

Focus groups are still helpful, particularly when one-on-one interviews precede them. Focus groups aid you in gaining an understanding of the surface, gut reactions of your customers. They also may yield insights about the effect of customer interaction on their propensity to buy.

Use focus groups judiciously, and don't use them to the exclusion of other techniques. More on this subject in Susan Abbott's Customer Experience Crossroads blog.


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

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

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