I didn’t prototype the screens. I prototyped the product.

I took Goals from research to a complete, working experience in code — exploring behaviour, states and edge cases before development. The prototype became the team’s reference for how the feature should work.

from handoff to the first build on staging
2 working days
whole experience, not a sketch
6,266 lines in prototype
working reference the team built from
47 commits to prototype
in the first 7 weeks
Locked figure goals created

Role

Sole product designer

Timeline

5 weeks Released 24 Jul 2026

Team

Product manager Front-end engineer Back-end engineer Tech lead

Scope

Research → UX → UI → coded prototype

In short

The brief
Bring Goals to Toggl 2.0 for solo users — a parity feature for Track users and a way to keep intended time front-of-mind while tracking.
What I designed
A new goal creation flow, progress and pace indicators, state badges, a Goals page with statistics, and a clearer empty state.
The approach
I explored the experience in the real codebase, using Storybook and prompt coding to test behaviour and edge cases before production.
What changed
Goals shipped 16 days after handoff and reached general availability in July 2026. The post-launch data reframed Goals as an early activation signal.

What shipped

Progress you can read at a glance, from setting a goal to reaching it.

Process

One feature. Designed, built and tested before production.

$Three rows of the old Goals panel: a ring and a fraction each$ 01 —ResearchOld Goals + user testing
03 —BuildStorybook variants + full coded prototype
05 —ShipPRs → staging → beta → QA → GA