Interaction Designer in Copenhagen.
Hi! I'm Edoardo. I see interactions as the answer to problems between people and the products they use. That took me deep into UX design and fully into building products, with the person (or being) using them always in mind. I'm a practical person: I look for what works, and I prototype early, in whichever form is most useful.
Today I'm a Product Designer at Alice, on AI products: I take features from the first question to the day they reach students.
My path so far
Takeaways from the detours
The journey, detours included, is part of the process
I was lucky with my detours: each one left a side skill I now use every day. Studying film directing gave me communication, and above all storytelling and motion. In Milan, alongside university, I worked as a web and UX designer: more animation, and the reality of shipping a product with real companies and stakeholders. Through all of it, research stayed: a method I carry everywhere.
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 (talking to an AI included).
Tuning the small things
In every product, AI-infused ones included, the small things decide whether people rely on it: when it speaks, when it waits, what it shows. I care about timing, states and motion, and about how each thing is said, from a colour to a line of text, for the person in front of it.
Working with a second pair of hands
AI is in most of my working day as a constant assistant: it helps me learn new tools faster, get through work that used to take much longer, and spend more time on the actual design. It is a running experiment: every day I find a better way to use it, and to work.
Currently working
Product Designer at Alice
Backed by Y Combinator. I work on product decisions across the whole flow and experience of what we build, for a better way to study.
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, re-evaluate or pause. Talking with users is how I find the frictions and the real problems. It shows me what people need, and I bring that to the team so we find the solution together, aligned with those needs.
I go straight to a version of the solution people can actually test: not polished, but working, so we can see whether they get the value it is meant to bring. The method changes every time; right now AI lets me build real working software, not just mockups.
Making
I map every interaction a person can have: every step, every touchpoint, every feeling along the way, from user tests, analytics, experiments and any data I can get. With a flow that detailed, the solution almost builds itself.
Usually in Figma, Paper or similar tools, and more and more directly in code, building with AI agents: reusable components that show the final form of the interface, ready for an engineer to put into the product.
A design system ties the interface to everything else: it sets the overall language and the brand, and it has to be reusable and easy to scale. Today I write it as rules an engineer can read and adapt to the app much faster than starting from a Figma file: a .md file, an HTML site, or a full prototype in the language and standards the engineers already use.
Motion helps people understand a product and feel it: it gives software a personality and says what words do not, always in service of the person using it. I work in After Effects or Figma, or I build my own tools with AI agents to make interactive elements I can test with users and refine directly in code. It skips the long polishing curve of the usual tools and goes straight to the real thing, with settings made for what I need.
Whatever I make has to be usable: by the person using the product, and by the engineer who builds it. I have done many hand-offs and handovers, and they stayed simple because communication comes first, with users and engineers alike.
Deciding
I start from the needs and ask the right questions, then help allocate resources and decide how the product develops. I keep an all-round view of the product and every feature: what is needed, when, whether it is feasible now, and whether it is the right thing to do now.