Individual perspectives
We share a studio and a standard, not a single way of thinking. Here's how each of us approaches the work.
Same studio, same standards. Different instincts about where good work begins.
“I start with words, not shapes. If we can't say what a brand stands for in one sentence, no logo is going to save it.”
“Everything moves eventually, on a screen, on a shelf or in someone's memory. I design for the moment something changes.”
“A design isn't finished until it works on a cracked phone with one bar of signal. That's where I do my best thinking.”
“My job is asking the awkward question early, so nobody has to ask it at launch.”
“I draw to think. Half my best ideas turn up in the margins of something else.”
Hand us a single brief and you'll get five different first moves. Here's where each of us would begin.
The brief
“A community clinic wants patients to book appointments online, instead of queuing outside before sunrise.”
First move
Before drawing a single screen, I'd see how patients book today, who struggles and on what phones. Then I'd wireframe the shortest path from “I'm sick” to “I'm booked”.
What you'd see firstClickable Figma wireframes we can test with real patients.
First move
Patients, staff, time slots, reminders. I'd map how data moves from the booking form to the clinic's daily list, then pick the simplest stack that holds it all together.
What you'd see firstA system diagram and an end-to-end prototype.
First move
One clinic, one doctor, one day of slots. I'd get a real booking through, front to back, in the first week, then grow it from there.
What you'd see firstA live booking flow the clinic staff can try themselves.
First move
Many patients will book on older phones with patchy data. I'd build light, accessible screens that load fast and stay readable for everyone, including people who rarely go online.
What you'd see firstResponsive booking screens tested on low-end devices.
First move
Double bookings and lost records are what break trust. I'd model patients, slots and appointments first, lock down who can see medical details, and build the API around that.
What you'd see firstA database schema and a documented, secure booking API.
Contact