Website Restructure Week 3: Audience Priority & Trust Barriers | Muskan

Two weeks of auditing produced a specification: a type scale, a contrast target, a line length. Every one of those is a decision design can make on its own. Muskan explains that week three of the Humanitarians AI website restructure is about the decisions design cannot make, because a measurement can tell you the hero section is media heavy, but it cannot tell you who the site is actually for.

Counting who the homepage is for

The week started by literally counting the homepage's intended audiences. It speaks to eight different groups at once: fellows and international graduates, donors, mentors, educators, partner organizations, children and families, volunteers, and the general public. Eight audiences share one page, with no stated order of priority among them. That absence of priority is itself the finding, since a page trying to speak to everyone equally often fails to speak clearly to anyone.

Twenty-four pieces of internal shorthand

The homepage runs about 1,200 words and carries 24 named internal concepts a first-time reader has to decode: terms like Tier One, Tiers Three to Six, Irreducibly Human, Botspeak, Atoms. That works out to roughly one piece of internal shorthand every 50 words. Layered on top of that are 13 separate "learn more" and "explore" links leading off the homepage, 13 equally weighted onward paths, which functions as 13 ways to leave the page and no clear way to be led through it.

Three competing calls to action

The same page makes three asks at once, presented side by side with identical visual weight: donate now, volunteer, and watch on YouTube. Which of those matters most is not a question a designer can answer from a layout decision. It has to come from the organization.

The donation transparency contradiction

For a donor, the trust picture on the site is mixed. The site states its 501(c)(3) status and its EIN, but does not publish an annual report, a Form 990, a named board, or a third-party charity rating. One finding needs an answer before anything gets designed around it: the homepage states that 100 percent of donations fund the programs, mentorship, and project support, while the footer of the same page states that 100 percent of all donations support direct operational costs, including legal fees and staff salaries. Both statements cannot be the actual promise, and resolving that contradiction is a prerequisite to any honest donor-facing design.

Missing outcome metrics

Every number currently on the homepage is a tier label, a legal identifier, a chapter count, or a copyright year, not one of them is an actual outcome. There is no count of fellows placed, no count of tools delivered. None of these gaps are design decisions; every one is an organizational decision that a designer can surface but should not make alone.

The stakeholder discussion guide

The output of the week is a structured discussion guide built around open questions across eight themes: audience priority, first impression, primary action, terminology, navigation, tone, trust, and success metrics. Sample questions include what a first-time visitor should take away from a single sentence before leaving, which single audience matters most this quarter, what visitors most often misunderstand about the organization, what one action a visitor should take if they do exactly one thing, which named concepts should survive if a stranger had to understand the site without help, what a donor would need to see to give with confidence, and where the site's writing should sound like a research group versus a program a family could join.

The hierarchy principle, and what stays undecided

Alongside the questions, a structural hierarchy strategy took shape, built on the principle the audit kept pointing toward: lead with what a visitor came looking for, and let what the organization offers follow from that. This fed one more round of hero-section refinement, but deliberately stays a direction rather than a finished layout. The hero should not be redrawn until the people who own the organization's message decide which message leads.

Key takeaways

• The homepage currently serves eight distinct audiences with no stated priority order among them.
• Internal shorthand appears roughly once every 50 words across the page's 1,200 words, and 13 equally weighted exit links give no clear path forward.
• The homepage and footer contain a direct contradiction about where donations go, one that must be resolved before any redesign proceeds.
• None of the homepage's current numbers represent actual outcomes, they are tier labels, legal identifiers, or dates.
• The week's output is a structured stakeholder discussion guide covering audience priority, action, terminology, trust, and success metrics, since these are organizational decisions design can surface but not make alone.

Who this is for

Anyone working on nonprofit website restructuring, especially teams facing competing audiences, inconsistent messaging, or unclear priorities, who wants a concrete example of separating design decisions from organizational ones.