Back to vistaly.com

Use Case – Segmenting by Customer

Matt O'Connell
Matt O'Connell

The other day, we looked through customer discovery data to determine how one customer's insights compared to others.

We organize our discovery work into opportunity solution trees (OSTs), so clustering pain points we hear from customers is easy. And for the most part, prioritization is as well. But, we were spending more time than we thought acceptable figuring out how one type of customer influenced our thinking over another (B2B vs. B2C, startup vs. enterprise, agency vs. product team, paid vs. freemium). Are there any patterns?

It's easy to throw up your hands and say, "I don't have time for this". Because you know you have to follow links back to Notion or Confluence (or Roam and Google Docs in our case), and you may find yourself referencing recordings or transcripts. And after you spend time doing that, you're unsure if it'll be worth the effort. That shouldn't be the case; we already captured that information when we put the opportunities into our tree. Just show me how a particular customer (or, in this case, a group of customers) influenced our discovery.

That wasn't acceptable to us, considering Vistaly's purpose is to enable teams working this way to do it more efficiently.

So, without further ado. Introducing...

"What does this customer or customer segment care about?"

Or maybe it's...

"What pain points are THESE customers specifically experiencing?" (working titles)

Open Vistaly – Add the customer(s) to a filter – 🎉 – you're LOOKING at the subset of your tree, informed by those customers, without having to piece it together by looking through notes.

Now you can:

  • Target release notes
  • Improve customer success
  • Inform your next set of research and interview questions
  • Collect additional prioritization information
  • Visualize how specific customer segments influence your decisions

Segmenting by customer

If you haven't checked out Vistaly yet, try it free with your team.

Vistaly the operating system for Outcomes-focused Product Teams

Identify and assign Outcomes, discover and prioritize opportunities (with OSTs), track assumption testing, now/next/later roadmap designed around Outcomes

Try Free

No CC required

Matt O'Connell
Matt O'Connell