Core foundations for all digital products built by ADAPT.
All products built by ADAPT ahere to a certain set of core values which guide the experience for case teams, designers, developers, clients and – most importantly – users. Together we have co-created these values within ADAPT.
These principles apply to both the products we build and when contributing to the ADAPT Design System itself.
The user is at the heart of our process. From a component level to an entire product, things should be designed and developed with a constant check of "does this help the user?".
Solutions should feel familiar, not foreign.
Not: "It should be this way because we think it matches our excel model"
More: "Users need to see high-level numbers at a glance and delve deeper when they need to"
Users should feel enabled to accomplish their goals and fulfill their needs by the products we design and build. Our products should feel supportive.
Hint: Use wording that encourages users to discover the tools we build. Avoid robotic "business-speak".
The Design System offers useful building blocks for piecing together larger solutions. These blocks should be lightweight and generic enough to allow flexibility in solutions and to support teams in building products that still feel organic and unique.
It can and will evolve over time, but this flexibility is fundamental to the success of the system.
Not: "Can we add this Sales Lever slider that presents XYZ data in a bar graph to the design system?"
More: "We have a set of new reusable components that could be put together to form things such as this feature..."
Got an idea for a component? Read more on Confluence
Part of the value of the design system is providing ready-made, road-tested components that provide a professional level of visual quality. Pursue the extra degree of polish in your work to contribute to a better user experience.
All components should have:
- Correct semantic HTML
- Visual design that harmonizes with the look and feel of other components in the design system.
- Appropriate accessibility requirements for components
Opt for familiar patterns that end users will recognize with little-to-no difficulty. The patterns we use in our designs should be self-explanatory.
Less: Here's a custom-styled dropdown that is all animated and stuff.
More: Here's standard dropdown, behaving just like it should on all devices.
Keep accessibility standards in mind. Users with additional needs are not ‘edge cases,’ but part of the pool of end users we place in the center of the process.