the iteration trap

there’s a version of iteration that makes work better. and there’s a version that just makes it different.

i’ve been in the second version enough times that i’ve started to recognise the feeling. it usually starts around round three or four of feedback. the work has been through the team, through stakeholders, through someone’s offhand comment in a meeting. each round you’ve adjusted something. some of the adjustments were right. some were appeasements. by round five it’s hard to tell which are which.

what you have at the end isn’t worse, necessarily. it’s more defensible. every specific choice has a reason — because someone asked for it. but the thing the work was originally trying to argue has quietly dissolved. you can justify every pixel and not be able to say what the work is for anymore.

the thing that makes this hard to catch is that it doesn’t feel like failure. iteration feels like responsiveness. incorporating feedback feels like doing your job. the work is still moving, which feels like progress.

but there’s a difference between feedback that sharpens the argument and feedback that replaces it. “the hierarchy isn’t working” sharpens. “can we try it with the logo bigger” replaces. and when you’re in the middle of a project under time pressure, trying to keep eight stakeholders moving, you don’t always have the bandwidth to sort those in real time.

so you incorporate both. and then you incorporate the next round. and then you’re explaining a design to a client that you no longer fully believe in, using reasons that aren’t quite yours.

the way i’ve tried to stay honest about this is to keep the original brief somewhere visible. not as a constraint — the brief is often wrong — but as a reference for what the work was trying to resolve. when a round of feedback comes in, i ask whether acting on it moves toward that resolution or away from it. sometimes the answer is clearly away. sometimes you still do it anyway, because the relationship matters or the timeline doesn’t allow a fight. but at least it’s a conscious choice rather than accumulated drift.

the other thing that helps is being able to say, at any point in the process: here is what this work is arguing. not describing — arguing. if you can’t say it in a sentence, the work has probably already drifted. getting back to that sentence is usually more useful than another round of visual refinement.

if you’ve got work that’s been through a lot of hands and you’ve lost the thread — not sure if it still has a clear argument, not sure what’s worth defending — i offer structured design critique. not aesthetic notes. an honest read of whether the work still has a position. $75.