↵

Ask DN : How to adopt a Design System?

almost 6 years ago from ahder junior, UI/UX Designer

  • Stu Collett, almost 6 years ago

    Hi Ahder,

    We’ve had most success designing the foundations first and then approaching chunks (which then feeds back into the foundations).

    The biggest thing here is make sure you align with development and DevOps (if the team has that capability). It’s important to have one single source of truth that can be iterated upon both in terms of front end dev and product design team members.

    You could also start with a ‘hero’ project if the redesign is large/enterprise scale, (to prove the value of living design systems).

    Any questions, let me know, happy to add further detail.

    Stu

    0 points
    • ahder junior, almost 6 years ago

      i have a question, what is the hero project looks like?

      0 points
      • Stu Collett, almost 6 years ago

        A ‘hero’ project is a smaller or simpler chunk of a larger platform, service or system, that is used to exemplify excellence.

        For example, a human capital management platform might have many different digital products or platforms. The idea here would be to pick one and redesign (using a user-centred approach and design system thinking) to exemplify what good looks like and prove that the design system works seamlessly with DevOps.

        I realise that this is mainly the case with enterprise projects. Not necessarily needed for smaller projects.

        Hope that helps!

        Stu

        0 points
    • Nick WNick W, almost 6 years ago

      the biggest struggle I've had with any system or style component is alignment with development and developing a single source of truth.

      What is your 'single source of truth'? and how did you iterate upon that? Is an iteration upon this source expected to affect all contexts that it's used in?

      0 points