Navigation labelled “Policy”, “Professional Development”, “Governance” and “Membership Services” may describe the organisation accurately. It can still make a member translate their task into an internal department before they find help.
A member-centric site is organised around people's needs, language and context while preserving the organisation's public, regulatory and governance responsibilities. It is not a homepage containing only the most popular links.
Find the real tasks
Begin with several evidence sources because each is incomplete.
Support tickets and call reasons reveal moments when digital service was absent, failed or felt less convenient. They do not show people who abandoned without asking for help, and some contacts require a person by design.
Site search reveals the words visitors use. A search for “CPD certificate”, “invoice” or “renew” may indicate weak navigation, or simply an efficient preference for search. Examine whether the result led to successful completion.
Analytics can show entrances, exits, paths and errors. An exit from a completed task is healthy. Define funnels around real journeys before interpreting drop-off.
Staff hear recurring member questions and understand policy constraints. Members reveal how the experience feels. Use task-based research with a varied sample across career stage, membership type, access needs, digital confidence and organisational role.
Ask participants to complete a realistic task with their normal device. Observe before explaining. Follow with questions about expectation, meaning and confidence. Avoid turning a handful of sessions into a percentage for the whole membership.
Write a task inventory
Combine the evidence into statements in the member's language:
- renew or change my membership
- obtain an invoice or receipt
- record and evidence professional development
- find current guidance on an issue
- book, change or cancel an event
- update my details and communication preferences
- understand a professional requirement
- contact a relevant person or peer group
For each task, record audience, frequency, consequence, current route, owner, evidence and known barriers. Include infrequent high-stakes tasks; popularity alone should not determine priority.
Group tasks by purpose and mental model, not the team delivering them. Test proposed labels through card sorting, tree testing and task observation. Plain wording usually outperforms branded internal names, although research should decide.
Map journeys beyond pages
Booking an event includes discovery, eligibility, price, registration, payment, confirmation, calendar, access, cancellation and possibly professional-development evidence. A site map covers only some of that service.
For each priority journey, trace:
- trigger and entry channel
- information and decisions required
- systems and teams involved
- authentication and permissions
- confirmation and status
- exceptions and route to help
- record the member needs afterwards
Identify repeated data entry, unexplained hand-offs, separate credentials and manual work. Improving a navigation label will not fix an event platform that loses context at login.
Design for returning members
The public homepage must serve prospects, media, employers and other audiences. A signed-in member often has a narrower purpose.
A useful account view may surface current tasks, bookings, learning records, saved guidance, renewal status and relevant communications. Personalisation should start with known membership facts and explicit preferences, used transparently.
Do not infer sensitive interests or make consequential decisions from sparse behaviour. Give members control over recommendations and channels. Provide a usable unpersonalised route.
Mobile, keyboard and assistive-technology use must be tested across the complete journey, including third-party systems. A main site that meets accessibility requirements cannot compensate for an unusable payment or learning step.
Resolve the internal politics explicitly
Primary navigation is scarce space, so it often becomes a proxy for departmental status. A team may fear that losing its label makes its work less visible.
Separate two decisions:
- How should members find and use the work?
- How should the organisation recognise, report and govern that function?
The website should solve the first for its audiences. Annual reporting, governance pages, newsletters and internal communication may help with the second.
Use research evidence and agreed design principles. Show that content can become more discoverable under member topics even when a department name leaves the main menu. Measure findability before and after.
A senior sponsor needs authority to resolve trade-offs. The sponsor should protect member outcomes while ensuring statutory, policy and corporate information remains appropriately available.
Build content governance around questions
Restructuring the menu without changing content moves the problem. Audit pages for audience, task, owner, currency, evidence and next action.
Translate internal terminology without losing professional precision. Define acronyms. Use titles members search for. Mark dates and superseded guidance clearly. Link related content by task and topic.
Assign subject ownership and editorial ownership. Subject experts protect accuracy; content specialists protect clarity, structure, accessibility and consistency. Establish review and retirement, since an easier-to-find outdated page creates more harm.
Avoid publishing the same guidance under several departmental sections. Use structured content and references where one source should appear in multiple journeys.
Measure member success and organisational effect
For each priority task, establish evidence such as:
- success and time to complete
- errors, abandonment and repeat attempts
- support contacts and reasons
- use of assisted routes
- comprehension and confidence
- accessibility failures
- operational processing and rework
Connect improvements to cost and retention carefully. A fall in support calls may indicate success or suppressed access. Renewal depends on proposition, price, employer support and many other factors. Use journey evidence, cohort analysis and member conversation before attributing change to the site.
Value should remain visible throughout the year, through access to learning, evidence, events, community and support. Avoid engineered renewal friction or claims that renewal should become automatic.
A three-week diagnostic
In the first week, classify top-level navigation and high-use pages by internal function or member task. Review content ownership and obvious accessibility or currency problems.
In the second, combine recent search, analytics and support data. Record definitions and limits. Recruit members for research.
In the third, observe priority tasks and map five journeys end to end. Produce a short list of immediate fixes, operating changes and larger platform constraints.
Immediate work may include clearer labels, task links, error messages and content consolidation. Deeper work may involve identity, system integration, account design and data governance. Distinguish them before proposing a rebuild.
The member-centric information-architecture audit checklist available with this article offers a quick initial review. A facilitated journey-mapping session can bring members, service teams and system owners together around the evidence. The decisive question is simple: can people accomplish what membership enables without first learning how the organisation is arranged?
