Feature naming workshop
Finding the most obvious (and best) feature name
At komoot, a route planning and navigation app, we follow a simple principle when naming features: we don’t invent names, we describe them. By focusing on clarity and benefits, we avoid creating a confusing list of terms that users struggle to connect with. Still, almost every feature needs a name—both for consistency within the UI and for internal communication.
Historically, most features were named by co-founders and product managers. But as I became more involved with different teams, I built trust, advocated for clear language, and eventually took a leading role in naming features. One way I did this was by running feature naming workshops—collaborative sessions designed to bring teams together and land on names that feel obvious, natural, and intuitive.
The workshop process
One particular naming workshop came about after I reviewed my colleagues’ near-final copy for a new paid feature. The feature name they used felt uninspiring, and I saw an opportunity to make it stronger. Given that this was a Premium offering, the name needed to clearly communicate value.
So, I pulled together a cross-functional team—two UX writers, two product designers, and two product managers—and ran them through a structured naming workshop that had worked well in the past.
The workshop follows five structured steps, each with a time limit:
STEP 1: Define the naming criteria – What constraints or guidelines must the name follow?
STEP 2: Dive into the feature’s details and benefits – What problem does it solve? Why does it matter?
STEP 3: Map out where the name will appear – Understanding its context within the UI.
STEP 4: Brainstorm freely – A rapid-fire session where no idea is off-limits.
STEP 5: Identify key themes and stand-out ideas – Extract the strongest contenders for further refinement.
We rarely walk away with a finalized name immediately, but this process ensures that every voice is heard, the best ideas rise to the surface, and the final decision is grounded in collective expertise.
The outcome
For this particular feature, we expanded an existing term already in the product—Trail View—to Trail View photo gallery. This not only provided clarity but also leveraged an established, recognizable name within our ecosystem. Here’s how I explained the rationale to the team:
The feedback was all positive—not just because we landed on a strong name, but because the process itself was collaborative, inclusive, and transparent. By involving people from different disciplines, we ensured alignment across teams while strengthening cross-functional relationships.
Why this matters
Naming may seem like a small detail, but it carries a big impact. A well-chosen name can enhance usability, reinforce brand trust, and improve feature adoption. And when teams feel invested in the process, they become champions of the final decision—making implementation that much smoother.