Anchoring the roadmap in customer jobs

Principal Product Designer · Product strategy · 2026 · Partners: [ADD] · Outcome: [ADD headline metric]

The job to be done

When product, design and engineering debate what to build next, they need a shared view of the jobs customers hire Veeam for, so every feature can be tied to an outcome customers care about.

Who it’s for

Backup admins, IT leaders and security teams who rely on Veeam, and the internal teams who plan for them. [ADD detail]

Why it mattered to the business

[ADD: e.g. roadmap driven by feature requests, unclear priorities, the metric leadership tracked.]

The problem

[ADD: what was broken, and the evidence.]

My role and the team

[ADD: what I owned and who I partnered with.]

Key decisions

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

The design

[ADD: the framework, the top jobs, how they show up in planning.]

Results

[ADD: decisions it changed, outcomes now tracked.]

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.