mozillaclient

Product Designer at Playground Inc. · Feb 2019 – Jan 2021

Mozilla Community Portal

UX and UI design across Mozilla’s community portal.

  • UX + UI design

Overview

Role
Product Designer at Playground Inc.
Period
Feb 2019 – Jan 2021
Team
  • Mozilla Project Manager
  • Mozilla Ecosystem Designer
  • Mozilla Product Manager
  • 2 × Mozilla Community Managers
  • Product Designer (me)
  • 2 × Software Developers
Platform
WordPress

The project

One home for the Mozilla community

The Mozilla Community Portal is a place that facilitates communication between the Mozilla community and its members, and directs efforts towards Mozilla’s initiatives.

As a Product Designer at Playground Inc., I worked on the portal: a collaborative web experience designed to connect Mozillians with key community initiatives. Our goal was to consolidate various communication channels into a single platform that showcases events, groups and impactful campaigns. By leveraging Figma’s sharing capabilities, we invited hundreds of community members to provide real-time feedback from initial sketches through to the final high-fidelity design.

Problem space

Too many places to be a Mozillian

Mozillians needed a centralized space where they could:

  • Discover events and groups
  • Learn about community members and initiatives
  • Access and engage with impactful Mozilla campaigns and activities

Prior to this project, Mozillians were juggling multiple platforms (Activate, Splash, Discourse, the Reps Portal) to meet their needs. A unified portal was essential for effective community management and consistent communication by Mozilla’s Community Managers.

Getting started

Working in the open

To manage communication and collaboration between our product team and the Mozilla community, we used:

  • Slack for team communication
  • Mural for collaborative design exercises
  • Google Suite and Figma for sharing functional and design artifacts

Our approach began with a comprehensive exploration:

  1. Researching existing platforms and breaking down client briefings
  2. Developing detailed user personas
  3. Outlining current user journeys and envisioning ideal states
  4. Generating persona-based user stories, then sorting and grouping them into epics for translation into the final product

UX research · Exploratory sprint

Four personas

After our preliminary research, we ran a focused five-day “Exploratory” sprint built around three group exercises: persona development, user journey mapping and user story development.

These exercises were critical in transferring knowledge between team members. Community Managers were extremely helpful in defining and transferring knowledge about the target audience. As a group, we were slowly uncovering and developing a shared knowledge of the problem space.

  • persona.katyaNew volunteer

    Katya

    “I’m always looking for new opportunities to gain new skills and meet new people.”

  • persona.rheaParticipant

    Rhea

    “I have similar values to that of Mozilla’s mission. I care deeply about privacy and security.”

  • persona.ajayOrganizer

    Ajay

    “I’ve always wanted to start something, a group or meetup. I love organizing and managing.”

  • persona.kirstyStaff

    Kirsty

    “I need to target and mobilize the right contributors towards impactful campaigns.”

UX research · Journeys

User journey mapping

We analyzed how Mozillians used various tools (Discourse for communication, Activate for hosting activities, Splash for event discovery) to accomplish their goals. By visualizing each persona’s relationship with Mozilla across multiple touchpoints, we created timelines that captured key user actions, thoughts and emotions.

Each narrative was then revised and condensed to form a more accurate representation of each persona’s optimal journey.

A virtual sprint board titled MDM Portal Virtual Sprint, showing three journeys for Kirsty, the community manager persona. Each journey has a goal and a row of steps, with sticky notes for actions, thoughts and opportunities, plus green notes with open questions.
Kirsty’s journeys, one of four persona timelines from our virtual sprint: her actions, thoughts and opportunities at each step, with the team’s open questions alongside.

UX research · Stories

From insights to user stories

The insights gathered were translated into a comprehensive set of user stories. Every team member, from community managers to developers, contributed ideas. We worked in two steps:

  1. Writing as much as possible. We encouraged everyone on the team to write as many user stories as they could; the goal was to be plentiful, not critical.
  2. Sorting and expanding. We then went through the user stories, removing redundancies, cleaning errors and looking for patterns. Related user stories were grouped into higher-level patterns (epics).

Each persona had its own set of user stories. We used Google Sheets to manage and sort them, and made the document available to the whole team.

A Google Sheet titled Mozilla MDM: Stories and Functional Specs, showing user stories for Katya, the new volunteer persona, in As a / I want to / so that columns, grouped under colour-coded epics: Search/Filter, Group and Events.
Katya’s user stories, grouped into epics such as Search/Filter, Group and Events. Each persona had its own tab.
Sticky notes: yellow user stories about learning who is active in a group, and a blue “Attend Events” epic with pink stories beneath it for RSVPing, checking in, sharing feedback, sharing on social media and being recognized for a first event.
Sorting sticky notes into epics, such as “Attend Events.”

UI design

From UX research to UI design

Each epic (for example “Create Event” or “Create Group”) was translated into a series of wireframes. These evolved through three stages:

  • Low-fidelity sketches to quickly iterate on concepts
  • Mid-fidelity wireframes to refine layout and functionality
  • High-fidelity screens that integrated community feedback into a polished design

A comprehensive design system was established to ensure consistency throughout the platform.

Community feedback shaped each stage. On the hand-drawn group page, one reviewer wondered whether “Join group,” the page’s main action, should sit higher in the hierarchy. By the mid-fidelity version it had moved to the top of the page, and in the final design it became the page’s primary button.

The high-fidelity Mozilla Community Portal group page: a verified group with a long sample name, About Us, Our Events and Our Members tabs, a photo of community members in matching blue shirts, Join Group and Share Group buttons, activity stats, related events and group admins.
High-fidelity: the final group page design.
The Mozilla Community Portal design system in three sections: Foundation, with icons, a colour palette and a type scale from Display XXL down to body text; Elements, with buttons, tags, input fields, dropdowns, checkboxes and radio buttons; and Components, with activity, campaign, event, group and member cards.
The design system behind every screen: foundations (icons, colour and type), elements such as buttons and form fields, and components like event, group and member cards.

Result

A central hub for Mozillians

The Mozilla Community Portal now serves as a central hub for Mozillians to discover events, join groups and engage with Mozilla’s initiatives, all while supporting community management efforts.

Visit community.mozilla.org (opens in a new tab)

Next project