sansserif.

← Back to recent work

Health data, told as a story.

Building the foundations of a young Swiss health-data platform: the athlete-side analytics surface, end to end. An open, one-line brief, scoped into the team's first roadmap and sprint cadence.

Engagement
obseed
Focus
Product, IA, data viz
Cadence
Roadmap & sprints introduced

The problem

Serious athletes don’t want a summary number, they want to read their data: heart rate against elevation against breathing rate at minute 02:23 of last Tuesday’s run; muscle mass by week across six months.

The brief was one line, “build the analytics,” for a young team with no roadmap or sprint cadence yet. The pipe in: Garmin and other wearables, sleep, RHR, HRV, body composition, GPS-traced runs. The surface to build: dashboard, body-composition statistics, the activity detail (route map, summary, multi-axis charts), and the calendar that ties planned training to recorded sessions.

The call

Layered depth over a dumbed-down summary: one number at a glance, three numbers with effort, the full multi-axis correlation on click. And one design vocabulary across all four surfaces, so a click down reads as a depth change, not a navigation change. The open mandate was scoped into a roadmap and sprint cadence rather than an open-ended build.

Progressive disclosure, one screen

At a glance Health Index 78↗ +3 One number, the headline state.
With effort Three vitals HRV, resting heart rate and sleep, each with its sparkline.
On click Full series The annotated 14-day trend, for users who want it.

Three layers, one screen. Headline state, contributing metrics, full annotated series, surfaced on demand, not by default.

Four surfaces, one drill-down

The athlete moves through four surfaces depending on what they're asking. Dashboard for the daily check-in, Health Index, three vital signs, an AI-generated read on the trend. Statistik for the long view, a single body metric (muscle mass, body water, RHR) plotted by week with min / max / average framing. Aktivität for a single session, route map, summary card, the option to tag, review and break down. Charts for the post-mortem, heart rate against elevation against breathing rate, primary and secondary Y-axes configurable, combined mode on by default. The same components, spacing and metric definitions follow the user down through every level.

One drill-down, one design vocabulary across all four

Daily check-in Dashboard Health Index, three vitals, an AI read.
Long view Statistik One body metric, grouped by week.
Single session Aktivität Route map, summary, review and tag.
Post-mortem Charts Heart rate against elevation against breathing, axes configurable.

Four levels of depth, from the daily check-in to a per-minute read of a single run. A click between levels is a depth change, not a navigation change.

Outcome

The analytics surface shipped, and the team now runs on the roadmap, backlog and release rhythm the mandate introduced, the structural layer that doesn't show up in screens but decides whether the visible work ships.

The bet: serious users reward depth on demand over simplification. Drill-down, not dumb-down.

The call, made tangible

Sequential, or all at once?

Design
Development
Marketing

Three phases, end to end. Every track waits for the last.

Left to default, a young team works in bursts: design finishes, then development starts, then marketing picks it up. I set the roadmap and sprints so the three ran at once, with no dependency blocking another track.

← Back to recent work

Currently available.

Product management, business analysis and customer experience across regulated banking, fintech and B2B.

Let’s talk