"Most design problems aren't 'design' problems. They're 'Thinking' problems.They're 'Clarity' problems.They're 'Too-many-tabs-open' problems. More prototyping. More pixel-shifting. More polish in Figma alone isn't going to help you with those. For me, without clear thinking, Figma just results in more confusion, more mess, and more mockups than I can mentally manage. The Problem: Figma wasn't the bottleneck - my thinking was Like most UX/UI designers, I used to jump straight into Figma the moment I had a product idea or a design task to complete."
"I'd tweak colors, mock up screens, build components, and then... get stuck. Not because I didn't know how to design, but because I didn't know what I was designing - who it was for, how it solved the problem, and what the business actually needed from it. I was designing aimlessly.Which meant I was redesigning constantly.Which meant I was wasting time. This is what most of my design students come into my course doing too, and it's why I teach..."
Many designers begin work in Figma immediately, tweaking colors, building components, and prototyping before defining the problem. Lack of clarity about who the design is for, how it solves the problem, and what the business needs causes aimless designing and repeated redesigns. Visual polish and more prototypes alone increase confusion, mockup volume, and cognitive load. The true bottleneck is unclear thinking rather than the tool. Prioritizing problem definition, user intent, and business objectives before detailed mockups reduces wasted time and produces more focused, actionable designs.
Read at Medium
Unable to calculate read time
Collection
[
|
...
]