Luca Moretti@lucamoretti · October 22, 2026

I’m Luca, a product designer in Italy. My favourite design question is usually a very ordinary one: what is someone trying to get done here?

That question is also a useful place to start a new profile. I could fill this page with polished screens, but I would rather explain why a screen exists, which decision was difficult, and what I would want to learn before calling the work finished. If you are building a business, that probably tells you more about working with me than a beautiful mockup on its own.

I chose to try Doop because I want my work to sit alongside conversations with people from other professions. Designers can become very good at discussing design with other designers. I’m equally interested in hearing from the person managing bookings, selling a service, answering support questions, or trying to explain a complicated offer. Those are the people who can tell us where a product is making life harder.

My plan here is quite practical. I’ll share small observations in the Feed: a label that could be clearer, a form that asks too much too soon, or a way to explain the next step before someone has to guess. When motion makes an idea easier to understand, I’d like to explore Watch for a short walkthrough. I want each example to be understandable even if designing products is not your job.

I also want to leave room for questions rather than presenting every opinion as a rule. A booking flow for a busy salon has different pressures from a tool someone uses once a year. Context matters. The useful conversation is often about which trade-off fits this situation, not which screenshot looks cleaner in isolation.

Building my brand on Doop will start with making that approach visible. I’ll use a clear profile, keep my name consistent, and write about the problems I enjoy thinking through. I want someone to recognise a way of working: curious about the user, willing to explain a choice, and comfortable changing direction when better information appears.

I’ll be looking for people to learn from as well. A thoughtful reply to someone’s actual problem feels like a better introduction than sending a generic message about my services. Over time, I hope those conversations can lead to collaborations and paid projects, but I’m not treating a follower count as proof that a business is working.

When I do describe an offer, I want the basics to be easy to find: the kind of problem I can help with, the scope we need to agree on, and what a first conversation would involve. That is part of designing the experience too. Nobody should need to decode a profile just to understand what happens next.

For now, tell me about one small thing in an app or website that repeatedly slows you down. No design vocabulary needed. What were you trying to do, and where did it become harder than it should have been?