Goals · Toggl 2.0 · Web app

From design handoff to staging in 2 working days.

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.

Process

One feature. Designed, built and tested before production.

The locked chapters

Some of the best parts aren’t public.

The full studies include deeper research, decisions, and outcomes from the work. One password opens all of them.

Ask me for a password via email or LinkedIn — also happy to walk you through them live!

More case studies

Case studyThe pattern that outlived my involvementProduct design · originator, then advisor

Case studyThe timesheet kept getting more complicated. The interface didn't have to.Product design · continuous ownership

Case studyFrom browsing to bookingWeb design · hospitality

In short

Process

01Don’t copy the feature. Understand it first.Research before rebuilding.

02Make progress obvious and Goals worth returning to.Turn tracked time into visible progress.

03The prototype became the handoff.Use code to reduce ambiguity between design and engineering.

00The hard part wasn’t designing the badge. It was defining when it was true.That exploration exposed a deeper problem: the product needed a state model.

00Sixteen days from handoff to everyone.Handoff on a Wednesday, the first slice on staging by Friday, feature-complete a week later, released to everyone on 24 July.

04We built for retention. Users showed us activation.Goals became an early activation signal — and the data showed us where discoverability still fell short.