Failure PatternDecision layer
The Retouch-By-Committee Trap: Why Image Editing Stalls at Client Approval
Symptom: A single hero banner for a retainer client enters round seven of revisions while the campaign launch date slips by nine days. Root cause: Approval authority is diffuse: brand, performance, and regional client leads each hold informal veto power, so every retouch pass invites a new stakeholder to reopen settled decisions.
By InnovaAI ResearchPublished Updated
How do you recognize it?
- •A single hero banner for a retainer client enters round seven of revisions while the campaign launch date slips by nine days.
- •Feedback arrives as three conflicting Slack threads, two marked-up screenshots, and one verbal note from a client stakeholder who was not on the original brief call.
- •The same skin-tone correction is applied, reverted, and reapplied across separate export files because no one owns the master layered source.
- •Junior designers spend 60 percent of their week on cosmetic tweaks to assets that were already approved at the concept stage.
- •Version filenames multiply into hero_final_v4_APPROVED_use-this-one.psd, and delivery teams cannot confirm which file actually shipped.
Why does it happen?
- •Approval authority is diffuse: brand, performance, and regional client leads each hold informal veto power, so every retouch pass invites a new stakeholder to reopen settled decisions.
- •Agencies sell retouching as an open-ended line item inside a fixed retainer, which removes any cost signal that would force the client to consolidate feedback.
- •The creative retouching layer is treated as the same operational pipeline as compression and resizing, so it inherits automation-style turnaround expectations without the governance that creative work requires.
- •Layered source files live on individual designer machines rather than a shared asset library, so each revision restarts from a flattened export instead of the editable original.
How do you fix it?
- •Cap retouch rounds in the statement of work at two, then price round three and beyond as a change order at a stated hourly rate.
- •Nominate one client-side approver in writing before the first retouch pass begins, and route all feedback through that person only.
- •Store every layered master in a shared library with a locked naming convention, and treat the flattened export as a derived artifact that is never edited directly.
- •Run a 15-minute pre-retouch call to capture all stakeholder notes at once, then freeze the brief and log any post-freeze request as a scope event.