Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

\uD83D\uDDD3Date

đź”´ Meeting recording

Link: https://web.microsoftstream.com/video/60f39caf-1688-4c4b-a4d2-05af1def2468

2022-01-31_Design System_Business case and usage discussion.mp4

\uD83D\uDC65Participants

  • Reckitt (RB):
    Kaustav Bhattacharya
    Ali Durrani
    Matt Lau
    Nathan McKean
    Pawel Ploneczka
    Radosław Kowalewski
    Robert Ruszczyk

  • DataArt (DA):
    Julia Boyarshchikova
    Sergey Kiselyov
    Anton Merkulov
    Alexey Strogov
    Natalia Voytovich

\uD83E\uDD45Goals

  • RB to discuss with DataArt around the business needs & goals for the design system

  • RB & DA to discuss use cases and agree with DA how to progress

âś…Action items

  • DA to schedule the additional session with the RB tech team
  • DA to schedule the session with Nathan to check what can we move forward already
  • Nathan to share the eKino deck with questions that might help DA to get the deeper understanding

⤴Key takeaways

  • As for now, the best approach seems to be to build the template with underlying components library, not just a separated component library and that’s it
  • DA proposed to use a chameleon template instead of the global component library - suggesting that we might reuse developed projects (like Finish) as the foundation for the initial templates, possible to use for AirWick/Harpic development.
  • We can’t aim to be Everything for Everyone - otherwise it’s not a system
  • Efficiency of the design system is not only in the creation, but it’s also in the maintenance
  • We should aim for Unified vision of quality expectations (check RB QA standards) + consistent delivery
  • The Design System should aim to increase speed to market (ideally by 2x) and reduce costs of delivery (ideally by 50%)

  • No labels