A customer advisory board is not the whole market
Define a customer advisory board's role, interpret its feedback in context and explain how the company used participants' views.
Article language: English

In this article
Your closest customers know the company better than a random survey respondent. They know what happens after a purchase, which workaround is effective and who actually solves difficult cases. That knowledge is valuable. It can also obscure the experience of someone who is still trying to understand the offer and does not have the right person's number in their phone.
A customer advisory board is a continuing group that a company returns to with particular questions. It does not represent the whole market or make the company's strategic decisions for it. Its value lies in access to experiences worth considering together. If a meeting serves only to announce a finished plan and collect polite praise, calling it a board will not give it an advisory voice.
Imagine a company that produces industry reports and information materials. It wants to develop how people use its service and how it describes its offer. It invites several existing customers to periodic discussions. It needs to make clear what it is asking them, who takes part, how the company makes its own decisions and what it will later say about the use of their feedback. Participants should not have to guess whether they came to advise, buy or approve somebody else's schedule.
A selected group has a particular point of view
The 2023 Google Cloud Customer Advisory Board charter describes direct invitation and appointment for a specified term. It is a document for one programme, not a universal template for an advisory board or an account of its current calendar. It illustrates a deliberately selected group of people that should not be confused with a random sample of the whole market.
In our example, selecting only the largest customers would give the company access to their experience while leaving other questions open. A smaller organisation may use a report differently. Someone starting a relationship may not know abbreviations familiar to long-standing customers. The company should record whose perspectives are present and who is missing from the discussion. A variety of industry names alone does not guarantee a variety of ways of using the service.
Explain the reason for each invitation. It might be a particular context of use, responsibility for choosing the material or experience introducing it within an organisation. Avoid reducing participants to the size of their account. A job title alone does not tell you whether someone knows the daily work involved in using the service or can explain the issue the company plans to raise.
The six Signal articles linked below are in Polish.
Not every decision calls for a board. If the company needs the detailed history of one task, individual customer interviews (in Polish) may be more suitable. A continuing forum has a different advantage: it allows people to return to earlier comments and see a changing context. A long relationship is part of its design and, at the same time, a limit on generalising its views.
Advising does not transfer responsibility for the plan
In the fictional company, the board can help reveal how recipients pass a report on to colleagues. It can identify difficulty finding the right version or describe the needs of a new department. It does not have to decide which project the company will fund. Participants know their own needs; the organisation is responsible for weighing those against its capacity, strategy and other commitments.
Explain that division before the first conversation. Feedback will inform a decision, but not every suggestion will become commissioned work. If the company makes a commitment to a particular customer, that needs its own appropriate route to agreement. Board notes should not accidentally promise delivery of something the group has only discussed.
The December 2024 OpenText programme charter describes responsibilities for participants and the organiser. Among the company's responsibilities are materials before meetings and later updates about changes affecting matters on which members provided input. It is a useful example of a two-sided commitment to the conversation, not evidence that every suggestion must be implemented.
When recording project priorities with a limited team (in Polish), the company should also show its own criteria. The number of votes in a meeting can be information about that group. It does not automatically become an assessment of the whole customer base or a sufficient reason for the order of work, especially when the proposed direction concerns people who were not invited to the board.
A good question lets people describe use
Our company might bring the question: "What happens to the report after it reaches its first recipient?" It is more specific than "What features do you need?" Participants can describe who reads the material, what they pass on and where context gets lost. Later, the group can consider different ways of supporting that situation.
Ask for experiences before showing a proposed solution. In our example, one person may use the whole report, another forward selected extracts and a third prepare their own summary. The facilitator should preserve these different routes in the notes. A prepared proposal should not immediately cover them up.
If the company wants to show a concept, explain its status and the question it is being shown to answer. Is the company checking whether people understand the variants? Whether a new way of accessing the material makes sense? What someone needs before buying? Participants should know what their feedback can usefully address. An opinion about the appearance of a mock-up will not automatically answer a question about the report's role in an organisation's work.
Provide enough material for a conversation without turning it into a long sales presentation. If most of the time is spent presenting the provider's plan, detailed understanding of customer experience is harder to obtain afterwards. The company does not need to hide its direction. It does need to leave room for information that might challenge that direction or reveal a previously unknown condition.
Agreement within the group still needs interpretation
Suppose everyone invited responds positively to the idea of a thematic package. The company can record their reasons and the situations in which they see a use for it. It should not immediately announce demand in a new segment. The group may consist of experienced customers who know the current material and assess the effort of starting to use another option differently.

If someone says, "This will definitely catch on," ask what that is based on. Are they describing their own intention, an observation of colleagues' behaviour or a guess about other organisations? Calibrating a team's forecasts (in Polish) helps distinguish a suggestion from a prediction of a specific event. Agreement on the board does not automatically give a prediction the right degree of confidence.
Keep differing views. If one organisation needs independent access and another needs regular discussion with an account manager, that difference may describe two ways of using the service. They do not have to be averaged immediately. Record the task context and reason for each preference. The company can then address a real difference instead of creating an option nobody can describe clearly.
Do not treat the board as the only channel for questions. Analysis of customer enquiries (in Polish) preserves another source: cases that actually reach the company. Comparing them may reveal a question absent from the meeting. That does not prove the board is failing. It shows the limit of one way of gathering information and the need to consider it alongside other material.
One person's voice has a specific scope
Return to the company producing reports. Suppose a board member orders material for the whole organisation. They know why it was purchased but do not follow how every user reads each chapter. They may be well placed to discuss the choice of scope, yet unable to reconstruct another department's daily task. The notes need to preserve that difference rather than presenting their statement as an account of every recipient.
For an important point, record whether the participant is describing their own experience, passing on information collected from their team or proposing a direction to investigate. There is no need to challenge every statement. There is a need to know what it can be applied to. If a question concerns another group's work, the appropriate outcome may be a request for a separate conversation with a representative of that group, not pressure on the board member for an immediate answer.
Imagine also that a participant changes professional roles. They still know the service, but their current tasks and needs may differ. The company should revisit the reason for the invitation and the scope of future discussion. A stable membership does not necessarily mean a stable point of view. In our example, someone who once used a whole report may now decide which several materials to buy for a team. The organisation's unchanged name on the attendance list will not explain that shift.
Do not turn silence into agreement in a shared summary. If only two people responded to a particular question, record their reasons and the absence of responses from the others. The company can return to the subject another way or recognise that more material is needed. A note saying "the board supports it" would blur what actually happened in the conversation. The detailed account need not be long; it should let the company understand the basis for a later decision.
A continuing conversation requires a response
After the meeting, separate a record of experience, a participant's proposal and the company's decision. If a change has been accepted for further investigation, call it that. If it has been deferred, give the reason to the extent it can be shared. If a particular customer's case needs a conversation, direct it to the right person. The board does not have to become a shared queue of individual requests.
At the next contact, return to several earlier points. What was clarified? What changed in the company's thinking? What material still needs to be gathered? This continuity helps participants see the value of the time they gave. The company does not have to announce a completed implementation to show honestly how it used feedback. Sometimes the result is abandoning an assumption the company had not previously recognised.
A review of the relationship with a particular customer (in Polish) remains a separate task. That is where the parties can account for their agreed scope and the open matters in that relationship. A board returns to a broader question about the service's direction. Keeping a separate route avoids burdening the group with details that require an individual solution.
Do not assume that participation also means consent to promote the provider. A reference conversation with a company's customer (in Polish) has a different purpose and requires its own agreement. An advisory account of difficulties should be able to remain advice rather than unexpectedly becoming a sales endorsement after the meeting.
How to use feedback on the offer page
If the board reveals that the difference between variants is unclear, the company should first establish how it actually distinguishes them. Only then should it revise the description. Imagine that "thematic package" is enough for regular customers, but new visitors do not know what material they will receive. The page needs to show the contents and how they are used rather than assume board members' experience is shared by every visitor.
With Aeneia Design, documented customer questions and approved differences between offers can be a starting point. The work concerns translating them into content architecture, descriptions of the variants and a clear contact route on the site. The company supplies the decision about the direction of the service; customer discussions help identify what the page needs to explain better.
Aeneia Design
Bring customer questions and the approved scope of each service variant. We will organise the offer description and the route that helps a visitor recognise the right option and the next step.
Turn customer questions into a clearer offer
A customer advisory board can give a company a conversation worth returning to. It needs a clearly defined question, a boundary to its influence and an honest response after the meeting. Close contacts do not have to become the whole market for their knowledge to matter. The important thing is to understand whose experience they are describing.










