"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."
Designers often jump into Figma without defining the problem, audience, or business needs. This leads to aimless design, constant redesigns, wasted time, confusion, and mental overload. More prototyping and pixel-level polish in Figma cannot fix unclear thinking. Figma can amplify confusion by generating more mockups and mess when the underlying understanding is missing. The real bottleneck is insufficient clarity about who the product serves, how it solves a problem, and what business outcomes are required. Teaching should prioritize thinking, problem definition, and clarity before spending time on tools and visual polish.
Read at Medium
Unable to calculate read time
Collection
[
|
...
]