UX Lead with a passion for all things UX, IA, Product Design, and Music


Mozilla + Design Gym Workshop #2

Our 2nd Design Gym / Mozilla Developer Network collaborative workshop was held at Parsons last week. Besides our regular group of participants, we invited students from the MFA Design and Technology program to join us. Their insight (and enthusiasm!) was really invaluable to the evening. 


Now that we've had a chance to get to know our audience and get introduced to the problem at hand (see workshop #1 post), workshop #2 continues to further deconstruct and understand. We do this by focusing more on specific topics and hypotheses and applying them to a number of design models. (i.e.: 2x2 Matrix, Empathy Map, Journey Map, etc - see images for examples)


The topics I asked the teams to focus on are as follows:

  • Trust
  • Communication
  • Continuity
  • Functionality
  • Notoriety

What we learned and assumptions to start designing for

Experts and beginners have a symbiotic relationship

Beginners tend to need more structure and experts, less structure

Some learners don't realize that they can teach and have worth in the community

There are competing and corresponding elements in the same environment:

- Structured vs. Unstructured

- Beginner vs. Experienced

- Solo vs. Community

- Contributor vs. Reader

- Linear vs. Non-linear

3 ways of presenting content:

1. pre-packaged & syllabus 

2. with expectation and context ("when you are learning, you need to know where your north star is")

3. choose your own adventure

Continuity and connections between our content will lead to better collaboration among the community as well as a better understanding of all that MDN has to offer. 

Questions to explore further

How do we allow intimidated users to feel welcome in the community?

Experts are more likely to play and take risks - how can we draw the same behavior from others?

Why should an experienced coder help a beginner?

Why should I return to MDN?

Holly Habstritt Gaal