Quality is an operational habit, not a design department.

»Quality is the commitment of an organization that talks openly about how they define good.«

Early on, I thought good craft would sell itself. But this does not work. You can’t build quality in spite of the business around it. Craft alone doesn’t convince anyone. You have to meet engineers, founders, and product managers where they are, with impact for them and the business, mostly numbers they care about. And you know a design practice is working and the quality question commitment is a success when an engineer asks the quality question before a designer does.

My background covers ten years in consultancies, where success came down to pricing, client trust, and scoping cleanly. Then six years building design functions inside early-stage startups from scratch. At Wandelbots, I helped steer a fundamental pivot across product, design, and engineering.

Deliveries’ impact alone is temporary. The work leaves when you leave. The real job is building a practice that holds up when you’re not in the room and keeps working after you walk out the door (for good).

How I work

I don’t start at the interface, and I don’t stop when code ships. My work connects business decisions to the people who carry them out. Deciding whether to build something at all, defining what good looks like, and making sure that standard holds when design isn’t in the room.

  • Should we build this?

    Informed conviction

    Clarity does not just appear. You have to find the real decision hiding under the brief, weigh the trade-offs, and state clearly what stays out. That takes clear ownership, not a committee.

  • What does good mean here?

    A shared commitment to quality

    Quality is an agreement between design, engineering, and leadership on what good means for this specific product. Direct customer research keeps that agreement honest.

  • What makes good work repeatable?

    Systems that run on their own

    Standards have to hold when design is not in the room. Clear systems carry the baseline, automated checks catch drift early, and shared principles guide the hard trade-offs.

  • Who owns the decision?

    Partners, not ticket-takers

    No company needs designers who just wait for instructions. I coach people until quality becomes their personal benchmark and they defend their own choices. Real ownership always carries accountability.

Clients & companies

Public institutions, industry and mobility, mostly in places where being wrong has consequences. Much of the work sits under NDA. If you’re curious about specific challenges or patterns, I’m happy to talk.

Write me
  • Volkswagen
  • BMW
  • Deutsche Bahn

Community and speaking

I enjoy exchanging ideas with other designers and leaders, and I like sharing what I learn along the way. Over the past years I’ve had many opportunities to share my knowledge, especially around data and data-first approaches, on stage and together with the community.

Rands Leadership Community

Design Leadership Call

A monthly call inside the Rands Leadership Community, the network of tech leaders around Michael Lopp, author of »Managing Humans«. Design leaders from Europe, the US and Australia, once a month for four years. We bring the problems we can’t take to our own teams.

Conferences

Where I’ve spoken in recent years, from research conferences to practitioner events.

  1. 2019
  2. 2022
  3. 2023
  4. 2025
  5. 2026

Conference links open in a new tab.

Get in touch

Open to conversations about design leadership, trust and complex products.

Write me