Anti-patterns

The filter buffet: every column gets a filter, none of them get used

Agents build filters from columns. A table with ten columns gets ten filter controls. The user's actual filtering question involves two of them. The rest is noise that teaches the interface to be ignored.

Give an agent a table with ten columns and ask it to make the data filterable. You'll get ten filter controls, one per column, probably displayed simultaneously in a collapsible sidebar. Every dimension of the data — status, date range, assigned user, category, priority, region, account type — gets its own input. The filter buffet: an exhaustive representation of how the data could theoretically be sliced, with no opinion about how the user actually searches.

The problem isn't that these filters are wrong. For power users doing exploratory analysis, some combination of them might be useful. The problem is that they're all treated equally, all visible at once, and none of them are shaped around the question the user is actually asking when they open this table.

Filtering is answering a question

Users filter data because they're looking for something specific. The filtering action is an implicit question: "show me X." In a support queue, the question is usually "show me the urgent open tickets assigned to me." In an inventory table, it's "show me the items that will go out of stock this week." In an expense report, it's "show me anything over the approval threshold."

These questions have answers. And the answer to each question involves a specific set of fields in a specific configuration. The agent knows the data model but not the question — so it exposes the entire data model as filter controls and leaves the question to the user.

The result is a filter panel that requires the user to translate their job-shaped question into data-model-shaped inputs every time they open the screen. That translation is extraneous load. It's not part of the job; it's a tax the interface charges for access to the job.

Pattern: filters should answer the questions the user is actually asking, not expose every column that exists. The right filter set is derived from the job, not from the schema.

Job-shaped filters vs. schema-shaped filters

Job-shaped filters look different from schema-shaped ones. Instead of "Status: [dropdown of all statuses]," they might be "Needs action" — a single toggle that filters to records where user input is required, regardless of what underlying status values produce that condition. Instead of "Date range: [from] [to]," they might be "Due this week" — a pre-configured range that matches the planner's actual review cadence.

This doesn't mean advanced filtering doesn't belong. It means the common-case filtering should be designed around what the user is actually trying to isolate, and the advanced filtering (including full column access) should be available but not the primary interface.

Saved views earn their place here. When users filter to the same configuration repeatedly — "my open urgent tickets" — a saved view with a name that describes the question is more useful than the same filter combination re-applied manually every session. Agents rarely add saved views unprompted, because they're not a feature that falls out of the data model.

Why agents reach for the buffet

The filter buffet is cheap to build and defensible on its face. "Every column is filterable" sounds like a feature. It's harder to argue against than "we filtered out most of the columns because we thought you'd only use three." The exhaustive option feels safer.

Agents also genuinely don't know which filters matter without knowing the job. The buffet is the answer you get when the agent has access to a schema but not to an understanding of how the table is actually used. It's not wrong — it just exposes the absence of job knowledge rather than making any decision.

How TheDesignAgent flags it

On the /ux lens, a filter panel with more than five or six controls simultaneously visible, derived directly from the schema without apparent job-shaping, triggers a jtbd_alignment flag. The patch is specific: identify the two or three filtering questions that account for the majority of use, redesign the primary filter bar around those, and move the rest behind an "advanced filters" disclosure.

The extraneous_load sub-score drops when the filter-question translation is visible — when the user has to know that "needs action" corresponds to statuses pending_review and awaiting_approval before they can use the filter correctly. That translation belongs inside the filter, not in the user's head.