abouse@umich.edu

Click to Copy!

abouse@umich.edu

abouse@umich.edu

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 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

  • 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.

Understanding the Audience

Our audience spanned three generations of Filipino Americans:

Instead of assuming what users needed, we grounded our work in direct feedback from the community. We surveyed 61 people and interviewed 12, covering three generations of users from digitally proficient retirees to busy working parents and younger professionals new to the area.

We brought those voices to life through three personas and a storyboard.

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

  • 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.

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

Instead of assuming what users needed, we grounded our work in direct feedback from the community. We surveyed 61 people and interviewed 12, covering three generations of users from digitally proficient retirees to busy working parents and younger professionals new to the area.

We brought those voices to life through three personas and a storyboard.

  • Daniel moves to Chicago for a new job and finds his way to a community potluck through the Rizal Center’s updated website.

  • Tony, an immigrant with limited tech proficiency, looking for structure and the sense of community that he misses from the Philippines.

  • 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.

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

Insights & User Research

We used mixed methods to deeply understand the users we would be designing for:

Surveys (n=61)

  • 51% of users were 18–34, 24% were 35–54, and 25% were 55+

  • 76% preferred in-person events, but 69.5% were interested in digital community features

Interviews & Usability Testing (12 interviews, 8 tests)

  • Device Use by Age
    54% use mobile to access the site. Users 55+ mostly use desktop; 26.7% don’t regularly use a computer.

  • Digital Belonging
    76.3% prefer in-person events, but 69.5% want an online space, showing strong demand for digital connection.

  • Site Feels Static
    Many said the site feels like an archive, not a vibrant community space. They want more dynamic, up-to-date content.

  • Navigation Gaps
    Rated 4.46/5 for ease of use, but users struggled to find key features, especially the newsletter sign-up.

  • Senior Accessibility
    Seniors had difficulty finding the newsletter and navigating on mobile, highlighting the need for clearer paths and mobile-friendly design.

  • Community = Belonging
    Users defined community as shared values and connection. Digital spaces are seen as essential for staying in touch especially when physically far from cultural hubs.

Design Goals

With our user research as our foundation, we came up with the following goals our design needed to deliver:

  • Ensure at least 80% of participating seniors can confidently navigate the redesigned website during usability testing.

  • Have over 50% of users report an increased sense of connection to the Rizal Center as a result of the new design.

  • Deliver a comprehensive final report summarizing our research insights, design decisions, and testing results to support future development efforts by the FACGC team.

Research & Strategy

We used card sorting to re-architect the navigation and uncover mental models across age groups. We learned that while the desire to stay involved was high, key friction points (especially around event access and outdated content) were pushing users away.

We translated our research into clear priorities using an impact vs. effort matrix. This allowed us to identify high-value, quick-win features like:

  • 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 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 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

  • 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

    For many, the redesigned site was the first time they saw their experiences reflected in the interface: clean, welcoming, and easy to use regardless of age or tech confidence.

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!

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

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.

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…

If we had more time beyond our project timeline, I would have continued work in five key areas:

1. Conducting more inclusive testing
I would have prioritized dedicated sessions with older adults who had limited digital literacy and Tagalog-speaking users to ensure accessibility across language and ability.

2. Refining navigation through A/B testing
Some participants were confused by labels like “Community” and “Contribute.” Testing alternate terms like “Get Involved” or “Support Us” would help improve clarity and engagement.

3. Expanding community-driven features
I would have explored more participatory elements, such as photo galleries, user-submitted stories, or member testimonials to bring more lived experience and community voice onto the site.

4. Deepening accessibility testing
While we used accessible design principles (e.g., contrast, visual hierarchy), I would have conducted formal testing with screen readers, keyboard-only navigation, and high-contrast modes to validate WCAG compliance.

5. Stress-testing the CMS with stakeholders
To support long-term sustainability, I’d pilot the redesigned site on a visual CMS like Webflow or Squarespace, working directly with FACGC staff to ensure they could confidently update content without developer support.

Get in touch with me at

Get in touch with me at

Get in touch with me at