PRAKRIA
A multidisciplinary design studio where speed meets precision. Joined as Full-Time UX Designer — building one system 15 different projects could actually use.
Role
Full-Time UX Designer
Tenure
1 Year
Output
15 Websites Shipped
Team
Designers · Devs · CS
Prakria is a multidisciplinary design studio where speed meets precision. Joining as a Full-Time UX Designer, I was tasked with bridging the gap between artistic vision and functional engineering — moving across diverse industries without sacrificing standards.
India
Cross-functional
Design Studio
Rapid Scaling
15 live projects, ranging from minimalist editorial platforms to complex e-commerce engines.
Corporate websites. Brand-first, content-led.
Content platforms. Reading experience as the product.
Consumer flows. Conversion without compromise.
Consultant tools. Internal tools for external results.
Studio systems. The tools that made everything else possible.
"No two projects were the same. The diversity of the client base forced a radical shift in perspective every few weeks, honing my ability to find the core user need instantly."
In a fast-paced studio, research must be *lean but deep.*
Rapid analysis through existing data — analytics review, competitive landscape scanning, stakeholder interviews condensed into 48-hour sprints rather than weeks.
3–5 competitive products audited per industry for IA patterns, visual language, and conversion architecture. Built a reusable research library across 15 projects.
Weekly design reviews. Kanban-driven project tracking. QA checklist maintained across all projects — standardised to remove subjectivity from quality decisions.
Precision is not an act, but a *habit.*
One of my primary responsibilities was expanding the Quality Control initiative. By establishing a rigorous QC checklist, we reduced post-handoff bugs to virtually zero and significantly increased client satisfaction across the board.
The smallest details — a 4px misalignment, incorrect padding on mobile, a hover state that doesn't fire — can break the entire illusion of quality for a client. QC turned design from craft into operations.
Bug reduction post-QC implementation
Button variants consolidated into one governed component
Components shipped into the shared system
Ten live websites I designed at *PRAKRIA*.
Each card below links to a live, public website where I led the UX and UI design. The work spans e-commerce, EdTech, SaaS, defence, pharma, impact investing, and the studio's own brand presence. Two of these sites credit Prakria publicly in the footer.
Every site above is live and publicly accessible. Two — Keepsakes and Synokem — credit Prakria publicly in the footer as design attribution.
Projects shipped
Year tenure
Avg delivery cycle
Trajectory
Design doesn't happen in a vacuum.
Technically flexible without compromising the studio's bold vision.
Components that scale across projects and industries.
No apologies for strong visual decisions.
Live system primitives
| Token | Value | Used In |
|---|---|---|
| color/accent | #00FF9C | Brand · CTA · focus rings |
| radius/sm | 4px | Cards · inputs · pills |
| space/4 | 16px | Default rhythm |
| type/display | Clash Display | Headings · hero · marketing |
| type/body | Cabinet Grotesk | Body · UI · labels |
What this project *actually taught me.*
Adoption is the only success metric
A design system that ships is worthless. A design system the engineers trust enough to use instead of building their own version is everything.
Documentation is a deliverable
Engineers needed decision-point guidance — 'use this when...' — not visual specs. Documentation quality is system quality.
Governance > generation
47 button variants existed not because nobody could draw a button, but because nobody owned the question of which one to use. Ownership beat output.
Speed comes from constraints
Standardising the boring parts is what made the interesting parts go fast. The system bought us creative time.
"A design system lives or dies on documentation quality and on whether the people building the product actually trust it enough to use it instead of building their own version."