AI & Emerging Interfaces
AI products earn trust the same way governed platforms do: by showing their reasoning. Most of my AI work applies an old discipline to a new material, making system logic legible to the people who act on it.
- Conversational UI
- Computer Vision
- Explainability
- AI Prototyping
How I work here
The explainability instinct predates the current wave. The real estate platform's compatibility score exists because brokers could not defend a shortlist they could not explain; search stopped being a filter and became an argument.
The applied record: a customizable chat interface for AI-driven support agents spanning text, voice, and video workflows (2024); computer-vision UX patterns developed with engineering and validated in usability pilots (2022); an AI-assisted diagnostic product supporting earlier skin-cancer recognition (2021).
AI is also a working tool. AI-assisted interactive prototypes now carry the stakeholder validation that static specs used to lose, ending debates rather than extending them.
Trust is designed, not assumed
AI features fail socially before they fail technically: people stop using what they cannot predict or challenge. So the core surfaces are the explanatory ones: what the system concluded, how confident it is, what evidence it used, how a person overrides it. A visible, defensible score turns output from a verdict into an argument a professional can take responsibility for.
Uncertainty gets designed with the same care as success: calibrated language for each confidence band, empty and error states that say what the system did not know, and escalation to a human that does not read as failure. Every failure state is specified with the same rigor as the happy path: what the system says, what it exposes about why, and what the person can do next.
Conversation is one interface, not the interface
Chat is the right surface when intent is genuinely open-ended, and the wrong one when a form, a table, or a button would answer faster. Across text, voice, and video, the design work is conversational structure: turns, memory, interruption, repair, and the handoff between modalities and to humans.
The rest is choreography with the surrounding product: where an assistant may act on someone's behalf, where it must show its work first, and how its actions land in the same audit trail as everything else.
Building with AI in the loop
AI has changed how the argument gets made, not just what gets designed. Working prototypes, increasingly AI-assisted, settle in days what static specs debate for weeks; stakeholders react to behavior, not promises. The same loop evaluates AI features themselves: prototype the behavior, test it against real cases, and let the observed failure modes design the guardrails.
None of this suspends the evidence rules. AI features get instrumented, tested with users, and labeled by how their outcomes were established, exactly like everything else.
What this covers
- Explainable scoring and confidence display
- Uncertainty, error, and fallback states
- Human override and escalation paths
- Conversational structure across text, voice, and video
- Modality choice: when chat is the wrong answer
- Computer-vision-assisted interaction patterns
- AI-assisted prototyping practice
- Instrumented evaluation of AI features
The work behind it
Enterprise Real Estate Management System
Explainable search: a visible compatibility score brokers could defend in front of clients.Case study →
Conversational AI Interface
Chat interface for AI support agents across text, voice, and video generation workflows (2024, archive).
Computer-Vision UX Toolkit
CV-assisted UX patterns developed with engineering, validated in usability pilots (2022, archive).
Questions, briefly
- What makes an AI product feel trustworthy?
- Predictability and recourse. Show what the system concluded and with what confidence, make the evidence inspectable, and give people an override that leaves a trace. Trust follows from the ability to challenge the machine, not from the machine being right.
- Is chat the right interface for AI features?
- Sometimes. Chat suits open-ended intent; it is slower than a form for structured tasks and worse than a table for comparison. The real design decision is modality choice, and the honest answer is often a conventional interface with AI behind it rather than in front of it.
- How do you design for a model that keeps changing?
- Design the contract, not the snapshot: the confidence display, the failure states, the override, the audit trail. Those surfaces stay stable while the model improves underneath, and they are what determine whether users forgive the model's bad days.
Elsewhere on this site
If this is the territory your product lives in, the case studies carry the detail and the contact page carries the practical part: roles, embedded engagements, and where to start.
Other areas
- Enterprise Platforms & Complex UXOperational software at organizational scale.
- Design SystemsTokenized foundations that survive their second year.
- Product Strategy & AccelerationFrom ambiguous mandate to shipped product.
- Design OperationsThe structure that lets design teams deliver.
- Gaming & Interactive DesignProducts where feel is the product.