Design taught me how to think.
That's not really a career story. It's the reason I trust the pattern enough to build proof of a discipline that doesn't have a settled name yet, instead of waiting for someone else to name it first.
Most of what convinced me isn't secondhand. A decade of UX and digital transformation inside a large retail business turned, gradually, into building AI workflows and operational systems for it. More recently I built Signal & Flow, a live multi-agent AI platform, to run competitor analysis and behavioural research using synthetic customer personas. Across all of it, I keep watching the same thing happen: hand a model a task without curating what it needs to know, and the output comes back confidently wrong or blandly generic. It usually isn't the model. It's what the model was given to work with.
That's why the three interactive demos on the Work page exist. The same task, the same model, three levels of curation, three completely different outputs, side by side. Once you can see the gap, you don't need me to argue for it.
None of this has a settled job title yet, and I've written more on why that's true — and why it doesn't matter — in The Job That Doesn't Have a Name Yet. What I can say here is simpler: I trust the pattern enough to spend the next stretch of my career building proof of it, rather than waiting for a title to catch up.
For grounding: my background is in design and UX — typography, broadcast motion design, illustration — with the last decade spent on digital transformation and AI workflows inside a large retail business, plus building Signal & Flow more recently.
If you'd rather see this than read about it, start with the Work page.