Product strategy
Clarify what a product should do, who it is for, and how the technical pieces need to line up.
- Product framing
- Roadmap shape
- Decision records
- Partner-ready requirements
Useful help where products get complicated.
Clear decisions and practical artifacts for connected products, onboarding, support, and privacy.
Ways to work together
Connected-device UX
Improve the parts where hardware, firmware, cloud, app, setup, and support meet the user.
- Setup flows
- Failure states
- Recovery paths
- Cross-stack behavior maps
Support automation
Design self-service and AI-assisted support flows that reduce effort without hiding accountability.
- Support journeys
- Virtual agent scope
- Knowledge structure
- Escalation rules
Privacy-first services
Shape products around data minimization, clear consent, and user-respecting defaults.
- Data maps
- Consent language
- Retention decisions
- EU-ready product notes
Start with the question
Most work starts with a narrow question: an onboarding flow that loses people, a support experience that needs structure, a device behavior that is hard to explain, or a product direction that needs sharper trade-offs.
The output should be something your team can use: a map, a decision, a product brief, a prototype, or a clearer path through the next build.
I am not trying to sell a heavy process. The point is to reduce ambiguity and make the next product decision easier to defend.