Renewals came in soft. The membership committee wants to know whether it is the economy, the dues increase or the value proposition, and the discussion runs forty minutes. At some point somebody says the renewal form is fine, they used it themselves last week.
They did use it. They used it signed in, on the office network, on a desktop, already knowing their member number, with a staff account that skips two of the steps a member sees. That is not a test. That is a demonstration.
Where this sits. This is the fourth of six posts on digital strategy. It covers three pages that carry most of your revenue and receive less scrutiny than your homepage, which carries none of it.
Staff Cannot See This Site
Everyone who works at an association is the worst possible test subject for its website, and the reasons compound.
- Staff are permanently signed in. Which hides every problem in the login, the password reset, the session timeout and the return path after authentication. Those four account for a large share of what we find.
- Staff know the internal vocabulary. Members do not know whether your education arm is a separate entity, that the event calendar is a different system, or what you call the thing they want. They search for what it does.
- Staff are on the office network on a desktop. Members join at home at nine in the evening on a phone, using a personal card, having arrived from an email link that opened in an in-app browser.
- Staff accounts are not member accounts. Staff accounts frequently bypass payment, skip required fields or carry permissions that shorten the path.
The Three Flows
Joining, renewing and registering are different problems and get treated as one line item in a redesign scope.
Joining. A stranger, no account, no history. Every field you require is a reason to stop, and the required fields on most association join forms were chosen by whoever configured the AMS rather than by anyone accountable for conversion. We regularly find required fields that a prospective member cannot answer at all, such as chapter affiliation or a membership category that assumes knowledge of your structure.
Renewing. A known member who has already decided. This should be the shortest transaction on your site and it is frequently the worst, because it begins with an email link, which requires a login, which lands on a dashboard rather than back on the renewal, at which point the member has to go find it again. Every hop loses people who fully intended to pay you.
Registering. A mixed audience, members and non-members, often at a price difference large enough that the member has to prove who they are before seeing the right price. That proof step is where registration breaks, and it breaks worst for the lapsed member you most want back.
What Actually Breaks
The failures we find most often are not design failures. They are seams between systems that each work correctly.
- The handoff to payment. Where the payment step opens in a new window or a vendor-hosted page and the return to your site fails, leaves the member on a blank confirmation, or completes the charge without completing the record.
- The return path after login. A member who signs in from a renewal link should land on the renewal. Landing on a profile page is the most common single defect we see in this area, and it is usually a two-line fix nobody has been asked to make.
- Session timeout during a form. Long forms plus a short session equals a member who fills everything in, gets signed out, and loses it. This is almost never noticed internally because staff sessions are refreshed constantly.
- The email that confirms it worked. Confirmation emails that go to spam, or that arrive from an address the member cannot reply to, generate a phone call for every silent failure and a lapse for every member who does not call.
One Member, Four Logins
Underneath all three flows is a question most associations have answered accidentally: how many separate places can a member sign in, and do those places agree about who they are.
A typical stack has the main website, the AMS member portal, the learning platform and the event registration system, and it is common for at least two of them to hold their own credentials. Members do not experience that as four systems. They experience it as your website asking them to sign in again for no reason, and then telling them their password is wrong when they are certain it is not.
Why this is a strategy question and not a convenience one. Single sign-on is the usual fix and it is not only a convenience feature. It is what makes the rest of the strategy possible, because it is the thing that lets behavior in one system attach to a known member in another. Without it your analytics cannot see members, your renewal campaign cannot see engagement, and each flow has to ask the member to identify themselves again at exactly the moment they are most likely to give up.
The version that fits a real budget. If single sign-on is genuinely out of reach this budget cycle, the interim version is worth doing: one password reset path that works, one place that is unambiguously the front door, and clear signposting when a member is about to be handed to a different system so the second sign-in is expected rather than alarming.
What Good Looks Like
Member experience is in reasonable shape when these are true:
- Somebody outside the organization can finish all three flows. Joining and renewing complete on a phone, off your network, without a call. Tested by a person who does not work for you.
- You know the completion rate. Not the traffic to the form. How many people started it and how many finished. Most organizations cannot produce this number, which is why the flows go unexamined.
- The required fields have owners. Every required field on the join form has a named reason and somebody who will defend it. Fields inherited from a form design nobody remembers are the cheapest conversion gain available.
- The website and the AMS agree about who is a member. So a member who pays does not also have to tell you they paid, and a member who lapses is not still receiving member pricing.
- Somebody tests the flows after every platform change. Scheduled, not triggered by a complaint. The systems underneath these flows update on their own timetable and a working flow does not stay working by itself.
How to Tell Where You Stand
Four questions. None of them require a vendor:
- When did a non-staff person last complete your join flow? If the answer is never, that is the finding, and it is the most common answer we get.
- Who is accountable for the renewal completion rate? If nobody owns it, nobody is watching the number that most directly predicts next year.
- How many fields does joining require? Count them. Then ask what each one is for. Then ask what happens to the answers.
- Can a lapsed member tell they are lapsed? Members frequently do not know which they are, and an organization that cannot tell them quickly has already lost the transaction.
Join Your Own Association
Do this before you call anybody. Take a personal phone, leave the building or turn off the office wifi, use a private browsing window and an email address that has never touched your systems. Then join, at full price, with a real card. Have someone time it and write down every moment you had to think. Do the same for a renewal and an event registration, using a test member account that has the permissions of an actual member and not of staff.
Most executives who do this exercise stop it partway through and go find somebody, which is the point. If you would rather we did it, we run the three flows as an outsider, on a phone, and send back a screen recording with a time-stamped list of every place the flow stalled, along with which failures are configuration, which are integration and which are content. We do not need access to anything to do it. It is the same walkthrough we run at the start of every partnership, because it is the fastest way to find out what a year of small reasonable decisions has added up to.