Best PracticesLesson 21 of 23
Iterating Based on Feedback
1 min readClaude Code for DesignersUpdated Feb 18, 2026
Saying "redo it" gets you a different version of the same problem. Saying "make the button taller and add more space between the inputs" gets you exactly what you wanted. This lesson is about that difference, plus using git to safely try things you might want to undo.
Iterating Based on Feedback
Ask for Small Changes, Not Rewrites
Don't:
I don't like this design, redo it
Do:
Make the button taller and add more space between the inputs
Use Version History
If you don't like a change, you can always go back to a previous version on GitHub:
- View your commit history on GitHub
- Click on an old version
- Compare what changed
Collaborate Effectively
- Show your prototype to teammates early (don't wait for perfection)
- Ask specific questions: "Does this button feel clickable to you?"
- Document design decisions in code comments
Iteration as a habit
- Made small surgical changes instead of asking for full rewrites
- Used git history as a safety net for risky experiments
- Showed work early and asked specific questions instead of "what do you think?"
You can refine. Now the question is how to hand it off cleanly. Next lesson.