Picture a website whose homepage offers three "Enter Site" buttons: "I'm a Donor," "I'm a Beneficiary," "I'm a Partner."

The organisation thinks it has solved multi-stakeholder navigation by letting people choose their own journey. What it has built is institutional confusion. Each group meets a different organisation depending on which button it presses: contradictory messaging, competing priorities, no coherent identity.

The problem is not execution. It is treating multi-stakeholder navigation as a routing problem rather than a governance question.

In my work on nonprofit websites, I have found that serving beneficiaries, trustees and donors at once does not require choosing one over the others, and it does not require building parallel versions of the site. It requires an architecture that treats all three as legitimate while holding one consistent account of what the organisation is and does.

Why "Choose Your Journey" Approaches Fail

The self-selection approach feels logical. Different stakeholders have different needs, so give each of them an experience built around their interests.

It works on commercial sites, where customer segments genuinely want different products. It fails for charities, because you are not selling different products to different customers. You are one institution with one charitable purpose, serving several groups who need different things from the same organisation.

This is not only an institutional argument. Nielsen Norman Group has tested audience-based navigation directly and recommends against it, for five reasons that all show up on charity sites: people do not know which group they belong to, they cannot tell whether a section is about that group or for it, self-identifying adds a step and a decision, they worry they are missing something in the section they did not choose, and overlapping content sends them bouncing between sections looking for the version that answers their question (Sherwin, 2015). Her conclusion is that people arrive task-oriented, so topics and tasks navigate better than audience labels.

Consider who actually visits a charity website. A trustee is often also a donor. A former beneficiary may be a volunteer and a campaigner. A grant assessor at a foundation may have a personal connection to the cause. The audience picker asks each of them to be one thing.

When you build parallel stakeholder journeys, you also fragment institutional identity:

Donors see: impact stories, emotional appeals, giving opportunities, financial transparency framed around "your donations make this possible."

Beneficiaries see: services available, dignity-focused representation, community resources, privacy-protected information framed around "we're here to support you."

Trustees and funders see: governance documentation, compliance evidence, strategic direction, accountability mechanisms framed around "we're responsibly governed."

Each journey is competently executed. Each is optimised for its group's immediate needs. The problem is that they describe three different organisations.

Donors conclude you exist to produce moving stories. Beneficiaries conclude you exist to deliver services with dignity. The board concludes you exist to demonstrate compliance. When these people talk to each other, which they inevitably do, they find contradictory versions of the same charity. The organisation that fundraises on transformation does not sound like the organisation that insists on beneficiary agency. The accountability narrative does not sit alongside the emotional one.

You have not solved multi-stakeholder navigation. You have created an identity problem visible to anyone who looks across two journeys.

The Actual Challenge: Coherence With Accommodation

Proper multi-stakeholder navigation reverses the order of the questions.

Start with institutional identity. What is this organisation? What is the charitable purpose? Which commitments define its character regardless of who is asking?

Then accommodate stakeholder needs inside that. How does the site serve beneficiaries, trustee oversight and donor transparency while saying the same thing to all three?

The website has to answer, simultaneously:

  • For beneficiaries: this organisation serves you with dignity, respects your privacy, can demonstrate its safeguarding, and publishes resources you can actually use.
  • For trustees and regulators: this organisation takes governance seriously, can prove compliance, and makes oversight possible from the outside.
  • For donors and funders: this organisation does meaningful work, uses resources responsibly, and can show you both.

All three answers must describe one organisation with consistent commitments, not three versions tuned to three audiences.

The Three-Stakeholder Framework in Practice

I work with three definitive groups. The reasoning behind reducing a long stakeholder list to three is covered in the three-stakeholder approach.

1. Beneficiaries (Charitable Purpose)

What they need from the website:

  • Dignity in representation, not poverty tourism
  • Privacy protection, not exposure for fundraising
  • Resources they can actually reach and use
  • Evidence that the organisation can be trusted with them

What this creates architecturally:

  • Consent protocols for any beneficiary representation
  • Privacy controls on personal information
  • WCAG 2.2 AA as a non-negotiable baseline, not an enhancement
  • Safeguarding policies published where they can be found

Beneficiary services, resources and information are accessible and dignity-focused. But beneficiaries are not hidden to spare donors any discomfort. They are represented with agency and consent rather than as objects of charity.

2. Institutional Oversight (Trustees and Regulators)

What they need from the website:

  • Governance documentation: annual reports, policies, transparency
  • Compliance evidence
  • Visible accountability mechanisms
  • Enough published material that a trustee can verify commitments from outside the organisation

What this creates architecturally:

  • A demonstration of public benefit. This is statutory, not reputational: under section 4 of the Charities Act 2011 it is not presumed that a purpose is for the public benefit, so it has to be shown.
  • Financial transparency and a findable annual report
  • Published safeguarding and data protection policies
  • Governance structure and trustee information

The Charity Commission's CC3, The essential trustee sets out six duties, two of which land directly on the website: ensuring the charity carries out its purposes for the public benefit, and ensuring the charity is accountable. For most organisations the website is where both are demonstrated to anyone who is not in the room.

So governance documentation is not something to bury in the footer. It is an architectural element. It is also not the homepage's main event, competing with everything else. It is findable, complete and clearly current.

3. Resource Providers (Donors and Funders)

What they need from the website:

  • Evidence of what the organisation achieves
  • Transparency about how resources are used
  • A clear route to supporting the work
  • Reasons to direct resources here rather than elsewhere

What this creates architecturally:

  • Impact demonstration that stays inside the beneficiary dignity constraints
  • Financial transparency and accountability evidence
  • Giving mechanisms and engagement opportunities
  • Credibility signals: governance quality, funder endorsements, named people

Impact is visible and compelling, but framed around organisational capability and beneficiary agency rather than beneficiary need and donor rescue. Giving pathways are clear without becoming the organisation's identity.

How These Integrate

These are not parallel journeys. They are three legitimate perspectives on the same institutional reality, which is why one piece of content can serve all of them.

Take the annual report. To a beneficiary it is evidence the organisation represents its communities accurately. To a trustee or regulator it is public benefit demonstration and financial transparency. To a funder it is impact evidence and proof of stewardship. Same document, three needs met, no contradiction, because the content describes what actually happened rather than what each audience would like to hear. Getting that document onto the site in a form all three can use is a discipline of its own, covered in publishing your annual report online.

Take a beneficiary case study. To a beneficiary it shows how the organisation represents people: with consent, dignity and agency. To a trustee it demonstrates safeguarding and ethical communication standards. To a donor it shows meaningful impact achieved without trading anyone's dignity for it.

I do not build separate entry points or parallel journeys. I build one structure.

1. Primary Navigation Reflecting Institutional Purpose

Not "who are you?" but "what does this organisation do?"

  • Our Work: what we do, who we serve, how we operate
  • Our Impact: what we have achieved, and the evidence
  • Our Governance: oversight, policies, transparency
  • Get Involved: support, resources, contact

This serves everyone because it is organised around institutional reality rather than audience segmentation. Beneficiaries find service information under Our Work. Trustees find documentation under Our Governance. Donors find evidence under Our Impact. All of them are reading about the same organisation.

The labels matter more than the shape. A menu item only works if someone can predict what is behind it, and charity sites are full of items that cannot be predicted: "Our Approach", "What We Stand For", "Resources". If a label needs explaining, it is not a label.

2. A Homepage That Establishes Identity Before It Routes

Not audience doors, but the commitments that matter to everyone:

  • Charitable purpose, stated plainly: what this organisation exists to do
  • Impact evidence: what it has achieved
  • Values and approach: how it works, which is safeguarding to a beneficiary, governance to a trustee and a trust signal to a donor
  • Engagement pathways: services, oversight, support, all present at once

Everyone understands what organisation they have arrived at before they pursue their own interest.

3. Content That Serves Several Needs at Once

Every major section carries the legitimate perspectives without producing contradictory versions. A programme page holds service information written for the people who need it, effectiveness and safeguarding evidence for the board, and impact demonstration for funders. It does not hold three versions of itself.

4. Accessibility as a Universal Commitment

WCAG 2.2 AA conformance is not an accommodation aimed at beneficiaries. It is an institutional commitment that reads differently to each group and means the same thing: to a beneficiary, evidence that inclusion is taken seriously; to a trustee, evidence of legal and ethical obligations being met; to a funder, a signal about organisational quality. One commitment, three readings, no fragmentation. The practical detail sits in website accessibility for nonprofits.

Where the Hierarchy Comes From

All three groups matter. They do not matter equally in every decision, and pretending otherwise is how navigation arguments become unresolvable.

The vocabulary for ranking them is stakeholder salience, set out by Mitchell, Agle and Wood in "Toward a Theory of Stakeholder Identification and Salience" (Academy of Management Review, 1997). Their argument is that how much attention a stakeholder merits depends on how many of three attributes they hold: power, legitimacy and urgency. Applied to a charity website:

Beneficiaries have absolute legitimacy through the charitable purpose itself, but usually little power and variable urgency. Their needs set constraints, on dignity, privacy and safeguarding, that everything else has to work within.

Trustees and regulators have legitimacy and power. Compliance requirements are not negotiable, and they set the governance baseline.

Donors have importance without primacy. Their needs are real and are accommodated inside the constraints the other two set.

This produces a hierarchy the architecture can actually use:

Non-negotiable foundations

  • Beneficiary dignity and safeguarding, which cannot be traded for donor engagement
  • Regulatory compliance, which cannot be subordinated to any preference
  • Trustee oversight capability

Optimisation opportunities

  • Donor impact visibility, inside the above
  • Beneficiary service accessibility, inside the governance framework
  • Engagement pathways, inside institutional commitments

The architecture never breaks a foundational commitment to optimise for anyone, including the people paying for it. That is what makes it a governance document rather than a design opinion.

Where Stakeholder Needs Genuinely Conflict

The hierarchy is necessary because the conflicts are real, not imagined. Four recur.

Homepage real estate

Your fundraising-minded trustees want the annual report linked prominently, impact metrics high on the page, transparency signals immediately visible, and "Donate" as the primary action.

Your programme team wants service information one click away, eligibility criteria plainly explained, a helpline number visible to someone in difficulty, and "Get help" as the primary action.

You cannot optimise for both. Lead with impact metrics and a donation button and you have told someone in crisis that the site is for donors. Lead with service access and a major funder assessing your credibility sees a site that does not communicate institutional accountability. The usual answer is a compromise in which neither audience is served and everyone is mildly dissatisfied. The better answer is a ranked decision, made once, written down, and defensible to whichever group did not win.

Information depth

A funder doing due diligence wants depth: several years of accounts, programme budgets, governance documentation, presented formally and organised so that years can be compared.

Someone seeking help wants the opposite: do you serve my area, am I eligible, how do I apply, in plain language, on a phone, without downloading anything.

The failure modes are symmetrical. Either you bury the second group in complexity, or you give the first group so little that they cannot assess you. Both are credibility failures, and they are not solved by picking a middle depth that satisfies nobody. They are solved by layering, which is the next section.

Tone and positioning

Institutional funders read formality as maturity: evidence of systematic approach, governance frameworks, risk management, a peer capable of handling significant money.

Grassroots partners read the same formality as distance. They are looking for openness, local knowledge and a collaborator rather than an institution.

The usual compromise is a corporate-nonprofit hybrid voice: professional enough for funders, never quite warm enough for partners, optimally credible to neither. The way out is not a blended voice but placement. The governance section can be formal because of what it is. The partnership pages can be warm because of what they are. One organisation is allowed to speak differently in different rooms, as long as it does not say different things.

Organise by audience and the pathways look clear, but you have fragmented what the organisation is, and the NN/g findings above say most visitors will pick wrong anyway.

Organise by function, with Our Work and Get Involved, and you keep coherence but ask every visitor to translate their need into your internal structure.

Organise by programme or geography and it works beautifully for staff and mystifies everyone else.

There is no option without a cost. Function, with labels written from the outside in and tested on real people, carries the lowest one.

Serving Conflicting Needs Without Fragmenting

Three mechanisms resolve most of these conflicts without an audience picker.

Layered depth. Surface simplicity with depth available underneath, calibrated per section rather than per audience. For services: is this for me, then how do I apply, then how the programme works. For governance: latest annual report and who governs the charity, then multi-year financials and programme budgets, then policies and frameworks. Nobody has to declare who they are; they simply stop descending when they have what they came for.

Content organised by the question it answers. A long annual report contains a funder's financial statements, a partner's outcome data, a journalist's summary and a researcher's methodology. Multi-stakeholder architecture does not make everyone download the PDF. It surfaces the relevant sections as pages in their own right, from the relevant parts of the site, while the document itself stays intact and citable.

Contextual calls to action. There is no single primary action on a site like this. There is the right next step for the page someone is on. On a programme page it is checking eligibility. On a transparency page it is a conversation about funding. On an impact page it is giving. Success is measured per pathway, which is uncomfortable for reporting and honest about the organisation.

What none of these require is a stakeholder-specific version of the site. Dedicated landing pages are the one legitimate exception, and only because of how they are reached: a page written for funder prospects and linked from an email, or a service page linked by a referral partner, is routing, not navigation. The visitor never had to choose a door. The menu on those pages still describes the organisation.

On "within two clicks"

Rules of thumb about click counts are worth naming and then setting aside. The three-click rule has been tested and does not hold: drop-off does not rise past three clicks and satisfaction does not fall (Laubheimer, 2019). What matters is whether each click is clearly a step towards the goal.

I do apply a two-click criterion, and it is mine rather than a sector standard: on a charity site, the current annual report, the safeguarding policy and the route into the main service should each be reachable from the homepage in two clicks. Not because a third click would lose people, but because those three things are what the hierarchy above says are non-negotiable, and depth is where organisations quietly demote what they would rather not show.

What This Looks Like in Practice

Take an education charity working with vulnerable young people whose website has separate "Donor" and "Community" sections that describe two different organisations.

The donor section runs transformation narratives, emotional appeals and prominent giving buttons, with young people represented as recipients of rescue. The community section runs agency-focused resources and dignity-preserved service information, with the same young people represented as capable and entitled to support.

These cannot coexist. They rest on incompatible values.

A rebuild starts from one identity: an organisation that supports young people to develop agency, access education and build futures, through community partnership, dignity-focused programming and governance accountability. That statement works for all three groups without being written for any of them.

The navigation follows the work rather than the audiences: Our Programmes, Our Impact, Our Governance, Get Involved. Programme pages carry service information young people can use, safeguarding and effectiveness evidence for the board, and impact demonstration inside the dignity constraints. No parallel journeys, no stakeholder doors, one organisation.

The Questions That Reveal Architecture Quality

When I run a Blueprint Audit, four questions reliably expose whether a site has multi-stakeholder architecture or fragmented routing.

If a beneficiary and a donor both visit, do they meet the same organisation? If not, you have a fragmentation problem, and it is visible to anyone who looks at two sections in one sitting.

Can a trustee verify governance quality from the public site? If oversight material is separated from the institution's public presence, governance is being treated as a private matter rather than public accountability, which is at odds with the accountability duty in CC3.

Does showing impact require compromising beneficiary dignity? If it does, the site is optimising for donors at beneficiaries' expense, and the hierarchy has been inverted.

Can each group find what it needs without meeting a different organisation on the way? If entry point determines identity, you have routing rather than architecture.

Why This Matters Beyond Navigation

Fragmented stakeholder approaches create credibility problems well past the inconvenience of a confusing menu.

Outsiders notice the contradictions. When donor materials emphasise transformation and beneficiary materials emphasise agency, observers see an inconsistency in values rather than two audiences being served. Funders start asking whether you believe your stated principles.

Insiders feel the misalignment. Staff working to a dignity framework see the fundraising materials and question what the organisation actually thinks. Fundraisers asked to work inside constraints their competitors ignore feel handicapped. Leadership spends its time managing the tension between two public faces.

Oversight becomes difficult. When trustees see a governance section separate from everything else, they cannot verify whether the public-facing identity matches the commitments they have signed off. Oversight requires seeing what stakeholders actually encounter, not a version prepared for the board.

Do You Actually Need This?

Multi-stakeholder architecture is more work than a standard site, and it is not always warranted. It is, if:

  • You serve three or more distinct groups with genuinely different information needs
  • Those needs actively conflict, so what one group needs prominent another needs de-emphasised
  • Groups arrive at very different levels of familiarity with you
  • You run several functions at once: service delivery, advocacy, research, fundraising
  • Credibility is proved differently to each group
  • Your team argues about homepage priorities because every department has a legitimate claim
  • People tell you they could not find something that is demonstrably on the site
  • You have already redesigned the navigation once and the confusion survived it

Four or more of those and your problem is architecture, not content or design.

It is not, if you have one clear primary audience, if stakeholder needs align rather than conflict, if the organisation has a single primary function, or if the current site already serves everyone adequately. In those cases a straightforward architecture built around the primary audience is the right answer. Do not overcomplicate it.

Why This Is Architecture, Not Design

Most agencies treat stakeholder complexity as a content organisation problem: create clear sections for each audience and the problem goes away.

It does not. The navigation gets cluttered, content gets duplicated and drifts out of sync, visitors still cannot navigate because "For Donors" does not help a donor who does not think of themselves as one, and you end up with several single-path experiences rather than one structure that works.

What it actually takes is a diagnostic phase before anything is built: real stakeholder mapping, the top task per group, an honest list of where needs conflict, and a ranked decision about which constraints are non-negotiable. Then an information architecture that lets one piece of content be reached from several directions, and a governance framework naming who owns what and how it stays current. Content governance is the part most projects skip, and it is the part that decides whether the architecture is still true years later.

The Core Insight

Multi-stakeholder navigation is not a routing problem. It is a governance question about what your organisation is, answered once, then expressed consistently to everyone who asks.

Beneficiaries, trustees and donors all need different things from your website. They need them from the same organisation, described the same way, not from three versions tuned to three audiences.

Start from institutional identity: what this organisation is and does regardless of who is asking. Then serve each group's needs inside that. It is harder than building parallel journeys, and it is the only version that survives your stakeholders comparing notes.

Struggling with stakeholder navigation that fragments your organisation? The Blueprint Audit maps stakeholder salience, produces the priority decision your navigation is missing, and sets out an architecture that serves beneficiaries, trustees and donors from one coherent identity.

Learn more about the Blueprint Audit

Further reading: