Testing content with users
Laying the groundwork for a long-lasting feature at komoot
One of my first projects at komoot, a route planning and navigation app, seemed simple at first: write copy for a button and a few related screens. What I didn’t realize at the time was that this small task would lay the foundation for years of iterations and enhancements.
The challenge
The button allowed users to send routes to their Garmin smartwatch or bike computer. Initially, this feature was exclusive to Garmin, but the long-term plan was to expand it to other partners. The broader functionality had already been given the name “Live Sync” before I joined the team.
Since I was familiar with komoot, but had never used a Garmin device, my first step was to understand how these users referred to their devices. I led a round of user research to validate the terminology I had chosen and to ensure that the copy used in the overall flow was clear and intuitive.
What we learned
The research confirmed that, for the most part, the terminology I chose was clear, and users could easily follow the process and anticipate next steps.
But it also revealed key areas where the copy created confusion rather than clarity.
Like on this screen, where a user remarked:
“I’m confused why it says ‘Discover what’s possible,’ but there’s a help icon. It seems like it’s trying to confirm that it’s been sent to a device, but there isn’t a confirmation that actually says that.”
To fix this, I edited the copy on the screen users see when a device isn’t connected, making the messaging clearer and more actionable.
On another screen, additional body copy was intended to provide context, but a user noted:
“Description is not necessary for me. I want as little text as possible on the screen.”
In response, I recommended moving this information to a support page rather than cluttering the UI.
The impact
After refining the copy, I utlimately landed on a set of clear, user-friendly strings. The product manager even said they’d ‘never been this confident in copy before.’
Over the following years, I continued evolving this feature. I contributed to adding group hikes, rides, and runs, and even helped name the term for this functionality. As business needs shifted, I also played a key role in transitioning the experience from “Send to” to “Navigate with”—a change that remains a topic of debate within the team but one that I stand by.
This project taught me that even the smallest UX writing decisions can have a lasting impact, shaping not just individual interactions but the evolution of an entire feature.