Reimagining the experience for 300,000+ real estate agents.
A 16-week discovery with a team of five researchers surfaced 126 pain points and 35 service gaps, then got stakeholders to agree on an MVP focused on onboarding.
Today I lead a three-person design team at a retail software company, and I design hands-on alongside them. I also co-founded Atelos, a desktop AI app. I ran its research, designed it, and wrote its front end.
How I work
Every case on this site follows the same six steps. This is Atelos, from the first desk study to the screen that shipped in November. Pick a step, or use the arrows.
I started with ten desk studies on why people abandon tools like Obsidian and Notion AI, plus an interview. Then I synthesized all of it into the jobs founders actually hire a knowledge tool to do.
Three personas around those jobs, plus anti-personas: the people we chose not to build for. That’s scope discipline. This is Sam’s journey, one of three, from first launch to day 90.

I worked the home screen through a dozen versions. v12 is the build I put in front of testers: tasks, files and chats split into tabs, and the briefing grouped by what needs attention. Here are v2, v4 and v12.
v2v4v12
I prototype in HTML, not static frames, so a tester can click a skill, open a file, and react to something real. For Quick Capture I built four entry paths side by side under one rule: see it, click it, done.

I moderated four sessions across the personas. On 10 April, none of the first three participants could find their way without help, and two of them never noticed the skills strip at all.
First run became a conversation, Teach Atelos, that builds your context one topic at a time instead of asking for a folder. The skills strip got a label, and the unsorted pile became a plain Inbox. I wrote that front end myself.

Selected work
Each one runs the same loop. Two are from my current role, so they need a password. Their outcomes are here in the open.
Concept to an MVP in early users’ hands in about two months. Usability testing broke my onboarding, and I rewrote it the next day.
My role: co-founder. All the research and design, plus the React and Electron front end.

One white-label storefront that has to work for a gas station, a restaurant and a large grocery chain. I designed five areas of it myself, from retailer research to prototype, and we showed it to retailers at our customer conference.
My role: hands-on designer for five areas, and lead on two more.
I designed and built a multi-agent research platform in six weeks. Its lead agent turned 26 hours of synthesis into 33 minutes. Then the beta showed users skipping the thinking, so I stopped.
My role: solo founder. Design, build, billing and onboarding.

I rebuilt my team’s process around AI, so every spec traces back to the brief that started it. Then I measured what it changed on a live redesign.
My role: design lead. I built the pipeline and the measurement.
Ten-plus teams disagreed on what problem they were solving. I ran the research and turned it into nine service blueprints, covering 150+ touchpoints, that got them to agree.
My role: principal design lead for a working group of eight designers and researchers.

Reviewing my application? The password is in my email to you. If it isn’t, ask me for it.
Leadership
I lead by making alongside my team and by going to bat for them. The best evidence isn’t mine to give. It’s what they say, and that they stay.
Designers on the team I lead today, and I still design alongside them.
Retention of the five designers I led at Kroger over three years, through a restructuring.
Tracks in the progression framework I wrote, so a promotion was a plan, not a guess.
He gave me opportunities to practice team leadership, trusting me to guide projects and coach peers. He brought in frameworks and tools for growth that went far beyond the typical KPIs. It made me want to take ownership of my career in a way no other leader had inspired before.
Dmitri leads with a calm, steady presence that gives his team the confidence to take risks and grow. He invests deeply in coaching, and balances empathy with high expectations. Under his leadership, a young team quickly matured and began delivering at a higher level.
Experience operations
A research and design organization had high attrition and inconsistent delivery. I journey-mapped our own onboarding, read the exit interviews, and found the systemic gaps: process, role clarity, project scoping. Then I led a cross-functional team to build the fix, a Center of Enablement with reusable templates, agile training and modular planning tools.
Before that
Shorter versions, same instinct: find the problem underneath, then build the thing that fixes it for everyone.
A 16-week discovery with a team of five researchers surfaced 126 pain points and 35 service gaps, then got stakeholders to agree on an MVP focused on onboarding.
Three workshops for 30 participants: what generative AI is, where it actually helps, and an ethical roadmap for using it in the design process. The groundwork for everything I’ve built since.
Hands-on product and scrum leadership on an at-risk data migration, plus a reusable process library. Outcome: better velocity, an approved authority to operate, and a playbook now used across the organization.
Writing
A working record of design and product as AI changes it. Partial thoughts, things that failed, and what I would do differently.

Fact-checking a post about my own work turned up a detail I had completely forgotten.

Automated design checks look at one screen at a time. The errors that survive live between screens.

The expensive part of metered AI isn’t the bill. It’s what people quietly stop trying.
Contact
I’m looking for Staff and design-lead roles on AI-native products, where design ships and I keep my hands on the work. Remote from St. Augustine, Florida (ET).