Design is one of the few jobs where "more polish" almost always feels like the right answer — and is almost always the wrong one. Productivity advice for designers tends to be generic ("timebox your work," "batch similar tasks") and skips the actual problem: knowing when something is done. The 6 focus types help name what's actually happening when you can't stop tweaking the spacing.
The focus problems designers actually face
"One more pass" is a polish loop
Each iteration genuinely improves the work — until it doesn't. Without external constraints, the brain's error-detection bias treats every micro-issue as worth fixing. The result: shipped work declines while quality plateaus.
Critique anxiety eats hours
A lot of design time goes into pre-emptive polish to defend against critique that may never come. The work was good 3 hours ago. The 3 extra hours weren't actually for the user.
Tool overhead is invisible
Switching between Figma, references, Slack, and the brief eats more cycles than the design work itself. Most designers undercount this.
Energy management ≠ time management
A 3-hour design session is not three 1-hour sessions glued together. Creative energy is non-fungible, and most calendars treat it like a commodity.
Which focus types are most common
Designers cluster heavily into three focus types — each with a distinct failure mode and a different fix.
Why You Stall at 90%
🔄Always Working, Never In It
🚀High Ignition, Low Sustain
The 2-minute quiz tells you which one fits your specific pattern, and the type page explains the underlying neuroscience and what to do about it.
Tactical changes that actually move the needle
Set a ship constraint, not a quality constraint
"This is done at 4pm" works better than "this is done when it's good." The brain's error-detector will always find more to fix; only an external constraint stops the loop.
Use staged feedback, not late feedback
Show the work at 30% and 70%, not just 95%. Late feedback triggers a polish-redo cycle. Early feedback is cheaper and shapes the work before it's been polished into a corner.
Separate exploration time from execution time
Two different cognitive modes. Mixing them — "I'll just explore one more direction" mid-execution — burns days. Block them separately.
Cap reference-gathering
30 minutes of reference work, then close the tabs. Reference rabbit-holes look productive and aren't.
Standard productivity advice was built for a generic worker who doesn't really exist. The 6 focus types name which brain pattern is creating your specific failure mode — which is the only place from which a system that survives can be built.
Frequently asked questions
Am I a perfectionist or just thorough?
Thorough work plateaus — at some point more time stops improving the result. Perfectionism keeps fixing past the plateau. If your work was 90% done two hours ago and is still 90% done now, that's the polish loop.
How do I stop over-polishing?
External ship constraints, not internal ones. "I'll stop when it's good" doesn't work because your error-detector never agrees. "I'll stop at 4pm and ship whatever's there" does.
Is Figma making my focus worse?
Figma is fine. The pattern that hurts is the always-on collaborative cursor — knowing you're being watched triggers a different kind of work (defensive polish) than solo work. Block out solo design time without sharing the file.
Should I use timeboxes for design?
Depends on your type. For Perfectionist Polishers, ship constraints are essential. For Sprint Starters, the issue is sustaining energy past Day 2. The 6-type quiz tells you which problem you're actually solving.
Find your focus type in 2 minutes
10 questions. No signup needed. Get your type, the neuroscience behind it, and a system designed for your specific pattern.
Take the Free Quiz →