Slide 1

Slide 1 text

Yesenia Perez-Cruz An Event Apart—Seattle April 2018 Scenario-Driven Design Systems

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

–Karri Saarinen, Building a Visual Language A unified design system is essential to building better and faster; better because a cohesive experience is more easily understood by our users, and faster because it gives us a common language to work with.

Slide 5

Slide 5 text

How do you define a design system?

Slide 6

Slide 6 text

A collection of reusable components assembled to build any number of applications?

Slide 7

Slide 7 text

A system is an interconnected set of elements coherently organized in a way that achieves something. –Donella Meadows, Thinking in Systems

Slide 8

Slide 8 text

–Donella Meadows, Thinking in Systems A system is an interconnected set of elements coherently organized in a way that achieves something.

Slide 9

Slide 9 text

Elements Interconnections Purpose

Slide 10

Slide 10 text

A good design system feels: Cohesive Unified Connected

Slide 11

Slide 11 text

A bad design system feels: Disjointed Confusing Difficult to use

Slide 12

Slide 12 text

Elements Interconnections Purpose

Slide 13

Slide 13 text

Start your design system 
 with user-scenarios.

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

8 brands 350+ websites 1 design system

Slide 16

Slide 16 text

Why? • Easier to design, build, launch, maintain, and evolve the sites on our platform.
 • Faster to launch new brands

Slide 17

Slide 17 text

Tell better stories, faster

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

Editorial Missions Content Types Audience Needs Typography & Branding Different

Slide 21

Slide 21 text

Unify eight brand sites into one design and code system. 1

Slide 22

Slide 22 text

Provide enough flexibility to allow brands to still feel distinct. 2

Slide 23

Slide 23 text

Problems to solve • What patterns/components do we need to build?
 • How can these components be combined to create distinct experiences? • How can we create a unique look & feel for 300+ sites using one visual design system?

Slide 24

Slide 24 text

Early assumptions

Slide 25

Slide 25 text

Smaller, modular components come together to define a page. 1

Slide 26

Slide 26 text

Address inconsistencies in design: layout, color, typography, & treatments of similar information 2

Slide 27

Slide 27 text

Hypothesis: A set of flexible, brand-agnostic modules with a theming system will give us the most range.

Slide 28

Slide 28 text

It’s legos, right?

Slide 29

Slide 29 text

Too focused on 
 LAYOUTS

Slide 30

Slide 30 text

4-up 2-up 1-up

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

Sites felt too similar Did not reflect critical differences in content, tone, and audience 1. 2.

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

Homes & Neighborhoods Maps, Guides Tech & Business News, Podcasts

Slide 37

Slide 37 text

Modules didn’t have a clear purpose.

Slide 38

Slide 38 text

–Donella Meadows, Thinking in Systems A system is an interconnected set of elements coherently organized in a way that achieves something.

Slide 39

Slide 39 text

Elements Interconnections Purpose

Slide 40

Slide 40 text

New Hypothesis: In order to create a flexible system, we needed to start by being specific.

Slide 41

Slide 41 text

What we learned

Slide 42

Slide 42 text

You can’t start with individual components

Slide 43

Slide 43 text

Successful design patterns don’t exist in a vacuum.

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

–Alla Kholmatova, The Language of Modular Design We should start with 
 language, not interfaces.

Slide 46

Slide 46 text

Successful design systems start with content and people.

Slide 47

Slide 47 text

Audience Editorial Content Revenue

Slide 48

Slide 48 text

What’s the audience goal? Is there a shared audience goal across all of our brands or are there differences? 
 What’s the editorial workflow? What range of content should this support?

Slide 49

Slide 49 text

Start with fast, unified platform
 Be scenario-driven when creating variations
 Find key moments for visual brand expression that serve our audience 1. 2. 3.

Slide 50

Slide 50 text

Fast, Unified Platform • Our platform should load quickly, be accessible, and work well across devices • We should have a unified core user experience
 • All components that we build should be available to all brands

Slide 51

Slide 51 text

Scenario-Driven Variations • Scenarios, not layout, should drive variation • All patterns should solve a specific problem • We’re not creating a one-size- fits-all solution

Slide 52

Slide 52 text

No hypothetical situations

Slide 53

Slide 53 text

Identifying Scenarios

Slide 54

Slide 54 text

“UI Inventory” Brad Frost, http://bradfrost.com/blog/post/interface-inventory/

Slide 55

Slide 55 text

“Purpose-Directed Inventory” Alla Kholmatova, https://www.smashingmagazine.com/design-systems-book/

Slide 56

Slide 56 text

–Alla Kholmatova, Design Systems Keeping this map in my mind helped me think in families of patterns joined by a shared purpose, rather than individual pages.

Slide 57

Slide 57 text

Identify core workflows and the patterns that need to support these workflows. Understand the role each pattern plays in a user’s journey. Define how the patterns work together 
 to create a cohesive experience.

Slide 58

Slide 58 text

No content

Slide 59

Slide 59 text

Know your use case. –Salesforce, Lightning Design System

Slide 60

Slide 60 text

Workspace Facilitates user collaboration on records Board For items that are advancing through a linear workflow Reference For when users are primarily jumping to related records Salesforce, https://www.lightningdesignsystem.com/guidelines/layout/

Slide 61

Slide 61 text

via: Shopify, https://polaris.shopify.com

Slide 62

Slide 62 text

“Put Merchants First”

Slide 63

Slide 63 text

No content

Slide 64

Slide 64 text

“Callout cards are used to encourage merchants 
 to take an action related to a new feature 
 or opportunity”

Slide 65

Slide 65 text

https:/ /playbook.cio.gov/designstandards/

Slide 66

Slide 66 text

No content

Slide 67

Slide 67 text

No content

Slide 68

Slide 68 text

Scenario-driven design in practice

Slide 69

Slide 69 text

No content

Slide 70

Slide 70 text

Features

Slide 71

Slide 71 text

No content

Slide 72

Slide 72 text

Turn 18 distinct templates with 81 code snippets into 
 1 flexible design system

Slide 73

Slide 73 text

Identifying Core Workflows

Slide 74

Slide 74 text

Audience goals consistent across brands, but content differed.

Slide 75

Slide 75 text

Audience Goals LEDE IMAGE TEXT BOX RECIRCULATION MODULE • Consume content
 • Find new content

Slide 76

Slide 76 text

Scenario-driven variations

Slide 77

Slide 77 text

No content

Slide 78

Slide 78 text

LEDE IMAGE VARIATIONS

Slide 79

Slide 79 text

HED BELOW Highlights photography

Slide 80

Slide 80 text

HED ABOVE Prioritizes text over photography

Slide 81

Slide 81 text

HED OVERLAY Photo as background, for lower quality images

Slide 82

Slide 82 text

HED BELOW
 SHORT IMAGE Short image, valuable for illustration or widescreen images

Slide 83

Slide 83 text

SIDE-BY-SIDE Specifically for vertical images

Slide 84

Slide 84 text

Only add a layout if there’s a content need.

Slide 85

Slide 85 text

Snippets

Slide 86

Slide 86 text

Content Audit

Slide 87

Slide 87 text

Content Audit • Does it add value?
 • Is it available to more than 3 brands? 
 • Is it a must-have for 1 brand?

Slide 88

Slide 88 text

Snippet Examples

Slide 89

Slide 89 text

Brand Expression

Slide 90

Slide 90 text

No content

Slide 91

Slide 91 text

No content

Slide 92

Slide 92 text

No content

Slide 93

Slide 93 text

No content

Slide 94

Slide 94 text

Reviews

Slide 95

Slide 95 text

No content

Slide 96

Slide 96 text

The Scorecard

Slide 97

Slide 97 text

No content

Slide 98

Slide 98 text

Initial design 1 SCORECARD component with 3 sections: meta info, open text field, CTAs

Slide 99

Slide 99 text

No content

Slide 100

Slide 100 text

Where to eat What to order What game to buy What product to buy

Slide 101

Slide 101 text

Address Cost Rating out of 4 stars Book a Table Platform(s) Publisher Score out of 10 points Release Date Product Image Pro/Con List Score out of 10 points Buy Now Buttons

Slide 102

Slide 102 text

VENUE CARD GAME CARD PRODUCT CARD

Slide 103

Slide 103 text

VENUE CARD Highlights content that helps you find where to eat

Slide 104

Slide 104 text

GAME CARD Highlights content specific to 
 games

Slide 105

Slide 105 text

PRODUCT CARD Highlights content that is specific to products with Buy Now buttons

Slide 106

Slide 106 text

No content

Slide 107

Slide 107 text

ONE SCORECARD First unified version: Content has the same hierarchy across the board

Slide 108

Slide 108 text

VENUE GAME PRODUCT After:

Slide 109

Slide 109 text

Scorecard Variants

Slide 110

Slide 110 text

No content

Slide 111

Slide 111 text

Homepages

Slide 112

Slide 112 text

No content

Slide 113

Slide 113 text

Identifying Core Workflows

Slide 114

Slide 114 text

• What’s the value of the homepage today?
 • Who’s our homepage audience?
 • What are they looking for?
 • How are our current homepages performing? Research Phase

Slide 115

Slide 115 text

Talk to your audience

Slide 116

Slide 116 text

The audience from our user survey was more likely to use a phone, more likely to follow links from social media.

Slide 117

Slide 117 text

• What’s new?
 • What’s important?
 • What’s helpful? The homepage should clearly answer these 3 questions:

Slide 118

Slide 118 text

3 Main Areas of Purpose

Slide 119

Slide 119 text

STORYFEED COVERS UTILITY

Slide 120

Slide 120 text

• Higher content density so users can see more content at a glance
 • Reverse chronological order
 • Priority is quick 
 consumption of content to serve the engaged homepage audience of repeat visitors STORY FEED

Slide 121

Slide 121 text

ENTRY BOX Standard entry box Map Review Storystream Group

Slide 122

Slide 122 text

Scenario-driven variations

Slide 123

Slide 123 text

4-up 2-up 1-up

Slide 124

Slide 124 text

No content

Slide 125

Slide 125 text

NEWSPAPER A text-heavy layout for busy news reporting

Slide 126

Slide 126 text

EVERGREEN A flexible layout that promotes both recent and evergreen content

Slide 127

Slide 127 text

MORNING RECAP A hero for the morning after a busy night of sporting events

Slide 128

Slide 128 text

“In the process of naming an element, you work out the function as a group and reach an agreement.” Alla Kholmatova, The Language of Modular Design

Slide 129

Slide 129 text

Brand Expression

Slide 130

Slide 130 text

PROMO BAR Featured hero area to highlight additional stories/ content underneath main stories section

Slide 131

Slide 131 text

No content

Slide 132

Slide 132 text

MASTHEAD Date, logo, tagline, image

Slide 133

Slide 133 text

No content

Slide 134

Slide 134 text

No content

Slide 135

Slide 135 text

No content

Slide 136

Slide 136 text

Scalable visual design system

Slide 137

Slide 137 text

Key Moments for Brand Expression • We must create a platform where brands can feel distinct • We need to express strong editorial voice and identity • Brand expression is more than just colors and logo

Slide 138

Slide 138 text

Foundational elements Room for customization +

Slide 139

Slide 139 text

Foundational elements • Type scale
 • Color system • Spacing variables

Slide 140

Slide 140 text

Type Scale

Slide 141

Slide 141 text

Color System

Slide 142

Slide 142 text

No content

Slide 143

Slide 143 text

Color System

Slide 144

Slide 144 text

Color System

Slide 145

Slide 145 text

No content

Slide 146

Slide 146 text

COLOR-HERO-GRADIENT COLOR-NAV-BG COLOR-LINK

Slide 147

Slide 147 text

Good Variation Bad Variation vs

Slide 148

Slide 148 text

Good Variation • If there’s a specific problem that we need a new pattern to solve • Determined by user scenarios and content needs • Strengthens brand voice in a way that serves our audience

Slide 149

Slide 149 text

Bad Variation • Visual variation on components that serve the same function across brands, • Don’t do much to strengthen brand voice

Slide 150

Slide 150 text

No content

Slide 151

Slide 151 text

No content

Slide 152

Slide 152 text

No content

Slide 153

Slide 153 text

No content

Slide 154

Slide 154 text

No content

Slide 155

Slide 155 text

Before:
 Custom one-off solutions

Slide 156

Slide 156 text

No content

Slide 157

Slide 157 text

No content

Slide 158

Slide 158 text

No content

Slide 159

Slide 159 text

No content

Slide 160

Slide 160 text

Now:
 Telling better stories, faster

Slide 161

Slide 161 text

What’s next?

Slide 162

Slide 162 text

Now that we’re on a unified platform, we can create even more tailored experiences at scale.

Slide 163

Slide 163 text

Successful design patterns don’t exist in a vacuum.

Slide 164

Slide 164 text

Successful design systems solve specific problems.

Slide 165

Slide 165 text

Successful design systems start with content and people.

Slide 166

Slide 166 text

Thank you! @yeseniaa

Slide 167

Slide 167 text

• The Language of Modular Design — Alla Kholmatova
 • Design Systems — Alla Kholmatova
 • A Pattern Language — Christopher Alexander
 • Thinking in Systems — Donella Meadows References