The Design Operating Model

What actually changed, why the artifact stopped being proof that judgment happened, how to write a rule with a failure condition, and where design's ownership line sits now that everyone in the building can generate.

• 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 at any point in the last twenty years.Template: The six operating rulesRead →
• 02The Receipt and the WorkWhy the artifact became the unit of credit, and what replaces it as proof that judgment happened.Template: Design decision record, one page, four fields
• 03Specifying BehaviorThe core method. How to write a rule with a failure condition instead of a principle.Template: Constraint template with twenty worked examples
• 04What Design Owns NowThe boundary conversation with engineering and PM, restated for a world where all three can generate.Template: One-page ownership map

The open problems nobody has named yet. Uncertainty, undo, disclosure, latency, refusal, and the thirty seconds after the system is confidently wrong.

• 05You Cannot Mock a DistributionNo final state to draw. Design the range: best case, worst acceptable case, refusal.Template: The range spec, three columns
• 06The Shape of UncertaintyHow a product says it is not sure without looking broken. Confidence, hedging, silence, asking.Template: Uncertainty pattern library, first pass
• 07Undo Is a Design PrimitiveWhat undo means when an agent acted at 3am on the user's behalf. Reversal, notification, and the window between them.Template: The undo checklist
• 08Disclosure Without OverwhelmHow much reasoning to show, to whom, and when showing it costs trust instead of building it.Template: Disclosure ladder, five levels
• 09Latency Is InterfaceWaiting was a spinner problem. Now it is a relationship problem, because the user does not know if anything is happening.Template: Latency states by duration band
• 10Designing RefusalWhat the product will not do, said in a way that reads as competence rather than limitation.Template: Refusal copy patterns
• 11Recovery and Trust RepairWhat happens in the thirty seconds after the system is confidently wrong.Template: Trust repair sequence

Rubrics, failure inventories, downside exposure for interface decisions, and research that runs at generation speed instead of once a quarter.

• 12The Rubric Is the SpecEval-driven design. Taste that executes without you in the room.Template: The design rubric template, flagship download
• 13Scoring Your Own WorkWho scores, what disagreement means, and when to change the rubric instead of the work.Template: Review protocol, thirty minutes
• 14The Failure InventoryList the ten worst plausible outputs of a feature before you design the good one. That list is a design doc.Template: Failure inventory worksheet
• 15Downside Exposure for InterfacesWhich interface mistakes are recoverable, which are not, and how the interface should differ between them.Template: Exposure grid
• 16Evidence as an AssetMost companies re-learn the same thing every planning cycle because nobody owns what they know.Template: The evidence register
• 17Research at Generation SpeedContinuous over project-based. Where synthetic users work and where they lie.Template: Weekly research cadence
• 18Reading Behavior You Did Not DesignInstrumenting a product whose surface is assembled at runtime. What a funnel even means now.Template: Measurement starter set

Apprenticeship moves from production to judgment. What to ask for instead of a portfolio of screens, what to kill, and what a design org looks like when generation is free.

• 19The Ladder, RebuiltApprenticeship moves from production to judgment, and here is how you actually teach it.Template: Twelve-week judgment curriculum
• 20Hiring for JudgmentPortfolios of screens tell you nothing now. What to ask for instead.Template: Interview loop, including the four-generated-options exercise
• 21The New PortfolioFor the individual reader. Decisions, constraints, rubrics, and the thing you killed.Template: Portfolio structure
• 22Design's Kill ListRituals that survive because they have a meeting attached. Every kill gets a replacement in the same paragraph.Template: The kill list, with replacements
• 23Team ShapeRatios, roles, and what a design org looks like when generation is free.Template: Three org patterns by company stage

Weekly, per sprint, per quarter, and who owns each. Your first ninety days on a team that has none of this, and the case you will have to make to a CEO who read that design is a bottleneck.

• 24The Operating CadenceThe whole handbook as a calendar. Weekly, per sprint, per quarter, and who owns each.Template: The cadence one-pager
• 25Your First Ninety DaysA leader arriving at a team that has none of this. Sequence, first fights, first wins.Template: Ninety-day plan
• 26The Case You Will Have to MakeTalking to a CEO who read that design is a bottleneck. Framed as capacity the company is currently wasting.Template: The one-slide argument