The Product Beneath the Interface
The book's defining lens. Names the system layers that shape what the visible UI can honestly express.
What the system currently is — the values that determine what is allowed and what comes next.
What the system carries forward across moments: history, context, identity, accumulated user truth, and what it chooses to forget.
Who can do what, when, and on whose behalf: the quiet rules that shape what is even possible to attempt.
When the system acts, waits, suggests, or stays silent: the rhythm of behavior.
How certain the system is about what it knows or proposes, and how that uncertainty changes what should happen next.
How separate parts coordinate: the choreography between user, machine, interface, data, and adjacent systems.
What happens when something goes wrong: the structure of undo, repair, retry, restore, and recourse.
What the system makes legible about its own behavior, state, memory, assumptions, and reasoning.
What it helps you see
It exposes the layers beneath the visible surface, so you can see where the product is really being decided.
How to use it
For any product, sketch what lives at each layer. The output is a system-layer map: the product behind the visible interface made clear enough to argue about.
Use it when
Use this when a product question in The Product Is Beneath the Interface needs structure before it becomes a screen, roadmap item, or portfolio claim.
Practice prompt
Choose a real product, project, or career decision and answer the framework's items in order. Carry forward the answer that changes the next move.
Source chapter
This framework was authored in The Product Is Beneath the Interface. Read the chapter for the full argument and the worked examples that produced this shape.