Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Building Flexible Design Systems

Building Flexible Design Systems

Yesenia Perez-Cruz

November 01, 2017
Tweet

More Decks by Yesenia Perez-Cruz

Other Decks in Design

Transcript

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

    View Slide

  2. View Slide

  3. View Slide

  4. –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.

    View Slide

  5. How do you define
    a design system?

    View Slide

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

    View Slide

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

    View Slide

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

    View Slide

  9. Elements
    Interconnections
    Purpose

    View Slide

  10. A good design system feels:
    Cohesive
    Unified
    Connected

    View Slide

  11. A bad design system feels:
    Disjointed
    Confusing
    Difficult to use

    View Slide

  12. Elements
    Interconnections
    Purpose

    View Slide

  13. Start your design system 

    with user-scenarios.

    View Slide

  14. View Slide

  15. 8 brands
    350+ websites
    1 design system

    View Slide

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

    • Faster to launch new brands

    View Slide

  17. Tell better
    stories, faster

    View Slide

  18. View Slide

  19. View Slide

  20. Editorial Missions
    Content Types
    Audience Needs
    Typography & Branding
    Different

    View Slide

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

    View Slide

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

    View Slide

  23. 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?

    View Slide

  24. Early
    assumptions

    View Slide

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

    View Slide

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

    View Slide

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

    View Slide

  28. It’s legos, right?

    View Slide

  29. Too focused on 

    LAYOUTS

    View Slide

  30. 4-up
    2-up
    1-up

    View Slide

  31. View Slide

  32. View Slide

  33. View Slide

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

    View Slide

  35. View Slide

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

    View Slide

  37. Modules didn’t have a
    clear purpose.

    View Slide

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

    View Slide

  39. Elements
    Interconnections
    Purpose

    View Slide

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

    View Slide

  41. What we
    learned

    View Slide

  42. You can’t start
    with individual
    components

    View Slide

  43. Successful design
    patterns don’t exist in
    a vacuum.

    View Slide

  44. View Slide

  45. –Alla Kholmatova, The Language of Modular Design
    We should start with 

    language, not interfaces.

    View Slide

  46. Successful design
    systems start with
    content and people.

    View Slide

  47. Audience Editorial Content Revenue

    View Slide

  48. 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?

    View Slide

  49. 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.

    View Slide

  50. 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

    View Slide

  51. 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

    View Slide

  52. No hypothetical
    situations

    View Slide

  53. Identifying
    Scenarios

    View Slide

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

    View Slide

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

    View Slide

  56. –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.

    View Slide

  57. 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.

    View Slide

  58. View Slide

  59. Know your
    use case.
    –Salesforce, Lightning Design System

    View Slide

  60. 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/

    View Slide

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

    View Slide

  62. “Put Merchants First”

    View Slide

  63. View Slide

  64. “Callout cards are used to encourage merchants 

    to take an action related to a new feature 

    or opportunity”

    View Slide

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

    View Slide

  66. View Slide

  67. View Slide

  68. Scenario-driven design
    in practice

    View Slide

  69. View Slide

  70. Features

    View Slide

  71. View Slide

  72. Turn 18 distinct templates
    with 81 code snippets into 

    1 flexible design system

    View Slide

  73. Identifying Core
    Workflows

    View Slide

  74. Audience goals consistent
    across brands, but content
    differed.

    View Slide

  75. Audience Goals
    LEDE IMAGE
    TEXT BOX
    RECIRCULATION
    MODULE
    • Consume content

    • Find new content

    View Slide

  76. Scenario-driven
    variations

    View Slide

  77. View Slide

  78. LEDE IMAGE VARIATIONS

    View Slide

  79. HED BELOW
    Highlights
    photography

    View Slide

  80. HED ABOVE
    Prioritizes text
    over photography

    View Slide

  81. HED OVERLAY
    Photo as background,
    for lower quality images

    View Slide

  82. HED BELOW

    SHORT IMAGE
    Short image, valuable
    for illustration or
    widescreen images

    View Slide

  83. SIDE-BY-SIDE
    Specifically for
    vertical images

    View Slide

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

    View Slide

  85. Snippets

    View Slide

  86. Content
    Audit

    View Slide

  87. Content
    Audit
    • Does it add value?

    • Is it available to more than
    3 brands? 

    • Is it a must-have for 1
    brand?

    View Slide

  88. Snippet
    Examples

    View Slide

  89. Brand Expression

    View Slide

  90. View Slide

  91. View Slide

  92. View Slide

  93. View Slide

  94. Reviews

    View Slide

  95. View Slide

  96. The Scorecard

    View Slide

  97. View Slide

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

    View Slide

  99. View Slide

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

    View Slide

  101. 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

    View Slide

  102. VENUE CARD GAME CARD PRODUCT CARD

    View Slide

  103. VENUE CARD
    Highlights content that helps you
    find where to eat

    View Slide

  104. GAME CARD
    Highlights content specific to 

    games

    View Slide

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

    View Slide

  106. View Slide

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

    View Slide

  108. VENUE
    GAME
    PRODUCT
    After:

    View Slide

  109. Scorecard
    Variants

    View Slide

  110. View Slide

  111. Homepages

    View Slide

  112. View Slide

  113. Identifying Core
    Workflows

    View Slide

  114. • 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

    View Slide

  115. Talk to your audience

    View Slide

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

    View Slide

  117. • What’s new?

    • What’s important?

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

    View Slide

  118. 3 Main Areas of Purpose

    View Slide

  119. STORYFEED COVERS UTILITY

    View Slide

  120. • 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

    View Slide

  121. ENTRY BOX
    Standard entry box
    Map
    Review
    Storystream Group

    View Slide

  122. Scenario-driven
    variations

    View Slide

  123. 4-up
    2-up
    1-up

    View Slide

  124. View Slide

  125. NEWSPAPER
    A text-heavy layout for busy news reporting

    View Slide

  126. EVERGREEN
    A flexible layout that promotes both recent and evergreen content

    View Slide

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

    View Slide

  128. “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

    View Slide

  129. Brand Expression

    View Slide

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

    View Slide

  131. View Slide

  132. MASTHEAD
    Date, logo, tagline, image

    View Slide

  133. View Slide

  134. View Slide

  135. View Slide

  136. Scalable visual design
    system

    View Slide

  137. 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

    View Slide

  138. Foundational
    elements
    Room for
    customization
    +

    View Slide

  139. Foundational
    elements
    • Type scale

    • Color system
    • Spacing variables

    View Slide

  140. Type Scale

    View Slide

  141. Color System

    View Slide

  142. View Slide

  143. Color System

    View Slide

  144. Color System

    View Slide

  145. View Slide

  146. COLOR-HERO-GRADIENT
    COLOR-NAV-BG
    COLOR-LINK

    View Slide

  147. Good Variation Bad Variation
    vs

    View Slide

  148. 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

    View Slide

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

    View Slide

  150. View Slide

  151. View Slide

  152. View Slide

  153. View Slide

  154. View Slide

  155. Before:

    Custom one-off
    solutions

    View Slide

  156. View Slide

  157. View Slide

  158. View Slide

  159. View Slide

  160. Now:

    Telling better
    stories, faster

    View Slide

  161. What’s next?

    View Slide

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

    View Slide

  163. Successful design
    patterns don’t exist in
    a vacuum.

    View Slide

  164. Successful design
    systems solve
    specific problems.

    View Slide

  165. Successful design
    systems start with
    content and people.

    View Slide

  166. Thank
    you! @yeseniaa

    View Slide

  167. • The Language of Modular
    Design — Alla Kholmatova

    • Design Systems — Alla
    Kholmatova

    • A Pattern Language —
    Christopher Alexander

    • Thinking in Systems —
    Donella Meadows
    References

    View Slide