Design isn't just about making screens. It's about knowing what should be made in the first place. Yet too many designers jump into Figma (or AI) before asking the right questions. Here's how to break that habit.
At my old job, I watched designers spend entire days in Figma, moving frames around. Screens looked great. Polished, perfect. But when I asked, "What problem are we solving?" Silence.
The same thing is happening now with AI. Instead of thinking first, designers jump into making. The tool changes, but the mistake stays the same.
For years, I told colleagues and mentees: If you don't know what question you're trying to answer, you shouldn't open Figma. But the reality is, in many workplaces, designers aren't given the space to ask those questions. They're expected to execute.
When Speed in Figma Wasn't Enough
I used to be really fast at making interactive prototypes. It gave me an edge. I could take an idea and turn it into a polished, interactive experience faster than almost anyone. But over time, I realized: No one cared how fast I was if we weren't solving the right problem.
The skill was still valuable, but only when used in the right context. The best design work isn't just well-crafted; it's intentional. And when execution takes priority over understanding, even the most beautiful work can become meaningless.
At some point, I started feeling drained. When design becomes just an execution treadmill, when there's no time to step back and ask why, it stops being fulfilling.
Even Figma Knows This Needs to Change
There's a reason Figma is branching out beyond frames. FigJam and Figma Slides aren't about pixel-perfect UI. They're about sense-making, collaboration, and storytelling.
Figma itself sees where things are headed: design isn't just about making things. It's about aligning on what should be made in the first place.
The industry is shifting, but many designers are still stuck in execution mode.
So Before You Open Figma (or AI), Ask:
- What problem am I solving?
- Who is this for, and what do they actually need?
- What's the simplest way to test this? (Maybe a conversation or a Miro board, not a prototype.)
Most of the time, you don't need Figma yet. You need clarity.