Iteration should reduce uncertainty against an approved direction. Uncontrolled AI variants often create attractive but unrelated work, making the client re-decide the whole brief each round.
Lock the Direction Before Varying It
Create a direction lock with audience, message, approved visual properties, must-keep elements, forbidden moves, applications and decision owner. Then log every request as one of four types: correction, refinement, extension or direction change.
Change one axis per round: symbol construction, composition, color balance, typography or image treatment. Produce three purposeful variants and state the hypothesis behind each. Version files as project_concept_round_variant, and keep the selected parent visible.
Approved direction: [facts]
Must keep: [list]
This round tests only: [one variable]
Generate three described variations. Preserve all locked elements.
Explain how each responds to the request; do not add new brand claims.
Worked Example
A client says, “Make it more premium.” The designer does not regenerate the identity. It asks what decision should change. The client means the social templates feel crowded. The round tests spacing only: increased margins, fewer type sizes and a simpler information block. Logo, palette and photography remain locked.
The client selects variant B. The decision log records why; the other variants remain evidence, not alternative directions waiting to return in round six.
Set a round limit and response window in the scope. If new stakeholders arrive after approval, recap the locked decision and price or schedule any reopened direction separately. AI makes variants cheap to render, but review, judgment and rework still consume professional time.
Failure Cases to Diagnose
- Treating vague feedback as a generation prompt.
- Changing multiple variables without a hypothesis.
- Showing 20 variants and transferring the design decision to the client.
- Losing the approved file in chat attachments.
- Calling a scope-changing direction request a minor revision.
- Using AI to imitate a competitor the client mentions.
🇵🇰 Pakistan Angle
Clients may send feedback through voice notes or mixed Roman Urdu/English. Convert it into a written decision recap and ask for confirmation. Record who can approve; feedback from multiple family members or business partners can otherwise create an endless loop.
When a low-bandwidth review is necessary, send a numbered contact sheet with three compressed proofs and keep the editable sources offline. The client can reply with a variant number and one reason without downloading a large project file. Remove private customer names, phone numbers, and unrelated brand assets before placing any feedback in an AI tool.
Hands-On Exercise
- Write a direction lock for one concept.
- Translate three vague comments into testable requests.
- Create one three-variant round changing a single axis.
- Record selection and reason.
- Identify whether any request changes scope.
Completion Rubric
- Approved properties and decision owner are recorded.
- Feedback is classified before iteration.
- Each round changes one clear variable.
- Variants have hypotheses, not random differences.
- Selection and scope changes are documented.
Sources
Key takeaway: Strong iteration keeps the approved direction fixed, translates feedback into one decision and produces only variants that test it.