irreplaceable

Irreplaceable › Guides › AI design frameworks

Frameworks · AI product design

Frameworks for AI product design decisions

AI can make the screen. It can't decide how much an agent should do alone, which metric would hide a failure, or where friction belongs. These 6 short frameworks help you make those calls.

By Sarit Elisha, founder of Irreplaceable · Updated October 10, 2026

Open the Library

The frameworks with the checklist, AI failures and senior takes, searchable. Free.

01 · AI behavior design

The autonomy dial

Decide what an agent does alone, with undo, after asking, or never.

  1. Cost: what does a mistake cost the user, in money, time or face?
  2. Reversibility: can it be undone completely, and for how long?
  3. Who else is affected: does the action reach anyone besides the user?
  4. Set the level: low on all three → just do it; reversible → do it with undo; costly or touches others → ask first; irreversible, legal or medical → never.

Worked examples: what should the agent do on its own?

ActionLevelWhy
Email agent: Archive newsletters you never openJust do itLow stakes and easy to find again.
Email agent: Unsubscribe you from mailing listsDo it + undoReversible, but annoying if wrong. Do it and offer an undo.
Email agent: Draft replies to customersJust do itA draft is only a suggestion; nothing leaves your inbox.
Finance agent: Categorize this month's expensesJust do itPure organizing, trivially fixable.
Finance agent: Pay the electricity bill, same as last monthDo it + undoRoutine and expected. Pay with a cancel window.
Finance agent: Send the quarterly report to your accountantAsk firstSharing financial data outside. Confirm the recipient.

82 more examples across 18 kinds of agent →

Practice this in a drill →

02 · Owning outcomes

Metric pairs

Never ship an AI feature with an adoption metric alone.

  1. Adoption (used, accepted, clicked) is paired with quality (edited after, undone, reopened, returned next week).
  2. Speed (handle time, time to reply) is paired with resolution (solved, no repeat contact).
  3. Engagement (searches, session length) is paired with goal reached (purchase, task done).
  4. Add a guardrail: the number that must not get worse, agreed before launch.

Practice this in a drill →

03 · Trust

Friction scaled to stakes

Uniform friction is ignored. Put it only where a wrong answer hurts.

  1. Sort answer types by harm: trivia, preferences, money, health, legal, safety.
  2. Low stakes: clean answer, no disclaimer.
  3. High stakes: sources, a clear limit, a human or professional route.
  4. Measure the behavior: how often people verify high-stakes answers.

Practice this in a drill →

04 · Problem framing

The reframe canvas

Turn a solution request into a problem worth solving.

  1. Write the ask in their words, and the fear behind it.
  2. Find one fact you already have that points to the user's real problem.
  3. Pick a metric that measures the problem, not the feature.
  4. Choose the cheapest first move that could prove you wrong this week.

Practice this in a drill →

05 · Influence

Win the room

How seniors stop bad ideas without becoming the blocker.

  1. Speak their metric first: deadline, revenue, demo.
  2. Offer a safer scope that still gets them a yes.
  3. Bring one concrete example, not a principle.
  4. Attach a guardrail metric you'll own after launch.

Practice this in a drill →

06 · Judging AI output

Reviewing AI output

A five-pass check before anything AI-made ships.

  1. Constraints: did it respect what the user actually asked for?
  2. Claims: is every fact sourced, and is uncertainty shown?
  3. Actions: did it act before asking on anything costly or shared?
  4. Exits: can the user undo, edit, or reach a human?
  5. Harm: who could this hurt, and does it hide that in fine print?

Practice this in a drill →

From framework to reflex

A framework helps when you remember to use it.

Drills give you the decision under a little time pressure, until the framework is how you think.

↑