I’m Tejus R Meda — a UX designer in Newcastle upon Tyne. I work at Ultramed, where the software I design sits between a patient and their surgery. That’s a lot of weight for small decisions to carry, and it’s the part of the job I like most.
For seven years I taught structural engineering at an architecture college in Bangalore. I liked the teaching. What I couldn’t stand was the paperwork — attendance registers, mark sheets, the same form typed out three separate times.
So I built them a system. Nothing glamorous: admissions, attendance, marks, all in one place. The software wasn’t what stayed with me. Watching the office’s whole week change shape because of it was. That’s when it landed: I wanted to shape how software feels to the person stuck using it at 4pm on a Friday.
I moved to Newcastle in 2023 for an MSc in Human–Computer Interaction. It gave that instinct a method — research, testing, the discipline to check whether something actually helped, or just looked like it did. I’ve been at Ultramed since.
Technology earns its place by taking something off someone’s plate.
In healthcare that stops being abstract quickly. Every flow I design is somebody’s pre-op assessment, and there’s a person on the other end of it with a surgery date. If what I ship today makes one of those days easier, that was a good day’s work.
Rotterdam · Cube Houses
My wife and I travel every chance we get — ten countries so far. We’re the sort who’d rather find where people actually eat than tick off a landmark. I’ll take an experience over an object almost every time. Tech’s the exception: I have opinions about monitors, keyboards and cameras that nobody asked for.
img/about/natter-con.jpg
img/about/hobby-1.jpg
img/about/hobby-2.jpg
img/about/hobby-3.jpg
img/about/hobby-4.jpg
img/about/hobby-5.jpg
I read mostly non-fiction, the self-improvement end of the shelf, and I watch a lot of films. Both do the same thing for me — borrowing how someone else thinks, for a couple of hours.
I’m a designer who learned to work with AI rather than around it. Concretely, this is how a feature goes from a vague request to something living in the product:
Pull it apart until I know what’s really being solved and for whom. Paper and pencil, most of the time.
I generate a few directions and click through them. It’s cheaper to throw away a working prototype than to defend a Figma file.
Our subject matter experts are the closest thing to end users I have in the building. They poke holes, I take notes, and I go back to step two.
Once the shape settles it becomes real components, built against our design system rather than next to it.
Claude Code and VS Code, into the actual product, so I can see how it behaves alongside everything else.
Developers tell me what won’t hold up. There’s almost always one more round after that, and it’s usually the one that matters.
An unclear brief is the interesting part. I’ll read what exists and find whoever knows, and if nobody’s free I’ll make an assumption, design against it, then bring it back to be corrected. Moving beats waiting.
Teaching, ERP, academia, healthcare startup: the context keeps changing and I’ve got used to picking up a new domain quickly and being useful in it early.
The odd spacing, the broken pattern, the label that’ll confuse someone at 2am. Catching those has been my most useful habit since the start of my career.
No ceremony required. Ask me where something’s at and I’ll show you the actual thing.
Then we should probably talk. I’m always up for a conversation about healthcare, design, or where to eat in a city you’ve just landed in.