introduction.

what is design? class discussion.

design isn't just how it looks and feels — it's how it works.

3 things for best designs: useful, usable, and beautiful.

design should first be useful.

after it's useful and usable, then it should be beautiful.

aesthetics should never come at the expense of usefulness or usability.

useful — usable — beautiful.

do not get hung up on what tools to use for designing.

avoid the mistake of spending too much time on the first version of a design.

fundamentals of design — CHATS model.

C — contrast.

H — hierarchy.

A — alignment.

T — typography.

remember to be consistent.

the art of design.

our company's design process.

find your own process, and trust it.

mental model #1 — don't fall in love with tools.

mental model #3 — aim for iteration, not perfection.

reviewing student examples.

mental model #4 — variable lottery tickets.

imagine that the lottery is worth $1Billion.

class questions.

Intro

How to deliver a better user experience at scale

3 key areas for internal product development

Measuring user experience

Benefits of rapid design

Benefits of UXbeam

Creating filters

Wrap up

How long did it take to get product teams to adapt the new process?

Conclusion

Intro

Architectural template

Template Walkthrough

Adding Details for the Garage

Adding a visual divider

Adjusting the divider stroke

Drawing the front door

Adding Cobblestone

Line weight in architectural sketches

Conclusion

Database Design

Backend Servers

Restaurant Info Service

General Data Flow

Design Storage

Ways to do Geo Indexing

Geo Index Update

Scattered DesignOps

Dedicated Structure

Dedicated DesignOps Structure

Specialized DesignOps

Elevated

Intro

Davy Talk

How do new teams, such as the Threads team, build foundational aspects of their Design Systems?

What does Design Delivery mean to you?

How does comms and shareouts work for International teams/async?

You mentioned using bots for the Design System Phone Tree, do you build the bots internally or is there a bot you like to use?

You and I both know that Slack messages sometimes gets lost in the ether. Do you recommend any tools aside from Slack?

Whats the best practice to work with engineering to create great engagement in design systems?

In regards to the Venn Diagram you shared with us, do Product Designers, DesignOps, and Engineering spend equal time building and maintaining Deign Systems?

Do you look at other Design Systems during your podcast and give feedback?

How do you document where all the components and designs live so that any updates don't "break" a design?

How to you manage roll out of a change to a component if not all dev teams can implement at the same time?

What's your philosophy on designing components for better buy-in? Smaller components allowing for more freedom?

Davy do you have a portfolio? As someone who's worked on multiple design systems i'm curious how you set up your case studies!

What are your favorite DesignOps resources? Podcasts, books, blogs, Twitter profiles, etc.

Agenda

Matthew

What Is a Design System

Visual Consistency

How I Got into an Actual Design System Role

Governance

Does any Mentor Like To Add on any Tools That They Are Using

Scalability

What Skill Set Are Essential To Have When Creating Building or Maintaining a Design System

Social Media Platforms