
A reading guide for design leaders
The Design TransitionDesign the behavior.
The practice of designing products that generate, decide, and respond.
7 published parts · Free to read
The shift
What changes when AI changes the product?
AI generates the screens, the flows, and the first prototype now. Design did not shrink. It got promoted, from producing artifacts to specifying behavior, owning the quality bar, and designing for output nobody can fully predict. This series is for designers and design leaders living through that shift, and for the product, engineering, and executive leaders who have to reorganize around it. It is the design seat of The Product OS. A new part every Tuesday, written against that week's findings. Part 1 is the thesis.
Start here
The reading order.
Follow the series from the first idea to the latest field note.

Part 01
17x the Code, 1.3x the Releases. Design's Job Is the Spec Now.
Figma shipped a spec editor for agents as its design chief reported 17x more code and 1.3x more releases. Design's job moved from screens to the spec.
Read the essay

Part 02
Your Prototype Made Decisions Nobody Made. Who Owns the Spec Now?
Ravi Mehta found an AI PRD full of decisions nobody made. When the prototype is free, the PM owns the question, design owns the behavior, nobody owns the rest.
Read the essay

Part 03
Reddit's Handoff Ships a Draft PR. Design Should Hand Engineering the Tests.
Reddit's feature capsule hands engineering code that may or may not merge. When prototypes are production-shaped, design hands engineering test rows, not code.
Read the essay
Continue the series
- 04LangChain's Design Agent Updates Its Own Design System Weekly. Someone on Design Should Sign the Diff.LangChain's design agent learns its own design system. When agents read the system, design owns the context budget, the reasons, and the weekly diff.
- 0584,000 Chats Show When Users Re-Ask the AI. Design Should Own the Repair Rate.A study of 84,000 ChatGPT and Gemini chats counts when users re-ask. When you can't predict the output, design the states and own the repair rate.
- 06People Paid More for AI-Designed Games. Make Your Design Beat the AI Version.Buyers paid 27% more for games an AI designed alone than for amateurs' games. Research's new job: prove a design beats the AI-only version with real users.
- 07Copilot Adopters Added 1.4 Hours of Collaboration a Month. That's Critique. Plan It.Copilot adopters added 1.4 hours of collaboration a month, much of it vetting AI output. That's critique with no format. Plan it, split it, and log it.
In The Product OS
The chapters this seat runs on.
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.
- Design Just Got Promoted7 min read
- The Receipt and the Work8 min read
- Specifying Behavior7 min read
- What Design Owns Now7 min read
- You Cannot Mock a Distribution7 min read
- The Shape of Uncertainty7 min read
- Undo Is a Design Primitive8 min read
- Disclosure Without Overwhelm7 min read
- Latency Is Interface7 min read
- Designing Refusal7 min read
- Recovery and Trust Repair8 min read
- The Rubric Is the Spec9 min read
- Design's Kill List8 min read
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