Turning a complex nonprofit website into clearer paths for finding support, understanding impact, giving, and getting involved.
Strategic prototype · Not launched
Role
UX/UI design · IA · donor path
Team
Two-person student team
Timeline
Spring 2026 · 10 weeks
Methods
Audit · flows · 2 sessions
My contribution
I led current-state analysis, persona and journey work, problem and solution framing, low-fidelity homepage and contact flows, key homepage modules, and accessibility direction.
Project outcome
Our two-person team translated a complex, program-centered site into a high-fidelity prototype organized around visitor intent. It was presented to the client and has not launched.
The problem
Visitors had to understand ReWA’s structure before they could find the right next step.
ReWA already had meaningful services and strong community impact. The friction came from hierarchy and organization: different audiences arrived with different goals, while programs, navigation, and contact options carried similar visual weight.
010203
01
Unclear action hierarchy
Donation, support, and informational actions competed for attention.
02
Fragmented service discovery
People had to interpret programs and departments before finding relevant help.
03
Disconnected help + contact path
Service information and the route to the right team felt like separate journeys.
Information architecture
Organize the experience around what visitors came to do.
Instead of asking people to decode departments and program names, the revised structure starts with intent and leads to one of four understandable pathways.
Homepage→What do you need?→Visitor intent
01
Find support
Plain-language services and a guided contact route.
02
Understand ReWA
Mission, impact numbers, and community stories.
03
Give
Impact context before donation choices.
04
Get involved
Volunteer, work, and partnership opportunities.
Earlier site
About · Services · Impact · Contact · Give — visitors had to interpret departments and program names.
Design response
Four decisions turned the strategy into a clearer experience.
Each decision answers a specific point of friction. The service-card direction reflects heuristic and current-state analysis plus positive stakeholder response; it is not presented as user-testing proof.
01
Homepage hierarchy
Mission and impact appear before the donation ask, helping visitors understand ReWA before acting.
02
Donor pathway
Impact context, giving frequency, suggested amounts, and other ways to give live in one coherent flow.
03
Find the support you need
Six plain-language service cards create direct, scannable starting points for people looking for help.
04 · Guided contact
Begin with visitor intent—not department names.
A three-step inquiry flow helps visitors choose support, involvement, careers, media, or general questions before reaching the appropriate team.
Qualitative evidence
Two exploratory sessions clarified both confidence and trust.
These sessions cover two different scenarios and are presented separately. They indicate useful directions; they do not represent statistically generalizable validation.
Support-seeking session · N=1
Henry · 26
The guided form clarified where his inquiry would go.
5/5 confidence · Expected a back buttonDonor session · N=1
Potential donor · 23
She wanted mission, services, and impact context before donating.
Selected a one-time $25 gift · Requested anonymity
Unresolved recommendations
01
Add back navigation
Give people a visible way to revise an earlier answer in the guided contact flow.
02
Add anonymous-giving and privacy options
Make anonymity and data expectations explicit before a donor completes the transaction.
My contribution
I led the framing and key experience paths while contributing to a shared team system.
This division keeps the case study transparent about individual ownership and collaborative work.
I led
Framing + core journeys
Current-state and user pain-point analysis
Jennifer donor persona and journey
Problem and solution framing
Low-fidelity homepage and contact form
Final hero, impact story, and donor path
Accessibility and inclusive-design direction
Collaborative
System + validation
Information architecture and user flows
Visual design system
Usability testing and synthesis
High-fidelity prototype refinement
Client work-in-progress presentation
Final presentation and project storytelling
Outcome + reflection
A strategic prototype for clearer support, giving, and contact journeys.
Our two-person team delivered a high-fidelity concept covering the homepage, donation journey, and contact experience. It reorganized key content around visitor intent, made important services easier to scan, and added impact context before the donation action.
04Visitor pathways
03Core experience flows
02Exploratory sessions
What I learned
Shared design standards made the team faster and more consistent, while testing exposed needs that polished screens alone could not: confidence in the contact path, context before donating, and clearer privacy choices. Next time, I would ask for client feedback earlier and validate the revised service categories with people who actively use ReWA’s support.
Next · Test in context · Validate service language · Resolve privacy requirements
010203
