The key points

  • Start with an everyday task that solves a recognisable member problem.
  • Support the people publishing content as well as those using it.
  • Look at successful tasks and useful feedback, not just login counts.

An activated account does not prove usefulness

The launch went well. Invitations went out. Members signed in. A few weeks later, document requests still arrive by email. This does not necessarily mean people reject the platform. They may not have found a clear reason to return, or the journey may feel harder than asking the secretariat.

The leadership question is practical: which task does the platform make easy enough to establish a new habit? Choose a recognisable, recurring use rather than a general ambition to “digitise member relations”. If the scope is unclear, start by distinguishing document sharing from organised collaboration.

Give members a first reason to come back

A committee is preparing its next meeting. Participants need the date, the papers and a place to find practical information. That is a stronger starting point than a tour of every feature. The invitation can link directly to the useful material; the next meeting creates a natural reason to return.

For a small association, the first task might be finding the latest sector briefing in a clear shared space, the purpose behind MembersCloud’s document sharing and engagement tools. For several active committees, the need may extend to cooperation, the agenda and reusable knowledge, making MembersDesk’s wider working environment a more relevant scope.

Test the first journey with real members

Do not restrict the pilot to administrators who already know the structure. Include representative users: an active member, an occasional participant, a new delegate and someone mainly using a phone. Give them a specific task and watch where they hesitate. Repeated hesitation often points to language, access or structure that needs attention.

The W3C recommends involving users in web projects, including to understand accessibility needs. In your pilot, look at readability, keyboard navigation and the meaning of labels. One participant’s feedback cannot replace a complete evaluation, but it can uncover barriers that an internal demonstration misses.

Organise publishing as carefully as training

Training members to use an empty space achieves little. Prepare the resources needed for the first task, use understandable titles and assign someone to maintain them. Who replaces an old version? Who publishes meeting information? Who retires outdated material?

Adoption depends on that consistency. If email contains the correct document and the platform an old copy, members learn to trust email. Explain where the reference version lives and use communications to lead people there. Email remains useful for drawing attention; the member space should make the content and its context easy to find again.

Use a communication rhythm that fits the work

A platform can disappear from view without reminders, or become tiring if every publication sends an email to everyone. Organise communications around topics, groups and the preferences available in the tool. A digest and an immediate alert serve different purposes; choose according to the information involved.

Connect each message with a clear next step: read a briefing, prepare for a meeting, comment on a document or find a resource. Newsletters can showcase the secretariat’s work and bring people back to useful content. Email volume is not an engagement objective; relevance matters more.

Measure use that helps people do something

Logins signal activity, but do not show whether people found what they needed. Depending on the information available, also examine resources consulted, tasks completed and recurring requests for help. Add short conversations: what were you able to do, and what did you still have to ask the secretariat?

Compare groups and periods that make sense. A committee with no meeting this month should not be judged against a group in the middle of a consultation. The GOV.UK Service Manual connects measurement with user needs and task completion. Adapt that thinking to your association’s working calendar.

An adoption plan the secretariat can sustain

Build the first phase around a pilot group and a defined task. Before access opens, check permissions and publish useful content. During the first use, support people who get stuck. After the first meeting or campaign, review difficulties, improve the structure and decide what can be extended to other groups.

Success does not require everyone to use every feature. It means the right members can complete their tasks and the secretariat can sustain the service without multiplying manual interventions. To choose a sensible scope, compare the member platforms or arrange a demonstration around your working day.

Further reading