Summer 2026

Summer 2026

Golden Hour

Golden Hour

Adventures

Adventures

I’m Harsh, and I like making complicated things simple.

I’m a product and project manager in Hatfield. I’ve spent four years deciding what gets built, designing it, and staying with it until it ships, and along the way I’ve run delivery for a wellbeing app, a ticketing platform, an SEO product and an arts studio. I built most of them myself.

Product Designer

A snapshot of the work so far

01

0+

0+

Years of experience

02

0+

0+

Projects shipped

03

0+

0+

Industries served

A journey shaped by the teams I ran it with

01
Aug 2022 to Nov 2022

Turito

SEO Intern

Delhi, India

I started on search, and that’s where I learned how much the content and the structure decide whether anyone finds a product at all.

02
Jan 2023 to Jul 2023

Silver House By RJ

UI/UX Designer

Lucknow, India

I designed for a jewellery brand where every screen was tied to revenue, and their online sales grew from nothing to over a thousand dollars a month.

03
Aug 2023 to Jun 2025

Blank Multimedia

Creative Media Director and No-Code Developer

Lucknow, India

I ran creative and web delivery, and I was responsible for whether the numbers actually moved rather than only for how the work looked. The redesigns I led lifted conversions by around 45%.

04
Jun 2025 to Sep 2026

7 Seers Media

Co-Founder and Head of Product Design

Lucknow, India

I co-founded the studio and led product design end to end, from deciding what got built to shipping it alongside developers.

Currently here
05
Sep 2026 to now

University of Hertfordshire

MBA, Extended Professional Practice

Hatfield, United Kingdom

I’m reading for an MBA in Hatfield, with Project Management Methodologies as my elective, and I’m working towards a product and project role in the UK.

How I work

I start with the decision, not the screen

Before anything gets drawn I want the brief turned into a numbered list of decisions, each one with an owner and a date, agreed in writing. Most of the work is deciding what to leave out, and it’s much easier to do that on a page than halfway through a build.

I start with the decision, not the screen

Before anything gets drawn I want the brief turned into a numbered list of decisions, each one with an owner and a date, agreed in writing. Most of the work is deciding what to leave out, and it’s much easier to do that on a page than halfway through a build.

decide it before you draw it.

the conditions are never ideal.

I design for the constraints that are actually there

Budgets are tight, dates are signed and legacy systems don’t move. I’d rather cut the scope early and ship the smaller thing on the date than hold on to a plan that was never going to work.

I design for the constraints that are actually there

Budgets are tight, dates are signed and legacy systems don’t move. I’d rather cut the scope early and ship the smaller thing on the date than hold on to a plan that was never going to work.

I write it down so nobody has to remember it

Every decision that moves money or time goes back to the team as a written document rather than a message in a thread. One update a week, in the same four parts: shipped, next, need from you, at risk.

I write it down so nobody has to remember it

Every decision that moves money or time goes back to the team as a written document rather than a message in a thread. One update a week, in the same four parts: shipped, next, need from you, at risk.

write it down.

stay until it ships.

I stay with it until it ships

I decide what gets built, I design it, and I’m still there when it goes out. I’d rather stay with something until it’s actually live than hand it over halfway.

I stay with it until it ships

I decide what gets built, I design it, and I’m still there when it goes out. I’d rather stay with something until it’s actually live than hand it over halfway.

My story

Core
Capabilities

Delivery

Project delivery, end to end

Scope and cuts

Risk and dependencies

Written updates

Stakeholder decisions

Product

Requirements

What version one is allowed to be

Prioritisation

User flows

Prototyping

Design

Design systems

Design tokens

Component libraries

Responsive design

Build

Framer

Shopify

CMS and integrations

Handover

FAQ

Question

Are you a designer or a project manager?
Harsh Upadhyay

Both, and that’s the point. I decide what gets built and write the requirements the build runs on, then I design it and I’m still there when it ships. On most teams those sit with two people, and the gap between them is where things tend to go wrong.

Question

Do you build design systems, or just screens?
Harsh Upadhyay

Systems, where the team is big enough to need one. On DadWell every colour was a semantic token so a change propagated instead of needing a sweep, and on Solika Arts four portals ran off one token set so a status colour landed in all four at once.

Question

What does your process actually look like?
Harsh Upadhyay

Four steps. Turn the brief into a numbered list of decisions with an owner and a date. Break the work down and name the risks early. Design the screens and build what I can myself. Then ship to the date and send one written update a week: shipped, next, need from you, at risk.

Question

What kind of roles are you looking for?
Harsh Upadhyay

Product and project management, particularly delivery roles in the NHS and IT, where the plan and the product decisions sit with the same person. I’m in Hatfield and I’m happy to travel to London.

I’d genuinely love to hear from you.

Let’s talk

Open to product and project roles

Connect on socials

I’d genuinely love to hear from you.

Let’s talk

Open to product and project roles

Connect on socials

I’d genuinely love to hear from you.

Let’s talk

Open to product and project roles

Connect on socials