Work About Journal Now Work with me Download resume ↓

Work / Case study 03

Tata CLiQ Luxury · Design system

Turning the feeling of unhurried luxury into a system anyone can use.

A luxury design system, built during a tool switch and a full rebrand, by the smallest design team in the company.

A laptop on a white desk showing design system components: colour tokens, toggles, icons, a product card and button styles.
My role
Design system leadVision, strategy and system creation; led 2 designers
Year
2022–2023
Team
3 designers · 2 engineersPlus product and creative partners
Timeline
9 months3 phases, alongside live product work
500+components
40%faster design turnaround
80%of needed components within 9 months

Scope · Tokens, atoms, molecules, organisms, documentation, Sketch → Figma migration

What everyone saw

We needed a design system, now. At the same time we were switching tools and rebranding, with three designers who still had a product to ship.

What we uncovered

"Slow commerce" was a feeling, not a style guide. Before anyone could build it, someone had to turn it into rules.

What we built

A phased system from tokens to organisms, with UI principles traced back to the brand personality, and documentation developers trust.

What changed

The foundation of Tata CLiQ Luxury's digital identity, built to extend to Fashion and Palette: 500+ components and 40% faster turnaround.

I. Three challenges at once

Three hard things, all at once.

I led two designers to build and document a complete design system for Tata CLiQ Luxury. Any one of these would have been enough. We had all three.

The Sketch logo with an arrow to the Figma logo.

1. Sketch to Figma

The design landscape had moved on, and every file had to migrate to Figma.

The old Tata CLiQ Luxury logo and gold palette, with an arrow to the new logo and violet palette.

2. A branding overhaul

The brand was redesigned to keep pace with a changing Indian luxury consumer.

A balance scale weighing one designer against two.

3. Resources vs vision

We needed a system urgently, but the product work couldn't stop while we built it.

II. Strategy & roadmap

A plan a team of three could actually keep.

Three designers, me included, had to keep shipping the product and build a new system at the same time. So I planned it in phases we could actually keep.

Process diagram: Plan (Discover), Build (UI and visual design, component construction, UX and product design), and Production (Figma library, design docs, code API, code docs).

Fig. 1 · Nine months, three phases, running alongside live production projects.

III. Decoding luxury

Taking a pause.

Before designing a single component, we worked out what luxury should mean in a digital space, together.

  1. What luxury means to each of usI ran brainstorming sessions with the whole team to surface our shared perceptions of luxury, good and bad.
  2. Everyday apps, reimagined as luxuryI asked the team to redesign two non-ecommerce apps as our own version of luxury. The fundamentals we found carried straight into the design language.
  3. Market insightsResearch across luxury brands showed us how luxury is being redefined today.
Brainstorming boards and market study snippets.
Fig. 2 Brainstorming snippets and market study.
IV. Slow commerce

Turning "slow commerce" into rules a team could follow.

The new brand stood for slow commerce: helping people enjoy finer moments and choose mindfully. For a shop, that means never rushing anyone into an impulse buy.

Not rushing people is a design decision. So is every pixel that follows it.

A map linking the brand traits Sophisticated, Inviting and Connoisseur to UI principles like white space, rounded forms, serif type, haptics and micro-animation.
Fig. 3 From brand personality to UI principles: sophisticated, inviting, connoisseur.

Together we pinned down what made the identity feel the way it should. Deliberate white space. Rounded corners for warmth. A palette of warm greys, timeless blacks and white, with sparing use of cool Veri Peri. Precision and attention to detail. Consistent hierarchy, so the experience felt effortless.

A mood board of calm, airy interiors, soft florals and monochrome fashion, labelled with feelings like 'Pause, take a breath' and 'Timeless yet modern'.
Fig. 4 The mood board became our North Star for colour and aesthetic direction.
V. Tokens to organisms

Building in phases, from the smallest decision up.

We built from the smallest decision up: tokens → atoms → molecules → organisms.

Tokens combine into atoms, atoms into molecules, and molecules into organisms.

We dropped H1, H2, H3 for Small, Medium and Large. It sounds minor. It meant the system could grow without renaming everything.

We also kept separate type styles for desktop and mobile. That naming paid off later: when we built the luxury editorial experience, which needed very different typography from the product, listing and checkout journeys, the system stretched to it without being renamed.

5X Large32 · BoldA story worth owning
3X Large24 · RegularThe Seamaster Collection in Summer Blue
XX Large20 · BoldKey features
X Large18 · Bold capsConsult an expert
Large16 · RegularCo-Axial Chronometer, 43.5 mm, steel on steel
Medium14 · RegularDelivery by Tuesday · Free returns within 15 days
Small12 · LightInclusive of all taxes

Fig. 5 · The type scale, with serif for storytelling and sans for everything functional. Shown here in this site's typefaces.

Named by scale, not position

Small to 5X Large instead of H1 to H6, so any new surface can pick sizes without renaming everything.

An averaged golden ratio

12 · 14 · 16 · 18 · 20 · 24 · 32. Each step grows by a near-constant ratio, rounded to sizes that render crisply.

Skip a level for hierarchy

A heading and its body never sit on neighbouring steps, so the contrast between them is always clear.

The highlight of this phase was a set of versatile text atoms, the building block behind everything from CTAs to editorial headings. To keep components modular, we developed a method that got the most out of auto layout without the complexity it often brings: simple booleans and dynamic spacing.

A range of components built from the text atoms, from simple multi-use elements to complex specific ones.
Fig. 6 From simple and multi-use to complex and specific.
VI. Documentation

Emotion, specified down to the line-height.

Every element got written down: variants, when to use them, and real examples, so anyone applies the same rule the same way.

The full button component documentation: variants, states, sizes, anatomy and do's and don'ts.
Fig. 7 How we documented the button component. Scroll inside the frame, or click to enlarge.
The UI guide, part one: font styles and weights, showing how Lato and PT Serif give the product its personality.
Fig. 8UI guide: type that communicates personality.
The UI guide, part two: weights, letter spacing and line heights, with annotated product screens.
Fig. 9UI guide: weight, spacing and line height.
VII. Migrating to Figma

Rebuilding the library, not just moving it.

We didn't just copy the old Sketch library into Figma. We rebuilt it with the new design language inside, and kept it simple enough for designers and developers alike.

The Figma library: button components organised under local components, with auto-layout properties for size, width and state.
Fig. 10 Components rebuilt with auto layout, booleans and clear naming.
VIII. Working with engineering

A system only works if it ships the way it was designed.

At first, developers built components differently from how we'd designed them. Instead of blaming the handoff, we sat with them, learned their constraints, and changed how we wrote things down. After that, designs shipped the way they were meant to.

A laptop on a wooden table showing the design system component overview.
IX. Impact

The foundation of a digital identity.

The system became the base of Tata CLiQ Luxury's look and feel. Every token went live, and new components land every sprint. It was built to extend to Fashion and Palette, and that roll-out is under way.

We did it as the smallest design team in the company.

500+components today
40%faster design turnaround
80%of needed components within 9 months
↓UAT effort, faster onboarding

Key contributions

  • Aarti Kava: Vision, strategy & design system creation
  • Aryan Kandhari: Design system creation
  • Anaya Purandare: Visual documentation
  • With Naman Jain (iOS developer) and Akshay Garg (iOS lead developer)

Keep reading

More case studies

See all work →