Vsync Redesign
2024 · Product Designer
Interfaces fail people when they hide intent behind chrome.
- Problem
- Vsync's scheduling flow buried the one action users actually came for under three layers of navigation and inconsistent affordances.
- Outcome
- A restructured flow and a small token-driven design system cut the primary task from nine taps to three.
Why this project
I started by asking why interfaces fail people. Vsync was a clear case: a tool people relied on daily, slowed down by accumulated UI debt.
What I did
- Audited the existing flows and mapped every step of the core scheduling task.
- Rebuilt the information hierarchy around a single primary action per screen.
- Introduced a minimal token-driven design system (spacing, type, color) so the team could ship consistent screens without re-deciding the basics each time.
Outcome
The redesigned primary task dropped from nine taps to three. More importantly, the design system gave the team a shared vocabulary — future screens started consistent instead of being made consistent later.
Placeholder case study. Replace this prose, the cover image, and metadata with the real project.
Discussion