- Product design
- Information architecture
- Data visualisation
obseed, every device’s data, made readable.
Athletes are split across devices. Oura reads sleep best, Garmin nails activities, others are solid everywhere. obseed aggregates all of it into one platform: every metric in detail, performance compared over time, and their own algorithm to correct the misreadings devices make on their own. The design: layered depth, drill down not dumb down.
The work
The dashboard, on the phone
The dashboard, on the desk
The calendar week
The chart configurator
A metric in statistics
The file behind it
Decisions, wireframes, flows, and every screen.
The motion specification with its timing table, the grid and colour foundations, the component library, and every screen at both desk widths and on the device. It relates to client work, so the file is password protected.
Open the Figma fileOverview
One home for every device’s data.
Serious athletes own several devices, each best at something different, and each platform shows the same run or night’s sleep its own way and at its own depth. obseed aggregates all of it in one place, so it can be read in full and compared over time. Their own algorithm streamlines the data and corrects the misreadings devices make on their own.
The brief was one line, for an early stage team with no roadmap or sprint cadence yet.
The problem
Scattered data, and an open brief.
We interviewed triathletes and turned what they said into the brief. Two things pulled at once.
Split across devices
Oura for sleep, Garmin for activities, another solid everywhere and great at nothing. Each platform shows the same data its own way, at its own depth.
An open brief
One line, and a young team. Open enough to sprawl into an endless build, so the first job was deciding what the product needed to be.
My part
From an open brief to a system.
Set the brief with users
Ran the triathlete interviews and turned what they said into the brief, so every surface traces to a real need rather than a guess.
Designed across the product
The athlete facing surfaces and the drill down that ties them, in one vocabulary, so a click down reads as a depth change and not a navigation change.
Designed the public site
obseed’s own site in the same visual language as the product, one voice from landing page to dashboard.
Shipped it with the founder
The CEO and CTO is one person and writes the code. Direction went straight into the live build, no formal handoff.
The approach
Layered depth, not a dumbed down summary.
One number at a glance, three with effort, the full multi axis series on click. The same vocabulary across every surface, so going deeper reads as a depth change and not a different app. Athletes who own four devices are not asking to be protected from their own data.
One visual rule underneath: a dot is a day, or a dot is one countable unit. The metric decides which, never the screen.
Impact
What it added up to.
Shipped
The analytics surface shipped
Built from the interviews that set the brief, and shipped to the team with the drill down that ties the surfaces together.
Shipped with the founder
Pain points fixed in the live product
Design direction turned straight into shipped code, and an open one line brief became the team’s first roadmap and sprint cadence.
Not shipped
The 2026 pass is mine
The redesign here came after the mandate ended. The metrics are obseed’s, the redesign is not theirs to answer for.