Define
- Product scope & priorities
- Core user flows
- Feature specifications
FLEX · PRODUCT MANAGEMENT
I protected Flex’s core loop—ride, earn EcoGem, plant trees—while repeatedly reducing MVP scope as the team became smaller.
Flex helps riders record their rides, revisit their journeys, and see their progress. It brings ride tracking, challenges, rewards, and community into one experience.
The hardest MVP decision was whether to ship riding functionality alone or preserve the experience that connected riding to EcoGem and tree planting. I advocated keeping the minimum experience needed to complete that loop, then reduced the surrounding scope as delivery capacity fell.
I led product definition and delivery planning, discussing trade-offs with the team and consolidating decisions when requirements or ownership were unclear.
Working across iOS, backend, frontend, design, QA, marketing, and leadership.
Leadership favored an MVP focused on riding functionality. I advocated including a small set of experience elements so riders could complete Flex’s intended loop: ride, earn EcoGem, and plant trees.
Departures across engineering and QA repeatedly reduced delivery capacity. The remaining team was me as PO, a designer, an iOS engineer, and our manager stepping in to support backend development.
I revisited the MVP repeatedly, reducing gamification and social scope while preserving the essential riding experience and its connection to EcoGem and planting.
What is the smallest experience that still lets a rider complete the ride-to-tree loop?
Riding functionality was essential, but it would not carry the full product proposition on its own. My rationale for retaining a few experience elements was to keep the connection between the ride, its reward, and the action that reward enabled.
Record the activity.
Receive value from the ride.
Use EcoGem to participate in a planting campaign.
The intended product loop; its presence does not establish repeat engagement or retention.
PROTECTED IN THE MVP
CUT BACK DURING SCOPING
This summarizes the MVP trade-off, rather than a complete launch feature inventory.
Riders could connect a recorded activity with EcoGem and a planting opportunity. This kept the intended product experience intact as the implementation became smaller.
The first version would have less depth in achievements, feedback, and social engagement. I accepted that narrower experience to focus the remaining team’s effort on the essential path.
I translated the ride-first strategy into PRDs, user flows, and feature specifications. These made the agreed scope concrete enough for product and engineering to review and implement together.
I re-scoped milestones and dependencies as resources decreased, then aligned release planning, QA preparation, and test checklists with the revised scope. The roadmap and test preparation carried the same product decisions into delivery.
I defined events and tracking plans around starting and completing rides. This gave post-launch review a concrete question: were people reaching the core ride experience after signing up? The tracking plan established a basis for investigation; it did not by itself demonstrate improved activation or retention.
I coordinated onboarding copy, achievement messaging, notification scenarios, support materials, policy pages, and launch messaging. These touchpoints needed to explain the same behavior users would encounter in the app.
Closed-beta surveys and behavioral data informed the privacy direction. Subsequent conversion analysis guided changes to ride entry, completion, and the transition from HRA.
Evidence: Surveys of active closed-beta users, considered alongside their behavior and data, showed caution toward a sports community and public sharing. Users wanted to focus on their own riding data and protect their privacy.
Response: We added route start/end trimming and clearer privacy explanations. In-app campaigns also encouraged riders to upload activities with photos, while sharing remained a user choice.
Product judgment: A richer feed needed to account for riders’ willingness to share and the information they wanted to protect.
Evidence: Ride conversion was below expectations. Riders coming from HRA were accustomed to connecting the bike and riding to accumulate data, then disconnecting to stop recording.
Response: We moved optional bike pairing into onboarding, added a home-screen start-activity button and a summary showing not-started, active, or paused status, and introduced TipKit guidance when users first reached the home screen.
Auto Finish supported riders accustomed to ending a ride by disconnecting. Push and email reminders were also added to encourage inactive users to return.
Intent: Improve pairing, ride participation, and return usage. These changes are presented as responses to the observed problem; a measured conversion lift is not yet reported in this case.
Observation: HRA-to-Flex conversion was below expectations. Many still-active HRA users connected their bike, opened the dashboard, and then quickly closed the app.
Hypothesis: They might be checking the bike’s condition before setting off. The behavior suggested this purpose; it did not confirm user intent.
Response: We added a message after bike connection in Flex showing whether the bike’s status was normal or an error was present, bringing that quick status check into the new experience.
Flex launched on iOS on September 10, 2026. I helped preserve its ride-to-tree proposition through repeated scope reductions, coordinated delivery with a much smaller team, and used feedback and behavior to guide subsequent product changes.
Account integration is being planned to support the transition between the two products.
Rework when and where campaigns appear, alongside Eco achievement feedback. One planned direction is a campaign card at the end of the post-ride flow when the rider has enough EcoGem to participate, with a direct path into planting.
Daily quests are being planned to encourage public activities or photo uploads, giving riders prompts to contribute while keeping the earlier privacy findings in view.
These are planned directions, not shipped outcomes. Quantified improvements in ride conversion, migration, planting participation, and retention are not reported here.
← Back to selected work