# Decision surfaces: putting the action where the eye already is

> A decision surface is a layout where each row is a unit of decision and the action is on the record. It's what agents should build when the job is deciding, not watching.

Source: https://www.thedesignagent.ai/field-notes/decision-surfaces · Patterns · 2026-05-06

The most common recommendation TheDesignAgent's patches produce is some variation of the same structural change: collapse the modal into the row, move the action inline, surface the confidence signal next to the record it applies to, let the running total update as decisions are made. These patches keep appearing across different domains and different agents because they're all solving the same underlying problem.

There's a name for what they're building toward: a decision surface. It's not a component or a widget — it's a layout pattern for jobs where the user's work is to decide on a list of things.

## What a decision surface looks like

The anatomy is specific. Each row is a decision unit — the record plus everything needed to act on it in one place. The primary action (approve, reject, override, escalate, accept, flag) is exposed directly on the row, not behind a click. A confidence signal or priority indicator sits inline with the record so the user can triage at a glance. Secondary context — reasoning, history, linked data — is one step away but out of the critical path. A running summary at the top reflects the cumulative state of decisions made so far, not the aggregate state of the dataset.

Keyboard shortcuts are table stakes, not enhancements. Batch workflows have a cadence. Users process tens or hundreds of rows in a session. A layout that requires a mouse click per action, per row, makes that cadence impossible to maintain.

> **Pattern:** a decision surface is a layout where each row is a decision unit — the action should be where the eye already is. The running summary reflects what the user has decided, not what the data says.

## How it differs from a dashboard

Dashboards and decision surfaces can look similar — both have tables, both may have summary numbers at the top. The difference is behavioral, not visual.

A dashboard is for monitoring. The numbers at the top reflect system state: how many items are in each status, what the current capacity is, whether something is trending in the wrong direction. The table is a drill-down into that state. The user reads, maybe filters, maybe exports. Decisions are secondary.

A decision surface is for acting. The numbers at the top reflect the user's progress through their own work — how many they've approved, how many remaining, what the accepted total adds up to. The table is the primary work surface. Every row is a prompt for a decision. Monitoring the aggregate state is useful as a side-effect of working through the list, not as the primary orientation.

The agent builds a dashboard when it can scaffold from the schema. It builds a decision surface when it knows the job. The schema doesn't tell the agent which one is right. The job does.

## When to use it

Decision surfaces fit jobs that share a structure: a list of records that each require a single discrete judgment, where the user is processing the full list in one session, and where the action per row is quick enough that the session feels like a batch.

Reorder recommendations. Expense approvals. Content moderation. Vendor quote comparisons. Support ticket triage. Loan application reviews. The specific domain varies; the shape of the job is the same. The user is the deciding agent. The interface's job is to make each individual decision as frictionless as possible while keeping the cumulative picture visible.

This pattern is distinct from a form (one record, many fields, deliberate attention per field) and distinct from a pure data table (browse and filter, decisions are incidental). It's the pattern for jobs where speed and volume matter and each row is a complete unit of work.

## How it shows up in patches

When TheDesignAgent flags a dashboard built for a deciding job, the patches follow the anatomy above: move actions inline, expose confidence or priority signals directly on the row, replace the aggregate KPI strip with a progress summary, add keyboard bindings for the primary actions.

The before is usually functionally correct — all the data is there, all the actions are accessible. The after is the same data and actions with the ceremony removed. Both look professional. Only one lets the user process fifty rows before lunch.

See the inventory planning example in the [homepage receipts](/#receipts) for the side-by-side. The before is a clean dashboard; the after is a decision surface. The structural difference is about four patches.
