Interaction Designer in Copenhagen.
Hi! I'm Edoardo. I see problems as interactions to create or improve, between people and the products they use. That took me deep into UX design and into building the product itself, always with the person using it in mind. I'm a practical person: I look for what works, and I prototype early.
Today I'm a Product Designer at Alice, on AI products: I take each feature from the first question to the day it reaches students.
My path so far
Takeaways from the detours
The journey, detours included, is part of the process
My path was never a straight line, and I made each piece useful. I studied cinema and helped with communication across media, so storytelling and an eye for motion came with me. Between Milan and Copenhagen I freelanced in web and UX design, with some animation, on projects with companies. Research stays a side interest I keep close.
Prototyping in any material
Code on fake data, a scene in Unity, a breadboard: the question picks the material, not the habit. So I can test an idea early, in whatever form answers it fastest.
Tuning the small things
In AI products the small things decide whether people rely on the system: when it speaks, when it waits, what it shows. That eye for timing, states and motion is the part of the job I like most.
Working with a second pair of hands
AI is in most of my working day: extra hands, not a second head. It lets me take a design all the way to a working build, while the decisions stay mine.
Currently working
Product Designer at Alice
Alice is a Y Combinator company. Day to day I work on product decisions there, across the whole flow and experience of what we build.
Eight things I do
Finding out
I decide the one question a round must answer and who takes part, run the sessions, and close each round on a written decision: go, redesign or pause. Sessions with users settle a choice; team reviews find friction, but they are opinion, so I keep them apart. At Alice, three rounds with students in 2026: 24, 9 and 7 people.
I build the cheapest thing that can answer the question in front of me, and I decide before building what answer would make me drop the idea. Most prototypes get thrown away, on purpose: the ones that survive are the ones that changed a decision.
Making
I map every path a person can take and every touchpoint on it before any screen exists: where information sits, what is asked once and then remembered, what happens when something goes wrong. Most of that work is choosing what not to show yet.
What a piece of interface is for and how it should behave is mine, set out up front, including what would count as broken. AI agents write the code; I check it on the real product before it counts as done. This site was made the same way.
I write the rules components are built by, their options, states and spacing, and apply them across a product. An exception is fine when it is deliberate and listed, and a rule that would break more than it fixes gets dropped in the open.
I give an interface a character through how it moves: timing, easing, how it settles. I read motion the way an animator does, in keyframes and speed curves. It lives under rules it never breaks (one body, smooth on any screen, no jolt), tuned by hand until it feels alive. At Alice, the animated character of the assistant, released in 2026.
I make things other people pick up and use without asking me first: sites for small associations in Italy, CUT in Prato among them, visual identities for small cultural groups, and the files behind them, made to explain themselves. The test is whether someone can use it the day after I hand it over.
Deciding
Inside the design role I carry a share of the product: turning open questions into specifications someone can build from without asking me, and proposing the order things ship in. At Alice, product management of the AI tutor in summer 2026, then UX advice.