Nolan Parker’s product perspective was shaped long before he had a product title.
As a former gym owner, CrossFit coach, and trainer, he understands the day-to-day reality of the people using fitness software: busy operators, time-strapped coaches, overwhelmed staff, and members who do not care how complicated the system is behind the scenes. Now, as a product leader at PushPress, he is building for those same workflows from the inside.
This episode is about the calls product teams actually have to make: when to trust customer feedback, when to challenge it, when to say no to a “good” feature, and how to keep a platform from becoming a bloated collection of edge cases.
Nolan also brings his experience from ROOK into the conversation, where he worked with digital health companies using wearable data as product infrastructure. That background opens up a deeper discussion on data, behavior change, onboarding, AI, and what it takes to build tools that are not just technically useful, but actually usable in the field.
Nolan breaks down:
→ Why being both the builder and the user can create better product instincts, but also stronger bias
→ How coaching taught him to simplify product experiences and avoid overloading users
→ The TrueCoach app rebuild that taught him the cost of adding too much information
→ Why SaaS products become bloated when every customer request turns into a feature
→ How he thinks about market parity, differentiation, world-class features, and “filler”
→ Why product teams need analytics to understand whether users actually love a feature
→ How Dashboard 2.0 showed him the difference between user resistance and product failure
→ Why adoption is often harder than building the product itself
→ How PushPress is thinking about AI, member intelligence, and surfacing the right context at the right time
→ Why pricing recommendation tools can be useful in theory but difficult to make work at scale
→ How gym owner benchmarking, AI assistants, and gamified performance loops could change fitness business software
→ Why internal trust matters before hard product tradeoff conversations happen
Follow Nolan:
LinkedIn: https://www.linkedin.com/in/nolan-parker
Follow Marco Benitez and Jonas Dücker
LinkedIn Marco: https://www.linkedin.com/in/marcobzg/
LinkedIn Jonas: https://www.linkedin.com/in/jonas-ducker-37460bb3/
Get in touch with This Feature Will Save Us Podcast
LinkedIn: https://www.linkedin.com/showcase/this-feature-will-save-us
Website: https://thisfeaturewillsaveus.com/
Powered by
ROOK: https://www.tryrook.io/
1:45 - Nolan’s most useful AI workflow
2:06 - Why product teams may over-index on NPS
2:49 - Garmin, Whoop, Polar, and Nolan’s wearable preferences
3:15 - Acquisition, retention, and the first habit moment
4:05 - Nolan’s underrated recovery habit
5:25 - Nolan’s role at PushPress and his coach/operator background
6:41 - From dietetics and gym ownership into tech and product
8:00 - ROOK, behavior change, and why information is no longer the main problem
8:51 - The advantage and bias of being both builder and user
9:21 - “Don’t make me think” as a product principle
11:26 - The TrueCoach app rebuild and the danger of too much information
13:48 - How product bloat happens in gym management software
15:40 - Market parity, differentiation, world-class features, and filler
17:00 - Using product analytics to decide what deserves to stay
18:17 - Dashboard 2.0 and why users resist better products
20:01 - Why adoption is often harder than building
20:58 - Meeting users where they are instead of being louder
21:45 - Member Intel and giving coaches the right context before class
23:53 - Turning scattered coach knowledge into usable product context
25:41 - Managing noise from CEOs, clients, tech teams, and the roadmap
28:00 - Building in public vs. using a smaller beta group
29:25 - A feature Nolan expected to work better than it did
31:20 - Gym benchmarking, pricing data, and business insights for operators
32:14 - AI assistants, gym leaderboards, and gamifying operator performance
33:31 - Where internal product friction really comes from
34:25 - Why relationship-building has to happen before hard product decisions
36:16 - Building trust and alignment on remote teams
