top of page

Pro Unlimited Contractor @Meta

I worked on the UXR Community Builders Pillar @Facebook.


Pillar Goals:

  • Help everyone express who they are and connect with others in their communities.

  • Support and empower everyone to build thriving, safe, inclusive, and well-governed communities.

  • Enable community builders to be deeply engaged, effective, and efficient in managing their communities.

I studied both Pages (both Admins & Followers), and Public Groups (both Admins & Members).

I designed studies that address user behavior and attitudes, generating insights that fuel ideation and design evaluation, including diversity, equity, and inclusion perspectives.

I used storytelling to convey results and illustrated recommendations in compelling and creative ways.



Advantages of Rolling Research

  • It is more efficient to implement than conventional session-by-session research because of its predetermined schedule and the same core methodologies used in each session.

  • Giving constant feedback from users to help support fast product development.

  • It provides new and vital insights on subjects that have not been prioritized yet.

  • Creating a consistent research-centric atmosphere that helps clear backlogs and help make room for small and significant projects.

  • It supports various teams simultaneously and allows multiple units to run multiple tests
    in one session.

  • Facilitating persistent connections with the users to ensure the designs meet their needs.

  • Demonstrating deep user-base expertise. Providing another channel for feedback to support dispelling research myths.

Disadvantages of Rolling Research

  • It can be limited only to evaluative questions.

  • Rolling research can be very demanding of time and resources, especially at a frequent cadence, weekly.

  • It is not a replacement for generative or foundational research.

  • The moderator typically doesn't have enough time for exhaustive probing because it's best to limit each hour-long session to 3 products or concepts so it's not overwhelming. 

Objective & Motivation

  • Provide the team with timely insights on this new product/project.

  • Conducting rolling research over six months for the Communities team, Admin Management team, and partner teams.

  • Goals: Understand users' reactions to the given design and provide that feedback to the product teams.




Monthly cadence

  • I prepped with cross-functional partners (XFNs) for a week.

  • The studies were conducted with Admins (Pages & Public Groups) for two days at the beginning of the month. The Members & Followers studies were conducted for two days at the end of the month.

  • I would spend three days to a week conducting the analysis depending on the number of participants (3-12).

  • I then prepared and presented the Share Out with stakeholders within 2-3 days of completing the analysis. 

I conducted four rounds during a 6 month period (4 rounds with admins and 4 rounds with followers and members).


Research Foundation

Previous Research:

  • Foundational: Perspective from Public Figures and Creators/Celebrities & Small and Medium Businesses

  • Admin Roles & Permission Research

  • “Product” Foundational Study and Follow-Up


Research Questions

  • What are users’ reactions to a given iteration?

  • Key dimensions include:

    • Comprehension

    • Usability

    • Value / Delight 

    • Manageability

Key Stakeholders

  • Community Builders UXR Team

  • Communities Team

  • Admin Management Team


Semi-Structured Interviews

1:1 Interview

Length: 60 minutes

Concept Testing

Moderated: validate product, design,
and content

Usability Testing

Moderated: evaluating the product and if users can successfully complete
given tasks

Content Testing

Moderated: users are
asked to respond
to copy only

Analysis Plan

Used a mix of open (Inductive) coding and closed (Deductive) coding methods.



  • The feedback helped unblock key product decisions and de-risk upcoming product milestones.

  • I provided feedback on new designs and content, unblocking key product questions around various features (including placement), naming, and content organization.

  • I identified the product's value to users.

  • I worked to identify key user pain points.

    • Example: comprehension and user educational gaps

  • We learned how the product would intersect with other teams and products.

bottom of page