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

Managing Design Systems (Smashing NY 2024)

Nathan Curtis
October 09, 2024

Managing Design Systems (Smashing NY 2024)

Nathan Curtis

October 09, 2024
Tweet

More Decks by Nathan Curtis

Other Decks in Design

Transcript

  1. © Copyright 2024 • Directed Edges LLC Managing Design Systems

    By Nathan Curtis for SmashingConf NYC Brighton, UK • October 9, 2024 From features and releases to roadmaps and backlogs
  2. © Copyright 2024 • Directed Edges LLC About me Fairfax,

    VA (near Washington, DC) Worked on ~85 design systems since 2006 Blog at medium.com/@nathan curtis a Socialize on linkedin.com, twitter.com @nathan curtis a Hi, I’m Nathan
  3. © Copyright 2024 • Directed Edges LLC Office hours &

    consulting Projects like component composition, library architecture, and strategy and planning Embedded as lead Learn more at www.directededges.com
  4. © Copyright 2024 • Directed Edges LLC Who am I?

    I’m a design system architect I ❤️ tokens and UI components
  5. © Copyright 2024 • Directed Edges LLC Who am I?

    I’m a design system architect that and designs codes
  6. © Copyright 2024 • Directed Edges LLC What role do

    I play? I’m a design system architect ...that system work manages
  7. © Copyright 2024 • Directed Edges LLC What am I

    called? Product manager? Project manager?
  8. © Copyright 2024 • Directed Edges LLC What am I

    responsible for doing? Drive strategy Ensure quality Deliver releases Manage workflows Prioritize roadmaps Foster collaboration Align external stakeholders Develop team and individual skills
  9. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on Releases Workflow Plan Design Spec Code Figma asset Initiatives Roadmap Boards?
  10. © Copyright 2024 • Directed Edges LLC What am I

    – and – for? Is our team doing ? Do my matter? Am I at the right time(s)? Is my teammate’s work ? Can we better design and engineering? Can we work ? ... ? Do I know the we are going? responsible NOT responsible enough ideas included visible align faster smarter direction
  11. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on ?
  12. © Copyright 2024 • Directed Edges LLC Features / Things

    that design systems produce Workflow process Training curriculum Strategy and plans Analytics reports Design tokens UI components UX patterns Content guidance
  13. © Copyright 2024 • Directed Edges LLC Features / Things

    that design systems produce Workflow process Training curriculum Strategy and plans Analytics reports Design tokens UI components UX patterns Content guidance Not features Features Today’s focus
  14. Design tokens UI components UX patterns Content guidance © Copyright

    2024 • Directed Edges LLC Features / Relative capacity Workflow process Training curriculum Strategy and plans Analytics reports Not features Features
  15. © Copyright 2024 • Directed Edges LLC Feature Something ,

    and as a system asset. made documented released attributes ” Published in 1+ ” Useful to and/or and/or ” Implicitly or explicitly librarie designers developers other versioned
  16. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on Workflow ?
  17. © Copyright 2024 • Directed Edges LLC Tabs Checkbox Radio

    button Text input Dropdown Alert Button Breadcrumb Accordion {Title} {Details} {Label} {Label}
  18. © Copyright 2024 • Directed Edges LLC Design Code Workflow

    / Steps {Title} {Details} {Label} {Label}
  19. © Copyright 2024 • Directed Edges LLC Design Code Workflow

    / Discipline {Title} {Details} {Label} {Label} R o l e Design Developer Product/project Content Specialist “Multiple assignee”
  20. {Title} {Details} {Label} {Label} © Copyright 2024 • Directed Edges

    LLC Design Code Document Publish Design ≠ docs Producing docs content is different than getting the design approved. Workflow / Discovery, 2016 R o l e Design Developer Product/project Content Specialist “Multiple assignee” NEW NEW
  21. {Title} {Details} {Label} {Label} © Copyright 2024 • Directed Edges

    LLC Discover Design Code Document Publish Scope a plan Audits, exploration, and agreeing scope as a milestone. Workflow / Morningstar, 2017 NEW R o l e Design Developer Product/project Content Specialist “Multiple assignee”
  22. {Title} {Details} {Label} {Label} © Copyright 2024 • Directed Edges

    LLC Discover Design Code Document Publish Scope a plan Audits, exploration, and agreeing scope as a milestone. Workflow / Morningstar, 2017 NEW R o l e Design Developer Product/project Content Specialist “Multiple assignee”
  23. {Title} {Details} {Label} {Label} © Copyright 2024 • Directed Edges

    LLC Discover Design Code Accessibility Document UI toolkit Publish External collaborator Accessibility requires a review from separate team of experts. Workflow / Target, 2017 NEW NEW R o l e Design Developer Product/project Content Specialist “Multiple assignee”
  24. {Title} {Details} {Label} {Label} © Copyright 2024 • Directed Edges

    LLC Discover Design Code Accessibility Document UI toolkit Publish External collaborator Accessibility requires a review from separate team of experts. Workflow / Target, 2017 Late changes Finalize the design asset after the code is final, to ensure alignment. NEW NEW R o l e Design Developer Product/project Content Specialist “Multiple assignee”
  25. Publish Document Harden Test Accessibility Code UI Toolkit Production Design

    Discover © Copyright 2024 • Directed Edges LLC Workflow / REI, 2018 Ten steps? That’s... a lot. NEW NEW NEW R o l e Design Developer Product/project Content Specialist “Multiple assignee”
  26. Publish Document Harden Test Accessibility Code UI Toolkit Production Design

    Discover © Copyright 2024 • Directed Edges LLC Specifications For the first time, specs (for handoff) ≠ design (approved by design org) Workflow / REI, 2018 NEW NEW NEW R o l e Design Developer Product/project Content Specialist “Multiple assignee”
  27. Publish Document Harden Test Accessibility Code UI Toolkit Production Design

    Discover © Copyright 2024 • Directed Edges LLC Specifications For the first time, specs (for handoff) ≠ design (approved by design org) Testing assignee Engineers assigned testing (cases, docs, etc) as separate task. Workflow / REI, 2018 NEW NEW NEW R o l e Design Developer Product/project Content Specialist “Multiple assignee”
  28. Design production Code doc Publish Design doc Figma asset Code

    © Copyright 2024 • Directed Edges LLC Plan Design Spec Workflow / Stable workflow, since 2020 R o l e Design Developer Product/project Content Specialist “Multiple assignee”
  29. © Copyright 2024 • Directed Edges LLC Workflow / Potential

    assignee Plan Design Specification Code Code docs Figma asset Design docs Anyone, really Designer Designer Developer Developer Content or Designer Designer Content or Potential assignee Task Must have DRI (Directly Responsible Individual)
  30. © Copyright 2024 • Directed Edges LLC Workflow / Outputs

    Plan Design Specification Code Code docs Figma asset Design docs Audits, explorations, and scope Detailed design (in Figma) Detailed specs (in a Figma document) Code package(s) Code docs, possibly within a code package Figma asset(s) published in the library Doc site content Output Task
  31. p r o d u c t i o n

    © Copyright 2024 • Directed Edges LLC Workflow / Defining done Decide not to pursue or set scope, ready to start D o n e w h e n Design approved by design stakeholders Handed off to assignees, agreed on API provisionally Figma assets tested, reviewed, ready to publish Code tested, reviewed, merged, ready to release Code docs reviewed and ready to publish Design docs reviewed and ready to publish Plan Design Specification Code Code docs Figma asset Design docs Ta s k Are we ready?
  32. © Copyright 2024 • Directed Edges LLC Workflow / Relative

    cost Cost Plan Design Specification Code Code docs Figma asset Design docs Task Automation Assets getting complicated Not vanilla HTML & CSS anymore Eased authoring <- <- -> ->
  33. © Copyright 2024 • Directed Edges LLC Workflow / Cross-functional

    reviewers assignee reviewers Plan Design Specification Code Code docs Figma asset Design docs Task Ensure broad participation Ensure right people review each output
  34. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on Plan ?
  35. © Copyright 2024 • Directed Edges LLC Plan objective Understand

    what we want to make, why, and if it’s worth it Activities Audit existing cases and comparative examples Always Sometimes Sometimes Design and/or explorations code Other research
  36. © Copyright 2024 • Directed Edges LLC Plan / Scope

    Design
 Questions to answer Anatomy 
 What might it include? Props 
 How might it work? Other areas and considerations 30-60 min
  37. © Copyright 2024 • Directed Edges LLC Plan / Decision

    Yes, let’s go...! -> Communicate to stakeholders -> Confirm the scope -> Assign remaining tasks -> Assign to release -> Initiate next task No, will not support -> Communicate to stakeholders -> Close task
  38. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on Design ?
  39. © Copyright 2024 • Directed Edges LLC Design objective Fully

    explore and validate a design solution outputs Figma concepts, iterated
  40. © Copyright 2024 • Directed Edges LLC Files from template

    Include examples from products Styled with design tokens Content examples Behaviors and states Interactive prototypes Responsiveness Variant configurations Sizing and density Examples in-situ to stress test across products and themes Accessibility Usability With assigned developer(s) With system team With design community With design head / director With key adopting team(s) By designer peer(s) By assigned developer(s) By accessibility Final edits Transfer to begin specification Start Make Test Share Review Deliver Design
  41. © Copyright 2024 • Directed Edges LLC Files from template

    Add examples from products Examples with real content Styled with design tokens ⚠️ Behaviors and states ⚠️ Interactive prototypes ⚠️ Responsiveness ⚠️ Variant configurations ⚠️ Sizing and density Examples in-situ to stress test across products and themes Accessibility Usability With assigned developer(s) With design head / director ⚠ With system team With design community With key adopting team(s) By assigned developer(s) By accessibility ⚠ By designer peer(s) By system team Final edits Transfer to begin specification Start Make Test Share Review Deliver Design Product designers Avoid or do Less Than / Minimal, the as, or system designers. Same More than
  42. © Copyright 2024 • Directed Edges LLC Files from template

    Add examples from products Examples with real content Styled with design tokens ⚠️ Behaviors and states ⚠️ Interactive prototypes ⚠️ Responsiveness ⚠️ Variant configurations ⚠️ Sizing and density Examples in-situ to stress test across products and themes Accessibility Usability With assigned developer(s) With design head / director ⚠ With system team With design community With key adopting team(s) By assigned developer(s) By accessibility ⚠ By designer peer(s) By system team Final edits Transfer to begin specification Start Make Test Share Review Deliver Design Do you usability test every desig system UI component you make? REALLY? Be honest. Product designers Avoid or do Less Than / Minimal, the as, or system designers. Same More than
  43. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on Spec ?
  44. Specification © Copyright 2024 • Directed Edges LLC nt name}

    Anatomy 1 {Layer name} Depends on : {Dependency} {Name} : {Value} {Name} : {Value} 2 {Layer name} {Name} : {Style/token} {Name} : {Style/token} {Name} : {Value} 3 {Layer name} {Name} : {Value} {Name} : {Style/token} {Name} : {Style/token} 4 {Layer name} Depends on : {Dependency} {Name} : {Value} {Name} : {Value} # # # # # # # # # # # # Properties {Variant property name} {Property value} (default) {Layer name} {Name} : {Style/token} {Name} : {Value} {Layer name} Depends on : {Dependency} {Name} : {Value} {Property value} {Layer name} {Name} : {Style/token} {Name} : {Value} {Layer name} Depends on : {Dependency} {Name} : {Value} {Property value} {Layer name} {Name} : {Style/token} {Name} : {Value} {Layer name} Depends on : {Dependency} {Name} : {Value} {Boolean property name} Property type : Boolean Default : {true/false} Associated layers : {Layer name} {Layer name} {Layer name} Layout and spacing Spacing {Layer name} {Name} : {Value} {Name} : {Value} {Name} : {Value} {Name} : {Value} {Name} : {Value} {Layer name} {Name} : {Value} {Name} : {Value} {Name} : {Value} {Name} : {Value} {Name} : {Value} 16 16 16 16 16 16 Overflow {Layer name} {Description} {Layer name} {Description} Touch targets Accessibility Screen reading For when the member is using a screen reader, including how elements should be identified, read, and in what order. ESDS Text input Reading : [ESDS Form label]. [Icon] [value/ placeholder], [role]. Example : “Cost rate, the internal cost that this person incurs on your business. Dollar 100, [role].” Role : text box {Layer name} Reading : {Reading} Example : {Example} Role : {Role} Focus order ##. {Name} {Role} ##. {Name} {Role} ##. {Name} {Role} ##. {Name} {Role} # # # # # # # # # # # # Announced order ##. {Name} {Role} ##. {Name} {Role} ##. {Name} {Role} ##. {Name} {Role} # # # # # # # Component tok ens {Subsection title} Tok en Alias Figma style Value 00 {Value} $ esds-... $ esds-... {Figma style} {Description} 00 {Value} $ esds-... $ esds-... {Figma style} {Description} Aa {Value} $ esds-... $ esds-... {Figma style} {Description} {Value} $ esds-... $ esds-... {Figma style} {Description} {Value} $ esds-... $ esds-... {Figma style} {Description} {Value} $ esds-... $ esds-... {Figma style} {Description} {Subsection title} Tok en Alias Figma style Value 00 {Value} $ esds-... $ esds-... {Figma style} 00 {Value} $ esds-... $ esds-... {Figma style} 00 {Value} $ esds-... $ esds-... {Figma style} 00 {Value} $ esds-... $ esds-... {Figma style} {Subsection title} Tok en {Value} $ esds-... {Value} $ esds-... {Value} $ esds-... {Value} $ esds-... {Value} $ esds-... {Value} $ esds-... {Value} $ esds-... {Value} $ esds-... Version history Version #.#.# • MMM DD, YYYY New features í {Descriptioná í {Descriptioná í {Description} Enhancements í {Descriptioná í {Descriptioná í {Description} Fixes í {Descriptioná í {Descriptioná í {Description} Version #.#.# • MMM DD, YYYY New features í {Descriptioná í {Descriptioná í {Description} Enhancements í {Descriptioná í {Descriptioná í {Description} Fixes í {Descriptioná í {Descriptioná í {Description} or or, simply “ Design spec” “ Spec” A document that describes how an interface is composed, configured, visually designed, behaves and more, whether a component, page or something else.
  45. Design production Code doc Publish Design doc Figma asset Code

    © Copyright 2024 • Directed Edges LLC Plan Design Spec Specs / Handoff as transition R o l e Design Developer Product/project Content Specialist “Multiple assignee” Handoff Cross-functional assignees
  46. © Copyright 2024 • Directed Edges LLC Design API Code

    API https://mui.com/material-ui/api/text-field/
  47. Anatomy {Title} {Details} Show less {Label} {Label} 1 2 3

    4 5 6 7 8 ESDSV Alert Width: ESDS Sizing/ platform/iOS default width (343) Border weight: 2 Border radius: ESDS Shape/ border radius/module (4) 1 Decorative Icon Depends on: ESDS-V Icon Name: <Instance name> Size: 20x20 2 Title Text color: ESDS Color/ Text/Primary (#0E1114) Text style: Heading/5 3 Icon button layout container Height: ESDS Sizing/ icon/small (16) Width: ESDS Sizing/ icon/small (16) 4 Dismiss Icon Depends on: ESDS-V Icon Name: <Instance name> Size: 16x16 Color: Primary 5 Details Text color: ESDS Color/ Text/Primary (#0E1114) Text style: Body/Small 6 Details drawer Depends on: ESDSV Details drawer State: Open 7 Action area Depends on: ESDSV Alert actions Actions: Button + Link 8 Properties Type {Title} {Details} Show less {Label} {Label} Basic ESDSV Alert Background color: ESDS Color/ Alert/Basic/Background (#F0F1F1) Border color: ESDS Color/ Alert/Basic/Element (#A6ACB0) Decorative Icon Color: Secondary {Title} {Details} Show less {Label} {Label} Informational ESDSV Alert Background color: ESDS Color/ Alert/Info/Background (#EDF0FB) Border color: ESDS Color/ Alert/Info/Element (#0E68D4) Decorative Icon Color: Info {Title} {Details} Show less {Label} {Label} Success ESDSV Alert Background color: ESDS Color/ Alert/Success/Background (#E6FDEB) Border color: ESDS Color/ Alert/Success/Element (#097D33) Decorative Icon Color: Success {Title} {Details} Show less {Label} {Label} Error ESDSV Alert Background color: ESDS Color/ Alert/Error/Background (#FCF0EF) Border color: ESDS Color/ Alert/Error/Element (#D90936) Decorative Icon Color: Error {Title} {Details} Show less {Label} {Label} Warning ESDSV Alert Background color: ESDS Color/ Alert/Warning/Background (#FCEFDA) Border color: ESDS Color/ Alert/Warning/Element (#785F07) Decorative Icon Color: Warning Layout and spacing Type: Basic {Title} {Details} Show less {Label} {Label} 8 16 16 16 16 ESDSV Alert Direction: Horizontal Alignment: Top left Vertical resizing: Hug Horizontal resizing: Fixed Item spacing: ESDS Space/ item-spacing/half-x (8) Padding: ESDS Space/ padding/1x (16) {Title} {Details} Show less {Label} {Label} {Title} {Details} Show less {Label} {Label} 16 ]-[ Direction: Vertical Alignment: Top left Vertical resizing: Hug Horizontal resizing: Fill Item spacing: ESDS Space/ item-spacing/1x (16) {Title} {Details} Show less {Label} {Label} {Title} {Details} Show less 12 12 ]-[ Direction: Vertical Alignment: Top left Vertical resizing: Hug Horizontal resizing: Fill Item spacing: ESDS Space/ item-spacing/three-quarter-x (12) {Title} {Details} Show less {Label} {Label} {Title} 24 ]-[ Direction: Horizontal Alignment: Top right Vertical resizing: Hug Horizontal resizing: Fill Item spacing: ESDS Space/ item-spacing/one-and-a-half-x (24) © Copyright 2024 • Directed Edges LLC Specs / Aligning API
  48. Anatomy section {Title} {Details} Show less {Label} {Label} 1 2

    3 4 5 6 7 8 ESDSV Alert Width: ESDS Sizing/ platform/iOS default width (343) Border weight: 2 Border radius: ESDS Shape/ border radius/module (4) 1 Decorative Icon Depends on: ESDS-V Icon Name: <Instance name> Size: 20x20 2 Title Text color: ESDS Color/ Text/Primary (#0E1114) Text style: Heading/5 3 Icon button layout container Height: ESDS Sizing/ icon/small (16) Width: ESDS Sizing/ icon/small (16) 4 Dismiss Icon Depends on: ESDS-V Icon Name: <Instance name> Size: 16x16 Color: Primary 5 Details Text color: ESDS Color/ Text/Primary (#0E1114) Text style: Body/Small 6 Details drawer Depends on: ESDSV Details drawer State: Open 7 Action area 8 Type {Title} {Details} Show less {Label} {Label} Basic ESDSV Alert Background color: ESDS Color/ Alert/Basic/Background (# F0 F1 F1) Border color: ESDS Color/ Alert/Basic/Element (# A6 ACB0) Decorative Icon Color: Secondary {Title} {Details} Show less {Label} {Label} In formational ESDSV Alert Background color: ESDS Color/ Alert/Info/Background (#ED F0 FB) Border color: ESDS Color/ Alert/Info/Element (#0E6 8D4) Decorative Icon Color: Info {Title} {Details} Show less {Label} {Label} Success ESDSV Alert Background color: ESDS Color/ Alert/Success/Background (#E6 FDEB) Border color: ESDS Color/ Alert/Success/Element (#0 97D33) Decorative Icon Color: Success {T {D Sh { Error ESDSV Alert Background color: ESDS Colo Border color: ESDS Color/ Ale Decorative Icon Color: Error Dismissable {Title} {Details} Show less {Label} {Label} Property type: Boolean Default: false Associated layers: Dismiss Icon Details drawer {Title} {Details} Show less {Label} {Label} Property type: Boolean Default: false Associated layers: Details drawer Action area {Title} {Details} Show less {Label} {Label} Property type: Boolean Default: false Associated layers: Action area Content are {T {D Sh { Property type: Boolean Default: false Associated layers: Content area Properties section {Title} {Details} Show less {Label} {Label} 8 16 16 16 16 ESDSV Alert Direction: Horizontal Alignment: Top left Vertical resizing: Hug Horizontal resizing: Fixed Item spacing: ESDS Space/ item -spacing/half -x ( 8) Padding: ESDS Space/ padding/1x (16) {Title} {Details} Show less {Label} {Label} {Title} {Details} Show less {Label} {Label} 16 ]-[ Direction: Vertical Alignment: Top left Vertical resizing: Hug Horizontal resizing: Fill Item spacing: ESDS Space/ item -spacing/1x (16) {Title} {Details} Show less {Label} {Label} {Title} {Details} Show less 12 12 ]-[ Direction: Vertical {Title} {Details} Show less {Label} {Label} {Title} 24 ]-[ Direction: Horizontal Layout and spacin g section Te xt 2 Opacity : token -studio -opacity 87% Text color : color -text -primary #0E1114 Text align : Right Font name : token -studio -font -family Arial Bold Font size : token -studio -font -size 16 .97 Text decoration : token -studio -text -decoration Underline Letter spacing : token -studio -letter -spacing 0 .1 Line height : token -studio -line -height 22 Paragraph spacing : token -studio -paragraph -spacing 35 Paragraph indent : 8.79 Text case : token -studio -text -case Upper Rectan gle 4 Opacity : token -studio -opacity 87% Height : 3 8.89 Width : 87.6 7 Background color : color -background -secondary # F0 F1 F1 Border color : color -element -red #D 90 936 Border top weight : shape -border -width -top 0 .2 Border bottom weight : shape -border -width -bottom 0 .3 Border left weight : shape -border -width -left 0 .1 Border right weight : shape -border -width -right 0 .4 Border radius : shape -corner -default 6 Drop shadow : token -studio -drop -shadow 2px 3px 4px 5px # 852121 Frame 5 Background color : color -element -red #D 90 936 Top left radius : shape -corner -top -left 16 Top right radius : shape -corner -top -right 12 Bottom left radius : shape -corner -bottom -left 14 Bottom right radius : shape -corner -bottom -right 10 Variables Name Applied as Applied to ESDS Color/ Alert/Basic/Background Background color ESDS V Alert ESDS Color/ Alert/Basic/Element Border color ESDS V Alert ESDS Color/ Alert/Error/Background Background color ESDS V Alert ESDS Color/ Alert/Error/Element Border color ESDS V Alert ESDS Color/ Alert/Info/Background Background color ESDS V Alert ESDS Color/ Alert/Info/Element Border color ESDS V Alert ESDS Color/ Alert/Success/Background Background color ESDS V Alert ESDS Color/ Alert/Success/Element Border color ESDS V Alert ESDS Color/ Alert/Warning/Background Background color ESDS V Alert ESDS Color/ Alert/Warning/Element Border color ESDS V Alert ESDS Color/ Text/Primary Text color Details , Title ESDS Shape/ border radius/module Border radius ESDS V Alert ESDS Sizing/ icon/small Height Icon button layout container ESDS Sizing/ icon/small Width Icon button layout container ESDS Sizing/ platform/iOS default width Width ESDS V Alert ESDS Space/ item -spacing/1x Item spacing ]-[ ESDS Space/ item -spacing/half -x Item spacing ESDS V Alert ESDS Space/ item -spacing/one -and -a -half -x Item spacing ]-[ ESDS Space/ item -spacing/three -quarter -x Item spacing ]-[ ESDS Space/ padding/1x Padding ESDS V Alert Detected variables , styles and To kens Studio to kens
  49. © Copyright 2024 • Directed Edges LLC Specs / During

    design, handoff, or final Figma asset production
  50. Design production Scoping Expressing scope as (very) rough anatomy and

    API Critique Cross-functional reviews of emerging design Code doc Publish Design doc Figma asset Code © Copyright 2024 • Directed Edges LLC Plan Design Spec Specs / Involving developers earlier and often Handoff R o l e Design Developer Product/project Content Specialist “Multiple assignee”
  51. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on Code ?
  52. © Copyright 2024 • Directed Edges LLC Create code branch

    Generate file(s) Source reusable code Draft API Obtain API feedback Code HTML, CSS, JavaScript Create visual test cases Document API Create usage examples Update dependent code Browsers & devices Functional Unit tests Accessibility (manual) Accessibility (automated) Visual regression tests With assigned designer(s) With system team With developer community With key adopting team(s) By developer peer(s) By assigned designer(s) By community developer(s) By accessibility Final edits Write changelog Merge pull request Start Make Test Share Review Deliver Code
  53. © Copyright 2024 • Directed Edges LLC Create code branch

    Generate file(s) Source reusable code Draft API Obtain API feedback Create visual test cases Document API Create usage examples Code HTML, CSS, JavaScript Update dependent code Browsers & devices Functional Accessibility (manual) Accessibility (automated) Visual regression tests Unit tests With assigned designer(s) With system team With developer community With key adopting team(s) By developer peer(s) By assigned designer(s) By community developer(s) By accessibility Final edits Write changelog Merge pull request 5 min 2 min ...when? 3 min Start Make Test Share Review Deliver Code
  54. © Copyright 2024 • Directed Edges LLC Create code branch

    Generate file(s) Source reusable code Draft API Obtain API feedback Code HTML, CSS, JavaScript Create visual test cases Document API Create usage examples Update dependent code Browsers & devices Functional Unit tests Accessibility (manual) Accessibility (automated) Visual regression tests With assigned designer(s) With system team With developer community With key adopting team(s) By developer peer(s) By assigned designer(s) By community developer(s) By accessibility Final edits Write changelog Merge pull request Start Make Test Share Review Deliver Code Technical design
  55. © Copyright 2024 • Directed Edges LLC Code / Technical

    design Developer expresses API Start with template Format as code Does designer see it? Shared in a common place?
  56. Design production Code doc Publish Design doc Figma asset Code

    © Copyright 2024 • Directed Edges LLC Plan Design Spec Code / Collaborative moments after handoff Handoff R o l e Design Developer Product/project Content Specialist “Multiple assignee” (V)QA Reviews & testing
  57. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on Figma asset ?
  58. © Copyright 2024 • Directed Edges LLC Create a branch

    in library file Create a page from template Integrate finalized design Draft API Obtain API feedback Compose anatomy and layers Apply visual style Create configurable variants Configure nested components Create visual test cases Create usage examples Update dependent assets Descriptions and metadata Anatomy and naming Property combinations Content (text/images) flow
 Layout resizing Visual style variation, modes Composition in situ Composition of slots Varying nested configurations Behaviors Common overrides With assigned designer(s) With assigned developer(s) With system team With design community With key adopting team(s) By assigned developer(s) By assigned designer(s) By community designer(s) By design lead Final edits Write changelog Merge branch (Publishable) Figma asset Start Make Test Share Review Deliver
  59. © Copyright 2024 • Directed Edges LLC Create a branch

    in library file Create a page from template Integrate finalized design Draft API Obtain API feedback Compose anatomy and layers Apply visual style Create configurable variants Configure nested components Create visual test cases Create usage examples Update dependent assets Descriptions and metadata Anatomy and naming Property combinations Content (text/images) flow
 Layout resizing Visual style variation, modes Composition in situ Composition of slots Varying nested configurations Behaviors Common overrides With assigned designer(s) With assigned developer(s) With system team With design community With key adopting team(s) By assigned developer(s) By assigned designer(s) By community designer(s) By design lead Final edits Write changelog Merge branch (Publishable) Figma asset Start Make Test Share Review Deliver You plan Figma assets?
  60. © Copyright 2024 • Directed Edges LLC Figma asset /

    Architect Figma components without building them Figma Props panel components
  61. © Copyright 2024 • Directed Edges LLC Figma asset /

    Architect Figma components without building them ESDS Card Mode Light Size Medium Action(s)? Custom areas None Card Container Type Primary State Initial Card Image Aspect ratio 16:9 Aspect ratio Cover Card Text Metadata? Description? Card Actions Variant Single Button Figma Props panel components Designers Developers
  62. © Copyright 2024 • Directed Edges LLC Figma asset /

    Explore API alternatives ESDS Card Mode Light Size Medium Action(s)? Custom areas None Card Container Type Primary State Initial Card Image Aspect ratio 16:9 Aspect ratio Cover Card Text Metadata? Description? Card Actions Variant Single Button ESDS Card Contained? Custom areas None Action(s)? Container Surface Light primary State Initial Image Aspect ratio 16:9 Text Size Medium Metadata? Description? Actions Variant Button Size Medium Should subcomponents include Card in the name? Nathan Curtis At what level do we expose surface color? Nathan Curtis Is description shown or hidden by default? Nathan Curtis F igm a Props panel c om ponents API explorations Al tern ativ e 1 Al tern ativ e 2 Al tern ativ e 3 Are actions req uired, and is that exposed at the top level? Nathan Curtis
  63. © Copyright 2024 • Directed Edges LLC Create a branch

    in library file Create a page from template Integrate finalized design Draft API Obtain API feedback Compose anatomy and layers Apply visual style Create configurable variants Configure nested components Create visual test cases Create usage examples Update dependent assets Descriptions and metadata Anatomy and naming Property combinations Content (text/images) flow
 Layout resizing Visual style variation, modes Composition in situ Composition of slots Varying nested configurations Behaviors Common overrides With assigned designer(s) With assigned developer(s) With system team With design community With key adopting team(s) By assigned developer(s) By assigned designer(s) By community designer(s) By design lead Final edits Write changelog Merge branch (Publishable) Figma asset Start Make Test Share Review Deliver You test Figma assets?
  64. © Copyright 2024 • Directed Edges LLC Figma asset /

    Testing 1. Metadata 1.1 Name Is it named consistently with code and web-based documentation? 1.2 Namespace Is it namespaced as ESDS-? 1.3. Description Does it include a one sentence introduction and any important "Use Whens? 1.4 Status Is status up-to-date with commensurate code version (X.X.X) and stability (Stable vs Experimental)? 2. Anatomy 2.1 Layer name Are element names consistent with specification and code? 2.2 Layer Are layer names formatted as actual names in sentence case, not “Frame ###”? 2.3 Layer shorthand Are naming conventions applied, such as using space between (]-[) for layers applying only autolayout or emoji for indicators like edi 2.4 Nested component names Are nested components named descriptively (such as Dismiss Icon) instead of nested component's default name (Icon)? 2.5 Default visiblity Are layers shown or hidden appropriately, including layers within hidden layers? 3. Color 3.1 Color accuracy Are background, text, and stroke colors applied accurately?? 3.2 Color styles Is every fill, stroke, solid color and gradient color applying a color style instead of a hardcoded value, when possible? 3.3 Color specificity Is each style applying the most semantically specific (Text > Link > On Dark) instead of generic (Palette > Blue > 50) style? 3.4 Hardcoded properties Where a hardcoded value is used, has it been discussed and agreed upon? 3.5 Buried Colors Are "buried" hardcoded colors - applied to shadow effects and other non-styled locations - applied accurately? 4. Text 4.1 Text styles Is each text layer associated with a defined text style? 4.2 Non-text style properties Are properties not styles - list style, vertical alignment, and horizontal alignment - accurately applied or omitted? 5. Properties 5.1. Property names Are properties named and formatted correctly? 5.2. Property order Are properties ordered sensibly, such as by priority, alphabetical, related sets, or documented order across components? 5.3. Option names Are property options named and formatted correctly? 5.4. Option order Are options ordered correctly, such as by scale order ( small then medium then large) or alphabetical? 5.5. Default option Diam quis enim loborti scelerxq. Cras semper auctor neque vitae. Quis amet. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Urna molestie at elementum eu. Sit amet consectetur adipiscing elit duis tristique. Eget felis eget nunc lobortis mattis aliquam A Custom Link Label {Title} {Details} {Button} {Title} {Label} C o n t e n t C o l l i s i o n W R O N G C O N T E N T M I S S I N G C O N T E N T
  65. © Copyright 2024 • Directed Edges LLC Figma asset Specification

    ESDS Card Contained? Custom areas None Action(s)? Container Surface Light primary State Initial Image Aspect ratio 16:9 Text Size Medium Metadata? Description? Actions Variant Button Size Medium ESDS Card Anatomy ESDS Card 1 Width : 375 Border radius : 8 ESDS Image 2 Depends on : ESDS Image Aspect ratio : 16:9 ESDS Card text 3 Depends on : ESDS Card text Metadata? : true Description? : true S urf ace : Light S iz e : Medium ESDS Card actions 4 Depends on : ESDS Card actions V ariant : Button S iz e : Medium S urf ace : Light ESDS Card container 5 Depends on : ESDS Card container S urf ace : P rim ary l ight S tate : I nitial { M e t a d a t a } {T itl e} { Description} { Lab el} 1 2 3 4 5 L ayou t and spacing Content Direction : V ertical Al ignm ent : T op l ef t V ertical resiz ing : H ug H oriz ontal resiz ing : F ill I tem spacing: 16 P adding : 24 { M e t a d a t a } {T itl e} { Description} { Lab el} { M e t a d a t a } {T itl e} { Description} { Lab el} 16 24 24 24 24 F or and system designers system developers F or product designers { M e t a d a t a } {T itl e} { Description} { Lab el}
  66. © Copyright 2024 • Directed Edges LLC Workflow / All

    the checklists, oh my! https://bit.ly/ds-tasks-and-subtasks
  67. © Copyright 2024 • Directed Edges LLC Workflow / What

    does your team need, now? ⚠️ Let’s discuss ︎ We aren’t doing this (for now) We do this
  68. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on Releases ?
  69. © Copyright 2024 • Directed Edges LLC Releases / Releases

    Release Publishing libraries of and to people to use them. design and/or code assets and/or docs communicating changes
  70. © Copyright 2024 • Directed Edges LLC Releases / Release

    plan Plan Design Specification Code Code docs Figma asset Design docs Card Partial takeover 2024 08 2024 09 2024 10 2024 11 2024 12 Secondary accents New icons Error messaging Elevation tokens Bottom sheet FEATURE Filter menu Task Release
  71. Features Tasks © Copyright 2024 • Directed Edges LLC Releases

    / Doneness matrix Used with permission, Target Corporation
  72. © Copyright 2024 • Directed Edges LLC Releases / Releases

    board Release Release Release Doneness, by Task
  73. © Copyright 2024 • Directed Edges LLC Releases / Communication

    cycle Week –2 Week –1 Release week Release announcement Release day Scope Draft Copy final Images final VQA Slack (Design) Slack (Dev) Email
  74. © Copyright 2024 • Directed Edges LLC Releases / Orchestration

    Week –2 Week –1 Release week “Go live” Release announcement Documentation site content Design assets Code packages Code tools (Storybook) Documentation site Design tools, plugins Figma library content Slack (Design) Slack (Dev) Email Doc site version history Doc site blog Version history Sticker sheet Comp. descriptions Handoff sheet
  75. © Copyright 2024 • Directed Edges LLC Releases / Orchestration

    Week –2 Week –1 Release week “Go live” Release announcement Documentation site content Design assets Code packages Code tools (Storybook) Documentation site Design tools, plugins Figma library content Slack (Design) Slack (Dev) Email Doc site version history Doc site blog Version history Sticker sheet Comp. descriptions Handoff sheet 54 Asana subtasks (pre)assigned individually, every release
  76. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on Initiatives ?
  77. © Copyright 2024 • Directed Edges LLC Initiatives / Initiative

    Scope and it’s related tasks that drive towards specific outcomes and outputs to solve a problem, often within a period of time.
  78. © Copyright 2024 • Directed Edges LLC Initiatives / Example

    INITIATIVE Modality # PROBLEM STATEMENT Teams are unable to consistently design and make common modal patterns in web & native experiences. # Outcomes Teams can..q wq implement diverse modal behaviors within web and native experience| €q quickly inform, gather data and make progress through workflows. OUTPUTS wq Modal, takeover, and bottom sheet component| €q Elevation visual language and layou¥ Œq Training, including playground| Šq Integrations with 2-3 key adopters
  79. © Copyright 2024 • Directed Edges LLC INITIATIVE Token taxonomy

    PROBLEM STATEMENT Tokens organization is poor. We can use Figma features, light and dark mode, or theming. Outcomes se Refactor deeper token taxonom ne Align token names with commun ‡e Implement across all componen OUTPUTS se Revised token taxonom• ne Figma theming approach and st ‡e Code integration across catalog INITIATIVE Web / native parity # PROBLEM STATEMENT Components across platforms are inconsistent with many gaps. # Outcomes se Identify components needed across ALL platform” ne Normalize names, anatomy, and props across platforms OUTPUTS se Evolved component codeÇ ne Single Figma source-of-trutÑ ‡e Consolidated docs INITIATIVE Feature development # PROBLEM STATEMENT Our feature catalog lacks and new and fixed features and must evolve to support the business. # Outcomes More UI components and visual foundations features are available, expanding the catalog and maintaining trust in the program. OUTPUTS se Component code package” ne Figma UI components and style” ‡e Documentation per features including guidelines, code API and example” Qe Communications per release INITIATIVE Composability # PROBLEM STATEMENT Popular components require core team work to make isolated changes to support team-specific use cases. # Outcomes se Key components afford much more flexible compositioŠ ne Teams deliver experiences with less reliance on system teaˆ ‡e System team support costs and irregular release demands go down OUTPUTS se List / Row component upgrad§ ne Card component upgrad§ ‡e Training with playground file” Qe Evolved docs and usage demos Modality PROBLEM STATEMENT Teams are unable to consistently design and make common modal patterns in web & native experienc Outcomes Teams can..e se implement diverse modal behav within web and native experien ne quickly inform, gather data and make progress through workflo OUTPUTS se Modal, takeover, and bottom sh component” ne Elevation visual language and la ‡e Training, including playground” Qe Integrations with 2-3 key adopt INITIATIVE Theming # PROBLEM STATEMENT # se Data visualization palette as token” ne Figma components for 5+ chart” ‡e Build your own Figma charts guidance and reference demos INITIATIVE Designer onboarding PROBLEM STATEMENT Designers lack resources to learn a INITIATIVE Designer onboarding # PROBLEM STATEMENT Designers lack resources to learn and apply the design system in day to day work with confidence. # Outcomes se Designer new hires can attend recurring live traininm ne Designers self-serve to learn the design system without live traininm ‡e Designers are better equipped to handoff work clearly to developers Initiatives / Attributes Initiatives are described via content including: Problem statement Outcomes Outputs Opportunities Risks Stakeholders Steps Delivery Plan
  80. © Copyright 2024 • Directed Edges LLC Initiatives / Gather

    structured stakeholder input Summarize data to generalize preferences How many stakeholders? 10+? 25+?
  81. © Copyright 2024 • Directed Edges LLC Initiatives / More

    about roadmapping https://www.youtube.com/watch?v=4MpGxmlOf7w&t=768s
  82. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on Roadmap ?
  83. INITIATIVE Feature development # PROBLEM STATEMENT Our feature catalog lacks

    and new and fixed features and must evolve to support the business. # Outcomes More UI components and visual foundations features are available, expanding the catalog and maintaining trust in the program. OUTPUTS €u Component code packages {u Figma UI components and styles hu Documentation per features including guidelines, code API and examples —u Communications per release INITIATIVE Web / native parity # PROBLEM STATEMENT Components across platforms are inconsistent with many gaps. # Outcomes €u Identify components needed across ALL platforms {u Normalize names, anatomy, and props across platforms OUTPUTS €u Evolved component code´ {u Single Figma source-of-trut¾ hu Consolidated docs INITIATIVE Charts # PROBLEM STATEMENT The system lacks robust data visualization foundations and starting points to create charts easily. # Outcomes €u Extend visual foundations to support data viz, especially coloÆ {u Enable teams to easily add and customize chart components (like Bar) with reusable parts (like Axis) OUTPUTS €u Data visualization palette as tokens {u Figma components for 5+ charts hu Build your own Figma charts guidance and reference demos INITIATIVE Composability # PROBLEM STATEMENT Popular components require core tea work to make isolated changes to support team-specific use cases. Outcomes €u Key components afford much mo flexible compositiom {u Teams deliver experiences with le reliance on system teak hu System team support costs and irregular release demands go dow OUTPUTS €u List / Row component upgradŠ {u Card component upgradŠ hu Training with playground files —u Evolved docs and usage demos © Copyright 2024 • Directed Edges LLC Roadmap / "All the work" +
  84. INITIATIVE Feature development # PROBLEM STATEMENT Our feature catalog lacks

    and new and fixed features and must evolve to support the business. # Outcomes More UI components and visual foundations features are available, expanding the catalog and maintaining trust in the program. OUTPUTS €u Component code packages {u Figma UI components and styles hu Documentation per features including guidelines, code API and examples —u Communications per release INITIATIVE Web / native parity # PROBLEM STATEMENT Components across platforms are inconsistent with many gaps. # Outcomes €u Identify components needed across ALL platforms {u Normalize names, anatomy, and props across platforms OUTPUTS €u Evolved component code´ {u Single Figma source-of-trut¾ hu Consolidated docs INITIATIVE Charts # PROBLEM STATEMENT The system lacks robust data visualization foundations and starting points to create charts easily. # Outcomes €u Extend visual foundations to support data viz, especially coloÆ {u Enable teams to easily add and customize chart components (like Bar) with reusable parts (like Axis) OUTPUTS €u Data visualization palette as tokens {u Figma components for 5+ charts hu Build your own Figma charts guidance and reference demos INITIATIVE Composability # PROBLEM STATEMENT Popular components require core tea work to make isolated changes to support team-specific use cases. Outcomes €u Key components afford much mo flexible compositiom {u Teams deliver experiences with le reliance on system teak hu System team support costs and irregular release demands go dow OUTPUTS €u List / Row component upgradŠ {u Card component upgradŠ hu Training with playground files —u Evolved docs and usage demos © Copyright 2024 • Directed Edges LLC Roadmap / The accountable owner’s question What’s going on with our big bets?
  85. © Copyright 2024 • Directed Edges LLC Roadmap / Board

    Impact Active initiatives Inactive initiatives Size (Discovery) Tasks Features give way to Initiative Initiative
  86. Plan Design Specification Code Code docs Figma asset Design docs

    Card Partial takeover 2024 08 Feature development 2024 09 Web & native parity 2024 10 Token taxonomy 2024 11 Modality 2024 12 API alignment Accessibility upgrade 2 Charts Composability Theming Dev support upgrade Designer onboarding Secondary accents New icons Error messaging Elevation tokens Bottom sheet Modal v2 FEATURE Filter menu Task Release INITIATIVES © Copyright 2024 • Directed Edges LLC Roadmap / Relating initiatives, releases and features
  87. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on Boards?
  88. © Copyright 2024 • Directed Edges LLC Boards / Summary

    Dev React Dev iOS Design Releases Roadmap Backlog Tasks Tasks Tasks Features Initiatives Features, Initiatives includes includes How are (React) devs progressing right now? includes include includes includes How are (iOS) devs progressing right now? How are designers progressing right now? What will be delivered by when? How are big bets progressing? OBJECT What might we do, eventually? Board answers
  89. Board Releases Release MM/DD Release MM/DD Release MM/DD Release MM/DD

    Release MM/DD Board Backlog Board Roadmap Board Dev React To be prioritized Plan Ready to start In progress In review Board Design To be prioritized Plan Ready to start In progress In review © Copyright 2024 • Directed Edges LLC Boards / Rituals anchored on boards Planning 1x / week or every other week Dev Standup 2x / week Design Standup 2x / week Attendees Dev manager (driver) All developers Product manager? Attendees Product manager (driver) Dev manager Dev lead(s) Design manager Design lead(s) Attendees Design manager (driver) All designers Product manager
  90. © Copyright 2024 • Directed Edges LLC Boards / Bucketing

    "To be prioritized" Discuss in planning When something comes up (request, proposal, complaint, ...), where do we put it to make sure we talk about it? PROBLEM Discuss in design standup
  91. © Copyright 2024 • Directed Edges LLC Boards / Intake

    Design Intake Dev Intake Board Releases Board Dev Board Design To be prioritized To be prioritized Plan Plan Ready to start Ready to start In progress In progress In review In review {Release name} To be prioritized {Release name} {Release name} {Release name}
  92. © Copyright 2024 • Directed Edges LLC Boards / Intake

    Design Intake Dev Intake Board Releases Support request Board Dev Board Design Support request Feature request Contribution proposal Feature request Contribution proposal To be prioritized To be prioritized Plan Plan Ready to start Ready to start In progress In progress In review In review {Release name} To be prioritized {Release name} {Release name} {Release name} Defect Defect
  93. © Copyright 2024 • Directed Edges LLC Boards / Intake

    Design Intake Dev Intake Board Releases Support request Board Dev Board Design Support request Feature request Contribution proposal Feature request Contribution proposal To be prioritized To be prioritized Plan Plan Ready to start Ready to start In progress In progress In review In review {Release name} To be prioritized {Release name} {Release name} {Release name} Defect Defect Design-specific Dev-specific Trafficer Trafficer
  94. © Copyright 2024 • Directed Edges LLC Boards / Intake

    Design Intake Dev Intake Board Releases Support request Board Dev Board Design Support request Feature request Contribution proposal Feature request Contribution proposal To be prioritized To be prioritized Plan Plan Ready to start Ready to start In progress In progress In review In review {Release name} To be prioritized {Release name} {Release name} {Release name} Defect Defect Design-specific Dev-specific Relevant to dev and design Trafficer Trafficer
  95. © Copyright 2024 • Directed Edges LLC Boards / Intake

    Design Intake Dev Intake Board Releases Support request Board Dev Board Design Support request Feature request Contribution proposal Feature request Contribution proposal To be prioritized To be prioritized Plan Plan Ready to start Ready to start In progress In progress In review In review {Release name} To be prioritized {Release name} {Release name} {Release name} Assign Assign Slot & scope Defect Defect Design-specific Dev-specific Relevant to dev and design Trafficer Trafficer
  96. © Copyright 2024 • Directed Edges LLC Boards / Intake

    Design Intake Dev Intake Board Releases Support request Board Dev Board Design Board Backlog Support request Feature request Contribution proposal Feature request Contribution proposal To be prioritized To be prioritized Plan Plan Ready to start Ready to start In progress In progress In review In review {Release name} To be prioritized {Release name} {Release name} {Release name} Assign Assign Respond and archive Slot & scope Refine and store Defect Defect Design-specific Dev-specific Relevant to dev and design Trafficer Trafficer
  97. © Copyright 2024 • Directed Edges LLC How do we

    produce Features in a of tasks like delivered across and organized on a , all visible and tracked on Releases Workflow Plan Design Spec Code Figma asset Initiatives Roadmap Boards?