Most association website redesign mistakes trace back to a single error: treating a broken operation as a decorating job. The organization approves a prettier homepage while members still can’t renew, find a document, or register for an event. A redesign that restyles the surface and leaves the AMS integration, the content, and basic findability untouched just relocates the failure to a better-looking page. Start with operations, not design.
The industry sells redesigns as a visual refresh — that’s the problem
The conventional redesign process looks like this: someone notices the site looks dated, the executive director agrees, a committee forms, and an RFP goes out. That RFP asks for a “modern, refreshed look.” The proposals that come back lead with homepage mockups. That’s what the board can evaluate in a 45-minute presentation. The project gets approved on the strength of a visual. The success criterion is set, by default, to how the site looks.
I don’t blame design-led agencies for this. The homepage comp is the one thing that can be judged in a meeting. Board members can’t evaluate AMS integration architecture or information structure, but they can tell you whether the homepage feels right. So the purchasing motion is built around what decision-makers can see. That’s how “our site looks dated” becomes the business case even when the real problem is that members can’t renew online without calling the office.
Research consistently shows the majority of website redesigns fall short of their stated goals, not because the visual work was poor, but because the project was scoped around the wrong problems. Practitioners who work specifically with associations have stated it plainly: the main failure in association website redesigns is not the site design. It’s misaligned and outdated technology infrastructure that can’t support membership operations like accreditation, renewals, CE tracking, and the member portal.
Redesigns fail because the project gets sold as a design problem when it’s an operations problem. That’s the trap, and the standard purchasing process sets it.
Redesigns fail because the project gets sold as a design problem when it’s an operations problem.
Why a prettier site doesn’t fix association website redesign mistakes
The visual failure is a symptom. The causes go deeper.
It gets judged by the wrong people on the wrong thing
The people approving the redesign (the board, the executive committee, the executive director) judge the one thing they can evaluate in a slide: the homepage. The people the site actually has to work for (a member mid-renewal, a prospect deciding whether to join, an attendee registering for the annual conference) aren’t in the room.
This gap creates a compounding problem: scope creep. When every stakeholder has equal weight and conflicting opinions about the header image, the navigation label, or the color of the call-to-action button, approvals stall and the project bloats. I’ve watched redesigns scoped for four months run to eight because no one had the authority to close a decision.
The fix is straightforward and almost never implemented: name a single point of contact for approvals at the start of the project. Not a committee. One person. That person collects input from the board, the programs team, and the membership staff, then makes the call. Without that structure, the project inherits the organization’s governance problem. No content management system solves a governance problem.
Set member-facing success criteria before you pick a vendor. Not “the site looks more modern.” New-member conversion rate. Renewal completion rate. Event registration volume. Support tickets from members who couldn’t find something. Those are measurable. The visual is not.
A new skin on the same broken plumbing
The real product of an association website is the infrastructure: AMS integration, single sign-on, dues renewal, event registration, gated member content, the member directory. That’s what members touch. Not the homepage. The homepage is what the board approved.
A redesign that restyles the pages but underscopes or skips the integration work leaves the actual failure in place. I’ve seen it happen repeatedly. A new site goes live with a genuinely improved visual design. Members still can’t renew online without calling the office. The event registration form still breaks on a phone. The member directory still pulls from a stale data source. The organization spent real money to move the same operational problems to a better-looking address.
This is why I describe an association website as a membership operating system, not a brochure. Restyling a brochure is a graphic design project. Re-plumbing an operating system is the actual job.
Integrations also need an owner after launch. Without clear operational governance, AMS integrations deteriorate. The sync that worked at launch starts drifting. Member records get stale. The directory surfaces outdated information. The organization discovers this when a member complains, not when the project closes. Someone has to own that infrastructure, or it becomes nobody’s problem until it’s everybody’s emergency.
This is also why comprehensive association redesigns take 6–12 months. Not because the visual work is complicated. It usually isn’t. AMS and CRM integration architecture, secure portal configuration, and payment processing testing take time to get right. Anyone promising a full association redesign in four weeks is compressing the work that actually matters to your members.
Moving stale content to a prettier page
Most associations redesign without auditing their content first. The result is predictable: the same buried governance documents, the same navigation that mirrors the org chart, the same dead pages nobody updated since the last board transition, now displayed on a better-looking template.
I’ve audited association websites with 47 pages about committee structure and three pages explaining why a first-year member should renew. Redesigning that site without addressing the content doesn’t fix the problem. It rehouses it.
The migration itself can make things worse. Lose the URL structure in the switch, break internal links, or drop high-performing pages without redirects, and the redesign actively destroys the organic search traffic the association already had. I’ve seen organizations launch a new site and watch their search rankings fall sharply over the following 90 days. That’s not a bad launch. That’s a bad scope.
As Josie Ahlquist has argued, redesigning without cleaning up on-site content means moving the same problems to a prettier space. Refreshed visuals don’t fix unclear messaging. A new template doesn’t answer the question a prospect has when they first arrive: why should I join?
Redesigning without cleaning up on-site content means moving the same problems to a prettier space.
How to run a redesign that actually fixes something
Start from what’s measurably broken. Not “the site looks dated.” How many members abandon the renewal flow before completing it? How many clicks does it take to reach the conference registration page? Does event sign-up work on a phone? Those questions have answers. Start there.
Before you write any RFP, decide honestly whether you need a full rebuild. Sometimes you don’t. If the problems are primarily content, findability, and a few broken flows, a full redesign may be the wrong tool for the job. The decision is worth taking seriously because it shapes the scope, the budget, and the timeline. The post on how to decide between a redesign and an optimization walks through the criteria in detail.
If a redesign is the right call, scope the AMS integration and the content cleanup as primary work, not as additions to the visual project. Bring in whoever manages the AMS on day one, not during QA. Map the content before you design the navigation. Set a content migration plan before you lock the site architecture. Name one person who closes approvals. Collect board input; don’t give everyone a veto.
The broader framework is in the broader association website strategy guide, which covers platform selection, governance, and the full decision sequence from first audit to ongoing maintenance. The short version: a website built on a broken membership operation will fail the operation, regardless of how well-designed the pages are.
That’s the premise behind how we scope an association website redesign at Adtelic. The same thinking applies to how we approach association website design from the ground up. The discovery phase is an operations audit. We map what’s broken before we design anything. The visual comes last.
Frequently Asked Questions
Why do most association website redesigns fail?
Most fail because the project gets scoped as a design project when the real problems are operational. The AMS integration is underscoped or skipped. Content isn’t audited before migration. Success criteria default to visual approval rather than member-facing metrics like renewal rates or event registration. The result is a site that looks better but performs the same.
Is a website redesign or an optimization better for our association?
It depends on whether the underlying problems are structural or surface-level. If your information architecture is wrong, your AMS integration is broken, or your platform can’t support where the organization is going, a redesign is likely warranted. If the issues are content quality, findability, and a few broken flows, optimization is often faster and less disruptive. The full decision framework is on the redesign-vs-optimization page.
How long should an association website redesign take?
A comprehensive association redesign typically takes 6–12 months. The visual work is a fraction of that. The timeline is driven by AMS and CRM integration architecture, content audits, secure member portal testing, and payment processing QA. Agencies promising a full redesign in four weeks are compressing the integration work — which is the part your members will actually notice.
Who should sign off on an association website redesign?
One person should have final approval authority, not a committee or the full board. That person collects input from staff, membership leadership, and board members, then closes decisions. Without a single approval owner, scope creep is nearly inevitable. The board should be consulted; they shouldn’t have a veto on every navigation label.
Can a website redesign hurt our search rankings?
Yes, and it happens more often than most organizations expect. Changing URL structure without redirects, eliminating high-performing pages during migration, or breaking internal links can destroy years of organic search traffic. Before any migration, audit which pages drive organic traffic, preserve URL structure wherever possible, and set up 301 redirects for any URLs that have to change.
If your association is weighing a redesign, the assessment we run starts with what’s operationally broken, not a moodboard. Schedule a Redesign Assessment to find out what’s actually standing between your site and the membership experience it should deliver.