Customer Council Template for User Research

Use structured facilitation techniques. Go around the virtual room and give each person 60-90 seconds to share their perspective before opening to discussion. Use polls or written responses before verbal discussion so quieter members commit to a position. If one member consistently monopolizes, have a private conversation: "Your input is valuable. I want to make sure we also hear from others. Could I call on you after a few others have shared?" Most people respond well to direct, respectful feedback.

Compensation depends on your market. For enterprise B2B, early access to features and direct influence on the roadmap is usually sufficient. For SMB or mid-market, consider modest incentives: a discount on their subscription, conference passes, or branded swag. Cash compensation is uncommon for customer councils (unlike paid research panels) because the value exchange is influence and access, not money. Whatever you offer, be consistent across all members.

Treat both as valid signals and investigate the discrepancy. Council members represent a specific segment (engaged, vocal power users). Your quantitative data represents the full user base. If the council says "search is fine" but your analytics show 40% of search sessions end without a click, the council members may have adapted to the current search and do not notice its limitations. Use the conflict as a prompt for deeper research, not as a reason to dismiss either source.

If you have fewer than 50 customers, a formal council may be premature. Instead, build 1:1 advisory relationships with 4-5 key customers. Schedule monthly check-ins with each. Once you reach 100+ customers, formalize the program using this template. For early-stage products, the [Product Discovery Handbook](/discovery-guide) covers lightweight feedback loops that work with very small user bases.

Yes, with an NDA in place. Most council members expect and appreciate roadmap previews. Use a simple mutual NDA that covers the session content. Label confidential materials clearly. Avoid sharing exact launch dates (they will hold you to them). Instead, share directions and priorities: "We are investing in AI-powered insights in H2" is better than "We are launching AI insights on October 15." ---