Guerrilla competitive research by way of UX-survey
Tags: startup, showdev, ux
Published: 2020-02-28 13:10:52

---
title: Guerrilla competitive research by way of UX-survey
published: true
description: Thanks to nearly 100 strangers from the internet, a path forward for my passion project is starting to appear
tags: startup, showdev, ux
canonical_url: https://pistola.io/blog/02-user-survey-results/
cover_image: https://dev-to-uploads.s3.amazonaws.com/i/z5mmi10kspedre3smzar.jpg
series: Building Pistola
---

**Note:** This is a cross-post from my site [Pistola](https://pistola.io/blog/02-user-survey-results), and is the [second in an ongoing series](https://dev.to/irreverentmike/building-my-passion-project-with-radical-transparency-introducing-pistola-2egh) about my passion project to build a service for athletes.  If you find this interesting, I'd love if you listened to the [Building Pistola podcast](https://pistola.io/podcast), and subscribed to the [Pistola Newsletter](https://pistola.io).

## Introduction

A couple weeks back, I posted a [typeform survey](https://gopistola.typeform.com/to/osVw3W) to several Strava and Zwift user groups on Facebook, reddit, and a couple cycling-related channels in Slack communities I belong to. It was the first outreach-related step in the process of deciding what Pistola should be aiming to do. The goal the survey was to learn about how these folks use Strava. I wanted to know what they like and dislike about it, and what their expectations were for future updates and changes to the product. I also asked some prying questions about what they pay for Strava (if anything), and whether or not they were satisfied with the product.

It's worth noting that in crafting the survey, I ran into a few difficulties. My first draft survey was directly only at people who **ride indoors** (with [Zwift](https://zwift.com/) or [Peleton](https://www.onepeloton.com/) or something similar). After some deliberation, I decided that I was interested in hearing from anyone who is interested in recording, viewing, and analyzing their workouts with an app or service. Zwift does have a large and growing audience, but I felt it might be too limiting to focus on just Zwift users, at least initially. So in the end I decided to shelf that survey, and start by asking any Strava user for feedback on product use.

## Results (n=91) and my analysis

First of all, thank you to anyone who took or shared the survey! I can't tell you how much of a relief it was to see responses rolling in. What follows are my takeaways after reading through the 91 responses to the survey that I received.

### About how many miles a year do you ride?

- **Count:** 86 responses total (some responders use strava for running rather than riding!)
- **High:** 12,000mi/yr
- **Low:** 40mi/yr
- **Average:** 3221mi/yr

### About how any miles a year do you run?

- **Count:** 22 responses total (again, some responders do not cycle, they just run, and vice versa)
- **High:** 2400mi/yr
- **Low:** 2mi/yr
- **Average:** 663.5mi/yr

### What Strava could be doing better

Athletes don’t like strava’s recent removal of bluetooth support. Sometime last year, Strava removed support for [bluetooth sensors](https://support.strava.com/hc/en-us/articles/360032979131-Removing-Direct-Sensor-Pairing-from-the-Strava-Mobile-App) in their mobile app. This stems from reliability issues with bluetooth sensors.

In a past life, spent _quite a bit_ of time working on an app to collect data from dozens of BLE sensors at a time. Let me be the first to tell you - I'm sympathetic to their engineers here. Bluetooth sensors are a pain in the ass. At times, it can feel like a complete miracle that any of them work at all. It's a cagey protocol with lots of inconsistencies and flaws, and with manufacturers of all stripes making sensors nowadays, you can imagine how Strava might be taking flak for poor quality control processes from some generic company overseas making millions of sensors for pennies on the dollar.

Nonetheless, athletes _really_ miss having Heart Rate data in their workouts - the only workarounds available now are to use other mobile apps (which are often really bad), or to buy an expensive GPS watch or bike computer.

People want a reverse chronological order for their timeline. This one's straight forward, and familiar if you've used pretty much any social network. Somewhere along the line, the powers that be (read: investors and shareholders) discovered that feed/timeline oriented apps can drive more profitable behavior if the timeline they show favors _sticky_ content (that is, content that is more likely to be engaged with, in whatever way is meaningful). Strava switched off their reverse-chronological feed at some point, and switched to an algorithmic one. That doesn't sit well with their users, who just want to see the latest from their friends.

Certain social features are kind of lacking. For example: even though you can _see_ people who rode the same route as you at the same time as you, there's no way to contact them directly. That's a bummer! People are also jonesing for more social sharing functionality. Being able to show off a landmark run, hike, or ride is often distilled to a single still shot with some stats plastered on it, which only really scrapes the surface of the accomplishment that lies beneath.

### What Strava is doing well

- UX is far better than things like [TrainingPeaks](https://trainingpeaks.com), [TrainerRoad](https://www.trainerroad.com/), and [Garmin Connect](https://connect.garmin.com/). Those services either feel neglected or old, or (in the case of Garmin Connect) are just not targeted toward a social audience, so they're less sticky.
- The social aspect is really great. People really seem to like being able to see what their friends are up to... thus the frustrations with the non-chronological timeline noted above.
- Quantified self / statistics. This seems like a natural commonality amongst strava users. Mileage counts, kudos, KOMs, and PRs and segments are delicious, endorphin-generating tallies that keep athletes coming back for more.
- Finding places and routes to ride by looking at global heatmaps and local segments helps athletes explore outdoors, and feel like they're seeing more of the world than they might otherwise.
- "Social media without typical social media bullshit" - Strava is a network that posts one thing. No false articles, political nonsense, or scam buffoonery comes from someone posting their ride online.
- Social, social, social - this came up again and again. With physical exertion being the core of the content generation for Strava, it's no surprise that people love sharing what they've done. It's sharing without oversharing - it's being proud without being a humblebrag. That's pretty rare.

### What's missing?

- Creation and editing of routes. It seems like people are hungry for something like [RideWithGPS](https://ridewithgps.com) or [Komoot](https://komoot.com), which are tools that help you _plan_ a ride before going out into the world.
- Exploration of segments - the more competitive athletes of strava want seemed to be interested in finding areas and routes where they might be able to capture a KOM
- Expansion of activity types! Several users mentioned that Strava doesn't seem to make space for "Walking" as a tracked activity.
- Experience parity between mobile / tablet apps and the website. Strava.com provides **loads** more analysis than their mobile apps (perhaps by design), and it seems like athletes really notice this when using their phones and ipads.
- Direct messaging - it's a great feeling when you meet a new friend while out on a run or a ride, but there's no way to contact someone directly through any of Strava's interfaces. At best, you end up bugging someone in the comments section of an activity for personal contact info, which is not great.
- Once again, chronological feeds came up quite a bit here. Several people also mentioned a desire to be able to filter their feed (to show only running activities, for example)
- Customer support! Again, 50 Million users - your problems get lost in the heap very easily.

### Value for Money

Those who pay for Strava's services on average rate value for money as 3.2 out of 5, with the majority of folks reporting 3 or above.

![Chart showing distribution of survey results for Strava Value for Money](https://dev-to-uploads.s3.amazonaws.com/i/m23stligfelb4qzb6xqe.png)
Although the average value-for-money was a 3, most paying users are happy with the money they're spending.


### What do you pay for other than Strava?

**63%** of respondants pay for more than just Strava, and **the vast majority of those pay for several other services**. That's a good sign for making room for one more(!)

### The $5 question - will they try something new?

Once again, the numbers are looking good! Of those who responded, the vast majority say they "Likely would" or "Definitely would" try out a new service. Here's hoping that holds true when we open up the flood gates on the MVP.

![Chart showing response to the survey question: "If you found a similar service to Strava today, how likely would you be to try it out?"](https://dev-to-uploads.s3.amazonaws.com/i/4sdseqtcxy99oci66trh.png)
63% of users would either "likely" or "definitely" try a new service. Oh, hello there! 😍

## Conclusion

Well - I don't know that there's a concrete conclusion at this point, but I think this strengthens my feelings about the planned MVP. You should check that out on the [Roadmap](https://github.com/orgs/gopistola/projects/1) - everything in the `MVP` column is considered must-have in order to get the most basic version of Pistola out into the world.

Want a sneak peek? I thought you might. As of this writing, the detail page looks like this:


![Work in progress screenshot of a detail page for a recorded activity on Pistola](https://dev-to-uploads.s3.amazonaws.com/i/wvzja3248xvjlsw51bcl.png)
A taste of things to come.


Thanks again for reading! If you find this interesting, I'd love if you listened to the [Building Pistola podcast](https://pistola.io/podcast), and subscribed to the [Pistola Newsletter](https://pistola.io).