Ramamoorthy Kumar · Product Design Leadership · Sprinto
Design systems are decision systems.
I build them for products, for AI, and for the teams that ship both. Eighteen years in, I still build them myself.
Receipts
At Sprinto, "done" only counts once it's verified. I hold my own claims to the same rule, so every number here carries a label.
Selected work
Each story is named for what I believe it proves. Each ends with what didn't work yet, because that's usually where the real decisions were.
SprintoX · AI-native onboarding
Turning compliance from a checklist into a state
Customers needed a person to walk them to audit readiness. We designed a system that sets itself up, keeps a living compliance state, and only interrupts people when its confidence drops. Setup went from 5–6 hours to 40 minutes.
Not yetEnterprise adoption hasn't followed. Accuracy and trust gaps are the reason, and they're named in the story.
Read the case study →Ask AI · AI UX patterns
Conversation as the control plane
Most B2B AI is a chatbot bolted onto a dashboard. Ask AI is an action layer that knows which record you're on. It runs on 15+ pages and sits on 12+ patterns with built-in guardrails.
Not yetOutput quality is still being improved. The story shows how we measure it and what changes each round.
Read the case study →Constitution · NeoGrid · RedPill · Datum · Forge
A design system is an organizational decision system
Five layers, from brand promise to executable code, with one rule between them. 92% coverage, 51+ components, 25% faster implementation, and the People area cut from seven tabs to three.
Not yetThe real test is an independent team reusing a pattern without us. That review runs in January 2027.
Read the case study →Three streams · Ownership ladder · Builder OS
Designing a design org that works without me in the room
Eight designers, three streams with different mandates, and a ladder from owning a solution to owning a business outcome. Builder OS, which I co-created and orchestrated, let designers ship small fixes with AI coding tools.
Not yetBuilder OS first read as activity, not outcome. Some designers felt the ladder made the job "basically a PM role." Both changed how I frame the work.
Read the case study →Earlier work: Sprouts.ai, Birdeye, Yubi, Chargebee, Ellucian →
How I lead
Most design leaders can show an org model or a design system. To me they're the same argument at two altitudes.
Product Design Constitution
Fourteen sections that turn brand into product law, including a written order for settling conflicts.
NeoGrid
Tokens, components and accessibility contracts. The shipped foundation.
RedPill
Patterns for agentic work, with a trust model as a required field.
Datum
A reference build. One source file generates five artifacts and fails the build on a bad value.
Forge
Where ideas get tested safely. Four promotion gates, and the default at each one is no.
One rule holds the stack together: a lower layer may specialize a higher one, but never silently contradict it.
The team
What each designer owns
Before any significant work starts: what metric moves, what's the baseline today, and how will we measure it.
Workbench
I still build. These are things I make with my own hands, mostly so the team has something better to design against.
Working React, not mockups
Multi-screen app flows, data tables with grouping and infinite scroll, and interactive prototypes for leadership reviews.
Datum
A reference build that turns design-system rules into checks. Raw hex values and failed contrast break the build instead of slipping through.
Skills and project instructions
A design-system skill so AI agents build with NeoGrid conventions, and project rituals that keep facts, guesses and decisions apart.
What people say
From people who managed me, worked beside me, and grew on my team.
An exceptional design leader who brings together strong creative vision, user empathy, and a deep understanding of how design drives business outcomes.
Goutham JoshiManaged RK at Sprouts.ai
He enabled me to move from IC work to leading pods. That space to grow was created by him.
Utkarsh BhandariDesigner on RK's team at Sprinto
The most skilled yet most humble designer I have known since 2017.
Prashant Kothari JainFirst PM hire at Chargebee
Field Notes
Essays that started as problems inside a build and turned out to travel.
AI UX is a behavior specification, not a visual style
Aug 2026 · 8 minNine stages of an agentic action, five automation classes, and the four stages after execution where trust is decided.
Most design system arguments are jurisdictional
Aug 2026 · 6 minWhy the button-colour meeting never ends, and the five-item order that settles it in ninety seconds.
Using AI as institutional memory, not as a chat window
Aug 2026 · 5 minFour files, two rituals, and one sentence that stops proposals from being recorded as decisions.
Where to next
Pick the door that fits why you're here.
Hiring a design leader?
Start with how I lead and the four case studies. The full résumé is on the About page.
See the résumé →Building an AI-native B2B product?
I advise teams on AI UX, design systems that agents can use, and design orgs that scale.
Work with me →Starting out in design?
I started in ad agencies with a Fine Arts degree. The path, the toolkit and the notes are for you.
See the path →