Product Design

Turning operations into insights.

The operations dashboard for Svaroots, a modular sneaker brand where customers co-create shoes with regional Indian textiles.

My role

Lead Designer, Operations Dashboard

Screens

7 pages, live prototype

Team

5 designers

Duration

6 weeks

Tools

Figma / Variables

My contribution

The entire dashboard, end to end.

I led research, information architecture, design system, UI, interaction states, and developer handoff across all seven screens.

  • Overview with KPIs, traffic sources, customer insights
  • Orders with status filters and management
  • Inventory with size run health, dead stock
  • Users with CLV, segmentation, at-risk tracking
  • Content & CMS with products, banners, campaigns
  • Analytics with patch-to-sneaker ratio, customisation rate
  • Settings with team roles and permissions
What the team built together

Brand, product, & consumer surface.

These were collaborative efforts across the full team. The dashboard was my individual contribution to the product.

  • Logo & brand identity
  • Modular sneaker concept
  • Consumer storefront & 3D customizer
  • Marketing & pitch materials
Chapter 01The tension

A modular shoe needs custom ops.

Svaroots sells a base sneaker plus swappable patches in regional Indian textiles. Five product types, each with its own lifecycle. The team was running all of it on spreadsheets and a generic Shopify backend.

The problem

The ops team is flying blind.

Patches sell fast but restock slow. Sneakers need size-run tracking across Indian sizing (IND 7-11). Drops are time-limited. Cleaning and gifting kits follow yet another rhythm. A single Shopify dashboard treats them all identically, so the team can't see dead stock building, can't track the patch-to-sneaker ratio, and can't anticipate which sizes will stockout next.

The answer

Seven screens, one operations hub.

A custom dashboard that gives each product category its own view, surfaces the metrics only a modular brand needs, and lets a two-person ops team manage inventory, orders, users, content, and analytics without switching tools.

The storefront is where the magic happens. The dashboard is where it keeps happening.

Design hypothesis
Chapter 02Backstory

The product the team built.

Quick context on Svaroots and the collaborative work that set the stage for the dashboard.

Team work - 01

Brand identity

A patch-shaped mark in indigo, yellow, and bottle green.

Primary mark
Horizontal lockup
Submark
Team work - 02

The product

Base sneaker for Indian feet. Three modular zones accepting Kalamkari, Ajrak, Paithani, Bandhani patches.

Modular zones
Patch detail
Textile system
Team work - 03

Packaging

Modular packaging system for sneakers, patches, and gifting kits. Designed to reflect the brand's textile heritage.

Featured on Packaging of the World
Home page
3D customizer
Artisans
Team work - 04

Consumer storefront

Home, 3D Lab, artisans page. Where the buyer becomes a co-creator.

Home
See full brand & consumer work
The dashboard

Once a customer hits order, the dashboard takes over.

From here on, every chapter covers the operations hub: research, design system, screens, and analytics.

Chapter 03Process

How we got here.

Research artifacts, sketches, and direct user feedback that informed every design decision.

Information Architecture
figjam.com / IA
Chapter 03Process

Sketches before pixels.

Low-fi paper wireframes used to test flow and hierarchy before any pixels were pushed.

Paper Wireframes
Overview
Orders
Inventory
Users
Content and CMS
Analytics
Settings
Overview
Chapter 03Process

What users actually said.

Direct feedback from real users that shaped the final flows.

Usability Testing
Test session
Revised - Overview
Revised - Orders
Revised - Inventory
Revised - Users
Revised - Content and CMS
Revised - Analytics
Revised - Settings
Test session
Chapter 03Stakes

Three numbers from the live dashboard.

Real metrics from the prototype. They shaped the hierarchy of every screen.

68%

Customisation rate.

68% of sneakers sell with patches. This metric does not exist in standard e-commerce. I put it front and center in Analytics.

2.4:1

Patch-to-sneaker ratio.

For every sneaker sold, 2.4 patches move. Patches contribute 42% of total revenue. They needed to be treated as a first-class category.

IND 9

Top selling size.

Drives 41% of sneaker sales. The Size Run Health Bar visualises demand across IND 7 through IND 11 for restock decisions at a glance.

Chapter 04Architecture

Seven screens, one sidebar.

Each screen answers a different question about the business.

Overview

What is happening right now?

KPIs, customer split, traffic sources, regional insights, recent orders.

Orders

Where is each order?

Status tabs, CSV export, patch names, delivery addresses.

Inventory

What do we have?

Category tabs, stock levels, Size Run Health Bar, dead stock management, inventory runway.

Users

Who are our customers?

CLV INR 12,500, repeat purchase rate, at-risk users, segmentation.

Content & CMS

What is the storefront showing?

Products, banners, campaigns and drops, stories, visibility, publish status.

Analytics

What does it all mean?

Revenue by category, patch-to-sneaker ratio, top products, customisation rate, campaign impact.

Chapter 05Foundation

A system built for density.

The dashboard runs on a custom design system built in Figma with tokens, components, and charts, all bound to Variables.

figma.com / Svaroots Design System

Typography, color tokens, spacing, components.

Chapter 06The hardest screen

Inventory is not one list.

Patches, sneakers, drops, cleaning kits, and gifting kits each have different stock logic. I designed a tabbed system with category-specific views, a Size Run Health Bar for Indian sizing, and a dedicated dead stock section.

The problem

Five product types sharing one screen.

Patches sell fast with low/moderate alerts. Sneakers move slower but need size granularity. Drops are time-limited. A single table would bury the differences.

What I designed
  • Category tabs. Patches, Drops, Sneakers, Cleaning Kit, Gifting Kit. Each shows only what matters for that type.
  • Size Run Health Bar. Demand across IND 7 to IND 11. Low, Moderate, High at a glance.
  • Dead Stock section. Slow-moving items surfaced with units and reorder actions.
  • Inventory Runway. Headline metric (6 months) so operators know stock duration instantly.
svaroots.dashboard / inventory

Screen 01 Inventory / category tabs / stock table / Size Run Health Bar / dead stock

Chapter 08The rest of the system

Four screens that complete the loop.

Overview for the morning glance, Orders for fulfilment, Users for lifecycle, Content & CMS for storefront control.

08.1 / Overview
svaroots.dashboard / overview

Screen 03 KPIs / customer split / traffic sources / insights / recent orders

08.2 / Orders
svaroots.dashboard / orders

Screen 04 Status filters / table / CSV export

08.3 / Users
svaroots.dashboard / users

Screen 05 CLV / segmentation / at-risk / AOV

08.4 / Content & CMS
svaroots.dashboard / content

Screen 06 Products / banners / campaigns / stories

08.5 / Settings
svaroots.dashboard / settings

Screen 07 Team roles / permissions

Chapter 07The story in the data

Metrics only a modular brand needs.

Standard analytics measures carts and revenue. Svaroots needed to know the relationship between patches and sneakers, the customisation rate, and which campaigns moved numbers.

Unique to Svaroots

Custom metrics for a modular model.

Patch-to-sneaker ratio, customisation rate, campaign impact, and revenue by category became the dashboard's core lens.

Metrics
  • Patch-to-Sneaker Ratio (2.4:1). Determines procurement balance across categories.
  • Customisation Rate (68%). Validates the entire modular concept.
  • Campaign Impact (+18%). Festive Fabric Edit drove 18% revenue uplift.
  • Revenue by Category. Patches contribute 42% of total revenue.
svaroots.dashboard / analytics

Screen 02 Analytics / revenue by category / patch-to-sneaker ratio / top products / insights

Live walkthrough

Click through all seven screens.

The full operator flow, clickable in your browser. Every sidebar link works.

Open prototype
Chapter 09What I learned

Three lessons from owning a product inside a team.

Designing a full product within a larger team comes with its own set of challenges. Here is what stood out.

Lesson 01

The product model shapes the IA.

Patches, sneakers, drops, kits. Once I stopped treating them as "products" and gave each a dedicated tab, the inventory screen stopped feeling like a spreadsheet.

Lesson 02

Invent the metrics the business needs.

Patch-to-sneaker ratio and customisation rate do not exist in Shopify. If the business model is new, the dashboard metrics have to be new too.

Lesson 03

Seven screens is a system, not seven pages.

Shared components, shared tokens, shared table patterns. The design system is what makes seven screens feel like one product.