Product thinking and strategy

• PROBLEM

Users struggled to set proof requirements that worked for all skill levels within the same club

Uniform tasks were often too easy for advanced users or too hard for beginners, making it difficult to keep everyone engaged and on track.

🪷

75 Hard Club

"Some wanted to do two workouts a day, while others only had time for one. We set the requirement to one workout to ensure those with less time wouldn't fail."

- Tommy, Student

🏋️‍♂️

Push-up Club

"The number of pushups we set was too easy for the guys to improve and too difficult for the girls to complete."

- Whitney, Production Agency

CHALLENGE

How might we help users set goals that match their skill level while staying accountable and connected to their community?

• RESEARCH

Key insights from analyzing leading habit building and social platforms

What worked

Gamification drives consistency

Progress streaks, XP, and badges encourage users to return daily

Community boosts accountability

Social features like groups, feeds, and challenge invites motivate users to stay engaged

Flexible structure fits many goals

Custom templates, goal tracking, and modular features appeal to diverse user types

What didn't

Cluttered or overwhelming UIs

Some platforms prioritize too many features at one, creating friction for goal tracking

Lack of group first design

Many tools are optimized for individuals, not groups, limiting social accountability

Customization and moderation gaps

Limited control over group settings and accountability tools weakens long term use

Image

A comparative analysis of Facebook, Duolingo, Notion, Strava, and Nike Run Club to identify overlooked opportunities

• EXPLORATION

Testing possible product solutions to balance flexibility and structure

Introducing

Club Challenges

Why limit a club to one goal? We restructured clubs to support multiple challenges, allowing users with different goals and skill levels to participate together.

Designing the challenge creation feature

• PAIN POINT DISCOVERY

I started by auditing the original club flow to decide what the challenge creation flow should keep or drop

An illustration from Carlos Gomes Cabral
An illustration from Carlos Gomes Cabral
An illustration from Carlos Gomes Cabral

01.

Lengthy and overwhelming process

The 37 screen setup was cluttered with many required fields, making the process feel more like paperwork than creating something fun.

02.

Confusing input sections

03.

Complex date selection

01.

Lengthy and overwhelming process

The 37 screen setup was cluttered with many required fields, making the process feel more like paperwork than creating something fun.

02.

Confusing input sections

03.

Complex date selection

An illustration from Carlos Gomes Cabral
An illustration from Carlos Gomes Cabral
An illustration from Carlos Gomes Cabral

01.

Lengthy and overwhelming process

The 37 screen setup was cluttered with many required fields, making the process feel more like paperwork than creating something fun.

02.

Confusing input sections

03.

Complex date selection

• GOALS

Pain points guided these three core design goals

01

Reduce cognitive load

Simplify the flow so users can create challenges without feeling overwhelmed

02

Design for clarity

Make navigation and field organization intuitive and easy to follow

03

Support personalization

Let users tailor challenges to fit their goals and preferences

02

Design for clarity

Make navigation and field organization intuitive and easy to follow

03

Support personalization

Let users tailor challenges to fit their goals and preferences

Feedback turned into priorities for future iterations

01

Simplify the experience

The flow still felt long and made users feel rushed to finish everything at once.

02

Clarify the structure

Users weren't sure where to start or what steps to follow.

03

Reduce friction in inputs

Some fields were confusing and slowed users down.

• IMPLEMENTATION

Turning scope into structure and specs

To keep design and development aligned, I broke early product ideas into modular specs that could evolve. I mapped out clear requirements in JIRA and shaped the end-to-end flow in FigJam, helping the dev team move quickly under tight time constraints.

With structure in place, the dev team could build, test, and iterate confidently, even while design was still in motion.

Image

Documented requirements in JIRA for dev handoff.

Image

Translated JIRA specs into a flow in FigJam.

Image

• FIRST ITERATION

First version I shared with the team

Combined start and end dates into one screen with clearer visuals so users could easily distinguish them. Simplified inputs and added info buttons to reduce confusion and make the flow quicker to complete.

Image

Early iteration focusing on simplifying date selection and proof setup for easier onboarding.

Feedback turned into priorities for future iterations

01

Simplify the experience

The flow still felt long and made users feel rushed to finish everything at once.

02

Clarify the structure

Users weren’t sure where to start or what steps to follow.

03

Reduce friction in inputs

Some fields were confusing and slowed users down.

01

Simplify the experience

The flow still felt long and made users feel rushed to finish everything at once.

02

Clarify the structure

Users weren't sure where to start or what steps to follow.

03

Reduce friction in inputs

Some fields were confusing and slowed users down.

Final design

• IMPACT

Redesign results that spoke for themselves

Within 3 months of rolling out challenges:

46%

Challenge completion rate

More users successfully started and finished their challenges

8 to 60

Growth in active clubs

Active clubs grew 7.5x within the first 3 months

Get in touch
Get in touch
Get in touch