Define
- Product scope & priorities
- Core user flows
- Feature specifications
HYENA FLEX · PRODUCT MANAGEMENT
From scattered vision
to a focused first release.
I turned an ambitious product vision into a shippable ride experience—rebuilding the roadmap around core rider value as development resources became limited.
Launched September 10, 2026
Explore the product decisions
01 / OVERVIEW
A product built around
the everyday ride.
Flex helps riders record their rides, revisit their journeys, and see their progress. It brings ride tracking, challenges, rewards, and community into one experience.
My task was to turn those possibilities into a focused first release that the team could deliver, measure, and improve.
- Role
- Product Manager / Product Owner
- Timeline
- June 2025 – Present
- First release
- iOS · September 10, 2026
- Focus
- Product definition, delivery & iteration
02 / MY ROLE
I connected product direction
with delivery decisions.
I led product definition and delivery planning, discussing trade-offs with the team and consolidating decisions when requirements or ownership were unclear.
Deliver
- Roadmap & release scope
- Cross-functional alignment
- QA & launch preparation
Learn
- Tracking plans
- User behavior review
- Post-launch iterations
Working across iOS, backend, frontend, design, QA, marketing, and leadership.
03 / CHALLENGE & STRATEGY
More possibilities.
Less capacity to pursue them.
A scattered vision
Ride tracking, gamification, planting, community, rewards, and future e-bike features competed for attention.
An unclear reason to switch
Existing HRA riders did not immediately understand why they should move to Flex.
A shrinking team
As team members left, the original roadmap no longer matched our development capacity.
The question became: what must work in the first release for riders to experience real value?
Make the ride valuable first.
I centered the first release on a clear value loop. Engagement features needed to reinforce the ride experience, not compete with it.
-
01
Record
Capture a daily ride.
-
02
Visualize
Revisit the journey.
-
03
Progress
See effort add up.
-
04
Return
Find a reason to ride again.
Core product loop · A simplified view of the strategy.
Define a release boundary.
I weighed rider value, dependency risk, implementation effort, and whether a feature was necessary for the first usable experience. When capacity changed, I revisited the scope—not just the dates.
FIRST RELEASE
Protect the core experience
- Ride recording, GPS maps & 3D ride records
- Reports, weekly challenges & achievements
- Rewards & planting
- Feed, community, profile & notifications
DEFERRED / FUTURE SCOPE
Keep expansion off the critical path
- Strava & HealthKit integrations
- Expanded e-bike connectivity & status
- Automatic ride start / finish & multi-bike support
- Streaks, leaderboards, more languages & Android
- Watch support & Live Activities
Scope summary, not a numerical scoring model. Deferred work is not presented as shipped functionality.
04 / LAUNCH RESULT
September 10, 2026.
Flex’s first iOS release went live on the App Store.
DEFINE
Focused first-release scope
BUILD & VERIFY
Delivery planning and QA
LAUNCH & LEARN
A live product to improve
05 / DECISIONS & EXECUTION
The trade-offs that
made a release possible.
01
Core ride value before ecosystem expansion
Translated the ride-first strategy into PRDs, user flows, and feature specifications, giving product and engineering a shared definition of the first release.
02
Rebuild the roadmap around actual capacity
Re-scoped milestones and dependencies as resources decreased, then aligned release scopes, QA preparation, and test checklists with the plan the team could execute.
03
Measure the journey beyond sign-up
Defined events and tracking plans around starting and completing rides so we could examine experienced value, not only account creation.
04
Align the experience from onboarding to launch
Coordinated onboarding copy, achievement messaging, notification scenarios, support materials, policy pages, and launch messaging so they reflected the same product behavior.
06 / ITERATIONS & IMPACT
A shipped product.
A clear path to improve it.
I helped turn scattered ideas and reduced team capacity into a shared release scope, an executable roadmap, and a launched product with a measurable basis for iteration.
IMPLEMENTED
Make rewards easier to understand
Added EcoGem and planting reminders to connect progress with a tangible next action.
NEXT RELEASE
Bring riders closer to the first ride
Revised onboarding, earlier bike pairing, a clearer home hero, and contextual TipKit guidance.
ONGOING
Clarify the reason to move from HRA
Refine entry messaging so existing riders understand what Flex offers before they enter the flow.
Long-term retention impact is still being evaluated.
← Back to selected work