Hello.
I'm James.
Platform Design
System Design
AI-Native Tools
I design the systems that help technical teams work with clarity and confidence.
I work at the system level — shaping how platforms, APIs, and data-heavy tools behave so the people using them can focus on their work, not on figuring out the tool. My focus is semantic clarity, trust, and reducing the cost of understanding in complex technical environments.
Thanks for visiting my site. I created it for you.
How I Work
Most of the complex systems I've worked on share the same root problem: the system works, but people can't reason about it. Teams talk past each other because they're operating from different mental models, unclear dependencies, and fragmented context.
I step into that gap. I map how the parts interact, define shared language, and design the experience layer that makes the system legible to everyone who depends on it — engineers, operators, product teams, leadership.
This usually means I'm operating upstream of interface design: framing the problem, modeling the domain, establishing the semantic foundations that make the UI decisions downstream almost obvious. I prototype in code, validate through conversation, and design for expert users who value precision over polish
Selected work
(1)
I design the systems that help technical teams work with clarity and confidence.
I work at the system level — shaping how platforms, APIs, and data-heavy tools behave so the people using them can focus on their work, not on figuring out the tool. My focus is semantic clarity, trust, and reducing the cost of understanding in complex technical environments.
Thanks for visiting my site. I created it for you.
How I Work
Most of the complex systems I've worked on share the same root problem: the system works, but people can't reason about it. Teams talk past each other because they're operating from different mental models, unclear dependencies, and fragmented context.
I step into that gap. I map how the parts interact, define shared language, and design the experience layer that makes the system legible to everyone who depends on it — engineers, operators, product teams, leadership.
This usually means I'm operating upstream of interface design: framing the problem, modeling the domain, establishing the semantic foundations that make the UI decisions downstream almost obvious. I prototype in code, validate through conversation, and design for expert users who value precision over polish
Selected work
(1)
Available for work
Product Design Leader
Based in Chicago, IL
Since 2013
© 2026