Customer Advisory Boards: the Good and the Bad

Some companies form customer advisory boards (CABs). Prospective and existing customers comprise these boards and provide input and feedback on one or more products the company is developing or offering.

Surely it's good to communicate with customers to understand their situations, problems, and suggestions. But is a CAB a good way to do so? Yes, but not for the reason you might think.

In general, you're much better off conducting one-on-one interviews with prospective and existing customers than convening meetings of a CAB. The group setting of a customer advisory board has many of the same drawbacks as focus groups. Above all, CABs are almost certainly not qualified to make decisions on which features to include or how to market your product. Board members are customers, not requirements analysts, design experts, or market strategists.

CABs are more useful for outbound marketing purposes. Forming a CAB is a great way of generating some word of mouth and PR for your product at a very low cost.

Recall the four-step process for developing a WOM marketing program:

Find an existing community of users of your product.
Determine what are they saying about your product.
Engage them in dialog.
Empower them to do things they might not be able to do on their own.

Do use your CAB (in addition to one-on-one interviews, ethnographic studies, and surveys) to gain an understanding of your market and get feedback on your product. But also figure out how they can help you market your product. Give them the information and the tools to get the word out on your product.

Comments

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...

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the four problems that companies face, or are trying to overcome, as they make product decisions . Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions. They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to ...

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 problems she faces or the ...

Cauvin

Search This Blog