Product direction
Define the user problem, the product boundary, and the decisions teams need before building.
Product framing / Roadmap decisionsConnected, made clear.
I work across connected devices, apps, cloud, onboarding, and support. My job is to make setup clear and recovery possible when something goes wrong.
Selected work
Professional product work, live products, and tools I have built myself.
Professional work
Connected Climate
Product leadership across a connected climate system.
Published product
Stratum
A published Pebble watchface for time, Bitcoin data, weather, and device status.
Live product
Brio Builder
A live family website for finding, sharing, and moderating BRIO Builder creations.
Open-source developer tool
Pebble Watchface Skill
An open-source Codex skill that builds a Pebble watchface from a written brief and checks it in the emulator.
Most connected-product problems happen at the handoffs.
A device can work, the app can work, and the cloud can work - and setup can still fail. I focus on those handoffs and on the teams that own them.
How I workOnboarding and recovery
Design setup, system states, failure messages, and recovery paths across the device and app.
Setup flows / State and error mapsSupport and automation
Decide what people can solve themselves, what automation can handle, and when a person needs to take over.
Support journeys / Virtual agent scopePrivacy and compliance
Make data collection, consent, retention, and user controls part of the product design from the start.
Data maps / Consent wordingLatest note
Notes on product work, connected technology, privacy, and open protocols.
A portable website with Nostr at the edges
How Jelm treats the website as the canonical home while using Nostr and Blossom for identity, syndication, and media durability.
Read noteI'm open to the right product leadership role.
I'm interested in work across connected devices, mobile onboarding, support, and applied AI.