01
Career growth
The first-five-years member building a career, a network and a reputation.
Member experience field guide
The member experience nobody designed
Your members already experience every gap between your teams, processes and systems. The question is whether anyone designed what happens there.
By Glen Rosie · developed from an Associations Forum talk
One member. Four systems. The same detail, asked for again.
Members do not see your stack. They feel whether their story travels with them.
Chapter one · the gaps between systems
The accidental experience.
Nobody sits down and designs a poor member experience. It happens by default – in the spaces between systems, where the member’s story stops travelling.
The gaps between systems are experienced by members as indifference.
A Frequent Flyer books a flight. The program knows his tier, his points, his birthday – and forgets his meal, every single time.
Times he has re-told them: 0
Next booking – the loop starts again.
Step 1 of 5 · Member
Every booking starts the same way – signed in, status recognised, points ready to earn.
Tap any step to read its part.
Your members have their own “typing gluten free in again” moment. They do not know your events platform and CRM are separate. They know they have told you the same thing four times.
Different reasons, different journeys
Members join for a reason.
One association sent the same weekly newsletter to the member building a career and the 30-year veteran winding down. Open rates fell, clicks fell, engagement fell. The technology worked. The story did not.
02
Connection
The member who joins to belong – community, peers, a place in the profession.
03
Credibility
The member here for education, standards and the letters after their name.
+24%
email open rate
+31%
click-through
+15%
average time on site
The fix was not new technology. It was three clear member stories, shared categories across the website, portal and email tool, and the freedom for members to choose what they hear about. Relevance is not the opposite of being front of mind. Irrelevance trains people to stop listening.
If you cannot articulate three member stories, you have a communications calendar – not a member experience strategy.
One sale, five people
Where the staff time disappears.
A member buys an event ticket and asks to pay on invoice. Nobody does anything wrong, but the untreated handoff turns one ticket into five people’s problem.
One association found this so painful they removed pay on invoice entirely. The member experience had been designed by operational convenience.
A member buys an event ticket and asks to pay on invoice – the only payment method available to them.
Staff time: ~0 min
Who can see the status:◉ Member◌ Event manager · in the dark◌ Accounts · in the dark
Step 1 of 6 · Member
The member registers for the event and ticks pay on invoice. So far, so normal.
Tap any step to read its part.
Closing the gap did not remove people. It moved their time into member-facing work that members could actually feel.
The lifecycle, honestly
Design the journey before it designs itself.
Retention starts at join. The first 30 days shape the first renewal, participation becomes a habit, and drift appears months before a lapse – if anyone is looking.
This is not a call for more technology. A spreadsheet is a perfectly good system if the whole story lives there and everyone uses it the same way.
- Join→
- Onboard→
- First value→
- Habit→
- Renewal→
- Advocacy
The quiet path
- Drift→
- Lapse→
- Maybe re-engage
For each stage, ask which system owns it and who owns the handoff. The gaps live at the handoffs.
The worked example
Sarah’s first 90 days.
Sarah’s experience crosses six teams and systems. Each interaction looks reasonable in isolation. The gaps only become visible when her whole story is plotted in one place.
AMS
membership
Website
portal
Events
platform
eDM
newsletter
Finance
package
Staff
manual work
Day 0Day 30Day 60Day 90Day 335…
Joins online
No 30-day check-in
…silence…Next day: portal shows no event, no ticket, no details
Browses continuing education courses
Registers for an event
Attends. Great night!
Generic welcome email
Retirement-planning feature
Opens drop off
Payment receipt (auto)
Manual credit note raised
Renewal invoice
Sarah emails to fix the price
Worked wellFriction / genericBroken / gap
The gaps
Sarah, 29, early-career, joins for education and networking. Each red gap is a place two systems don't talk – and to Sarah, every one of them just feels like indifference.
Tap any red gap to read its part.
Earlier than renewal
Three signals to watch.
Renewal rate is the autopsy, not the diagnosis. These signals give your team time to pay attention while attention can still change the outcome.
01
Time to first value
Join date to first meaningful interaction. If it is more than a fortnight, your onboarding is a receipt and a newsletter.
02
Drift signals
Declining opens, no event in months, unused benefits. The lapse is announced long before it happens.
03
The gluten-free metric
How many times does a member have to re-tell you something you already know?
The other half
Now watch it go right.
Everything above is the experience nobody designed. The companion piece follows the same member through a fortnight on one record, showing what she does and what her association learns from it, side by side at every step.
Fourteen days on one record →One member, properly seen
Attention is the point.
An airline with billions forgot Glen’s meal. A volunteer-run cricket club noticed his 200th game and ten years on the committee. The difference was not budget or technology. It was whether someone could see the whole story.
The club had a scorebook, a spreadsheet and someone who cared. Integration is not the point – it is how attention becomes scalable.
Member milestone
200
games played
Recognised
Do you know which member reaches 20 years next month?
From insight to a working map
A method you can use on Monday.
Start with one real member, follow what they experience, and fix the handoff they feel most. The method is deliberately smaller than a transformation program.
01
Write the stories first
Three user stories for your key cohorts. Design starts with who it is for, not what systems you have.
02
Map the lifecycle against your systems
Every handoff is a design decision currently being made by nobody.
03
Pick the gap the most members feel
Prioritise by member impact, not internal annoyance.
04
Fix by connecting, not buying
Shared structure, agreement on use, sync where it matters.
05
Instrument it and watch
Three signals plus milestone attention, so the design keeps up as members change.
The Monday questions
Start with what your team can already see.
Use Miro, FigJam, Whimsical, Smaply or butcher’s paper. The map matters; the tool does not.
- 01
Pick one real member. Can anyone on your team tell their whole story – joins, events, courses, emails, payments – without opening more than one system?
- 02
What happens in a new member's first 30 days, and who designed it? If the answer is “an invoice receipt and the newsletter”, that is your biggest gap.
- 03
Do you know why your members joined – and could a member in year 1 and a member in year 30 tell the difference in how you treat them?
- 04
What does your team maintain manually that two of your systems each half-own? That is the stack serving itself, not your members.
Practical appendix
Benchmark your next RFP.
Seven outcomes to demand, not features to tick. Score your current systems first, then let the gaps write the useful part of your next brief.
If a vendor cannot demonstrate an outcome with your data in the room, it does not count. Answer for the systems your team uses today.
Seven outcomes. Start anywhere.
01Data flows both ways, always
02One member, one record, one story
03The member controls their own experience
04The system tells you, you don't ask it
05Staff are never the integration layer
06It plays well with others – including your next system
07Your team will actually use it
No single system does all of this equally well. Look for where a vendor is strong, where they are honest about being weak, and whether the gaps land on things your members will feel.
One real member is enough to begin
Bring us the experience nobody designed.
We will map one member journey with you, find the handoffs your members can feel, and work out whether the next useful step is process, connection or technology.
No need to have the answer – bring the member story you cannot quite join up.