Stride

The gym partner you never had, for any goal in your life.

Overview

Most accountability tools are built for the individual. Stride is built for the pair. It matches users with someone on the same personal goal, fitness, learning, wellness, career, and ties their daily check-ins into a shared streak so both people have skin in the game.

The core behavioural insight: people show up differently when someone else is counting on them. Stride is built entirely around that psychology, not as a feature, but as the product contract.

Tech

Figma for all design, prototyping, and handoff. Stride is a product concept and UX system, the deliverable is the design, not an engineering build.

Solution

Shared streak

Both users' streaks reset if either person misses. That mutual skin-in-the-game isn't just a feature, it's the entire behavioural contract. It makes absence feel like letting someone down, not failing yourself.

Person-first home

The buddy's name and photo fill the screen. Three full redesigns to get here, I kept building utility dashboards before realising the relationship is the product. Once the screen treated it like one, everything else fell into place.

Did [name] show up?

The check-in screen asks one question: 'Did [name] show up today?' Not 'log your check-in'. That language shift makes accountability interpersonal rather than transactional, and it's the highest-engagement screen in the app.

The Problem

Most people who quit their goals aren't lazy. They're just doing it alone. Habit trackers record your behaviour but don't care about it. Social feeds are passive, Strava claps are not accountability. Finding a real accountability partner is awkward: either you're asking too much of a friend, or cold-DM'ing a stranger with no structure around it.

The gap isn't motivation tools, the market is full of those. The gap is structured mutual accountability between two people with the same goal. Stride isn't competing with Habitica or Streaks. It's competing with the absence of a gym partner.

Key Product Decisions

Designing against the ghost problem before writing a single screenBuddy going silent was identified as the #1 retention killer before design started. Every feature decision got filtered through one question: does this reduce ghosting, or make recovery from it easy? Re-matching was designed to be one tap, no explanation required, framed as finding someone new, not abandoning someone old. Shame around leaving would have killed retention. Removing it was a product decision, not a UX nicety.

The home screen took three complete redesigns to become honestV1 was a dashboard, streaks, stats, activity log. It was useful and completely wrong. The product's value is a human relationship, and I was building a spreadsheet. V2 introduced the buddy card but buried it in navigation. V3 went full-screen, person-first, photo and name dominant, single action. The design reference was Apple's contact posters, the person fills the frame because they're the point.

Onboarding ends with a match suggestion, not a browse listEvery extra step in onboarding is a drop-off risk. The original flow had users browsing a list of potential buddies, familiar, browsable, low-commitment. But it deferred the moment of value. Redesigning the flow to end with a single suggested match, one decision, yes or no, cut the path to first connection from 7 steps to 4.

Safety was non-negotiable from day oneStride connects strangers. All communication stays in-app. Messages are filtered for phone numbers and emails before sending. Every screen has a report button. None of this is visible to users who don't need it, but it had to be there before launch, not after.

What Almost Killed It

Building the wrong mental model for three iterationsThe first two versions of the home screen treated Stride like a habit tracker with a social layer. The UI reflected that, lots of data, stats, recent activity. It took three full redesigns and honest user feedback to admit the product wasn't a tracker at all. Stride is a relationship manager. Once that was the frame, the right UI was obvious. The lesson: the product needs a clear mental model before the interface does.

Launching to silence because the community hadn't been built yetThe first Reddit post for Stride was a product announcement. It got four upvotes. The go-to-market assumption, build it, post it, people come, was wrong. What worked was starting over: spending three weeks genuinely contributing to r/Accountabilibuddies, r/selfimprovement, and r/getdisciplined before mentioning anything I'd built. By the time the product appeared, there was already trust. The meta-irony, building an accountability app and needing accountability to ship it, became the hook that drove the first wave of organic signups.

Scope creep dressed as product thinkingEarly on I added a habit library, goal templates, weekly reviews, and a leaderboard, all in the name of making the product more valuable. Each feature made sense in isolation. Together they blurred what Stride actually was. Stripping it back to the core, match, check-in, streak, was uncomfortable because it felt like doing less. It was the right call. A product that does one thing well is easier to explain, easier to market, and easier to love.

What I Learned

"The relationship is the product"Every design decision that treated Stride as a habit app produced the wrong interface. Every decision that treated it as a relationship app produced the right one. Knowing what category your product actually lives in, not what it superficially resembles, is the most important design brief you can write.

"Ghosting is a design problem, not a user problem"When buddies went silent in early testing, the instinct was to blame user behaviour. The real cause was that the app gave no gentle re-entry point after a missed day, silence compounded into shame. Re-matching with no explanation required, warm empty states, and positive re-engagement copy all reduced ghosting. You can't fix human behaviour, but you can design for it.

"Community trust before product announcement"The product launch that worked wasn't a launch post, it was weeks of genuine participation that made a launch post feel like a natural next step. Distribution isn't a phase after building. It runs in parallel, and it starts with giving, not asking.