About· Experience and career· Berlin
Researcher by
conviction, builder
by curiosity.
Ten years of enterprise UX taught me one thing: the hardest design question is not how something looks, but whom people trust, and when. Working with agents is that question in its purest form.
I ask questions until the answer fits, write methods down so teams and agents do the same work, and run trails around Berlin in between.
My route through this field was not planned. It started with web design for a fashion retailer and ran through fitness, fintech and digital health before it arrived at rail infrastructure. What connects them is not an industry but a recurring problem: a system that knows more than the person using it, and an interface that has to close that gap without lying about it.
That is also why I write. Most of what I learn is only useful to other people if it leaves my head in a form they can check. The essays are here.
Not what I made.
How I decided.
Outcomes are easy to claim. Two pieces of work where the decision could have gone the other way, and what followed from taking the harder route.
01 DB Systel
The obvious move was more research readouts. I built async-first documentation instead, so knowledge is available when someone needs it rather than when a meeting is scheduled.
Enterprise scale at Deutsche Bahn: UX research strategy, DesignOps, and stakeholder management across tech, business and compliance. Open exchange sessions where stakeholders meet real users instead of reading about them.
The conversation shifted from "do we need this?" to "how do we fix this?". And it laid the groundwork for everything after: before an agent can take over research, research has to be documented, standardised and verifiable.
- UX research strategy and DesignOps
- Stakeholder management across tech, business, compliance
- Async documentation as an organisational stance
- Foundation for automated reporting flows
02 actio
I did not propose a design system. I named the problem and let the system be the answer, pitched as "we ship twice as fast". That is what got it resourced.
Tokenised, component-based, built together with frontend. Scope for v1 deliberately kept small. The foundation held long after I left.
In hindsight it was pattern codification before I had the word for it: standards, documented, adoptable by people who were not in the room.
- Head of Brand Design, built a team of five
- Token architecture aligned with frontend
- Scope for v1 intentionally kept small
- Two times faster UI delivery
The whole route
Fourteen years, nine roles, five industries. Listed plainly, because a career is a sequence of contexts, not a claim.
- – Senior UX Consultant DB Systel GmbH, Deutsche Bahn · Berlin UX research strategy and DesignOps for enterprise rail platforms. Stakeholder management across tech, business and compliance.
- – Head of Brand Design actio GmbH Promoted within ten months. Built and led a design team of five. Conceived the company design system and tokenised it with frontend.
- – User Experience Designer actio GmbH End-to-end product design for digital health products. Research, wireframing, prototyping, validation.
- – Senior Product Designer Haalo Technology GmbH End-to-end UX for a B2B SaaS core product, from concept to handoff.
- – UX Consultant P3 Group UX consulting and interface design across enterprise and tech clients.
- UX Designer fairr.de GmbH UX design for a digital investment and pension platform.
- – Screendesigner McFIT Global Group GmbH Visual and web design for one of Europe's largest gym chains.
- – Webdesigner Holy Fashion Group Web design across brand touchpoints for a fashion retail group.
- – Webdesigner Web.ItFine UG Early career. Web design and front-end development at a small agency.
What I am
working on
Agentic UX in enterprise supply chain software, where a wrong automated decision has a physical consequence somewhere in the world. An agent that reorders the wrong quantity does not produce a bad screen, it produces a truck.
Alongside that, the essays. They are the part of this work that is public and checkable, and the reason this site exists.