Busy ≠ Useful
There’s a version of a design day that looks incredibly productive. Tabs open across the screen. Artboards multiplying. Versions saved as final, then final_v2, then final_final_v2. Color palettes explored type pairings tested, margins adjusted by two pixels, then adjusted back.
Hours pass. The file is unrecognizable from the morning. But nothing has really moved forward.
I’ve had a lot of those days. And for a while, I mistook them for progress. Movement felt like momentum. A fuller canvas felt like better thinking. The more I touched the work, the more it seemed like I was taking it seriously.
The problem is that busyness in design is very easy to perform. Even to yourself.
Get Looks Right’s stories in your inbox
Join Medium for free to get updates from this writer.
It’s easy to keep exploring when you’re not sure what you’re looking for. It’s easy to add a new section to a layout when the existing one isn’t working but you don’t yet know why. It’s easy to try a bolder font, a softer palette, a different grid, not because the brief is asking for it, but because doing something feels better than sitting with the discomfort of not knowing.
Iteration has a good reputation. So does exploration. And they should, they’re real parts of the process. But they can also become a place to hide. When the problem isn’t clear, making things feels like solving things. It isn’t, always. I started noticing this when I’d look back at a long work session and struggle to explain what changed and why. The file was busier. The thinking wasn’t. I’d added a lot but decided very little. And decisions, actual grounded ones, are what move work forward.
Not output. Not volume. Not hours logged.
There’s also something uncomfortable about stillness in design. About opening a brief, reading it carefully, and just thinking for a while before touching anything. It doesn’t look like work. It doesn’t feel productive in the way that filling an artboard does. But that quiet time, where you’re actually trying to understand the problem before solving it, is often where the useful stuff happens. A full file and a solved problem are not the same thing. Some of the clearest design decisions I’ve seen come from people who made fewer of them, not more. Who spent time figuring out what the work actually needed, and then did that, without the extra layers, the backup options, the just-in-case explorations left in the file like evidence of effort.
The work didn’t look busy. It looked considered. And I think that’s the difference. Busy is motion. Useful is direction. One fills the day. The other fills a purpose.
Takeaway: If you can’t explain why you made a change, you probably made it to feel productive, not to solve something. Before adding more to the work, ask what the work actually needs. Busyness is easy to generate. Useful decisions take longer but they’re the only ones that move anything forward.
