Frameworks
Frameworks turn the argument into things you can use.
Browse the complete set by name or by the tenet it supports. Each card opens into a working diagram, usage prompt, and source chapter.
From The Practice of Product Authorship
Authorship Practice
The six commitments that constitute the practice of product authorship over time: standards, point of view, taste, responsibility, consistency, reflection.
From Designing Behavior, Not Just Interaction
Behavior Design Questions
A working list of questions to ask when designing behavior rather than interaction.
From Prototype the Behavior
Behavior Prototype Checklist
What a prototype should test before it is styled: assumption, trigger, system response, visibility, user control, failure case, recovery path.
From Designing Behavior, Not Just Interaction
Behavior Spec
A structured template for stating a feature as a behavior rather than an interaction: trigger, inputs, confidence, system action, user control, visibility, correction, backoff.
From Repositioning Without Pretending
Credible Repositioning Triangle
Names the three legs of an honest career reposition — real capability, visible proof, clear language. Removing any leg collapses the position.
From The Era of the Screen-Only Builder Is Ending
Layers of Product Value
Shows how product value appears across surface, flow, logic, behavior, and strategy.
From Builders Need Strategy Now
Leverage Lens
A strategic filter for product bets: clarity, speed, confidence, quality, coordination, decision-making. A bet that improves none of these is noise.
From From Deterministic Software to Negotiated Software
Negotiated Software Loop
Describes the new contract between user and machine in probabilistic systems: intent, interpretation, suggestion, review, correction, adaptation.
From Taste as Operational Judgment
Operational Taste Test
Converts taste from aesthetic preference into a set of operational decisions: what to automate, where to keep friction, what should not exist at all.
From Technical Depth Without Technical Captivity
Product-Level Technical Fluency
Names the minimum technical surface area a product builder needs to reason about quality without disappearing into implementation.
From Build Evidence of a New Identity
Proof of Product Architecture
Names the kinds of evidence that make the new role legible to others: reframing a problem, redesigning a workflow, modeling system behavior, showing tradeoffs, expressing a point of view, building a concept with real logic.
From Introduction — You Are Probably Not Misaligned. The Role Is
Role Friction Map
A diagnostic that surfaces the gap between the reader's hired role and the work their thinking actually wants to do.
From The Product Is Beneath the Interface
The Product Beneath the Interface
The book's defining lens. Names the system layers that shape what the visible UI can honestly express.
From Trust Is Now a Product Layer
The Trust Stack
Names the structural materials of trust in intelligent systems, from expressive at the top to foundational at the bottom.
From Workflow Authors Reshape the Work
Workflow Authorship Canvas
A canvas for redesigning a workflow rather than wrapping it in better UI.