For designers

The most important artifact isn’t the Figma file, or even the annotations.

It’s the conversation it facilitates about UX with the devs.

UX stands for User Experience

As a designer, it’s your responsibility to direct developers to create a good experience for all people.

Developers will make the UX decisions you don’t.

Helping people read stuff is good UX

People don’t come here to look at your glorious UI design. They are here to consume words that will solve their own problems.

Workshop 1: Page structure

Workshop 2: Alternative text

Helping people click stuff is good UX

We set expectations visually that help people understand and trust our product. We must do the same for people using a screen reader.

Helping people have a conversation is good UX

Inputs allow people using our product to talk to us. Our job is to make sure we aren’t making it difficult to speak by choosing the right inputs.

Workshop 4: Text inputs are harder than you think

Helping people refine the conversation is good UX

Radio buttons, checkboxes, switches and selects allow you to have a precise conversation with people using the product. But what happens when a control doesn’t look like one of these?

Workshop 5: Input mental models

Single selection

Multiple selection

System settings

What is it?

Sometimes interrupting the conversation is good UX

There are good reasons to stop the flow, but let’s do it the right way.

Workshop 6: Complex content interactions

Stopping everything

Deciding what’s important now

Intentionally hiding content

Workshop 7: Things going wrong can be good UX