Core Circle | Increasing Retention Rates With Social Gamification

Core Circle had a real problem. The app helped friends and families stay accountable by sharing fitness progress. The first three weeks? Engagement was strong. After that? People disappeared.

The company's hypothesis was simple: add messaging. More communication means stronger accountability, which means people stick around. But here's the thing, adding a feature doesn't fix a behavior problem. I needed to understand what was actually causing people to delete the app in the first place.

Since this was a hypothetical product, I did not have access to real user data to investigate the cause of user drop off. I had two possible explanations for the drop-off: either the app had limitations that deterred users, or users were struggling to maintain fitness routines in real life and the app couldn't save them.

To explore these possibilities, I planned to conduct secondary research and a competitive analysis. That's where I found the connection point: habit formation. Consistent fitness journeys are built on habitual routine. Repeat app usage is built on habitual communication. These findings validated that messaging could work, but its success depended on how interactions were structured rather than simply adding communication tools.

Here's what I discovered: Long-term workout habits form when users have a clear purpose, choose activities they actually enjoy, create realistic routines, and consistently track progress. I also found out what breaks people’s routines: unrealistic workouts, missed workouts, competing responsibilities, and the shame that comes with not sticking to a plan.

And accountability relationships? They can support habit formation, but only if expectations are clearly defined and flexible. If they're rigid, they create pressure. Pressure leads to drop-off.

I confirmed the most likely reason for drop off was that users couldn't follow through on their set routine. This directly informed the design direction: if a routine doesn't work, don't quit. Just change it up. Flexibility needs to be embedded into the entire experience so that users can easily adjust routines and expectations, personally and socially, without feeling like they've failed.

When examining competitors, I observed how they approached engagement. I noticed something consistent: they all emphasize performance metrics and data tracking. Those features work for seasoned fitness junkies. But for people struggling with consistency? It feels overwhelming and discouraging. Core Circle has an edge: focus on workout frequency instead of workout intensity.

I mapped each stage of fitness habit formation and identified three critical moments:

1. Creating a fitness plan (Define purpose, choose an enjoyable activity, and create a realistic routine)
2. Logging workouts (Consistently track progress)
3. Messaging accountability group (Cue and reinforce habit loop)

These became my three red routes: Onboarding, Logging a Workout, Forming Your Fitness Circle.

While the original brand direction emphasized humor, research indicated that users valued trustworthiness, authenticity, and friendliness. I developed the style guide with the intention of being warm and supportive; feel earthy, yet energetic. The tone needed to feel grounded in progress, not performance, but still motivating enough to keep people coming back.

I conducted two rounds of moderated usability tests. Eight tests total. Four in person, four remote due to scheduling constraints.

My participants ranged: six worked out consistently, one inconsistently, one wanted to but lacked motivation. I needed perspectives from different fitness levels.

Tests focused on onboarding, logging workouts, creating a fitness circle, and sharing workouts. After each round, I compiled a usability report and prioritized issues by severity.

Here's what worked: Users loved the non-competitive social experience. They cited the Circle Mojo feature as something fun they'd want to do with friends. They valued the customization and flexibility when logging workouts. They appreciated that the app wasn't bloated with metrics.

Here's what didn't: Users said they wouldn't manually log workouts. They wanted automated methods. They also wanted prewritten "why" statements to choose from instead of writing their own. And they asked about weight tracking and weigh-in reminders.

1 / 3

If this project moved forward, here's what I would do next:

First: Automated workout syncing. Build out features such as scanning or syncing workout routines.

Second: Onboarding tweaks. Replace the open text "why" input with structured selection options. Introduce optional weigh-in reminders during onboarding.

For the above changes I'd conduct usability tests again to see if these changes actually reduced friction and improved consistency.

Third: Simulated screens. Build prototypes that simulate how screens would look after weeks of repeat usage showing streaks, trophies, workout counts, workout re-entry, and notifications.

I'd use concept testing to ensure these features felt motivating rather than overwhelming, and whether they'd encourage people to return.

When I designed the "Log a Workout" flow, I made a strategic decision: test the worst case scenario. Most fitness apps focus on cardio like walking, running, biking. But that's easy to log. Duration, distance, incline. Done.

The real friction is strength training and other activities people actually do but can't easily log. Popular fitness devices recognize movement, but don't actually recognize and note each specific exercise taking place. So I had users manually enter workouts to see the true hang ups.

It worked. Users told me exactly what I needed to hear: they didn't want to manually log workouts! They all had fitness devices and were accustomed to automated logging.

What I should have done: instead of testing manual entry, I should have built and tested the scan feature. The idea is users can upload a photo of a workout plan, have the information scanned, and then automatically logged into the app. I let the logic of testing "worst case" override the logic of testing what users actually needed. If I could redo this, I'd build the scan feature and validate it with users.

On testing: I conducted eight tests across two rounds. Industry standard is fifteen across three rounds. If I could redo it, I'd test five in round two and five in round three instead. More people, more confidence in the findings.

Finally, this was a theoretical project, so I couldn't actually measure whether retention improved. But if I had real user data, I would have conducted a cohort analysis comparing user behavior before and after the redesign. I'd monitor KPIs like workout consistency, messaging activity, and routine adjustments to see if users were actually returning through that Week Three drop-off period and building habits instead of losing momentum.