Principles

• Collaborative - team built, maintained, and used together through collaboration

• Economical - “mise en place” approach, not letting tech and resources go to waste in terms of effort, time, and cost

• Structured - unique methodologies and processes to create structure for proper use

• Inclusive - being open with all aspects of sharing, contribution, collaboration, and accessibility

• Quality - even through efficiency, maintain or exceed quality standards to be modern, tested, and maintained

Goals

Adoptable process for web based products (desktop and mobile). Flexible components that can be used for many platforms or frameworks seamlessly

• Reduce dependency on high 3rd party costs*

  • Reduces cost by allowing vendors to use design system to easily develop products in the way they have already been built without custom labor, or even be so simple to use that we do not require vendors

• Higher quality in less time

  • Less time spent determining styles, consistency, interaction, functionality. The components are built ahead of time, tested, and validated as working or usable/reusable

• Open source model to benefit organizations

  • We share and want all teams to succeed, this is not to be hoarded by our organization and does not follow the principles of inclusiveness and accessibility

• Less time to complete = more time to work on the futures

• More flexibility with headcount and budget

  • Saving time, money, and progressing quicker on initiatives should allow infrastructure and growth for PERMANENT team growth

• Individual and team growth is possible

  • Having an ecosystem of support like this helps teams and individuals grow, by showing trust and commitment to what we offer employees and the strategies we invest in. NOT just quick product wins that rely on optics only

Multiple Branches of UI Kit & Library

Nova contained two main active branches:

1. Employee Experience
2. Player Experience

Each branch was created off of the core use cases universal to all consumer and enterprise products. Components that didn’t fit the use cases of the core library were created in the branch libraries.