Designing with AI — From Prompt to Product — 5. Iterating and Escaping the Generic

19 min read min de lecture
Chapter 05

Iterating and Escaping the Generic

Chapter 5 of 10 · 50%

Chapter objectives

  • Give actionable feedback
  • Recognize the signs of a "generic AI" render
  • Dare a memorable design

Why everything ends up looking the same

Open ten AI-generated landing pages made without direction: you'll see the same page ten times. Purple-blue gradient, rocket emoji in the headline, three cards with soft shadows, an "AI-powered" badge. That's no accident: an AI model produces what is statistically probable in its training data. Without constraints, it converges toward the average of everything it has seen — and the average, by definition, looks like nothing in particular.

Understanding this mechanism changes your posture: the generic isn't a fatality of the tool, it's the default result in the absence of direction. Everything you've built in this course — the brief with don'ts, the design system, the surgical iterations — is precisely the set of constraints that force the model out of its average. This final chapter adds the top floor: demanding critique and owned boldness.

There's also a market dynamic: as everyone generates interfaces, the cost of "decent" collapses. What becomes rare — and therefore valuable — is personality: a design people remember, that they attribute to a specific brand. For Studio Mango, it's the selling point against clients who could "just ask the AI themselves": anyone can get a decent page; few know how to take it upmarket.

Feedback that moves things forward

"It's not great" is useless — to a human or to an AI. The model doesn't know what displeases you: it will change things at random, sometimes damaging what was working. Effective feedback is surgical: "the headline/background contrast is too weak", "the vertical rhythm is irregular between sections 2 and 3", "the CTA gets lost among three elements shouting as loudly as it does". The more precise the feedback, the better the iteration.

The structure that works has three beats, already met in chapter 3: zone (where?), problem (what, in design vocabulary?), direction (toward what?). Add a fourth reflex for long sessions: also say what must be preserved. "The hero is perfect, don't touch it anymore; focus on the pricing section" protects your gains — without that, an AI that regenerates can "improve" what was already validated.

Lock in your gains at each iteration: explicitly name what's validated and must no longer move. It's the creative counterpart of the developer's "don't touch what works".

The critique grid: five questions to ask your mockup

To critique your own mockup rigorously — and not just "by feel" — run it through five questions. One: hierarchy — squinting at the page, what stands out first, second, third? Is it the right order relative to the goal (for Sereno: headline, promise, CTA)? Two: flow — does the eye travel naturally from top to bottom, or does it stumble over elements competing for attention?

Three: consistency — do spacing, radii and weights follow the system everywhere, or do you spot orphan values? Four: accent — does the accent color guide toward the action, or is it sprinkled to the point of meaning nothing? Five: personality — if you mask the logo, can you still guess the brand? This last question is the hardest and the most important: it's what separates the decent from the memorable.

The powerful reflex: hand this grid to the AI itself. It's a surprisingly good critic of its own output when given an evaluation framework — that's structured self-critique. You get a reasoned diagnosis, which you confront with your own eye before deciding on the fixes.

PROMPT
Here is the current Sereno landing page [code or screenshot attached]. Critique it as a demanding art director, along five axes:
1. Hierarchy: what does the eye see 1st, 2nd, 3rd? Is it the right order to convert toward the free trial?
2. Flow: where does the eye stumble?
3. Consistency: list the values (spacing, radii, sizes) that fall outside the design system.
4. Accent: does the accent color guide toward the action or is it diluted?
5. Personality: if you mask the logo, what distinguishes this page from a template?
For each axis: one finding, a score out of 10, and ONE priority fix. Don't propose the fixes yet, just the diagnosis.

The signs of the "AI template"

Here is the checklist of generic-render symptoms — the one Studio Mango pins on the wall. If your mockup ticks several of them, it needs a personality pass before being shown to anyone:

  • Purple or blue-pink gradients everywhere, with no intent
  • Emojis in the headings to "feel lively"
  • Timid spacing, everything crammed
  • Generic soft shadows and rounded corners, identical on every card
  • Default typography (the same average sans-serif from top to bottom, no committed weight)
  • Accent color sprinkled everywhere instead of being reserved for the action
  • Interchangeable filler copy ("Boost your productivity") that could sell anything

If your render ticks these boxes, explicitly ask for boldness: strong typographic choices, a committed accent color, crisp contrast, generosity of space. Note an interesting point: these symptoms are the exact negative of what you've learned. Cramming violates the spacing scale, the diluted accent violates 60-30-10, the limp type violates the ratio scale. The generic isn't a style: it's the absence of a system.

The levers of personality

Escaping the generic doesn't require reinventing everything — it's enough to pull two or three levers with conviction. The first and most powerful: typography. A committed display face for headings (a serif with character, an extreme weight, an unusual width) transforms a page more than any other change. It's the brand's voice: Sereno with a warm serif at 64px no longer looks like any template.

Second lever: the disciplined accent. A single accent color, used in three places maximum, creates more impact than five colors everywhere. Third lever: generous space — doubling the space around the hero is the cheapest way to look premium. Fourth lever: a signature detail — a recurring shape, a consistent illustration style, a polished micro-interaction — that returns across the page like a musical motif. One well-held signature detail beats five scattered ideas.

Boldness isn't accumulation: it's a small number of choices held with conviction. If everything is bold, nothing is — exactly like the accent color.

The two-versions method: safe vs bold

When you hesitate about the level of risk, don't decide in the abstract: ask for two versions. A "safe" version — clean, coherent, risk-free — and a "bold" version — display type, frank accent, less expected layout. The marginal cost is near zero (a few minutes of artifact), and the side-by-side comparison makes the decision obvious, where the theoretical discussion was going in circles.

This method also shines in client presentations: showing safe and bold positions the conversation on "how far do we go?" rather than "do we like it?". The client projects themselves, compares, often picks an intermediate point — and feels like an actor in the direction. Studio Mango will present both tomorrow: it's the mark of a studio that masters its risk palette, not of a studio that can't choose.

flowchart LR
  M["Current mockup"] --> CR["Critique on 5 axes"]
  CR --> S["Safe version: targeted fixes"]
  CR --> A["Bold version: type + accent + space"]
  S --> CH["Side-by-side comparison"]
  A --> CH
  CH --> D["Owned decision + justification"]
The two-versions method: the side-by-side comparison replaces the abstract debate.

Micro-interactions and finishing touches

The last 5% make 50% of the impression. Micro-interactions — the gentle transition of a hover, a progressive reveal on scroll, a field confirming input — signal care. The rule for Sereno: movements that are short (150-250 ms), gentle (natural easing curves, no flashy bounce) and meaningful (every animation communicates something: "you can click", "successfully saved"). A decorative animation that says nothing is noise.

Finishing touches are also the thankless details: real copy instead of lorem ipsum (a credible testimonial with a first name and occupation beats ten "Amazing product!"), empty states and error messages, the favicon, the images' alt attributes. Ask the AI for an explicit "finishing pass": "reread the whole page as a perfectionist: missing transitions, weak copy, neglected details — list everything, then fix it".

Delivering with confidence

Let's recap the road traveled: an intent set in a brief (chapter 1), a coherent and accessible token system (chapter 2), a prototype iterated in a short loop (chapter 3), clean and accessible components (chapter 4), and a pass of critique, boldness and finishing (this chapter). When rhythm, hierarchy and accent are mastered, you deliver a design that has personality — not yet another template. That's what Studio Mango proudly presents to the client tomorrow morning.

A final word on posture: the AI saved you the entire day of execution, but every visible decision on this page went through your judgment. That's exactly the right division of roles — and it's a skill that's gaining value: knowing how to steer the machine toward a result it would never have produced on its own. The taste stays yours; the AI accelerates.

🛠️ Your turn

Context

It's 5 p.m., the day before the presentation. The first complete version of the Sereno landing page is there, but the studio director walked by your desk: "It's clean, but it looks like a template. The client is paying for character." You have the evening to take the page upmarket — without breaking what already works, and with a clear justification for each choice for tomorrow's presentation.

Instructions

  1. Run your mockup through the 5-axis grid (hierarchy, flow, consistency, accent, personality) — you first, then ask the AI for the same diagnosis and compare.
  2. Tick the "AI template" symptom checklist: identify your page's 3 most blatant flaws.
  3. Request a targeted fix for each of the 3 flaws, one per message, explicitly locking in what's validated.
  4. Request a "bold" version in parallel: committed display type, disciplined accent, doubled space around the hero.
  5. Compare the two versions side by side and choose (or compose an intermediate), justifying it in two sentences.
  6. Launch the finishing pass: gentle micro-interactions (150-250 ms), credible real copy, states and neglected details.
  7. Prepare your presentation: three screenshots (before, safe, bold) and one sentence per major choice to defend the direction.
Hint — A single strong accent and lots of space are often enough to escape the generic. And start with typography: it's the lever that transforms the page the most for the least effort.

In summary

  • The generic is the default result of an AI without direction: it converges toward the statistical average of its data.
  • Precise feedback (zone → problem → direction) produces a much better iteration — and locks in what's already validated.
  • The 5-axis grid structures the critique: hierarchy, flow, consistency, accent, personality.
  • The AI is a good critic of its own renders when given a structured evaluation framework.
  • Spot the AI-template symptoms (gradients, emojis, cramming, diluted accent): they're the exact negatives of your system.
  • Four levers of personality: committed typography, disciplined accent, generous space, signature detail.
  • The two-versions method (safe vs bold) replaces the abstract debate with a concrete comparison — internally as with the client.
  • Finishing touches (meaningful micro-interactions, real copy, polished states) make 50% of the final impression.

Quiz — check your understanding

1. Which feedback moves things forward best?

Surgical feedback (zone, problem named in design vocabulary, direction) enables a targeted iteration. Vagueness produces random changes.

2. Why does the AI produce the generic without direction?

Without constraints, the model produces what's most probable in its data — the average of everything, which looks like nothing. The brief, the system and the don'ts are the constraints that pull it out.

3. How do you escape the generic render?

Boldness comes down to a few committed choices: typography with character, a single well-placed accent, generosity of space. Accumulation, by contrast, recreates noise.

4. What is the two-versions method (safe vs bold) for?

The marginal cost of a second version is near zero, and the side-by-side comparison makes the decision obvious. With the client, it positions the discussion on "how far?".

5. What should you do with what's already validated during iterations?

Without explicit locking ("the hero is validated, don't touch it anymore"), a regeneration can "improve" — and therefore damage — what was already working.

6. What is the rule for good micro-interactions in a calming mood?

Every animation must communicate something (clickable, saved…). A decorative animation that says nothing is noise — especially for a meditation app.

Auteur(s)

R

REHOUMA Haythem

Haythem Rehouma est un ingénieur et architecte IA et cloud, formateur et enseignant technique, avec un profil orienté IA médicale, AWS, MLOps, LLM/RAG et vision par ordinateur.