A briefing goes out. A consultation deadline approaches. The secretariat sends a reminder, then another. It is tempting to read a quiet response as a lack of interest. First, check whether a busy member can see exactly why their contribution matters and what you need them to do.
Make each request relevant, specific and easy to act on. More communication is not automatically more participation.
Start with the member’s decision, not your attachment
A member representative may be balancing your request with a full internal agenda. A message headed “Documents for review” asks them to discover the purpose before they can decide whether to respond.
Instead, explain the issue and the contribution needed. For example: “We need practical examples of how the proposed requirement would affect your operations. Please answer the three questions below by Thursday so we can prepare the working group discussion.”
This gives the reader a reason to act, a defined task and a connection to the association’s next step. It also helps them identify the right colleague if the request falls outside their own expertise.
Reduce the work required to participate
Separate essential reading from background material. Link to a stable location for the relevant documents, identify the current version and make the questions easy to find.
Check the request from the member’s perspective before sending it.
- Is it clear which members or specialists should respond?
- Can the reader understand the request without opening several attachments?
- Is the expected response defined: an example, a comment or an approval?
- Is the deadline visible, with enough context to explain why it matters?
- Is there one clear place to contribute or ask for clarification?
A shorter request is not always a better request. The aim is to remove unnecessary interpretation while keeping the context needed for an informed contribution.
Create a rhythm people can recognise
Distinguish an action request from an update that is simply useful to know. If every message appears equally urgent, members must work out the priority themselves.
A regular digest can help members keep track of developments without treating every new document as a separate interruption. Topic choices can make updates more relevant to different responsibilities within a member organisation.
Keep urgent requests explicit, and make sure members know how ordinary updates are organised. The communication pattern should become familiar enough that they can judge what needs their attention.
Close the loop after members contribute
Explain what happened to the input. Share the resulting document, summarise the main themes and clarify what remains open. If suggestions could not be taken forward, explain the constraints where appropriate.
Participation becomes more meaningful when members can see how their effort informed the association’s work. A request followed by silence gives them little basis for deciding whether the next request deserves time.
Review participation with care. A document view is not an endorsement, and a download is not proof of influence. Combine available activity information with direct conversations about whether members can find, understand and act on what you share.
ONE PRACTICAL STEP
Start here this week.
Rewrite your next member request around five elements: who it is for, why it matters, the contribution needed, the deadline and what will happen afterwards.
PUTTING IT INTO PRACTICE
Members Cloud brings documents, comments, discussions and member updates into one space. A demo can start with a real participation challenge from your working groups.