Designing AI review loops

AI makes it easier to produce a first draft. That is not the same as making good work easier.

The important question is what happens after the draft exists. Does anyone pressure-test the states? Does the copy survive real context? Does the component match the system? Does the code preserve behavior? Does the release note explain risk? Does the human still know why the decision is right?

That is where review loops matter. I do not want AI to be only a builder. I want it to be part of a loop: generate, inspect, critique, revise, verify, and ship. The loop should make the work more legible and less fragile.

Used well, AI can help expose weak assumptions. Used badly, it can make weak assumptions sound finished.

DraftMake it visible

Generate a screen, spec, test, article, migration, or PR candidate.

CritiqueFind risk

Ask for missing states, false assumptions, accessibility issues, and system drift.

ProofVerify

Run commands, browser checks, route checks, schema checks, and human review.

Define the loop before using the tool

The workflow should say what AI is allowed to produce, what it must review, and what proof is required before shipping.

The questions I would use are:

• What is the artifact?
• What is the critique lens?
• Who decides?
• What verification is required?

The mistake is asking for output and treating the first plausible version as the final version. That mistake makes the work look finished while hiding the decision that actually matters. It can make a portfolio page louder, a PR harder to review, or a product surface more fragile than it needs to be.

The artifact I want is a loop definition with draft, critique, revise, verify, and ship steps. It should be plain enough to inspect and specific enough to be useful. If the artifact cannot show the constraint, the decision, and the proof, the story is probably still too vague.

For AI-assisted product work that needs critique, verification, and human judgment before it becomes real, I want the artifact to be useful before it becomes presentable. It should help someone make a decision, review the risk, or explain the tradeoff without needing a private meeting.

The proof is a process where speed increases without losing accountability. I would rather show a narrow proof that survives questions than a broad claim that only sounds impressive. A hiring manager should be able to ask how I know, what I owned, what changed, and what I would do differently next time.

Use AI as a second reviewer

A second model pass can catch issues the builder missed, especially when the prompt asks for specific risks.

The questions I would use are:

• What states are missing?
• What copy is vague?
• What data assumption is hidden?
• What accessibility path could fail?

The mistake is asking AI whether the work is good and accepting a generic answer. That mistake makes the work look finished while hiding the decision that actually matters. It can make a portfolio page louder, a PR harder to review, or a product surface more fragile than it needs to be.

The artifact I want is a critique prompt targeted to the artifact and the risk. It should be plain enough to inspect and specific enough to be useful. If the artifact cannot show the constraint, the decision, and the proof, the story is probably still too vague.

This is where AI-assisted product workflow matters. The work should not depend on taste alone; it should leave a small operating model that another designer, engineer, or reviewer can reuse.

The proof is a review that surfaces concrete risks early. I would rather show a narrow proof that survives questions than a broad claim that only sounds impressive. A hiring manager should be able to ask how I know, what I owned, what changed, and what I would do differently next time.

DesignHierarchy

Information, copy, density, state clarity, and product promise.

EngineeringContract

Data shape, state model, accessibility, performance, and tests.

ReleaseRisk

Migration, rollback, support notes, analytics, and first-hour watch.

Give the reviewer real context

AI critique is weak without context. The review prompt needs product goal, constraints, target audience, and known boundaries.

The questions I would use are:

• What is the product promise?
• What should not change?
• Which design system exists?
• Which constraints matter?

The mistake is asking for critique without the criteria needed to judge the work. That mistake makes the work look finished while hiding the decision that actually matters. It can make a portfolio page louder, a PR harder to review, or a product surface more fragile than it needs to be.

The artifact I want is a review context block pasted above the artifact. It should be plain enough to inspect and specific enough to be useful. If the artifact cannot show the constraint, the decision, and the proof, the story is probably still too vague.

For AI-assisted product work that needs critique, verification, and human judgment before it becomes real, I want the artifact to be useful before it becomes presentable. It should help someone make a decision, review the risk, or explain the tradeoff without needing a private meeting.

The proof is feedback that matches the actual product rather than generic taste. I would rather show a narrow proof that survives questions than a broad claim that only sounds impressive. A hiring manager should be able to ask how I know, what I owned, what changed, and what I would do differently next time.

Ask for failure modes

AI review gets more useful when it is asked to find failure modes instead of praise.

The questions I would use are:

• How can this break?
• What happens with bad data?
• Where can users misunderstand?
• What would support hear?

The mistake is using AI review only to polish language or confirm the chosen direction. That mistake makes the work look finished while hiding the decision that actually matters. It can make a portfolio page louder, a PR harder to review, or a product surface more fragile than it needs to be.

The artifact I want is a failure-mode review pass for UI, code, content, and release notes. It should be plain enough to inspect and specific enough to be useful. If the artifact cannot show the constraint, the decision, and the proof, the story is probably still too vague.

This is where AI-assisted product workflow matters. The work should not depend on taste alone; it should leave a small operating model that another designer, engineer, or reviewer can reuse.

The proof is a draft that gets stronger before it reaches production. I would rather show a narrow proof that survives questions than a broad claim that only sounds impressive. A hiring manager should be able to ask how I know, what I owned, what changed, and what I would do differently next time.

SurfaceWhat to inspect

Route, component, article, migration, flow, or PR diff.

LensHow to inspect

Accessibility, state coverage, design-system fit, copy, data, or release risk.

ReceiptWhat to return

Findings with location, impact, fix, and confidence.

Separate suggestion from decision

A model suggestion is not a decision. The human should record what was accepted, rejected, or deferred.

The questions I would use are:

• Which findings are real?
• Which are out of scope?
• Which are wrong?
• Which need a follow-up ticket?

The mistake is letting generated critique create churn without human prioritization. That mistake makes the work look finished while hiding the decision that actually matters. It can make a portfolio page louder, a PR harder to review, or a product surface more fragile than it needs to be.

The artifact I want is a review disposition table with accepted, rejected, deferred, and why. It should be plain enough to inspect and specific enough to be useful. If the artifact cannot show the constraint, the decision, and the proof, the story is probably still too vague.

For AI-assisted product work that needs critique, verification, and human judgment before it becomes real, I want the artifact to be useful before it becomes presentable. It should help someone make a decision, review the risk, or explain the tradeoff without needing a private meeting.

The proof is a cleaner review trail and less arbitrary iteration. I would rather show a narrow proof that survives questions than a broad claim that only sounds impressive. A hiring manager should be able to ask how I know, what I owned, what changed, and what I would do differently next time.

Review for design-system fit

AI-generated UI often invents patterns that look plausible but do not belong to the local system.

The questions I would use are:

• Which components should be used?
• Which tokens exist?
• Which variants are missing?
• Which local styles are suspicious?

The mistake is shipping a pretty draft that creates new design debt. That mistake makes the work look finished while hiding the decision that actually matters. It can make a portfolio page louder, a PR harder to review, or a product surface more fragile than it needs to be.

The artifact I want is a system-fit checklist that maps output to existing components and tokens. It should be plain enough to inspect and specific enough to be useful. If the artifact cannot show the constraint, the decision, and the proof, the story is probably still too vague.

This is where AI-assisted product workflow matters. The work should not depend on taste alone; it should leave a small operating model that another designer, engineer, or reviewer can reuse.

The proof is AI output that respects the product's operating model. I would rather show a narrow proof that survives questions than a broad claim that only sounds impressive. A hiring manager should be able to ask how I know, what I owned, what changed, and what I would do differently next time.

Review for data realism

AI drafts usually assume clean data. A review loop should force ugly records, missing values, stale states, permissions, and long content.

The questions I would use are:

• What data shape is assumed?
• Which fixtures are ugly?
• What state is missing?
• Does mobile still work?

The mistake is approving a screen that only works with model-perfect content. That mistake makes the work look finished while hiding the decision that actually matters. It can make a portfolio page louder, a PR harder to review, or a product surface more fragile than it needs to be.

The artifact I want is a fixture review pass with ideal, damaged, and restricted data. It should be plain enough to inspect and specific enough to be useful. If the artifact cannot show the constraint, the decision, and the proof, the story is probably still too vague.

For AI-assisted product work that needs critique, verification, and human judgment before it becomes real, I want the artifact to be useful before it becomes presentable. It should help someone make a decision, review the risk, or explain the tradeoff without needing a private meeting.

The proof is a UI that survives production-shaped data. I would rather show a narrow proof that survives questions than a broad claim that only sounds impressive. A hiring manager should be able to ask how I know, what I owned, what changed, and what I would do differently next time.

Attach verification to the loop

The loop ends with proof, not with a better paragraph from the model.

The questions I would use are:

• Which command proves it?
• Which route was opened?
• Which screenshot matters?
• Which migration or asset was checked?

The mistake is using AI critique as a substitute for running the product. That mistake makes the work look finished while hiding the decision that actually matters. It can make a portfolio page louder, a PR harder to review, or a product surface more fragile than it needs to be.

The artifact I want is a verification receipt attached to the AI review notes. It should be plain enough to inspect and specific enough to be useful. If the artifact cannot show the constraint, the decision, and the proof, the story is probably still too vague.

This is where AI-assisted product workflow matters. The work should not depend on taste alone; it should leave a small operating model that another designer, engineer, or reviewer can reuse.

The proof is work that stays grounded in actual behavior. I would rather show a narrow proof that survives questions than a broad claim that only sounds impressive. A hiring manager should be able to ask how I know, what I owned, what changed, and what I would do differently next time.

Keep prompts reusable but not generic

Reusable review prompts are useful when they include slots for context, artifact, constraints, and expected output.

The questions I would use are:

• What repeats?
• What must be customized?
• Which examples help?
• What output format reduces review cost?

The mistake is saving vague prompts that produce vague critique. That mistake makes the work look finished while hiding the decision that actually matters. It can make a portfolio page louder, a PR harder to review, or a product surface more fragile than it needs to be.

The artifact I want is a small prompt library with task-specific review lenses. It should be plain enough to inspect and specific enough to be useful. If the artifact cannot show the constraint, the decision, and the proof, the story is probably still too vague.

For AI-assisted product work that needs critique, verification, and human judgment before it becomes real, I want the artifact to be useful before it becomes presentable. It should help someone make a decision, review the risk, or explain the tradeoff without needing a private meeting.

The proof is a repeatable AI workflow that still respects each product problem. I would rather show a narrow proof that survives questions than a broad claim that only sounds impressive. A hiring manager should be able to ask how I know, what I owned, what changed, and what I would do differently next time.

Show AI loops as candidate evidence

The hiring signal is not that I used AI. The signal is that I used it with judgment, review discipline, and verification.

The questions I would use are:

• What did AI accelerate?
• What did human review change?
• What proof was added?
• What risk was avoided?

The mistake is presenting AI work as magic output without showing ownership. That mistake makes the work look finished while hiding the decision that actually matters. It can make a portfolio page louder, a PR harder to review, or a product surface more fragile than it needs to be.

The artifact I want is a case-study sidebar with AI loop, accepted critique, rejected critique, and QA receipt. It should be plain enough to inspect and specific enough to be useful. If the artifact cannot show the constraint, the decision, and the proof, the story is probably still too vague.

This is where AI-assisted product workflow matters. The work should not depend on taste alone; it should leave a small operating model that another designer, engineer, or reviewer can reuse.

The proof is a portfolio story that shows modern workflow and senior judgment. I would rather show a narrow proof that survives questions than a broad claim that only sounds impressive. A hiring manager should be able to ask how I know, what I owned, what changed, and what I would do differently next time.

What I would show in the work

The public version should show the working artifacts, not only the final opinion. For AI-assisted product work that needs critique, verification, and human judgment before it becomes real, I would include the matrix, the state map, the review checklist, and the before-and-after decision path. Those artifacts make the work feel authored because they reveal how the decision was made.

I would also include what I did not do. That is often where judgment is clearest. Not every useful idea belongs in the first version. Not every dashboard needs live sync. Not every component needs a new prop. Not every AI suggestion belongs in the PR. Naming the boundary helps the reader trust the result.

The page should make the work inspectable without turning into internal documentation. I want enough specificity for an engineering manager to ask serious follow-up questions, and enough restraint that the story still reads like product judgment instead of a dump of process artifacts. The best version makes the artifacts feel inevitable: this was the pressure, this was the decision, this was the receipt, and this is why the outcome is believable.

AcceptKeep

The critique is valid and the change improves the product.

RejectExplain

The critique is plausible but not relevant to this scope.

DeferTrack

The critique is real but belongs to a follow-up.

Downloadable companion

This topic deserves a companion resource: an AI review-loop prompt sheet for UI critique, code review, content QA, accessibility, and release risk. It should be useful as a working file, not a decorative download. The resource should help someone repeat the review, pressure-test the decision, and carry the same quality bar into their own product work.

I would keep it concise: one page if possible, with fields for context, constraint, decision, evidence, owner, and follow-up. The value is not the file format. The value is that the artifact turns the article into something someone can use.

Review checklist

Before publishing this work, I would run a short review against the same standard I use for product changes:

• Is the product pressure concrete?
• Is my ownership clear?
• Is the system constraint named?
• Is there at least one artifact that proves the decision?
• Does the artifact show a real tradeoff?
• Is the metric or signal honest about its limits?
• Are support, operations, accessibility, or release risks named when relevant?
• Does the writing explain what I intentionally left out?
• Can a recruiter skim the point quickly?
• Can an engineer ask a deeper technical question?
• Does the downloadable resource make the idea reusable?
• Would I be comfortable defending the claim live?

That checklist keeps the work from becoming a polished but vague page. It also protects the voice. The goal is not to sound like a process manual. The goal is to make the product judgment visible enough that a hiring team can trust the story.

Implementation notes

The implementation version of this idea should be small enough to ship and specific enough to prove. I would start by naming the route, artifact, owner, and verification path before adding polish. If the work touches content, I would check the source body, generated route, metadata, sitemap, and social image. If it touches UI, I would check desktop, mobile, long content, empty state, keyboard path, and the most likely failure state. If it touches data, I would name the source of truth, freshness, migration path, and what support or product should see after launch.

That implementation note matters because AI-assisted product workflow can drift when the work moves from idea to code. A good article can describe the principle, but a good product change needs the boring details: filenames, states, commands, rollback, ownership, and the reason the first version is intentionally narrow.

I would also write the follow-up before shipping. Follow-up is not a sign that the work is incomplete; it is a sign that the boundary is known. The first version should solve the risky problem, prove the pattern, and leave the next step visible. That is how small teams move quickly without pretending every release is final.

For portfolio proof, these implementation notes are useful because they make the story harder to fake. They show that I understand the difference between a good idea, a shippable version, and a maintainable system. They also give an interviewer concrete places to dig: why this scope, why this artifact, why this verification path, and what changed after the first release.

Case-study packaging

If this became a Work section detail, I would package it as a small evidence stack. The top should explain the product pressure in plain language. The middle should show the artifact and the operating decision it supported. The bottom should show the verification and the follow-up. That structure keeps the story from becoming either a pretty screenshot or a private engineering note.

The captions matter here. A caption should not say "dashboard view" or "component states" and stop there. It should explain what the reader is supposed to learn: this matrix shows why the first version stayed narrow, this state map shows where recovery mattered, this QA note shows how the release was proved, or this event taxonomy shows how product language became measurable.

I would keep the packaging honest by including one caveat. The caveat might be a metric limitation, a data freshness issue, a rollout boundary, a support dependency, or a follow-up that intentionally stayed out of scope. That caveat does not weaken the case study. It makes the judgment feel real.

The final test is whether the page creates a better conversation. If the artifact helps someone ask a sharper question about product judgment, implementation detail, or release proof in real live interviews together, it belongs in the story.

Interview angle

In an interview, I would explain this through review loops that make AI output more inspectable instead of merely faster. The story should start with the product pressure, then move into the system constraint, the artifact, and the proof. That order keeps the answer grounded. It also gives the interviewer several places to go deeper: data, frontend architecture, design systems, support, migration, accessibility, or release process.

The strongest version of the answer includes a tradeoff. I want to be able to say what I chose, what I left alone, and how I knew the work helped. That is more credible than presenting every project as a clean win.

The hiring signal

AI review loops are a hiring signal because they show I can use AI as leverage while keeping taste, verification, and product responsibility human.

That is the level I want this site to communicate. The work should show taste, but it should also show operating judgment. It should make me look like someone who can enter a real product system, understand the messy middle, ship the useful version, and leave enough proof for the next person to trust it.