Members come to your association website with one thing in mind: renew, register for an event, find a CE credit, log in to their account. But most association website navigation is built around the org chart (Membership, Programs, Education, About), so members have to translate their task into your departments before they can act. This post shows how to build navigation around what members actually do.
Your navigation is where members decide you are worth the trouble
Navigation is the first interaction every member has with your site, and the one they repeat most. A member who renews once, registers for two events, and hunts down a CE transcript touches your menu dozens of times a year. If that menu encodes your departments instead of their tasks, every visit charges a small tax. Lean teams pay that tax back as support tickets and “where do I find…” emails.
Here is the distinction that trips people up. Information architecture is the whole-site structure: the tree of pages, the categories, the labels underneath everything. Navigation is the system members actually click to move through that tree. You can have sound IA and still bury it behind a menu nobody can parse. This post is about the menu; the structure beneath it is the information architecture underneath it, which is its own job.
The stakes are not aesthetic. Your Join, Renew, and Login paths are your dues and non-dues revenue funnel. When those controls get demoted into a dropdown three levels deep, renewals stall and prospects leave. And member preference is not vague: WeAreTenet, summarizing standard UX findings, reports that 94% of users name easy navigation as the most wanted part of an online experience. Org-chart navigation is not a trade-off. It is a mistake.
Org-chart navigation is not a trade-off. It is a mistake.
How to build association website navigation around members
Start from the member’s top tasks, not the page tree
List the ten to fifteen things members actually come to do: renew, register for an event, find and claim a CE credit, update a chapter roster, pay an invoice, reach a human, log in. Pull that list from your AMS support tickets, the renewal inbox, and your site-search query logs, not from a staff brainstorm. Navigation exists to surface tasks. The upstream structure work already decided what the site contains; the menu decides which of those tasks earn a spot members can see.
The common mistake is asking each department which of its pages belong in the menu. Every department answers “ours, prominently,” and you rebuild the org chart in the menu bar. A member trying to claim a CE credit does not care which department owns the transcript. They care that the path is one click, not five.
Put Join, Renew, and Login where members already look
Place Join (or Become a Member), Renew, and Login as persistent controls in the top-right of the header, visible on every page. Make Login dynamic: once a member authenticates, it becomes their account or dashboard link with a Log Out option, and the Join prompt gives way to Renew when a membership is lapsing. The top-right corner is the learned location for account and conversion actions. PaidMembershipsPro, MemberSpace, and Join It all converge on it for a reason. Members do not hunt for a convention they already know; they only hunt when you hide it.
The common mistake is a single generic “Member Area” link that sends a lapsed member who wants to renew and a logged-in member who wants a transcript down the same undifferentiated path. Split them.
Pick a menu pattern that matches your real page count
Choose the pattern by the size of the structure behind it. Seven or fewer top-level sections: a simple horizontal bar. Eight to twenty pages with clear groupings: dropdowns. Twenty-plus pages or three-plus levels of depth: a mega-menu that shows the groups at a glance. Nielsen Norman Group’s menu-design research is blunt about the middle ground: simple dropdowns work for one tier, get frustrating at two, and are inadvisable past two, because users mis-hover and the menu collapses out from under them. Mega-menus let members see every option at once instead of remembering it, which is what a content-heavy association site needs.
A mega-menu makes a bad structure bigger and louder, not better.
The common mistake is bolting a mega-menu onto an org-chart structure. A mega-menu makes a bad structure bigger and louder, not better. Fix the structure first. That is the work behind how we approach association website design. Then choose the menu, and hold the top level to roughly five to seven task-based items.
Separate the prospect path from the member path
Design two distinct journeys off the homepage. Prospects need one sequence: what is this, why join, how much, join now. Members need another: renew, register, my account, my CE credits. Use the Login state to flip the experience. A logged-in member should land on member tasks, not a marketing pitch they converted on years ago. One menu trying to serve both audiences serves neither. The prospect drowns in member-only links; the member wades through join-us messaging. This is not a phase-two upgrade. It is the difference between a menu that knows who is reading it and one that does not.
The common mistake is treating the homepage as a recruitment poster, so existing members, who are most of your traffic, have to navigate around the sales pitch to do their actual business.
Design mobile navigation as a real layout, not a collapsed afterthought
Decide what lives behind the hamburger and what stays visible. Keep the highest-value actions (Login, Renew, search) reachable without opening the menu, using a persistent header control or a bottom bar of three to five core destinations. Make the hamburger discoverable; label it “Menu” if the icon alone is not pulling its weight. Flatten deep hierarchies so a member is not tapping four times to reach a CE transcript. Nielsen Norman Group has measured this: hidden navigation reduces discoverability and engagement compared with visible navigation, and on mobile members are more likely to go straight to search. Whatever you build has to support keyboard and screen-reader access to the menu, not just touch.
The common mistake is shipping the desktop mega-menu jammed into one hamburger with every department expanded. The org chart returns, now on a 390-pixel screen.
Make site search a real fallback, not an excuse for weak navigation
Give members a visible search box, not a hidden magnifying-glass icon on desktop, mine its query logs every month, and feed what members repeatedly search for back into the menu. If “CE credits” is a top search, it should be a menu item. Roughly 30% of users go to search first, and both AddSearch and Doofinder report that search users convert at a markedly higher rate. But “members can just search” is what teams say when they have given up on structure. Search and navigation should reinforce each other: search reveals the gaps the menu should close.
“Members can just search” is what teams say when they have given up on structure.
The common mistake is treating the search box as a substitute for a clean menu. Good navigation removes the searches that should never have been necessary.
Test the navigation with real members before you ship it
Run a tree test (labels only, no design) and give members real tasks: “find how many CE credits you have,” “renew your membership.” Measure whether they reach the right destination. Add first-click testing to see where instinct sends them on the first tap, because the first click is the strongest single predictor of task success; tree testing validates the labels and paths against real tasks rather than staff consensus. Fifteen to twenty members give a clear signal.
The common mistake is validating the menu with staff, who already share the org-chart mental model you are trying to escape. We treat navigation as something you prove with members, not something you settle in a stakeholder meeting. Test the people who will use it.
Where member-centered navigation quietly slides back to the org chart
Menu creep sets in between launch and six months later. Each department lobbies to add “their” link back to the top nav, and within a year you are at eleven items again, itself a sign your site needs a redesign. Fix it with one owner for navigation and a rule that any new top-level item requires removing one.
Another failure is a login that drops members into a marketing site. SSO works, the member signs in, and the menu still shows join-us messaging instead of their tasks. Test the whole authenticated path, not just the login button.
Mobile parity gets neglected too. The desktop menu gets the task-based redesign while mobile keeps the old collapsed dump. Most member traffic is mobile, so test there first, not last.
And the search log gets ignored. Your site search is collecting the exact evidence you need to fix the menu, and nobody reads it. Make the monthly query-log review someone’s job. The data is already there, waiting.
Frequently Asked Questions
What is the best navigation structure for an association website?
The best structure organizes the menu around member tasks (renew, register, find a CE credit, log in), not around your departments. Hold the top level to roughly five to seven task-based items, place Join, Renew, and Login in the top-right of every page, and let the page count behind each section decide whether you use a simple bar, dropdowns, or a mega-menu.
Where should the Join, Renew, and Login buttons go on a membership website?
Put them in the top-right of the header, visible on every page. That corner is the learned location for account and conversion actions, so members look there first. Make Login dynamic: once a member signs in, it becomes their account or dashboard link, and the Join prompt yields to Renew when the membership is lapsing.
Should an association website use a mega menu or a simple dropdown menu?
It depends on how many pages sit behind the menu. Seven or fewer top-level sections work as a simple horizontal bar. Eight to twenty pages with clear groupings suit dropdowns. Twenty-plus pages or three-plus levels of depth call for a mega-menu, which lets members see all options at once instead of remembering them. Fix the structure first; a mega-menu on a bad structure is just a bigger problem.
How many items should an association website navigation menu have?
Aim for five to seven top-level items, each tied to a member task rather than a department. Nav bloat is the default failure, not the exception. Every team that does not actively police the menu ends up at eleven items within a year. A useful rule keeps it honest: any new top-level item requires removing one.
How do you make association website navigation work on mobile?
Treat mobile as a real layout, not a collapsed desktop menu. Keep your highest-value actions (Login, Renew, search) reachable without opening the hamburger, using a persistent header control or a bottom bar of three to five core destinations. Flatten deep hierarchies so members are not tapping four times to reach a transcript, and make sure the menu works with keyboard and screen-reader access too.
Is a search bar enough to replace good website navigation?
No. Roughly 30% of users go to search first, and search users tend to convert at a higher rate, but “members can just search” is what teams say when they have given up on structure. Search and a clear menu reinforce each other: search reveals the gaps the menu should close. Use the query logs to fix the navigation, not to excuse it.
How do you test whether your website navigation works for members?
Run a tree test (labels only, no design) and give real members real tasks like finding how many CE credits they have or renewing a membership, then measure whether they reach the right destination. Add first-click testing, since the first click strongly predicts task success. Fifteen to twenty members give a clear signal. Test members, not staff.
Before you redesign the menu, prove it with members
A redesign budget spent on a prettier menu buys you nothing if the menu still encodes your departments. Navigation is one layer of our broader association website strategy, and it is the layer members touch most. Most navigation overhauls happen during an association website redesign. It is the right moment to settle the menu against member tasks rather than staff opinion. If you want that work done with members in the room, Schedule a Redesign Assessment.