Cucù, Viola here!

I usually start with the problem and the people behind it. Before thinking about solutions, I try to understand who we're designing for and what they're actually trying to accomplish. From there, I look for both quantitative and qualitative insights to get a clearer picture of what's really going on. That context helps guide the direction and prevents jumping too quickly to conclusions. Then it's time to explore ideas, challenge assumptions, and turn concepts into prototypes that can be tested and validated as early as possible. Simple on paper. Messier in reality. Assumptions keep getting challenged, validation sometimes comes later than expected, priorities shift and new insights pop up along the way. It's rarely a straight line, but I've always liked wavy, wobbly ones anyway.