Product direction
Define the user problem, the product boundary, and the decisions teams need before building.
- Product framing
- Roadmap decisions
- Requirements
- Stakeholder alignment
How I work.
I help teams make connected products easier to ship and support. My work usually starts where ownership is split across hardware, firmware, cloud, mobile, operations, and support.
Device App Cloud Support
Onboarding and recovery
Design setup, system states, failure messages, and recovery paths across the device and app.
- Setup flows
- State and error maps
- Recovery paths
- System behavior
Support and automation
Decide what people can solve themselves, what automation can handle, and when a person needs to take over.
- Support journeys
- Virtual agent scope
- Knowledge structure
- Escalation rules
Privacy and compliance
Make data collection, consent, retention, and user controls part of the product design from the start.
- Data maps
- Consent wording
- Retention decisions
- GDPR and EU Data Act requirements
Start with a specific problem
It might be an onboarding flow that loses people, a device state that is hard to explain, or a support journey with no clear owner.
I map the problem across the systems and teams involved, then identify the decisions needed to move forward.
I leave the team with something concrete: a requirement, journey, decision, prototype, or a clear definition of the next release.