
Strava, the ubiquitous social network for athletes, has built its success on understanding what motivates cyclists, runners, and a multitude of other active individuals. A significant, yet perhaps less visible, part of that understanding comes from a powerful internal resource: its own employees. At Strava, the line between user and creator is often beautifully blurred. The company's culture not only encourages but often expects its team members to be active participants on the platform, creating a dynamic feedback loop that directly shapes the product from the inside out.

### A Culture Steeped in Activity and Authenticity

Strava's company values, often referred to as their "ABCs," paint a clear picture of this internal dynamic. "Authenticity" dictates that they "design with data insights, not assumptions. We use data, lived experiences, and feedback to guide decisions." "Balance" emphasizes that "We practice what we preach: there's always time for a workout." And "Camaraderie" highlights that "Culture is a team sport. Our best work comes when we honor each other's stories and strengths." These aren't just aspirational posters on a wall; they are lived principles that translate into a workforce deeply engaged with the product they're building.

As stated on their [careers page](https://www.strava.com/careers), Strava aims to build a team that reflects the world it serves, valuing "lived experiences." Perks like race entries and gear discounts further incentivize this active engagement. This means that when product managers, engineers, designers, and marketers at Strava are discussing new features or iterating on existing ones, many are doing so not just as professionals, but as daily, passionate users of the app.

Michael Horvath, one of Strava's co-founders, has often spoken about the importance of understanding the customer. In an interview with [Acquired.fm](https://www.acquired.fm/episodes/strava-with-michael-horvath-and-mark-gainey) (Note: While a specific quote on internal dogfooding from this interview wasn't pinpointed in the search, the founders' athletic backgrounds and user-centric philosophy are well-documented), the genesis of Strava itself stemmed from their own desire as athletes to see and share their activities in a more compelling way. This foundational "build what you need" mentality naturally evolved into a "use what you build" culture.

### From Internal Kudos to Public Features: The Feedback Loop

While Strava might not use the formal "dogfooding" label extensively in public communications, the practice is evident. The "lived experiences" and "feedback" mentioned in their values translate into a continuous, informal, and sometimes formal, testing and iteration cycle driven by employees.

Consider the development of new features. Before any new functionality reaches the broader Strava community, it's highly probable that Strava employees are among the first to test it in their own workouts and daily routines. This provides invaluable early insights into usability, bugs, and overall appeal. An interview with Strava executives published on [Android Central](https://www.androidcentral.com/apps-software/strava-interview-athlete-intelligence-inaccurate-gps-race-leaderboards-and-more) regarding the "Athlete Intelligence" feature noted that for some sports, more internal testing might be needed before a feature is "fully baked," implying a rigorous internal validation process.

Strava also heavily relies on data analytics to inform product decisions, as detailed in a [case study with Amplitude](https://amplitude.com/blog/strava-analytics-efficiency). While this data encompasses the entire user base, the insights gleaned also benefit from an internal team that understands the nuances of athletic data because they are generating it themselves. This allows them to "find gaps in our product offerings, and build features and experiences that increase value."

The social features that are core to Strava's success—segments, leaderboards, clubs, kudos, and comments—are features that Strava employees themselves actively participate in. This direct engagement ensures that the evolution of these community-building tools is guided by people who genuinely understand their power and appeal.

### Benefits of an Athlete-Centric Development Team

This internal usage model offers several key advantages for Strava:

* **Authentic User Perspective:** Employees provide genuine insights as active users, understanding the desires and pain points of the core athletic community.
* **Rapid Iteration:** Issues can be identified and addressed quickly when the developers and designers are also the users.
* **Feature Relevance:** New features are more likely to resonate with the target audience because they've often been conceived or validated by a passionate internal user base.
* **Strong Company Culture:** A shared passion for activity and the product itself fosters a strong sense of camaraderie and commitment among employees. As highlighted on their [Comparably culture page](https://www.comparably.com/companies/strava), employees rate their team highly and look forward to interactions.

### Potential Blind Spots and Evolving Perspectives

While having a team of dedicated athletes using the product is a significant strength, it could also present challenges. A highly athletic and tech-savvy employee base might inadvertently develop features that cater more to the "hardcore" user, potentially overlooking the needs of beginners, more casual users, or those with different accessibility requirements.

Strava is aware of the need to serve a broad community. Their mission to "connect athletes to what motivates them and help them find their personal best" applies to everyone, regardless of their current fitness level. The ongoing evolution of the platform, including features designed for a wider range of activities and motivations, suggests an effort to address these potential blind spots, likely informed by broader user data and dedicated user research alongside internal feedback.

The company's engineering team, as seen on the [Strava Labs page](https://labs.strava.com/) and their [developer portal](https://developers.strava.com/), clearly innovates with their rich dataset. It's plausible that internal hackathons or employee-driven projects using their own APIs also contribute to new feature ideas or improvements, further embedding the "use your own platform" ethos.

### The Finish Line: A Product Shaped by Its People

Strava's success is intrinsically linked to its community, and that community starts within its own walls. By fostering a culture where employees are encouraged to be active users, Strava ensures a continuous flow of authentic feedback and "lived experiences" into its product development cycle. This approach doesn't just help them "sweat the details"—it helps them build a platform that genuinely understands and serves the needs of athletes worldwide, because, in many ways, they are building it for themselves.

Sweating the Details: How Strava's Athlete Employees Shape the Platform from the Inside Out


Garmin has become synonymous with precision GPS technology and robust athletic wearables, particularly its renowned Forerunner and Fenix lines of running watches. While their success is built on strong engineering and a deep understanding of athlete needs, a significant, often less visible, component of their product development prowess comes from within: Garmin employees are not just creators but are often dedicated users of the very devices they design and build. This culture of "eating your own dogfood" is instrumental in shaping the features, reliability, and user experience that runners worldwide have come to trust.

### A Culture Bred from Passionate Users

Garmin's company ethos fosters an environment where innovation can spring from any corner, often driven by the personal passions of its employees. As highlighted in a piece by [RocketMind Strategies titled "Garmin: The quiet run to the top of the world,"](https://rocketmindstrategies.com/mindcase-blog-post-en/garmin-the-quiet-run-to-the-top-of-the-world) the company champions a "bottom-up culture." The article notes, "The impetus for the first running watch came from engineers when the company was still in the navigation business... Today's watch portfolio is made by employees who want to have these products themselves and who have the same high performance standards."

This intrinsic motivation is powerful. When engineers, product managers, marketers, and even IT staff are themselves runners, cyclists, swimmers, and outdoor adventurers, their daily experiences and training regimens become an informal, yet highly effective, testing ground. They understand the nuances of what an athlete needs – whether it's pinpoint GPS accuracy on a trail, reliable heart rate data during a tempo run, long battery life for an ultramarathon, or intuitive training metrics that genuinely aid performance.

Garmin CEO Cliff Pemble himself leads by example, having participated in fitness challenges using Garmin devices, showcasing a top-down encouragement of an active lifestyle that naturally involves using the company's own products. This internal user base, with its varying levels of athletic ability and diverse use cases, provides a rich tapestry of feedback.

### From Internal Runs to Refined Features

While Garmin doesn't heavily publicize a formal "dogfooding" program under that specific moniker, the mechanisms for internal feedback influencing product development are evident:

* **Iterative Development and Testing:** New features and algorithms, especially those critical to running like GPS tracking, heart rate monitoring (including their Elevate™ wrist-based HR), and advanced training analytics (like Training Status, VO2 Max, and Recovery Time), undergo rigorous testing. It's almost certain that Garmin's own employees are among the first to put these features through their paces in real-world conditions, identifying bugs, suggesting improvements, and validating performance long before they reach the public.
* **The Public Beta Program:** Garmin runs a well-utilized [Public Beta Program](https://support.garmin.com/en-US/?faq=bVo5U5BV292BSr2gkZhY2A), which allows enthusiastic users (a group that undoubtedly includes many Garmin employees) to test pre-release software. This program provides a structured way to gather feedback on new features and bug fixes. Employees participating in this program can offer highly informed insights, understanding both the user perspective and the underlying technology.
* **Feature Requests from Active Employees:** The story of a Garmin dive computer being conceived by an IT employee who was a diver (mentioned in the RocketMind Strategies article) illustrates how personal needs of employees can directly lead to new product categories or specialized features within existing lines. It's highly probable that similar internal advocacy has driven many of the running-specific features we see in Forerunner and Fenix watches today.
* **Garmin Connect and Connect IQ:** The Garmin Connect platform, which analyzes and visualizes activity data, and the Connect IQ app store, which allows for customization and new functionalities, are also ecosystems that Garmin employees would heavily use. Their experience as users of these platforms would directly inform improvements to the user interface, data presentation, and the capabilities offered to third-party developers (who also include internal teams building apps and watch faces).

### The "Engineered on the Inside for a Life on the Outside" Philosophy

Garmin's tagline, "Engineered on the inside for a life on the outside," perfectly encapsulates this approach. The engineering and design process is not an abstract exercise; it's directly connected to the active lives of the people building the products. This leads to a focus on features that truly matter to athletes:

* **Durability and Reliability:** When your own employees are relying on these watches in challenging outdoor conditions, there's a strong incentive to build them to last.
* **Battery Life:** The legendary battery life of many Garmin devices is a key differentiator, likely born from the frustrations of employees needing their watches to last through long training sessions, multi-day adventures, or simply a full week without a charge.
* **Accuracy of Core Metrics:** Passionate runners within the company would be among the first to notice and flag inaccuracies in GPS distance, pace, or heart rate, driving continuous improvement in these core sensor technologies.
* **Advanced Training Insights:** Features providing deep physiological insights, such as those developed in collaboration with Firstbeat Analytics (a Garmin company), are likely tested and validated by knowledgeable internal users who can appreciate and critique their utility for serious training.

### Potential Challenges: The Expert User Bias?

One potential challenge of relying heavily on an internal user base that is likely more skewed towards experienced and tech-savvy athletes is the risk of developing products that might be overly complex or intimidating for beginners or more casual users. The sheer number of features and customization options in high-end Garmin watches can sometimes be overwhelming for those new to GPS running watches.

However, Garmin has also made efforts to cater to a wider audience with watches at different price points and feature sets (e.g., the more accessible end of the Forerunner series). The feedback from a diverse range of employees, not just elite athletes, would be crucial in striking this balance. Furthermore, the extensive data gathered from the broader Garmin Connect user base (used responsibly and with a focus on privacy) likely provides insights into how different demographics use their devices, helping to inform product decisions beyond just the internal employee perspective.

Noted tech reviewer DC Rainmaker pointed out in a 2019 article, "[Garmin's Biggest Competitor Is Their Own Software Instability](https://www.dcrainmaker.com/2019/06/competitor-software-instability.html)," that historically, Garmin sometimes seemed to prioritize "features first, stability later." While this critique highlights past challenges, the public beta program and a continuous focus on software updates suggest an ongoing effort to address such concerns, likely bolstered by internal quality assurance driven by employee usage.

### Conclusion: Running Their Own Race, Refining for All

Garmin's leadership in the running watch market is a testament to its robust engineering, innovative features, and a deep understanding of what athletes need. A significant part of this understanding is cultivated by its own passionate employees who use, test, and live with the products they create. This internal feedback loop, whether through informal daily use, structured beta testing, or employee-driven innovation, ensures that Garmin watches are not just designed *for* athletes, but in many ways, *by* athletes. This commitment to "engineering on the inside" is a powerful advantage, helping Garmin to continuously refine its technology and stay at the forefront of the pack.

Articles tagged with "Employee Feedback"

Sweating the Details: How Strava's Athlete Employees Shape the Platform from the Inside Out

Engineered on the Inside: How Garmin's Own Athletes Help Forge Its Leading Running Watches