Skillstrainer

Client: Skillstrainer Years: 2021 - 2023 Role: UX Lead and Product Designer

1.5 million learners. That number did not happen by accident.

Skillstrainer is one of India's largest vocational skilling platforms - a platform designed to help people across the country build practical job-ready skills. When I came in, they were at 300,000 users and growing fast. The challenge was not the growth itself. The challenge was that the existing design and product infrastructure was not built to handle it. Without a serious rethink, the growth would break things.

---

My Role

• UX lead across the platform overhaul
• Design system architecture and component library
• User research and journey mapping
• Coordination with product managers and development teams
• Handover and documentation for ongoing development

---

The Challenge

Scaling a learning platform is not the same as scaling an e-commerce site or a SaaS dashboard. The users are diverse - different literacy levels, different devices, different comfort with technology. A design that works for an urban professional does not necessarily work for someone in a Tier 3 city completing a vocational course on their phone.

The key problems:

1. No design system - every screen was a one-off. Inconsistency across the product made it feel unreliable, and it meant every new feature started from scratch
2. Drop-offs at critical steps - users were abandoning at course enrolment and mid-course. The flows were confusing, not compelling
3. No scalable component architecture - developers were rebuilding UI elements repeatedly, slowing down every sprint
4. Accessibility gaps - the existing design made assumptions about users that did not hold at the platform's actual scale

---

The Approach

Starting with a design system

The first decision was to build a component library before touching any user-facing screens. It sounds counterintuitive when there is a growth problem to solve, but it was the right call. Without a shared component language, every fix creates new inconsistency.

I built the design system in Figma - a comprehensive set of components, patterns, and guidelines that the development team could implement once and reuse everywhere. Every element was documented, every state accounted for.

Mapping the real user journey

I spent time understanding how Skillstrainer's users actually interacted with the platform - not how the product team assumed they did. The gap was significant. Enrolment flows were optimised for users who already knew what they wanted. In practice, most users needed guidance to find the right course before they could commit.

Restructuring the discovery and enrolment journey around how users actually behaved reduced the friction at the critical conversion point.

Building for longevity

One of the outcomes I was most focused on was making sure the work did not create dependency. I documented every decision, structured the design system to be extendable, and ran working sessions with the development team so they understood the architecture - not just the output.

Several of the developers I worked with during this project went on to join Skillstrainer directly. That says something about the quality of the team and the work environment we built together.

---

The Solution

• Full design system in Figma - components, patterns, guidelines, and documentation
• Restructured enrolment and discovery flows - simplified paths to course selection and sign-up
• Revised course interface - clearer progress indicators, reduced cognitive load mid-course
• Accessibility improvements - better contrast, clearer hierarchy, reduced assumptions about user familiarity with interfaces
• Handover package for the internal development team with component specs and implementation guidance

---

Key Outcomes

• 300,000 to 1.5 million users - 5x growth, with platform stability maintained throughout
• Design system adopted across the full product - development velocity improved significantly
• Reduced drop-offs at enrolment and mid-course on key journeys
• Multiple team members from the project joined Skillstrainer directly - a sign the working relationship was strong

---

What I Took From It

This project taught me the difference between designing for a product and designing for the people who will scale a product after you are gone. The design system was not just about consistency - it was infrastructure. The documentation was not busywork - it was the thing that made the work last.

Scale changes everything. What looks fine at 300,000 users can fall apart at a million. Building for that from the start is the only way to avoid a painful rebuild later.