I work where product, design and engineering overlap.

20+
Years in product & UX
1
Inside the team, not at a hand-off
AI
native practice, built with AI

I’m Justin Roberts, a principal product designer. For twenty years I’ve worked inside product and engineering teams, not beside them: discovering what’s worth building together, designing it, and shipping it with the people who build it.

01 — The overlap

Three disciplines, one loop, worked with the team.

Product

Discover what’s worth building.

Discovery, validation and prioritisation, done with the team rather than for it. I’ve mentored product managers, and at PatientPop helped shape what became the Tebra Care marketplace, still live today.

Tebra →
Design

Make the answer feel obvious.

Principal product designer on Singapore’s Ministry of Manpower work-pass rebuild. The most senior design practitioner at Smokeball, holding the hardest problems and mentoring the designers around them.

Smokeball →
Engineering

Ship it, not a mockup.

I hand-coded my first sites twenty years ago and have shipped front-end ever since. At Chime Labs I take Jira stories to production: scoped branches, automated tests and AI-reviewed pull requests, released with the engineers.

Chime Labs →
02 — The method

Discover. Design. Ship. Learn. Again.

Reloop is the loop a good team works in, and the mark is drawn from it. The left loop is product: discover, validate, prioritise. The right loop is engineering: build, release, monitor. Design isn’t a stage between them. It runs through the whole loop, from the first conversation to the release.

Then it loops. What shipped tells you what to build next, so the work never ends at a handover.

Fig. 02 — The Reloop method. Design, in volt, runs through the whole loop.
03 — The practice

A practice, not an agency.

When you engage Reloop you get me — the same person through strategy, design and delivery. There is no team behind the name to hand the work to, which is the point: nothing is lost in translation between the person who understood the problem and the person who solves it.

I’ve built design functions from nothing, mentored designers, product managers and engineers, and set product direction with executives across three countries — always as the senior practitioner in the room, never as the person writing the performance reviews. That’s a deliberate choice rather than a gap. Put me on the hardest problem with a team around it and that’s where I’m worth the most.

04 — In their words

From the people I build with.

From product

“He raised the bar for successful design and UX, constantly challenging me as a PM to step back and see the customer experience from a wider lens.”

Nicole Povey
Staff Product Manager, Tebra
From engineering

“It’s rare to find such an experienced Product Designer with deep knowledge of agile methodologies and software development.”

Michael Simpson
Head of Engineering, Atomi
From the founder

“Justin is one of the best and most versatile designers I’ve worked with. The tools made him fast; his taste is what makes the work good.”

Alexis Griveau
Co-Founder & CEO, Chime Labs

I work the way a small team does and move at the pace one can: research, design and delivery in the same head, decisions made once rather than negotiated across a handover. That suits teams who are shipping and need the thinking to keep up, and teams who have stalled and need someone to find out why.

Based in the Southern Highlands of New South Wales, working with clients here and overseas — Sydney, Singapore, Los Angeles. Most of the work is B2B: software with a buyer and a user who are rarely the same person, where the hard part is serving both without the product becoming a compromise.

Design, user experience, product management and front-end have all been my job at different times, and often at once — at Neo Innovation the designers held product, because there were no product managers to hand it to. That is still how I work. It means I can sit in the research, make the roadmap call, draw the screen and check what the build actually did.

Evidence, then judgement.

Design decisions get made against evidence rather than taste, but evidence is not a substitute for judgement — most of what matters in a product has never been measured and never will be. The craft is knowing which is which.

Ideas are cheap. What teams need is the part after: putting the thing in front of real users, watching it fail in ways nobody predicted, and changing it together. Some of the work I’m proudest of ended with a recommendation not to build.

See my work →
Tell me what you’re building. I’ll tell you if I can help.
Email me →