role
UX/UI Designer
type
Enterprise, Insurance, Web + Mobile App
MY CONTRIBUTION
I co-designed the system with another designer, with my focus spanning research synthesis, interaction patterns, responsive behavior, accessibility standards, component documentation, and application across key agent workflows.
EY x TATA-AIA
Design System that unified 3 enterprise products
Built a responsive, WCAG AA design system and applied it across 30+ high-use agent workflows, reducing navigation time by 48% and creating a shared interaction language across products.
3 months · 2023 · Team: 2 UX/UI Designers (me+1), Design System (me + 1), Design Manager, PM, Engineering
,
−48%
Reduction in agent navigation time
For key workflows.
+96%
,
Cross-platform UI consistency achieved
Measured through design audit
after system rollout.
3
,
Products
Using the system
OVERVIEW
Multiple apps. No shared language. Too much relearning.
Tata AIA's agent network relied on multiple applications for onboarding, renewals, commissions, and relationship management. These products had been built independently, creating inconsistent patterns and forcing agents to relearn common interactions across workflows.
PROCESS
Audited existing products to identify where inconsistency created the most friction.
I compared recurring UI patterns, responsive behavior, accessibility, and high-frequency agent workflows to identify where standardization would have the greatest impact.
3
Products audited
20+
Screens reviewed
50
User surveys
AUDIT FINDINGS
Similar workflows behaved differently across products
The audit surfaced recurring inconsistencies in interaction patterns, responsive behavior, and accessibility.
Research
Insight
INSIGHTS
The experience assumed customers understood tree logistics
The experience assumed customers understood tree logistics. Research surfaced the same three questions again and again:
Teams recreated the same patterns differently
Common controls and workflows behaved differently across products, increasing maintenance and forcing agents to relearn familiar interactions.
Responsive behavior wasn't systematic
Components were often designed for individual screens rather than as reusable patterns across desktop and mobile.
Accessibility varied by product
Contrast, field states, responsive behavior, and interaction feedback lacked consistent standards.
challenege
How might we create one coherent product experience without slowing delivery?
The pressure
Stakeholders wanted screens quickly.
Teams needed reusable patterns.
Agents needed less ambiguity.
Engineering needed clearer implementation rules.
The strategic bet
Build the foundation first, then redesign the highest-value surfaces on top of it.
STRATEGY
Build the foundation first. Redesign the portal second.
I focused on turning repeated design choices into reusable product infrastructure: color, type, spacing, components, states, responsive rules, accessibility criteria, and implementation guidance.
01
Design reusable patterns
02
Mobile-first, then desktop
03
WCAG AA by default
04
Prioritize high-value workflows
EXPLORATION & SYSTEM DECISIONS
Designing patterns that could scale across products and breakpoints
One status model across three products
I mapped existing status patterns across products, separated semantic meaning from visual treatment, and consolidated them into a shared model that could scale across workflows.
Adapting complex components across breakpoints
Date picker:
Design system
A shared language for design and engineering.
Each component defined usage, responsive behavior, interaction states, accessibility requirements, and implementation guidance so design and engineering worked from the same source of truth.
Foundations
Tokens, type, spacing, color, accessibility
Components & Patterns
Inputs, cards, tables, badges, modals, navigation. Forms, status, responsive workflows, complex states
Documentation
Figma library, Storybook references,
usage rules, contribution process, and
handoff notes.
Layer 01 — Atoms
Foundations that scale across products
Tokenizing color, type, spacing, and layout meant global changes could propagate across components instead of being updated screen by screen.
Layer 02 — Molecules
Composable components
Components were designed across responsive breakpoints and documented with interaction states, accessibility requirements, and developer handoff guidance.
Adoption strategy
A design system only creates value when teams use it.
01
Documentation & Training
Created comprehensive documentation in Figma and Storybook. Ran workshops with design and engineering teams to demonstrate component usage, best practices, and the system's underlying logic.
Figma Library
Published components with usage guidelines
Storybook
Interactive component documentation for devs
Workshops
Training sessions with design and engineering on component usage, responsive behavior, and contribution guidelines.
02
Governance & Maintenance
Established a contribution model for proposing components, requesting changes, and reviewing updates so the system could evolve without fragmenting.
Monthly Reviews
System updates & new components
Office Hours
Weekly support for teams
Contribution Process
Clear guidelines for adding to the system
02/02
Then I applied the system to 30+ agent portal screens.
I applied the system to high-frequency agent workflows to validate that the patterns could handle real product complexity across desktop and mobile.
Priority-first home
Surfaced pending work and high-priority actions directly on the dashboard so agents didn't have to navigate across modules to understand what needed attention.
Unified policy status view
Standardized status patterns across workflows so agents could interpret progress consistently without relearning each module.
In-app invoice generation
“Hard to find GST” was the third most common survey pain point. I brought invoice generation into the portal with OTP verification, removing a manual workflow and repeated data entry.
Identity + self-service hub
Redesigned as a proper identity hub — showing designation, rank, and performance
signals. Agents can manage bank details, contact information, and documents
themselves without routing through support.
KEY LEARNINGS
What this project taught me
01. Standardization should remove decisions, not flexibility
A useful system defines recurring decisions once while leaving room for product-specific needs. The goal wasn't to make every experience identical—it was to make familiar interactions predictable.
02. Adoption is a product problem
Components alone don't create consistency. Documentation, governance, contribution paths, and engineering partnership were as important as the library itself.
Validate systems through real workflows
Applying the system to high-frequency agent workflows exposed gaps that isolated components couldn't. Testing the system against real product complexity made the foundation stronger.
This summer I had the pleasure of working directly with Anjali through our Harris Entrepreneurship Program.
Anjali played a critical role in ideating and designing major deliverables for this program. Her ability to quickly analyze and problem-solve in an adaptable way was refreshing to observe. Anjali consistently sought and embraced feedback. This humble approach allowed her to conceptualize and produce user-centered design with tailored depth.
More importantly, Anjali was such a pleasure to be around as she consistently brought positive and enjoyable moments to our culture. Her high-quality work ethic and quick ability to create applicable solutions was impressive. There is no question in my mind that Anjali will have a major ha
nd in bringing forth new, user-centered designs for substantial impact.
AUSTIN MACKRILL,