7 Questions That Expose Your Design Blind Spots
The best designers don't have better answers—they have sharper questions. These seven are worth returning to on every project.
What problem are you actually solving?
Not the problem in the brief. The one that made someone write the brief. If you can't name the pain in one sentence a stranger would nod at, you're decorating, not designing. Write it on a Post-it. Stick it to your monitor. If a feature request doesn't serve that sentence, it's a distraction with good manners.
The blank page test
Strip the branding, the copy, the familiar icons. Can a user still find their way? If not, your design is leaning on context that won't always be there.
Who did you design for that isn't you?
You know the keyboard shortcuts. You know where the 'skip' button hides. That's a superpower and a curse. Watch one real person use it. Not a usability test—just coffee and curiosity. Count the times they hesitate. Each one is a tiny apology your interface owes them.
The details are not the details. They make the design.
What would you remove if you had to cut 30%?
Constraints are the fastest route to clarity. Pretend the page costs $1 per pixel. What disappears? Usually the things you added because you were afraid of silence. White space isn't empty—it's where the user thinks. Give them room to breathe and they'll forgive almost any missing feature.
The 5-second glance
Show the screen for five seconds, then hide it. Ask what they remember. If the answer is 'a lot of options,' your hierarchy is a democracy where nothing wins.
Does this decision make the next one easier?
A good design system is a series of small mercies to your future self. The button you align today saves an hour next sprint. The naming convention you fight for now prevents a migration later. Design isn't just what you ship—it's the trail you leave for the next person who opens the file.
