Iterative Design and Feedback Tools
Iterative design and feedback is a short loop, build a rough version, test it with real users, learn what's wrong, refine, repeat, that trades one big upfront bet for a series of small, correctable ones.
Build, test, learn, refine: a short loop that circles back to the start once the lesson lands.
Reach for this when…
- You're about to spend months building something nobody outside the team has seen yet.
- Feedback only arrives after launch, when it's expensive to act on.
- A 'finished' version keeps missing what users actually needed.
How to run it
- Build the roughest version that lets someone react to something real.
- Put it in front of actual users or stakeholders, not colleagues being polite.
- Gather specific feedback: what worked, what confused them, what they'd change.
- Make the smallest change that addresses what you learned.
- Repeat with the same or a new group until the thing holds up on its own.
A worked example
Situation. Amine Ben Salah ran Atelier Carthage, a product design agency in Tunis, Tunisia, hired to design packaging for a client's new range.
Applied. Instead of the usual single polished concept, his team put three rough cardboard mock-ups in front of twelve shoppers in the first week.
Result. Two of the three concepts were rejected outright within days, for reasons the team hadn't considered, saving weeks of refining designs the client's customers were never going to want.
The catch
Iteration only works if you're willing to genuinely change the thing based on what you hear, teams often run the loop as theatre and ship the original plan anyway. It also needs real users, not colleagues being kind, or the feedback just confirms what the team already believed. A string of small refinements can also drift a long way from the original brief without anyone noticing.
If every round of feedback comes back 'looks great', you're testing with the wrong people.