Diandra Grubbs
Product Designer · Information architecture & interaction

Structure first. Then the screens.

I'm a product designer who starts with how the work actually happens — auditing real tasks, defining the product, and building the architecture everything else hangs on. Most recently I led the redesign of Control Tower, the internal operations platform behind every Ritchie Bros. transaction.

Information architecture Interaction design Product definition Prototyping in code
01Selected work

Three projects, one way of working

Flagship · Internal operations platform

Control Tower 2.0

Re-architecting the internal platform every Ritchie Bros. support team uses to move a transaction from auction to released asset. I grounded a full Retool→React redesign in an audit of 51 real support actions, derived a six-section architecture from how the work actually flows, and led both product definition and design — without a PM.

Read the case study
PlatformRetool → React
Architecture6 primary sections
Users5 support roles
Grounded in51-action SOP audit
OwnershipProduct + design, solo
02How I work

A method, not a style

01

Audit

I start with the real work — SOPs, tasks, the actions people actually take — before any layout exists.

02

Architect

Structure comes out of that audit, not out of a guess. The IA is something I can check decisions against.

03

Prototype

I build flows in HTML to pressure-test them before committing to polish, so feedback is on the real thing.

04

Refine

Then into Figma — with the reasoning logged, so the why behind each decision survives the handoff.

Open to product design roles

Let's talk.

grubbsdiandra@gmail.com