Shushant Kumar — Product Design Manager

Leading — team, practice and craft standards

My job is the quality of the decisions the team makes without me.

Which is an easy thing to claim and a hard thing to prove. So this page leads with the part of my record that is externally verifiable — four years of teaching design to people who had no obligation to find me useful — and is explicit about the rest.

The mandate at Firstclub

I'm on the founding team at Firstclub, heading product design. My role sits between product strategy, design leadership and execution. I work with product managers, engineers and designers to shape direction, navigate the problems nobody has framed yet, and raise the quality of what we ship — while leaving the work itself with the designer who owns it.

In practice that means four responsibilities: deciding what the team should be solving, making sure each designer has the context to solve it, getting Product and Engineering to a decision early enough that the design survives contact with it, and holding a bar on craft that doesn't depend on me reviewing every screen.

Developing designers

Four years of faculty work, run in parallel with full-time design.

Why this belongs in a manager's portfolio

Every design manager claims they make other designers better. Almost none can point at anything outside their own company to back it. I can: four years as faculty, 20+ workshops and talks across India, and a set of topics I had to be able to teach — not just do.

It also changed how I manage. Teaching a room of students why an accessibility decision matters, or where B2B and B2C design genuinely diverge, forces you to make your own reasoning explicit. Once it's explicit you can hand it to a designer instead of handing them your answer — which is the difference between coaching and correcting.

Taught across 20+ events in India

  • UI/UX Design Bootcamp
  • Design Optimization
  • Digital Product Design
  • B2B vs B2C Design
  • Accessibility in Product Design
  • Designing for Emotional Engagement

Things I changed

Not projects — changes. This is the section a Head of Design reads hardest.

Fill these three — they are the highest-value thing on this page

  • What did you change about how the Firstclub team works? Rituals, critique, discovery, handoff, hiring, onboarding, the design system, how PMs bring work in.
  • For each: what was actually happening before, what is happening now, and how do you know it stuck.
  • Keep them concrete. “Improved collaboration” is invisible; “design joins the problem-framing session, so specs now arrive with a UX point of view already in them” is evidence.
  • Add or remove rows freely — three is a minimum, six is plenty.

How I run design

The tangible artefacts of a management practice, rather than a philosophy.

Critique

A critique that opens with “what do you think?” produces opinions. One that opens with the decision on the table produces a decision. I ask for the question first: what are we choosing between, on what criteria, and who calls it.

One-to-ones

Craft, product, career and how the week actually went — in that order of frequency, not importance. The status update is the least useful thing that can happen in a 1:1.

Design review

Five questions, in order: is this the right problem, is the interaction understandable, does it fit the product's direction, is it feasible, and what evidence do we have. Visual polish is the last conversation, not the first.

Discovery

Enough research to know which decision the user is stuck on. Not a study for its own sake, and not a jump to solutions because the deadline is close.

Make this tangible — replace or extend with what you actually use

  • If you have a 1:1 template, critique format, design review checklist or discovery doc, send it and I'll typeset a redacted version. A real artefact beats a description of one.
  • Also worth adding if it applies: hiring loop and how you evaluate candidates, onboarding for a new designer, how you set and review goals, how you handle a designer who is stuck.

Team impact

Trajectory, not private detail.

Add whatever is true — no names needed

  • Designers who took on a larger scope, a promotion, or their first end-to-end ownership while reporting to you.
  • Designers you hired, and what you changed about how you evaluate candidates.
  • A designer who started presenting to leadership, or running their own critique.
  • Reduced review cycles; work arriving at review already defensible; fewer reversals after launch.
  • Anything a designer can now do without you that they couldn't a year ago. That is the only real metric here.

What people say

Three quotes, not fifteen. Each one should evidence a specific behaviour.

A designer who reported to you — on what it was like being managed by you.
Designer · role, company
A product manager — on how you influenced product decisions.
Product · role, company
An engineering lead or your own manager — on how you operate cross-functionally.
Engineering · role, company

How to ask for these

  • Ask for one specific thing, not a reference. “Could you write two sentences about how the critique format changed how our team made decisions?” gets a usable quote; “could you say something nice” gets “great to work with”.
  • Your LinkedIn recommendations may already contain usable material — check there first.

Recognition

Split by what it was actually for.

For how I work

For what shipped

Want to talk about running a design team? I'm easy to reach.

shushant0657@gmail.com

Open to Design Manager and Head of Design conversations