AI-generated illustration of a designer working on an AI product

The Product OS · the design seat

Design the behavior.

Design moves from producing artifacts to specifying behavior: the rubric, the states, and the system agents generate from.

What this seat owns

Behavior and the quality bar: the rubric agents build against, the states around output nobody can predict, and the repair rate that says which state failed.

When building is cheap, the outcome is decided by the loop from customer to adoption. One loop needs one owner. The CPO owns the whole product outcome, and product, design, product marketing, and forward deployed engineering run it together. See the whole OS.

  1. 01CustomerField signal from deployments, support, and usage, read daily. Measured in hops and days from finding to fix.
  2. 02 · leadsSpecThe problem, the behavior, the claim, and the eval that says it works. Measured by the eval pass rate.
  3. 03 · leadsBuildAgents and Product Builders take the spec to working software. Measured by the repair rate in use.
  4. 04StoryPositioning and proof that buyers, sellers, and AI assistants read, shipped in the same release as the build. Measured in story lag, the days until assistants describe a change correctly.
  5. 05AdoptionVerified jobs done on every path, with the cost per job beside it. The number moves, or the loop runs again.

The handbook

14 chapters for this seat.

How to do the work, chapter by chapter. Every seat starts from the same core.

See this section in the full handbook →
  1. 01Design Just Got PromotedThe claim that design is lost contains a category error. Drawing got cheap. Deciding got more valuable, and there is more to decide than in twenty years.7 min read
  2. 02The Receipt and the WorkThe design file was never the work. It was the receipt, and it stopped working as one the moment anyone could produce one in ninety seconds.8 min read
  3. 03Specifying BehaviorA principle has never stopped anyone shipping anything. A constraint is a rule you can catch being broken, the only kind that survives generated output.7 min read
  4. 04What Design Owns NowWhen design, PM, and engineering can all generate, the old handoff boundaries stop describing anything. The argument moves to who decides.7 min read
  5. 05You Cannot Mock a DistributionThere is no final state to draw when the output is assembled at runtime. What you specify instead is a band, and everything inside it ships without your review.7 min read
  6. 06The Shape of UncertaintyHow a product says it is not sure without looking broken. There are four moves, and the wrong one is why products read as falsely confident or hedged.7 min read
  7. 07Undo Is a Design PrimitiveUndo used to mean the last thing you did. It has to mean the thing the system did while you slept, which is three design problems instead of one.8 min read
  8. 08Disclosure Without OverwhelmShowing everything is not transparency. It is a way of making the user responsible for checking work they never asked to supervise.7 min read
  9. 09Latency Is InterfaceWaiting used to be a spinner problem. It is a relationship problem now: the user cannot tell if anything is happening or if they are still needed.7 min read
  10. 10Designing RefusalRefusal is the most under-designed surface in AI products and the one users judge fastest, because a bad refusal is indistinguishable from a broken product.7 min read
  11. 11Recovery and Trust RepairThe thirty seconds after your product is confidently wrong decide whether the person keeps using it. Almost nobody designs that moment.8 min read
  12. 12The Rubric Is the SpecYour taste lives in a recurring meeting, which caps quality at what you can personally review. A rubric is that taste in a form that runs without you.9 min read
  13. 13Scoring Your Own WorkA rubric review is a different meeting from a critique. Scores, disagreements classified, and one decision: ship, fix, or change the rubric.7 min read
  14. 14Design's Kill ListA ritual belongs on the kill list when it produces a receipt rather than a decision. Nine of them, each with the replacement that does the same job.8 min read

Short answers

Questions this seat gets asked.

All answers →

Part of The Product OS

One loop. Five seats.

This seat runs one part of the loop from customer to adoption, under the CPO. See how the other seats connect to it.

See the whole Product OS