Inclusive Component Library Case Study: How a Fintech Rebuilt Its System for Neurodiversity

Design · 5 min read

The fintech team began by auditing support transcripts and running participatory workshops with neurodivergent users to understand pain points: dense forms, sudden micro-interactions, and inconsistent terminology were recurring issues. They prioritized changes at the design-system level so improvements would scale across products.\n\nKey changes included a 'calm mode' token set that reduced motion, simplified color palettes with higher semantic spacing, and an information-density token that components could consume to switch between compact and expanded states. The team also standardized terminology tokens and created a microcopy style guide aimed at unambiguous instructions.\n\nAfter rolling the new system out, the company reported a decline in task-time variance and a drop in support calls related to navigation and form errors. The case underscores a central lesson: investing in inclusive system-level tokens and components benefits everyone and saves product teams time by reducing ad-hoc fixes and exception handling.