One place for everything customers tell us

Principal Product Designer · Research operations · 2026 · Used by: [ADD teams] · Outcome: [ADD headline metric]

The job to be done

When a product team is about to make a roadmap or design decision, they need to see what customers have already told us, so they decide on evidence instead of opinion.

Who it’s for

Product managers, designers, engineers and leaders across Veeam, plus the customer-facing teams who hear from customers every day. [ADD detail]

Why it mattered to the business

[ADD: e.g. duplicated research, slow decisions, features built on guesswork.]

The problem

[ADD: where customer insight lived before, and the evidence it was being lost.]

My role and the team

[ADD: what I owned, who I brought in, how adoption spread beyond my own team.]

Key decisions

  • [ADD: decision 1, the options, what we chose and why]
  • [ADD: decision 2]
  • [ADD: decision 3]

The design

[ADD: 3–5 visuals, each with a one-line caption.]

Results

[ADD: teams using it, insights logged, decisions it informed.]

What I learned

[ADD: two or three lines.]

Published by Karsten Rowe

Karsten Rowe is a product design leader with 20 years of experience turning complex, high-stakes systems into products people can trust. He has built and led design and research teams across public safety, fleet management, and enterprise cloud, including as Director of Product Design & UX Research at Axon and Head of Design at Nutshell. He is now a Principal Product Designer at Veeam. Based in Seattle, he has also worked in London, Berlin, and San Francisco.