# The dashboard default: why agents build viewers when the job is deciding

> Four KPI cards, a table, a date filter. The dashboard is the agent's lowest-effort answer to 'build me a tool for this data.' It's also wrong most of the time.

Source: https://www.thedesignagent.ai/field-notes/the-dashboard-default · Anti-patterns · 2026-04-08

Ask an AI coding agent for a tool and you'll get a dashboard. Four KPI cards in a strip across the top, a table below, a date filter, an export button. It looks competent. It usually isn't.

The problem is that **most jobs aren't monitoring jobs**. They're deciding jobs. Watching is what dashboards are for. Doing is what most users were hired to do.

## Watching vs. doing

Consider a planner reviewing weekly reorder recommendations. The agent ships a dashboard: out-of-stock count, reorder-soon count, capacity used. A row table. A row click opens a modal, the planner edits, saves, closes, clicks the next row. Twenty rows takes ten minutes of ceremony.

The job, though, is to decide on twenty recommendations. Each row IS the decision. The KPIs are useful as a running side-effect — but the planner doesn't need them to *start*. They need: a confidence signal per row, the AI's reasoning if they want it, and inline accept / override / reject. The capacity bar at the top is the cumulative cost of their decisions, not a measurement of system state.

> **Pattern:** when the user is going to take an action on every row of data they see, put the action on the row, not behind a click. The dashboard pattern hides the decision behind ceremony.

## Why agents reach for it anyway

The dashboard is the lowest-effort answer to "build me a tool for this data." It maps cleanly to the data shape: each KPI is an aggregate, each row is a record. The agent doesn't need to know the user, the job, or the workflow — just the schema. That's why it's the default. It's also why it's wrong most of the time.

For a JTBD that's about deciding, the right pattern is a *decision surface*. Each row is a unit of decision. Confidence is in line. AI reasoning is one click away, not gone. Keyboard shortcuts because batches are the actual usage pattern. A summary that updates as you decide, not as the data updates.

## How TheDesignAgent flags it

On the `/ux` lens, a dashboard built for a deciding job triggers two things: a `layout_fights_action` cognitive flag, and patches that reframe each row as the decision unit. The agent gets back "collapse modal into row" and "move actions inline" before the build is in your PR.

We use this case in the [homepage receipts](/#receipts) as the inventory planning example. The before is a clean dashboard. The after is a decision surface. Both look professional. Only one fits the actual job.
