a handoff.
now it's
a branch.

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 engagement is under NDA, so what you can open is my own rebuild of it: same problems, same decisions, none of their data.

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.

Telling a student what it costs, while they can still fix it.

The student side of an AI evaluation platform for professional education. The engagement isn’t mine to name, so the client’s name and branding came out and the demo you can open is that build, rebranded. A student thinks the job is upload → submit → done; the system needs complete → readable → evaluable before grading can start. Almost every platform reports that gap after submission — when it is a verdict, not information.

The constraint shaped everything. Reading a document with a model is expensive, and the client put that on the table in week one rather than hiding it. So validation splits into three tiers, and the interface is honest about which one you are in: the checks you can act on run while you watch, the expensive one is queued and you are released.

The decision I’d defend. Everyone designs the success and failure states; the warning state is the one that actually costs marks. So the consent dialog names each criterion, prints its exact weight, and states what proceeding costs — then tells you there is still time, and that resubmitting cannot lower your grade.

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. It’s the only one of the three with no client on the other side of it, so it goes out exactly as written.