The systematic approach to refining design work through cycles of feedback and improvement.
Iteration is how good becomes great. It's the disciplined process of making something, evaluating it, and making it better—repeated until quality meets standard. Effective iteration balances exploration with convergence, knowing when to push further and when to call it done.
What Iteration Accomplishes
Improvement Through Feedback
Each cycle:
- Reveals weaknesses
- Surfaces edge cases
- Tests assumptions
- Guides enhancement
Convergence Toward Quality
Iteration narrows toward excellence:
- First passes are rough
- Middle passes are functional
- Final passes are polished
Risk Reduction
Iteration catches problems early:
- Test before commitment
- Fail small, not big
- Build confidence through validation
Types of Iteration
Internal Iteration
Refining within the design process:
- Designer reviews own work
- Team critiques together
- Multiple passes before client sees anything
This is where most refinement should happen.
Client Iteration
Incorporating client feedback:
- Present → feedback → revise → present
- Typically 2-3 rounds for most projects
- Should refine direction, not restart exploration
Testing Iteration
User or market feedback:
- Test design with target audience
- Identify issues through observation
- Revise based on findings
More common in product design, but applicable to brand when possible.
The Iteration Cycle
1. Create
Make something reviewable:
- Complete enough to evaluate
- Not so precious that feedback hurts
- Focused on specific aspects to test
2. Evaluate
Assess what exists:
- Against objectives (does it work?)
- For quality (how good is it?)
- For completeness (what's missing?)
3. Decide
Determine next action:
- What needs to change?
- What should stay?
- Is another cycle needed?
4. Refine
Make improvements:
- Address identified issues
- Implement decisions
- Prepare for next evaluation
5. Repeat (or Complete)
Continue until:
- Quality meets standard
- Objectives are achieved
- Time or budget requires stopping
Managing Iteration Rounds
Define Scope Per Round
Each round should focus:
Round 1: Major direction and concepts
- Fundamental approach
- Core creative idea
- Strategic alignment
Round 2: Design development
- Refinement of chosen direction
- Application exploration
- Detail development
Round 3: Polish and finalization
- Fine-tuning
- Edge cases
- Production preparation
Set Expectations
Clients should understand:
- What changes are appropriate in each round
- What constitutes a "revision" vs. new work
- How many rounds are included
- What additional rounds cost
Prevent Scope Creep
Keep iteration focused:
- Reference original brief
- Distinguish refinement from new requests
- Document scope changes
- Renegotiate when appropriate
Giving Effective Critique
In Self-Critique
Questions to ask yourself:
- Does this solve the stated problem?
- What's the weakest element?
- Would I be proud to show this?
- What would I do with more time?
- What's my gut saying?
In Team Critique
Constructive critique principles:
Be specific: "The weight difference between the mark and wordmark feels unbalanced" vs. "Something's off"
Focus on work, not person: "This layout could have more breathing room" vs. "You crowded this"
Offer alternatives: "Have you considered centering the tagline?" vs. "The tagline is wrong"
Ask questions: "What led you to this color?" vs. "That color is wrong"
Balance: Note what's working alongside what needs attention
Critique Formats
Desk crit: Informal, quick feedback at the desk Pin-up: Work displayed, team reviews together Formal review: Scheduled, structured critique session Digital review: Comments in Figma, recorded video feedback
Receiving Feedback
From Clients
Listen first: Resist defending immediately Understand the concern fully Ask clarifying questions
Evaluate feedback: Is this valid? Does it improve the work? Is this preference or requirement? Is there an underlying concern beneath the surface comment?
Respond thoughtfully: Acknowledge valid points Explain trade-offs if relevant Propose solutions if you disagree with suggested fixes
Document clearly: Capture what was said Confirm your understanding Track what you'll address
From Team
Stay open: Check ego at the door Assume good intent Look for the useful in every comment
Distinguish: Essential vs. optional Opinion vs. expertise Quick fixes vs. major rework
Avoiding Iteration Traps
Endless Iteration
Symptoms:
- Work never feels done
- Each revision opens new issues
- Deadlines repeatedly slip
Solutions:
- Time-box iteration rounds
- Define "good enough" criteria
- Force decisions with deadlines
- Accept diminishing returns
Superficial Iteration
Symptoms:
- Changes only address obvious issues
- Deep problems persist
- Work plateaus in quality
Solutions:
- Ask harder questions
- Seek outside perspective
- Challenge fundamental approach
- Don't protect early decisions
Iteration as Procrastination
Symptoms:
- Comfortable work on non-essential refinement
- Hard problems avoided
- Progress feels productive but isn't
Solutions:
- Prioritize highest-impact issues
- Address difficult problems first
- Recognize avoidance behavior
- Set minimum viable quality, then enhance
Revision Whiplash
Symptoms:
- Feedback contradicts previous feedback
- Changes ping-pong between options
- Client (or team) can't decide
Solutions:
- Document feedback sources and rationale
- Confirm understanding before revising
- Highlight contradictions explicitly
- Force prioritization
Knowing When to Stop
Quality Indicators
Work is ready when:
- Objectives from brief are achieved
- No significant weaknesses remain
- Further changes are marginal improvements
- You're proud to deliver it
Practical Indicators
Stop when:
- Time runs out
- Budget is exhausted
- Client has approved
- Diminishing returns are clear
The 90% Rule
Getting from 90% to 100% often takes as much effort as 0% to 90%. Know when 95% is good enough—perfection is often not worth the cost.
Iteration Documentation
Version Control
Track iterations:
- Clear file naming (v1, v2, v3 or dates)
- Don't overwrite—save new versions
- Annotate what changed between versions
Change Log
Document what changed and why:
- Client requested X
- Team identified issue Y
- Designer improved Z
Useful for handoff and future reference.
Decision Record
Track decisions made:
- What was decided
- Why it was decided
- Who approved it
- What alternatives were rejected
Prevents revisiting settled questions.
Iteration in Different Contexts
Logo Design
Typical rounds: 2-3 concept rounds, 2-3 refinement rounds
Focus areas:
- Core form and proportion
- Typography refinement
- Color optimization
- Size and application testing
Brand Identity
Typical rounds: 3-4 overall, iterating across elements
Focus areas:
- Primary logo
- Visual system components
- Application mockups
- Guidelines development
Design Systems
Iteration approach: Continuous, ongoing
Focus areas:
- Component refinement
- Pattern validation
- Documentation improvement
- User feedback incorporation