From changing ideas to 77+ delivered screens

Role: Product Designer (2-designer team)

Timeline: 4 Weeks

Responsibilities: UX Research, User Flows, Wireframing, UI Design, Design System, Dev Handoff

Outcome: Structured a growing, shifting scope around one core idea, and shipped 77+ connected screens

CrickRoo turns a phone camera into a cricket training tool. Record a session, get individual deliveries broken down into clips and insights, revisit them later. Most tools in this space need dedicated cameras or specialised setups. CrickRoo just needed the phone already in your pocket.

We joined the project midway as a 2-designer team after earlier concepts weren't meeting client expectations. The product lacked a clear direction, requirements continued evolving, and the team needed to rebuild confidence

Limited references - Cricket analytics interfaces had very few mobile examples

Frequent requirement changes - Features evolved continuously during design exploration

High iteration pressure - 3 core flows required 3-4 redesign cycles before final alignment

After reviewing PRD, existing designs & client meet, 4 insights came out as dark theme, modern UI, minimal layout & a dialogue. “Feel you are a cricket player playing in a stadium & your stats are on a TV” So, we created onboarding 1st drafts that made the client stay

Existing cricket analytics UI often felt gamified, so we converted TV broadcast graph to mobile, which added the familiarity.

Recreated TV broadcast graphs to make cricket analytics instantly familiar

Added session duplication flow to reduce repetitive setup effort by 40%

Reduced onboarding friction by merging inputs & cutting steps from 7 → 5

Introduced reel-inspired session analysis flow for faster content consumption

77+ screens delivered with dev handoff and design system

Product overall structure held together despite scope growing well past its original brief

Client conversations shifted from fixing flows to discussing what's next

This project changed how I think about scope that won't sit still. When requirements keep shifting, designing faster isn't the fix. Finding the structure underneath them is.

Somewhere along the way, the conversations stopped being about revising flows and started being about what to build next.