The work, in one line
Making computer-vision workflows legible — for users, teams, and the market.
Clearer workflows across data, training, deployment, and monitoring.
Personas, workshops, and shared language for priorities and product direction.
Launch storytelling, demos, releases, and campaign assets that made the product easier to understand.
01 Four connected layers
- 01
Product understanding
Personas, workflows, team structures, and opportunity framing.
- 02
Product experience
Interfaces for data, training, deployment, monitoring, and live model behavior.
- 03
Team alignment
Workshops and facilitation to clarify priorities and turn ambiguity into direction.
- 04
Product storytelling
Launch videos, releases, decks, demos, and campaign assets that helped explain the product.
02 The product was a workflow system
A learning loop, not a linear flow
Not a single interface. Users move through a loop — prepare data, train models, deploy and monitor them, then feed real-world signal back into the data. My work helped make that loop easier to understand, design, and discuss.
DataCollect · Upload · Annotate · Review
TrainConfigure · Run · Compare · Stop / retry
Deploy & monitorDeploy · Observe · Detect issues · Improve03 From ambiguity to direction
A persona & workflow framework
The goal was not to document personas. It was to give the team a shared language for product priorities — workflow archetypes, from individuals to enterprise teams, that the product had to serve.
04 Designing the core workflows
Helping users prepare better datasets.
Collect, upload, annotate, and review data — with AI-assisted and manual workflows designed as part of one quality loop.

Making model training observable and actionable.
Users need to see what is running, compare performance, and stop experiments before they waste time and compute.

Closing the loop between real-world behavior and the next decision.
Once a model is live, teams need to read performance, detect issues, and turn those signals back into better data and better models.

The design challenge was to make each stage visible enough for the next decision.
05 Post-launch workflow audit
Closing the feedback loop
After launch I audited the live workflows end to end — where users stalled, where the loop leaked — and turned the findings back into data, training, and monitoring decisions.

06 Explaining the product outside the interface
A complex AI product has to be understood in more places than the UI.
Launches, demos, release notes, growth campaigns, and company milestones all had to explain the same product logic clearly.







07 What changed
Connected product areas
Data, training, deployment, and monitoring became easier to discuss as one workflow loop.
Clearer backlog and priorities
Workshop outputs and workflow audit findings were translated into structured follow-up work in Linear.
Better product communication
Launch, release, and growth materials explained complex AI capabilities in a more consistent product language.
Stronger decision-making
Personas, workflow maps, and audit artifacts helped the team align around where to focus next.
08 Reflection
Product design in AI is often about making invisible systems discussable: model behavior, user maturity, team workflows, constraints, and the story around the product.
The most useful artifacts were not always the prettiest ones. They were the ones that helped the team make a better decision.
Working on a product with this kind of complexity?


