An invitation to give feedback can mean very different things. An organisation may want to understand a practical difficulty, test an explanation or find a story that makes its work visible. Those purposes should not be blurred simply because the same person could contribute to each. In healthcare service communication, I want someone to be able to describe what they found confusing without feeling that their participation also makes them available for a public account of the organisation.
That position is partly about the quality of what we learn. If the invitation is framed around a favourable story, it may become harder for a participant to describe an inconvenient experience or say that a proposed explanation still does not help. It is also about responsibility. A person who has agreed to discuss an administrative route has not thereby agreed to supply a quotation, photograph or account of their care. The organisation needs to decide what it is asking before it invites someone to take part.
Agree what the invitation is for
In May 2026, we established a six-month listening programme about practical service information at Orlaven Health. An early suggestion was to combine the feedback work with stories that might be used in publicity. I separated the activities. The programme would use fictional tasks and general access questions, without collecting clinical histories for marketing purposes. Participation would help us examine explanations and contact routes; it would not create permission to feature the person in advertising or imply an endorsement of the service.
Sixteen people were invited through an agreed participation process. Thirteen accepted and three declined. The A$95,000 budget covered coordination, accessible meeting arrangements and participation support under the programme's terms. It was not payment for favourable statements. I wanted those facts clear inside the organisation as well as in the invitation, because an internal misunderstanding can reappear later as a request that the participant reasonably did not expect. The programme team needed a shared account of the purpose it had promised to honour.
The selected group was not a representative sample of everyone who might use the service. Its contribution could reveal useful questions without establishing how common each difficulty was. I regard that as a strength when it is reported honestly: a small discussion can make an overlooked issue visible and help the organisation decide what to examine next. It becomes misleading when the group is described as speaking for an entire population or when a useful observation is converted into a percentage that the method cannot support.
The invitation also needed boundaries around what the group would discuss. Marketing could examine whether an administrative explanation was understandable, but it could not use the session to settle a clinical question. Participants should not have to reveal personal health information to make a useful contribution to a fictional task. The relevant professional and service colleagues helped define the work so that a general communication discussion did not drift into advice or review for which it was not designed. Those boundaries made the programme more focused, not less attentive.
Separate the suggestion from the decision and the change
By October, two of the three planned sessions had taken place. They produced eleven recorded suggestions about explanations and contact routes. Five were accepted within marketing's remit, four required further operating review and two could not proceed in their proposed form because they changed matters belonging to clinical owners. Those categories described the decisions on suggestions. They did not describe completed implementation. Keeping the two accounts separate prevented a favourable response in a meeting from being presented as a finished change to the service information.
Of the five accepted communication changes, three had been published and two were still being prepared in October. The four items under operating review remained open. I wanted participants and internal sponsors to see that position without needing to decode an optimistic project summary. An accepted idea can still require editorial work, specialist confirmation or changes in several publications. If the organisation counts it as completed at the moment it agrees, the report loses contact with the experience the participant was trying to improve.
Not adopting a suggestion also deserves an intelligible explanation. The two items that could not proceed as proposed were not dismissed because the participants had asked an inconvenient question. They crossed into decisions that marketing could not make through a communication programme. We could explain that boundary and consider whether a different administrative explanation would help, without promising a clinical change or using the group's interest as authority for one. Listening seriously does not require pretending that every recommendation belongs within the listener's power to implement.
The same care applies to ideas that appear easy. A wording change might solve one difficulty while creating another ambiguity for a different reader. I want the responsible team to consider the purpose, affected material and necessary review before treating a suggestion as an immediate instruction. That is not an excuse to delay indefinitely. It is a way to connect the participant's contribution with a decision someone can own and explain. Where more work is needed, the next step and its responsibility should remain visible.
Close the conversation without manufacturing agreement
A feedback programme can fail its participants after the session even when the discussion itself was well run. If people hear nothing further, they cannot tell whether their contribution mattered or disappeared into a report. I therefore wanted a return account showing what had been accepted, what remained under review and what could not proceed in its proposed form. The account should not ask participants to endorse the organisation's response. They may still disagree, and that disagreement should not erase the value of what they helped us examine.
I also resist the pressure to finish the story before the programme has finished its work. In October, the third session was still scheduled and two accepted changes were still being prepared. The record is therefore provisional. We can explain the decisions already taken and the resources committed without supplying an invented final result. There is no measured clinical benefit attached to this listening work, and no claim that the published changes have resolved every access difficulty. A responsible leadership account should be comfortable with that unfinished position.
For a CMO, the discipline is to protect the purpose of listening when another use of the material would be convenient. A campaign team may see an appealing human story, while a programme sponsor wants a simple success statement. Neither interest should silently expand the participant's agreement or the evidence available. I want service feedback to improve the organisation's questions and explanations first. The value of a person's contribution does not depend on whether it can become a public quotation, and the integrity of the programme depends on remembering that after the session is over.