+91 98726 60544 hello@mitstech.co Mon–Sat · 09:00–18:30 IST

A customer advisory board that is not theatre

IT Strategy By Mits Engineering Team 2 min read
A customer advisory board that is not theatre

A customer advisory board is a small group of customers who meet periodically to discuss where your product should go. Done casually, it becomes a session where you present the roadmap and customers nod, which produces a pleasant meeting and no information. Done deliberately, it is the cheapest access to informed judgement about your market that exists.

The difference is what you bring. A roadmap presentation invites approval. A genuine question — we can build one of these two things, here is what each would mean for you, which and why — invites the disagreement that is actually useful. So does showing something unfinished, or describing a problem you have not solved. Customers who see that you are asking rather than announcing engage very differently.

Choose members for diversity of situation rather than for size or friendliness. The largest customer's problems are not representative and their voice will dominate. A mix of sizes, sectors and maturity produces conversations where members disagree with each other, and that disagreement is where you learn — it tells you which needs are universal and which belong to one segment you might be over-serving.

Keep it small enough that everyone speaks — six to ten — and rotate membership on a stated term so it does not calcify into the same voices for years. Meet two or three times a year with a real agenda, minute what was said, and report back at the following meeting on what you did with it. That last part is what determines whether members take it seriously the second time, and skipping it is the commonest way these boards quietly die.

Be clear with yourself about what it is not. It is not a substitute for talking to users who are not on it, who are the majority and who are systematically different — advisory board members are engaged, senior and invested, which is why they agreed. And it is not a decision-making body: you are gathering input, not delegating strategy, and being explicit about that prevents the awkwardness of a member expecting their request to be built because they asked at the board.

Need help with this? Explore our Software Development services. Learn more Back to all news

Keep reading

More on IT Strategy