abouse@umich.edu

Click to Copy!

Bringing Community to the Forefront of the Rizal Center Website

Bringing Community to the Forefront of the Rizal Center Website

Client

Client

Filipino American Council of Greater Chicago (FACGC)

Filipino American Council of Greater Chicago (FACGC)

FACGC

Duration

Duration

August 2024 - May 2025

August 2024 - May 2025

August 2024 - May 2025

Role

Role

UX Researcher & Designer

UX Researcher & Designer

UX Researcher & Designer

Context & Mission

The Rizal Center’s website was not meeting the needs of its community.

The Rizal Center has long served as a cultural hub for Filipino Americans in Chicago. However, their old website wasn’t keeping up. It felt outdated, hard to navigate, and disconnected from the community it aimed to serve. Our team partnered with the Filipino American Council of Greater Chicago (FACGC) to overhaul the site into a welcoming, accessible, and culturally meaningful digital hub.


Problem

The site was confusing, inaccessible, and disconnected from users.

  • Seniors struggled to navigate it, mobile usability was poor, content felt static, and distant community members had no clear way to engage. Poor accessibility for older adults and users with limited digital literacy.

  • Outdated content made the site feel static and unreliable.

  • Navigation was confusing, especially on mobile.

  • Community members (especially those living far away) felt disconnected.

Problem

The site was confusing, inaccessible, and disconnected from users.

  • Seniors struggled to navigate it, mobile usability was poor, content felt static, and distant community members had no clear way to engage. Poor accessibility for older adults and users with limited digital literacy.

  • Outdated content made the site feel static and unreliable.

  • Navigation was confusing, especially on mobile.

  • Community members (especially those living far away) felt disconnected.

Our goal: Redesign the website into a true digital extension of the Rizal Center’s community mission, a place that feels useful, useable, and worthy of the vibrant community it represents.

Our goal: Redesign the website into a true digital extension of the Rizal Center’s community mission, a place that feels useful, useable, and worthy of the vibrant community it represents.

Our goal: Redesign the website into a true digital extension of the Rizal Center’s community mission, a place that feels useful, useable, and worthy of the vibrant community it represents.

Understanding the Audience

We interviewed and surveyed users across three generations to guide our design.

We surveyed 61 users and conducted 12 interviews with seniors, parents, and younger adults. Their input shaped three personas and a storyboard that helped us prioritize features across different needs, habits, and devices. Rather than generalizing, we designed around specific, recurring user stories.

  • Maria, a busy mother, wants to share Filipino culture with her kids.

  • Helen, a tech-savvy retiree, is looking for cultural connection and easier access to events.

  • Antonio, a retiree in Chicago, stays socially active through in-person community events but struggles with navigating websites and prefers direct communication.

  • Daniel, a 30-year-old professional, moves to Chicago and finds his way to a community potluck through the Rizal Center’s updated website.

These stories shaped our priorities and allowed us to balance usability with emotional/cultural resonance.

Insights & User Research

Users wanted clearer navigation, up-to-date content, and stronger digital connection.

Our survey of 61 participants and 12 follow-up interviews showed that users across generations had different needs but shared frustrations with the old site.

  • Older adults often relied on desktops, had trouble finding key features like the newsletter signup, and preferred phone or in-person communication.

  • Younger users accessed the site via mobile and wanted faster access to events and volunteer opportunities.

  • Despite most users preferring in-person events, nearly 70% expressed interest in online features like a newsletter, photo gallery, or announcements to help them stay involved from a distance.

  • Many described the site as feeling outdated or “archival,” signaling a need for more dynamic, community-driven content.

    These findings helped us prioritize accessibility improvements, clearer content structure, and features that supported digital belonging.

Design Goals

Improve usability across age groups and increase connection to the Center.

We set measurable goals: 80% of seniors should be able to confidently use the site, and over half of users should report feeling more connected after using it. We also aimed to create a system that the FACGC team could update independently.

Research & Strategy

We used card sorting and an impact-effort matrix to focus on what mattered most.

Card sorting helped us simplify and reorganize the site’s structure based on how users expected to find content. The impact-effort matrix allowed us to identify high-value, quick-win features such as:

  • An events calendar with filtering and pop-up RSVPs

  • A persistent, well-placed newsletter sign-up

  • Quick action buttons to reduce friction

  • A resource spotlight on the homepage

  • Visual labels to help categorize types of events

Key Design Decisions

We focused on clarity, accessibility, and maintainability across desktop and mobile.

We embraced a mobile-first, accessible layout system and built out scalable components to ensure consistency across pages and devices. Each phase of design (low fidelity to high) was critiqued by peers, clients, mentors, and test users. Some key decisions included:

  • Event access was redesigned around list views and modal pop-ups, since full calendar views tested poorly with older users and on mobile.

  • Navigation was restructured around six clear tabs: Home, Events, Community, Contribute, Newsletter, and About—with breadcrumbs and template pages for scalability.

  • The newsletter was embedded both as a page and persistent footer sign-up, based on task success rates and industry conventions.

  • Accessibility was addressed via visual contrast, button sizing, mobile responsiveness, and simplified copy, especially for users with lower digital literacy.


Key Design Decisions

We focused on clarity, accessibility, and maintainability across desktop and mobile.

We embraced a mobile-first, accessible layout system and built out scalable components to ensure consistency across pages and devices. Each phase of design (low fidelity to high) was critiqued by peers, clients, mentors, and test users. Some key decisions included:

  • Event access was redesigned around list views and modal pop-ups, since full calendar views tested poorly with older users and on mobile.

  • Navigation was restructured around six clear tabs: Home, Events, Community, Contribute, Newsletter, and About, with breadcrumbs and template pages for scalability.

  • The newsletter was embedded both as a page and persistent footer sign-up, based on task success rates and industry conventions.

  • Accessibility was addressed via visual contrast, button sizing, mobile responsiveness, and simplified copy, especially for users with lower digital literacy.


Key Design Decisions

We focused on clarity, accessibility, and maintainability across desktop and mobile.

We embraced a mobile-first, accessible layout system and built out scalable components to ensure consistency across pages and devices. Each phase of design (low fidelity to high) was critiqued by peers, clients, mentors, and test users. Some key decisions included:

  • Event access was redesigned around list views and modal pop-ups, since full calendar views tested poorly with older users and on mobile.

  • Navigation was restructured around six clear tabs: Home, Events, Community, Contribute, Newsletter, and About, with breadcrumbs and template pages for scalability.

  • The newsletter was embedded both as a page and persistent footer sign-up, based on task success rates and industry conventions.

  • Accessibility was addressed via visual contrast, button sizing, mobile responsiveness, and simplified copy, especially for users with lower digital literacy.


Testing Outcomes & Impact

Usability testing showed major improvements in speed and satisfaction.

  • We ran a between-subjects usability test with 40 participants comparing the old vs. new site.

    • Task times dropped by 77% on mobile and 55% on desktop

    • Event discovery on mobile was 92% faster

    • SUS scores rose from 77 to 89 (96th percentile)

    • Users felt more likely to attend in-person events after using the new version

Full Mobile Prototype
Final Design Highlights

We delivered a modular, accessible design system built for both users and maintainers.

  • Welcoming homepage with resource spotlights

  • Event RSVP modals and calendar integration

  • Newsletter sign-up embedded site-wide

  • Flexible template page system for sustainability and easy content updates by board members

  • Clean mobile-first navigation with breadcrumbs and sticky table of contents

💻 View Desktop Prototype Here! | 📱 View Mobile Prototype Here!

Final Design Highlights

  • Welcoming homepage with resource spotlights

  • Event pop-ups with RSVP and calendar integration

  • Template page system for scalability

  • Newsletter sign-up embedded site-wide

  • Clean mobile-first navigation with breadcrumbs and sticky table of contents

💻 View Desktop Prototype Here!

📱 View Mobile Prototype Here!

Reflection

Designing for a multi-generational community site pushed me to rethink assumptions, prioritize simplicity, and stay grounded in user realities.

Challenges I Faced:

  • Designing for multiple generations at once
    We had to balance the needs of seniors with low digital literacy, middle-aged professionals short on time, and younger users familiar with modern UI patterns. Their expectations, devices, and mental models were very different.

  • Translating emotional needs into usable features
    Users described feeling disconnected, unwelcome, or confused. It took work and thoughtful consideration to translate those feelings into design decisions like newsletter placement, event labeling, and homepage tone.

  • Letting go of ideas that weren’t feasible
    We explored ambitious features like a community bulletin board and forum system. But without clear moderation plans, we had to scale back and find simpler ways to support engagement.

  • Navigating stakeholder expectations and constraints
    Our client team had a strong cultural vision but limited technical resources. Every decision had to consider future sustainability, even if it meant dialing back on more complex UI components.

What I Learned:

  • Accessibility isn’t a just checklist
    From calendar pop-ups to text size and button placement, every decision was an opportunity to make the site easier to use for someone who might otherwise be excluded.

  • Simple features can create real impact
    A well-placed event card or a resource banner on the homepage can make the difference between someone closing the tab or deciding to show up in person.

  • Community-centered design requires humility
    I had to slow down, ask better questions, and not assume what users needed. The best takeaways often come from letting these community members serve as the expert in their own experiences, and my team's function is to be the facilitators. I learned how to let the community lead and build tools around their lived realities, not just best practices.

Reflection

Challenges I Faced:

  • Designing for multiple generations at once
    We had to balance the needs of seniors with low digital literacy, middle-aged professionals short on time, and younger users familiar with modern UI patterns. Their expectations, devices, and mental models were very different.

  • Translating emotional needs into usable features
    Users described feeling disconnected, unwelcome, or confused—but not in UX terms. It took work to translate those feelings into design decisions like newsletter placement, event labeling, and homepage tone.

  • Letting go of ideas that weren’t feasible
    We explored ambitious features like a community bulletin board and forum system. But without clear moderation plans, we had to scale back and find simpler ways to support engagement.

  • Navigating stakeholder expectations and constraints
    Our client team had a strong cultural vision but limited technical resources. Every decision had to consider future sustainability, even if it meant dialing back on more complex UI components.


What I Learned:

  • Accessibility isn’t a just checklist
    From calendar pop-ups to text size and button placement, every decision was an opportunity to make the site easier to use for someone who might otherwise be excluded.

  • Simple features can create real impact
    A well-placed event card or a resource banner on the homepage can make the difference between someone closing the tab—or deciding to show up in person.

  • Community-centered design requires humility
    I had to slow down, ask better questions, and not assume what users needed. The best takeaways often come from letting these community members serve as the expert in their own experiences, and my team's function is to be the facilitators. I learned how to let the community lead and build tools around their lived realities, not just best practices.

Reflection

Challenges I Faced:

  • Designing for multiple generations at once
    We had to balance the needs of seniors with low digital literacy, middle-aged professionals short on time, and younger users familiar with modern UI patterns. Their expectations, devices, and mental models were very different.

  • Translating emotional needs into usable features
    Users described feeling disconnected, unwelcome, or confused—but not in UX terms. It took work to translate those feelings into design decisions like newsletter placement, event labeling, and homepage tone.

  • Letting go of ideas that weren’t feasible
    We explored ambitious features like a community bulletin board and forum system. But without clear moderation plans, we had to scale back and find simpler ways to support engagement.

  • Navigating stakeholder expectations and constraints
    Our client team had a strong cultural vision but limited technical resources. Every decision had to consider future sustainability, even if it meant dialing back on more complex UI components.


What I Learned:

  • Accessibility isn’t a just checklist
    From calendar pop-ups to text size and button placement, every decision was an opportunity to make the site easier to use for someone who might otherwise be excluded.

  • Simple features can create real impact
    A well-placed event card or a resource banner on the homepage can make the difference between someone closing the tab—or deciding to show up in person.

  • Community-centered design requires humility
    I had to slow down, ask better questions, and not assume what users needed. The best takeaways often come from letting these community members serve as the expert in their own experiences, and my team's function is to be the facilitators. I learned how to let the community lead and build tools around their lived realities, not just best practices.

If I Had More Time…

I would have expanded inclusive testing, refined wording, and supported long-term implementation.

With more time, I would’ve conducted dedicated testing sessions with Tagalog-speaking seniors and users with low digital literacy to better validate accessibility across language and ability. I’d A/B test navigation labels like “Community” and “Contribute,” which some users found unclear. I also would’ve piloted CMS training with staff and explored additional participatory features like user-submitted photos or testimonials to bring more community voice onto the site.