Iterating with AI: The Feedback Loop

Iterating with AI

The first output is rarely perfect. Here's how to refine through iteration.

The Iteration Mindset

Expectation Setting

• First prompt: Get the structure right (60-70% there)
• Round 2-3: Refine design and functionality
• Round 4+: Polish details

Don't Aim for Perfection First Try

It's faster to iterate than to craft the perfect initial prompt.

The Iteration Process

Step 1: Initial Build

Start broad, get the foundation: "Build a [type of app] for [audience] with [core features]."

Step 2: Structure Review

Check the basics:

• Are all sections present?
• Is the layout logical?
• Does navigation work?

If not: "Add the missing [section]. Move [element] to [location]."

Step 3: Functionality Review

Test interactions:

• Do buttons work?
• Do forms submit?
• Is data saved?

If not: "Fix the [feature]. It should [expected behavior]."

Step 4: Design Polish

Refine visuals:

• Colors correct?
• Spacing consistent?
• Typography readable?

Prompt: "Adjust the design: [specific changes]."

Step 5: Mobile Review

Check responsive:

• Does it work on phone?
• Are touch targets adequate?
• Is text readable?

Prompt: "Fix mobile layout for [section]. [Specific issues]."

Effective Iteration Prompts

Adding Features

"Add [feature] to the [page/section]. It should [description of functionality]."

Modifying Existing

"Change the [element] to [new behavior/appearance]. Keep everything else the same."

Removing Elements

"Remove the [element] from [location]. Adjust the layout to fill the space."

Fixing Issues

"The [feature] has a bug: [description]. Fix it so that [expected behavior]."

Iteration Patterns

Broad to Specific

1. Overall structure
2. Section by section
3. Component by component
4. Detail by detail

Priority-Based

1. Fix broken functionality
2. Address major design issues
3. Improve user experience
4. Polish details

Page by Page

1. Complete homepage
2. Move to second priority page
3. Continue through site

Common Iteration Cycles

Design Iteration

"Make the hero section taller." → "Add more padding to the feature cards." → "Increase contrast on the CTA button." → "Add subtle hover animations to cards."

Functionality Iteration

"Add user authentication." → "Show user name in navigation when logged in." → "Add logout button to user menu." → "Redirect to dashboard after login."

Content Iteration

"Change the headline to [new text]." → "Update feature descriptions to [new copy]." → "Add testimonials with [content]." → "Update footer links to [links]."

When to Stop Iterating

Good Enough Signals

• Core functionality works
• Design is clean and consistent
• Mobile experience is good
• Users can accomplish their goals

Diminishing Returns

If you're spending more time on prompts than the improvement is worth, ship it.

Get Real Feedback

At some point, real user feedback is more valuable than more iteration.

Tips for Efficient Iteration

Batch Similar Changes

Instead of 5 prompts for colors, do one: "Update colors throughout: primary to #3B82F6, secondary to #10B981, backgrounds to #FAFAFA."

Be Specific About Scope

"Only change the header section, leave everything else unchanged."

Reference Previous State

"The previous version had [feature], add it back while keeping the new [feature]."

Save Progress

If something is working well, note it. You may want to revert later.

Key Takeaways

1. Plan for iteration—first output won't be final
2. Review systematically: structure → function → design → polish
3. Be specific in iteration prompts
4. Batch similar changes
5. Know when to ship