🖐 Friday Five (Pair Designing, Strategy for Success, Designing in Code)

Hi friends!

We're back with our 18th issue of Friday Five, a weekly email with our top 5 finds to help you level up as a designer. Here's what we want to share with you this week.

👀 ICYMI: Our second UI Prep project "Recreate Asana's Dashboard" launches next week! You'll learn how to build a fully responsive dashboard with auto layout, constraints, variants, and more. It's 100% free. Keep an eye out for the email on Tuesday.

This week's Finds:

  1. Designing in Code

  2. What's a Design System?

  3. Discord's Product Strategy

  4. Strategy for Success

  5. Pair Designing

1) “Should designers code?” is an obsolete debate

At this point, the age-old “should designers code?” debate is mostly irrelevant. Designers should do whatever they need to do to make things happen, in whatever circumstances they’re in.

2) So, what actually is a Design System?

Design systems are systems of systems, but not all systems are part of the design system. Confused? You’re certainly not alone. This post articulates how Brad Frost's own definition of a design system has recently changed to address hard-earned lessons.

3) Discord is a Portal to the Metaverse

A detailed breakdown of Discord's product strategy and how they can position themselves to be the gateway to the Metaverse.

4) Do the Real Thing

Success largely boils down to a simple distinction. It’s glaringly obvious once you see it, but also easy to find ingenious ways of ignoring it: do the real thing and stop doing fake alternatives.

5) Rethinking the term "Design Critique"

People are starting to think “critique” is the wrong framing, because it’s inherently negative, and collaborative design is more about working positively towards the best solution. Engineers have "pair programming", perhaps it's time for designers to have "pair designing".

Have a great weekend!

Molly and Jake at UI Prep