What a Restaurant Menu Taught Me About Information Hierarchy
Waiting forty minutes for a table, I studied a menu instead of my phone. It turned into the best design lesson I had all year.
UX researcher in Lyon. Listening to users for a living and designing what they actually need.
Waiting forty minutes for a table, I studied a menu instead of my phone. It turned into the best design lesson I had all year.
A small confession about letter spacing, optical illusions and the difference between correct and right.
Most button debates are not about colour. They are about which action matters most, and that is a decision, not a style.
A practical, timeboxed process for turning raw interview notes into findings your team will actually read and act on.
I abandoned every elaborate weekly review I tried. This stripped-down version is the first one I have kept for a full year.
The screen a new user sees before adding any data tells them what your product is for. Most teams design it last, if at all.
Questions about the future produce wishes. Questions about recent, specific moments produce evidence. Here is how to make the switch.
Limiting my day to three tasks made me calmer and more productive, right up until it didn't. A candid two-month report.
We stopped treating research as an archive and started treating it like a product, with users, formats and a maintenance plan.
Every open tab was a small promise to my future self. Breaking those promises on purpose turned out to be a relief.