Zero-to-One Calling Experience for Android Phones

How I turn an ambiguous brief into testable design directions

• Structure before design - Built a framework and principles that became shared references across the team
• Motion as design argument - Animation prototypes changed a skeptical PM's mind
• North star with approachable steps - Visionary direction while delivering practical baseline for quick shipment

This project is under NDA and exact details are Google-internal only. I can't share the problem, solution, or specific outcomes publicly. What I can share is how I work: how I structure thinking, make design decisions, and use craft to move a team forward.

Mapped the product space, then ran two tracks: a shippable baseline and a visionary north star.

Map the system first

Before designing the feature, I mapped the entire product space it sits in by categorizing scenarios by user state and context. This framework showed where the feature fits, what it touches, and what constraints it inherits. The team adopted it as their shared reference.

North star first, then a path to get there

• Visionary north star - How can we maximize this moment? Research showed Gen Z and Gen Alpha value expressivity and emotional connection. This direction explored how far the feature could go: creating something people enjoy beyond solving just the problem.
• Baseline UX - Work backward from the north star to a solution that solves the core need efficiently while preserving engineering velocity.