A design system product

A design system product

This presentation shares our journey at Ansarada of identifying challenges in maintaining our design system and solving them with product thinking.

C19ad910f6de3de7bfba85471496e0c4?s=128

Charlotte Jackson

October 04, 2018
Tweet

Transcript

  1. 3.
  2. 4.
  3. 10.
  4. 12.

    Questions What is the adoption of existing components? How many

    instances are overridden and why? What’s the process for users to adopt the system? What are their pain points? How satis!ed are users with the process and experience?
  5. 13.

    What is the adoption of the design system? Code search

    for quantitative data Survey - Ask users which components they use - User satisfaction rating & feedback
  6. 14.
  7. 16.

    Interviews What’s the end to end process for front-end design

    and development? E.g. “Tell me what triggers the need for a new feature?” Ask open questions Listen Record the interview to make notes after the session
  8. 18.
  9. 19.

    Lack of adoption Evolving technologies Updating ACE versions was time

    consuming Speed of development in the core team
  10. 22.
  11. 23.

    Product questions What is the goal of the design system?

    What problems will it solve for Ansarada? What does success look like and how do we measure it? Who are the users and how do they work? Who are the customers? Who are the buyers and how do we communicate the bene!ts to them?
  12. 24.

    Product personas Customers = Leadership team Users = Product teams

    Customers’ customers = Ansarada customers
  13. 26.

    Product team Product manager - new Design lead - new

    QA - new Tech lead Team lead Developers, designers Dev ops
  14. 30.

    “The Design System informs our Product Design. Our Product Design

    informs the Design System.” — Jina Anne https://medium.com/salesforce-ux/the-salesforce- team-model-for-scaling-a-design-system- d89c2a2d404b
  15. 32.

    Collaboration Slack channel Cross discipline catch ups Stand ups open

    to all Workshops PRs reviewed in 24 hours Talking to each other
  16. 34.
  17. 35.
  18. 38.

    Team OKR Objective: We provide a platform to enable product

    teams to deliver cohesive and consistent experiences Key result: 100% of components in products are served by ACE
  19. 40.
  20. 49.
  21. 50.

    Design system products Discovery & Research Who are you customers

    and personas? Create a product team Set goals (team and product) OKRs Roadmap Release management Marketing