Why empathy isn't optional in UX
Empathy isn't about being nice, it's about understanding context. On curiosity, observation, and better questions.
Read on UX Studio →Senior Product Designer who starts with the real problem, makes complexity understandable, builds it with the team, stays close to the outcome, and learns enough to unblock the work
I design for complex, high-stakes products, the kind with messy workflows, technical constraints, and real operational weight behind them. Research, systems thinking, and increasingly hands-on execution, for startups and teams that need someone who can hold all three.
Research, data and observation until I know what is actually in the way. If it is beyond me, I go at it until it is not.
Messy workflows, technical constraints and dense information, turned into something a person can act on. What you ask for, and in what order, is the product.
I ask questions and go find the answer where it lives. Understanding why someone disagrees gets further than proving them wrong, and knowing what to trade away is part of the job.
I like seeing what gets built, measuring what happened, and changing it from there. I would rather find out early and cheaply than be right on paper.
HTML so a content team did not need a developer. An app and its database for a rescue with no budget. Not to become an engineer (yet), but to know what I am asking for.
Different industries, and the same person on the other side: somebody at work. A driver mid-route. An analyst comparing funds for a client. A compliance officer who cannot miss a sanctioned supplier. A volunteer with an animal in one hand. Half of them are not at a desk, and that changes what a screen is allowed to ask for.
Checkout and growth on a funnel that already beat benchmark. 30% faster, 10% less drop-off.
An operations tool for an all-volunteer animal rescue, designed and built end to end, on my own.
Data visualization for a fund comparison tool, in a product where accessibility is not optional.
A crowdsourced delivery network built from 0 to 1. I wrote the offer, the sign-up and the app.
For people whose job is checking whether a company is what it says. A domain I knew nothing about.
Lu is always thinking from the user's perspective, and invites the whole team to learn from them too.
Developer | Jimdo
She's super organized and makes handoffs seamless. Her Figma files are the gold standard.
Product Designer | Jimdo
Lu is proactive and always curious. She makes sure everyone is aligned before moving forward.
Engineering Manager | Jimdo
I came into design through journalism, and I never really left it behind: how a product explains itself is part of whether it works. Two pieces from my time at UX Studio, one about understanding people, one about the words you hand them.
Empathy isn't about being nice, it's about understanding context. On curiosity, observation, and better questions.
Read on UX Studio →Products tell a story whether we design it intentionally or not. Why content deserves a seat at the table from day one.
Read on UX Studio →Senior Product Designer, 8+ years across different industries and three countries. I came into this through communication and journalism, and I have always been more interested in understanding people than in designing screens. Everything I have built is a tool somebody uses at work, which is not an accident any more.
I am a generalist by choice. Research, roadmap calls, dev handoff, and increasingly the build itself. I move fast without losing structure: Argentina taught me the first part, Germany the second.
What I want next is a small team doing something that matters, where the distance between a decision and its consequence is short enough that I am still around for it.
Senior Product Designer based in Munich, Germany, working across UX research, product discovery, interaction design, design systems, accessibility, prototyping, and complex B2B software. Experience across marketplaces, logistics, asset management, SaaS and data-intensive products.