About
Designer, Engineer, Researcher. Not always in that order.
My career path looks like someone shuffled three different people's resumes and stapled them together. I've looked at products from many different perspectives. This shapes how I bring data and humans closer together.
I build frameworks on solid foundations
Ambiguity is where the work starts. Every product has patterns that predate me — legacy decisions, workarounds, mental models nobody documented. I spend a lot of time here before I design.
So before I propose anything, I map the territory: structured audits, stakeholder interviews, building a shared picture of what's actually happening. At Celonis this meant auditing 15+ canvas interfaces before touching anything. On peace process tools it meant sitting with researchers and lawyers until I understood not just their tasks but how they thought about them. I design after I understand, not before.
Data is my material
I design interfaces that allow people to explore data, explain data, understand the messiness of their data, make decisions based on data. Figma wasn't built for this — it can't transform real data into something visual while keeping the design malleable. So I prototype heavily using AI-assisted code. An interactive prototype with real data communicates faster than any PRD.
But building fast creates its own trap. I force myself to understand the system before executing, explore multiple directions before committing, and kill ideas that aren't working — even when the AI really wants to convince me they do. Knowing when the AI is wrong matters more than knowing how to prompt it.
Data is my method
I'm a data visualization designer because I love data — including the data about my own designs. I rely heavily on usage analytics to understand existing frictions and map the impact of design interventions against them.
At Celonis, this means tracking how changes to the visualization system affect user behavior across the product. At Life Lessons, it meant developing KPIs from sales data and platform telemetry to understand what was actually driving growth — which products retained customers, where the drop-offs were. Design had done its job. The data showed us what to focus on next.
Product Designer
Celonis · Berlin
PhD, Computer Science
University of Edinburgh · Edinburgh
Research Associate
Urban Complexity Lab · Potsdam
HCI & Visualization Research Intern
Autodesk Research · Toronto
Founding Designer
Life Lessons · Berlin
Data Visualization Engineer
Nokia Bell Labs · Cambridge
MA, Urban Futures
Fachhochschule Potsdam · Potsdam
Co-Founder
Thinkfarm Berlin · Berlin
Creative Director Digital
sinnwerkstatt Medienagentur · Berlin
UX Designer
sinnwerkstatt Medienagentur · Berlin
BEng, Printing Technology
Berliner Hochschule für Technik · Berlin
I live in Berlin with my family. I have two kindergarten-age kids — turns out complexity was never really a choice anyway.