Getting Microsoft 365 back after a bad day

Principal Product Designer · Veeam Data Cloud for Microsoft 365 · 2026 · Team: [ADD team] · Outcome: [ADD headline metric]

The job to be done

When a mailbox, site or Team is deleted, corrupted or hit by ransomware, an IT admin needs to find exactly what was lost and put it back, so the business keeps running and nobody notices.

Who it’s for

Microsoft 365 admins and backup operators at mid-size and enterprise companies, often under pressure from leadership while a restore is in progress. A wrong decision means lost data, downtime or restoring over good data. [ADD: research detail]

Why it mattered to the business

[ADD: the metric leadership cared about, e.g. restore success, support tickets, retention or competitive win rate.]

The problem

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

My role and the team

[ADD: what I owned, who I led or influenced, how we worked with product and engineering.]

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 saying what it solves.]

Results

[ADD: before and after, business and user metrics.]

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.