Part 2
UX
In delegated systems, the user’s burden shifts from operating the interface to judging what the system hands back. This part covers the relationship the product creates, how results get evaluated, why reactions beat feedback, and how trust forms across the first fourteen moments. It then turns to the frontend: AI states, the handoff from Figma to code, and recovery when a result is wrong.
Tools in this part
- Relationship critique · Fill-in card
Chapter 9 · Design the Relationship, Not the Screen
- Relationship critique: manual or autopilot · Example
Chapter 9 · Design the Relationship, Not the Screen
- The design standard · Use it checklist
Chapter 9 · Design the Relationship, Not the Screen
- Make the result inspectable · Fill-in card
Chapter 10 · Ease of Evaluation Is the New Ease of Use
- Make the result inspectable: a vendor agreement review · Example
Chapter 10 · Ease of Evaluation Is the New Ease of Use
- An evaluation audit · Use it checklist
Chapter 10 · Ease of Evaluation Is the New Ease of Use
- Situational prototype · Fill-in table
Chapter 11 · Reactions Are Solid Gold. Feedback Is Cheap.
- Watch the silence · Fill-in table
Chapter 11 · Reactions Are Solid Gold. Feedback Is Cheap.
- An automation prototype · Example
Chapter 11 · Reactions Are Solid Gold. Feedback Is Cheap.
- Run a reaction-first session · Use it checklist
Chapter 11 · Reactions Are Solid Gold. Feedback Is Cheap.
- The first fourteen · Sequence map
Chapter 12 · The First Fourteen: Where Trust Forms Before Value Is Explained
- The first fourteen: an AI review product for a compliance lead · Example
Chapter 12 · The First Fourteen: Where Trust Forms Before Value Is Explained
- Map your first fourteen · Use it checklist
Chapter 12 · The First Fourteen: Where Trust Forms Before Value Is Explained
- Deliver intent, not output · Fill-in card
Chapter 13 · Front-End Design Engineering Is the Product
- Deliver intent, not output: action preview and consent · Example
Chapter 13 · Front-End Design Engineering Is the Product
- Design the arc, not isolated screens · Fill-in card
Chapter 13 · Front-End Design Engineering Is the Product
- A production-ready design test · Use it checklist
Chapter 13 · Front-End Design Engineering Is the Product
- State inventory · Fill-in table
Chapter 14 · Every AI State Is a UX State
- State inventory: a draft that lost its policy record · Example
Chapter 14 · Every AI State Is a UX State
- Run a state inventory · Use it checklist
Chapter 14 · Every AI State Is a UX State
- One component conversation · Fill-in card
Chapter 15 · From Figma to Frontend Without the Translation Tax
- One component conversation: the frame from the opening · Example
Chapter 15 · From Figma to Frontend Without the Translation Tax
- Vertical slices · Sequence map
Chapter 15 · From Figma to Frontend Without the Translation Tax
- A translation-tax audit · Use it checklist
Chapter 15 · From Figma to Frontend Without the Translation Tax
- Safety net · Fill-in card
Chapter 16 · Error Recovery Is Product Strategy
- Recovery path · Fill-in card
Chapter 16 · Error Recovery Is Product Strategy
- Recovery path: the unavailable research library · Example
Chapter 16 · Error Recovery Is Product Strategy
- A recovery review · Use it checklist
Chapter 16 · Error Recovery Is Product Strategy
Next part
Do people check every AI result twice?
Start with the checklist to spot what needs attention.
Run the self-checkBook a 30-minute call. Bring one result screen and we’ll look at how it’s evaluated and recovered.
Book a call