Intake — whatever exists so far
One Claude Project per client. The first message carries every document sales hands over. That is the start of the thread.
Akash Kalsi · UI/UX Lead · Mindbowser · Panchkula, IN
The distance between deciding something and it being real —
a handoff.
now it's
a branch.
I lead a design team that stopped delivering Figma files. We design directly in Claude Code, in the client's repo — and I wrote the delivery standard that makes that safe for complex, regulated products. The proving ground: US healthcare, where getting it wrong is expensive.
follow the thread
§1 · carrier oneClaude Chat
one project, one conversation
one project, one conversation
Everything we hear, read or decide goes into one thread.
A design sprint fails in the gaps — the decision made on a call nobody wrote down, the constraint that lived in one person's head. So we removed the gaps. Nothing is allowed to live only in someone's head.
Every document, call, email and correction goes into the same running conversation, and the artefacts the client signs are built straight out of it — so the sheet and the conversation can never drift apart.
Discovery, on the record
Every client call is recorded and transcribed. Internal calls too. Each transcript goes into the same chat — after I've read it and corrected what the model misheard. My brain is the checkpoint.
EPICO → transcript → thread
artefact
The feature list
Built from the whole context. One tab per role, grouped by section — screens, data points, purpose, actions, modals. Never one combined list.
artefact
The workflow diagram
Feature list, information architecture and user flow in one picture — per role. The loop is always the same: internal review → senior → client → feedback back into the thread.
⚑
Client approval — the gate.
They sign the list and the diagram. Only now does the thread change carrier.
They sign the list and the diagram. Only now does the thread change carrier.
the shift · chat → code
Chat and Code share no memory. The context is carried across by hand.
The most fragile point in the whole flow. Nothing crosses on its own — it crosses on .md files, into every repo, on the right branch.
CLAUDE.md
PROJECT_BRIEF.md
design.md
constants.md
feature.md · if it's needed
What isn't written down doesn't make it across.
§2 · carrier twoClaude Code
sessions, stitched by handoff files
sessions, stitched by handoff files
One feature, one branch, one commit, two pull requests.
The coded deliverable auto-deploys to the client's review site, so one fact drives everything: a merge is a publication. The standard I wrote has two jobs beyond tidy code — make an accidental publication impossible, and make a bad deploy detectable rather than merely unlikely.
✓
typechecktsc --noEmit
✓
lint0 errors
✓
prettier--write .
✓
buildread the chunk sizes
Review it uncommitted, in a browser
Against the spec — never by reading the diff. Defects that pass typecheck, lint and build while being plainly wrong on screen are the normal case, not the exception.
Two PRs, two different reviews
The design PR is a publication and it's mine to merge deliberately. The dev PR belongs to the engineering team, on their schedule — a naming comment never holds up a client demo.
Verify the deploy — the tick is not the check
A green pipeline says the job ran; it has run green while shipping the wrong build. I diff the deployed asset hashes against my own build. diff local.txt deployed.txt
Nothing in the standard is theoretical. Every warning in it is something that went wrong once — and cost real time to find.
§3 · selected workthe problem, the decision,
what changed
what changed
Three products, one process.
Client work is under NDA and stays that way — no names, no screens. What I can show you is the shape of the problem and the decisions that mattered. The rest, redacted like this, I'll tell you in a room.
the problem — organ viability is measured in hours
Coordinating a transplant, against the clock.
A multi-role platform for a US transplant network where a slow screen costs outcomes, not conversions. Roughly one in four kidneys recovered for transplant is never transplanted — the search for a recipient outruns the organ's shelf life.
The constraint inverted the architecture. The registry that governs allocation has no API for anyone outside it. So the product runs beside it rather than through it, and the coordinator alerts centres directly. The scramble was always manual; a layer over a manual process is the truer fit, not the compromise.
The decision I'd defend. The brief listed favourite centres drive prioritisation as a feature — the precise mechanism the equity literature criticises. I replaced it with criteria centres declare in advance, matched per donor. Same speed, nobody chosen by hand, and every centre left off says why.
what changed The pitch stopped being “place organs faster” and became place organs faster, and make the fast path defensible — which is what a regulator tightening oversight is asking for.
under nda
cold ischemia · running
11h 40m
cross-clamp
12h
24h
36h
it only goes one way. every screen in the product answers to it.
the problem — too many roles, one workflow
A second healthcare sprint.
The case where the design call was hardest to argue for — a regulated clinical workflow where accessibility wasn't a checklist at the end but the constraint that reshaped the information architecture.
awaiting input which project, and what made it genuinely difficult.
under nda
the problem — the deliverable stopped being a file
Taking Figma out of a design team.
Not a tooling swap. Once the deliverable is a running app on a branch that auto-deploys to the client, every habit a design team has needs rewriting — how work is reviewed, who may publish, what happens when feedback lands after a merge.
I wrote the standard, versioned it, and taught the team to run it. The piece of work I most want to be judged on — and the one I can publish in full.
§4 · on papercounted, not claimed
4y 10m
at Mindbowser —
designer → senior → lead
designer → senior → lead
4
gates before
every push
every push
40+
design sprints —
most in US healthcare
most in US healthcare
3
annual company awards,
three years running
three years running
2
master's degrees —
the second in UX + AI
the second in UX + AI
M.Des in User Experience Design, AI specialisation — Jindal School of Design & Architecture, O.P. Jindal Global University. Earned in the margins of a full-time job.
§5 · historya career, committed
git log --oneline
~/akash-kalsi $ git log --oneline --graph
*f2a9b41(HEAD → open/to-work) feat(next): looking for the room where this is normalnow
*b4d02aafeat(process): delivery standard v1.0 — figma removed from the pipelineaug 2026
*3e5a90fdocs(degree): M.Des UX Design, AI specialisation — JGU · alongside the day job2026
*8c17d3efeat(role): promoted — UI/UX Leadmay 2026
*91cc7f0feat(role): promoted — Senior UI/UX Designermay 2025
*4d8e2b9feat(recognition): annual company award — third year running×3
*a7f31c5feat(craft): 40+ design sprints shipped · US healthcareongoing
*0b6d94efeat(career): joined Mindbowser — UI/UX Designernov 2021
*c59e01dinit(career): first design role — DarkLion Studiomar 2021
§6 · the domainwhere I'm deep
US healthcare, where getting it wrong is expensive.
Nearly five years of it. Regulated workflows, many roles, real accessibility requirements, and stakeholders who know their domain far better than I know mine. It's the environment that taught me to write everything down. The domain is the proof, not the ceiling — the same discipline carries anywhere the stakes are real.
- Accessibility
- Not a checklist at the end — in healthcare it's frequently the constraint that reshapes the information architecture.
- Multi-role systems
- Feature lists and flows built per role, never combined. The discipline that stops a platform collapsing into one confused screen.
- Regulated workflows
- Where copy is a claim, seed data carries authority, and an unbuilt claim in the interface is a defect — not a wording problem.
- Stakeholder rooms
- Clinicians, PMs and engineering leads disagreeing productively. Getting to a decision is most of the job.
§7 · the humanoff the clock
Selectively extroverted. Reliably obsessive.
I'm from Panchkula, near Chandigarh — studied here, live here, never particularly wanted to leave. I did my second master's in the margins of a full-time job: two years of intensives, immersions and a great many late nights.
The thing I'm actually good at is finishing. I like the part most people find tedious — the state nobody designed for, the edge case in the role matrix, the fourth review pass. My work reads as pedantic until the week it saves someone.
Away from the desk: snooker, cricket, and an unreasonable number of Nolan rewatches.
§8 · end of threadthe merge
If your designers ship code — what are you calling them?
I asked that publicly and never got a good answer. If you're hiring for the thing I actually do — design judgment carried all the way to the merge — let's talk.
feat(team): add akash kalsi
#0001 · akash wants to merge 1 commit into your-team:main from akash:open/to-work
✓ design review — passed · you're looking at it
✓ code review — passed · view source, it's hand-written
✓ gates — 4/4 · typecheck · lint · prettier · build
Merge pull request
merging opens your mail client · akashkalsi9@gmail.com