Your nonprofit's website issues are likely not technical. They're organizational.
We've worked with nonprofits for over fifteen years, and the pattern is consistent: organizations come to us thinking they need a better CMS, faster hosting, or a fresh design. What they need is clarity on who owns the website and how decisions are made.
The technology works fine. It's the governance that's broken.
The Reality of Nonprofit Website Ownership
Here's what we see constantly: a marketing or communications director gets approval from leadership to upgrade the website. Simple enough. But nobody loops in legislative affairs. Nobody talks to the membership. Procurement finds out when someone asks them to sign a contract. Legal learns about it when someone mentions the project in a meeting.
And suddenly, each of those departments has work landing on their plate. They're being asked to review content, rewrite sections, produce new assets, and approve layouts. This comes as a surprise, on top of their existing workload, and they're not happy about it.
What started as "let's improve our website" became an organizational conflict unrelated to web development.
The Board President Story
The worst governance failure we've ever witnessed happened after a successful launch.
We'd worked with a large organization for months to rebuild their website. Every department approved the work. We went through the client's launch process — midnight deployment to minimize downtime, comprehensive SEO redirects, and the whole production. The site went live. Everything worked perfectly.
The next morning, we got an email from our contact: "How hard would it be to put the old website back up?"
The board president was furious. Not because anything was wrong with the site, but because nobody had run it by them. They felt they should have had oversight and were making noise about legal issues, procedural violations, and other concerns that sounded serious.
When we finally got them calmed down and asked what changes they actually wanted, the requests were entirely superficial. Different fonts. Adjusted letter spacing. Layout tweaks. They even suggested changing colors, which was impossible because we'd followed their existing brand guidelines.
The complaints weren't substantive. Someone's ego was hurt because they weren't included in a process they felt entitled to oversee.
That project could have ended badly. It nearly did. And the root cause wasn't technical — it was a governance failure. Nobody thought to define who needed to approve what before the work began.
Why Governance Breaks Down
Nonprofit website governance fails for predictable reasons, and those failures are rarely about technology.
The Approval Bottleneck
Departments withhold sign-off due to busy schedules. Membership can't review their section during a recruitment drive. Capitol Hill hearings consume legislative affairs. Legal needs to consult with outside counsel first.
Meanwhile, the project lead gets frustrated, the timeline stretches, and every delay creates more work — content needs updating, designs need revising, and the launch window keeps moving.
The Fear of Responsibility
In some organizations, nobody wants to sign off on anything. We've had conversations that go like this:
"Is this content approved?"
"I don't know. Let me check."
"But you collected it. You sent it to us. You reviewed it."
"I know, but I need to find out who can officially approve it."
This is especially common in organizations with hierarchical cultures. Individual staff members don't have the autonomy to make decisions, even about content they created and reviewed themselves. Everything has to go up the chain, and the chain is unclear.
Too Many Decision-Makers
When everyone gets a say, you end up with chaos.
We've received feedback in every imaginable format — forwarded emails, Word documents, Google Docs, printed pages with handwritten notes. And the feedback contradicts itself:
"Make the banner red." "Remove the banner entirely." "I think the banner should be bigger."
Then there's the opinion problem. Does the legal department get to weigh in on font choices? Does marketing get to redesign the membership workflow? When everyone provides feedback on everything, you're drowning in subjective preferences that have nothing to do with anyone's actual expertise.
"I don't like that color." "I don't like two-column layouts." "I don't like long pages."
None of that is actionable. None of it reflects organizational priorities or user needs. It's just opinions from people who feel entitled to have them.
Authority Confusion
A fancy title doesn't automatically confer decision-making authority over the website. Board members may have fiduciary oversight of the organization, but that doesn't mean they should be approving homepage layouts. A department head may run their division brilliantly, but that doesn't qualify them to make design decisions.
From our side, we can't know who actually has authority. We just see titles and assumptions. The organization needs to define this clearly — not for our benefit, but for their own.
What Good Governance Looks Like
After years of navigating these dynamics, we've learned what works.
Start With a Single Point of Authority
When we begin a new engagement, we ask two questions: Who is my primary contact? Who can authorize work?
This isn't about gatekeeping. It's about sanity. When someone in the organization sends us a request for substantial changes, we need to know who to check with. Even if the organization's president emails us directly with instructions, we'll often verify with our point of contact first.
Why? Because that contact might say, "Hold on — let me talk to them first. They're not thinking about the compliance implications." Or "That contradicts what marketing decided last month." Or "They're new and don't know how this connects to the membership system."
The point of authority shouldn't be determined by title. It should be the person who understands what's supposed to be on the website and all the rules, regulations, and organizational dynamics that affect it. That person might be a communications director, an operations manager, or someone whose title doesn't suggest responsibility for the website at all.
Let Committee Structures Emerge Naturally
Once we've worked with an organization for a while, informal committee structures tend to develop. We learn that database and CRM integrations go through the IT person. Homepage and marketing content go through communications. The membership director handles membership workflows.
These aren't formal committees with charters and meeting schedules. They're just understood lanes of responsibility. The IT person won't ask us to redesign the homepage, and the marketing director won't request changes to the membership database schema.
This works well — but only when that centralized point of authority still exists to coordinate. Someone needs to make sure the distributed pieces don't conflict.
Distributed Ownership Requires Coordination
Some organizations slice website ownership into clear pillars: membership owns its section, legal owns theirs, and marketing handles the rest. This works when boundaries are clear and respected.
But even in distributed models, you need someone who can see the whole picture. Departments will make requests that conflict with each other. Design decisions in one section will affect the user experience in another. Content updates may have compliance implications that the requesting department isn't aware of.
Distributed ownership without coordination creates a website that feels fragmented — because it is.
The Staff Turnover Problem
Nonprofit staff turnover is constant, and it's devastating for website governance.
We work with organizations with 2 or 3 staff members managing millions in grants, overseeing major legislative activities, and running substantial membership programs. These aren't small operations — they're lean ones. When the one person who knew how to manage the website leaves, that knowledge walks out the door with them.
A well-built WordPress site is relatively intuitive. But that doesn't mean the remaining staff have time to learn it, want to learn it, or can fit it into their job descriptions.
The New Leadership Bulldozer
One of the most disruptive scenarios is when new leadership arrives — a new ED, communications director, or C-level executive — and wants things done their way.
They ask questions that sound accusatory: "Why was this set up like this? Why wasn't it done properly?"
The answer is usually: "Because you weren't here, and the previous person wanted it this way." There was good rationale at the time. The new leader just doesn't have the legacy knowledge to understand the decisions that were made.
But that doesn't stop them from coming in like a bulldozer, demanding changes based on preferences rather than problems.
Why Technical Partners Become Institutional Memory
This is where long-term technical partnerships prove their value.
We've worked with the American Board of Facial Plastic and Reconstructive Surgeons for years. They maintain a complex membership and certification system with multiple audience types — people seeking initial certification, active diplomates maintaining their credentials, fellows, retired members, and more. Each category has different requirements, access levels, and workflows.
At this point, we know their data flow better than they do. When they ask why a surgeon can't access an exam, we can look at the data points and explain exactly why. When they're confused about why someone doesn't appear in the directory, we can trace it back to a classification issue. We're not just maintaining their website — we're maintaining their institutional knowledge about how the system works.
Similarly, we've worked with a political advocacy organization for over twenty years. They operate a PAC, a Super PAC, a 501(c)(4), and do bundling for candidates — each governed by different campaign finance laws. Their internal staff turns over regularly. We're often the ones reminding them why a form was built a certain way, why the UX follows a particular flow, and whether a proposed change needs legal review.
We've outlasted multiple generations of their staff. We flag compliance concerns that they haven't thought to ask about. We're not their developer or their webmaster — we're their partner.
Setting Expectations for Board Involvement
Board members want to help. That's not the problem. The problem is when "help" means everyone gets to redesign the homepage in their head.
Boards should have input on strategic direction. Does the website support our mission? Does it serve our members? Does it represent our organization appropriately? Those are board-level questions.
Boards should not have input on font sizes, color choices, column layouts, or where the donate button goes. Those are execution decisions that people with relevant expertise should make — whether that's internal staff or external partners.
The clearest way to prevent board interference is to define it upfront. Before a website project begins, establish what kinds of feedback the board will provide and at what stage. Strategic input early. High-level review at milestones. Not line-by-line opinions on the finished product.
If the board president learns about the new website when it launches, you've already failed at governance — even if the website itself is perfect.
When Your Governance Model Isn't Working
Signs your current approach is broken:
Projects stall for approval. Content sits in review for weeks. Launch dates slip repeatedly. Nobody knows who can say yes.
Feedback contradicts itself. You're getting conflicting instructions from different stakeholders, and there's no process for resolving disagreements.
Small changes require escalation. Fixing a typo turns into a discussion about whether anyone has the authority to request changes.
New leadership disrupts everything. Every time someone new joins, they want to redo systems without understanding why they exist.
You're explaining the same things repeatedly. Staff turnover means constantly re-educating people about how the website works and why it's built the way it is.
These aren't website problems. They're governance problems. And they won't be solved by a redesign, a new CMS, or better hosting.
The Case for External Partnership
A technical partner who understands your organization can serve as a stabilizing force through internal chaos.
Staff will turn over. Board members will rotate. Leadership will change. But the partner relationship persists.
At FatLab, we've been that constant for nonprofits through multiple leadership transitions, staff turnovers, and strategic pivots. We remember why things were built the way they were when no one internal does. We flag issues that new staff wouldn't think to ask about. We provide continuity that organizations can't maintain internally with lean teams and constant change.
This isn't about dependency. It's about recognizing that some institutional knowledge needs to live outside the organization — with a partner who's invested in your long-term success, not just the current project.
If your nonprofit struggles with website governance — unclear ownership, approval bottlenecks, feedback chaos, or knowledge loss from turnover — the solution probably isn't technical. It's organizational.
But a good technical partner can help you navigate it.