Posts

AI Won't Replace Designers. But Designers Who Use It Will Work Differently.

  I used to think coding wasn't part of my job as a designer. My job was to understand users, design flows, create interfaces, prototype them, and hand everything over to developers. Then AI changed the workflow. Not by turning me into a developer. But by making the distance between idea → prototype → product much smaller. That's where AI workflows and vibe coding became interesting to me. I'm not trying to become a developer When I say I use vibe coding, I don't mean that I've suddenly become a software engineer. I still think like a designer. I start with: What problem are we solving? Then: What should the experience be? Then: How should the interface behave? The code comes after that. Tools like AI coding assistants, v0, and other generative tools allow me to turn those decisions into something interactive much faster. Instead of spending hours imagining how an interaction might work, I can sometimes build a rough version and experience it myself. That's a c...
Post a Comment
Read more

What Running My Own E-Commerce Brand Taught Me About Product Design

  What Running My Own E-Commerce Brand Taught Me About Product Design I didn't learn product design only from courses. I learned a lot of it by breaking things in a real business. Before I started seriously pursuing product design, I was running an e-commerce jewellery brand. I was responsible for almost everything: Product photography. Catalogues. Packaging. Marketing. Customer conversations. Orders. Payments. Operations. At the time, I didn't think of these things as “UX problems.” I just thought: This business is becoming difficult to manage. Looking back, I realize I was experiencing product design problems every day. The first lesson: messy workflows create invisible costs Customers could reach us through different channels. Some orders came through marketplaces. Some came through Instagram. Some came through WhatsApp. Information was distributed across different places. That created small problems. A customer would ask about an order. I'd search through conversations....
Post a Comment
Read more

“I Stopped Designing Screens. I Started Designing Decisions.”

  I Stopped Designing Screens. I Started Designing Decisions. What changed when I stopped asking “What should this screen look like?” and started asking “What decision is the user trying to make?” When I started learning UI/UX, I thought good design meant making interfaces look clean. I focused on spacing, typography, colors, components, and whether a screen felt “modern.” Those things matter. But I eventually realized something uncomfortable: A polished interface can still be a bad product. The real challenge isn't creating a beautiful screen. It's understanding what the user is trying to accomplish, what is getting in their way, and what the business needs to achieve at the same time. That changed the way I design. The screen isn't the problem Imagine a user opening a health app before visiting a doctor. At first glance, the problem might seem simple: “They need a place to store their medical records.” So you could design: Upload button Documents section Search Categories...
Post a Comment
Read more

Empathy Is Not Guessing What Users Feel

  Empathy Is Not Guessing What Users Feel I used to think empathy meant understanding how the user feels. Now I think it means something slightly different: Being willing to accept that I might be wrong about them. That's a much harder thing to practice. As designers, it's easy to look at a problem and immediately create a solution. A user can't find something. → Add a button. Users are confused. → Improve the copy. People aren't completing a flow. → Reduce the number of steps. Sometimes those solutions are right. But before designing them, there is a more important question: Why is this happening? Empathy starts with curiosity When I started learning UX, I often approached problems with assumptions. I thought I knew what users wanted because the solution seemed obvious to me. But users don't experience products the way designers do. They don't see our information architecture. They don't know our design system. They don't understand the reasoning behind...
Post a Comment
Read more