# Screens that fight how people work

Prompt · Architecture and hidden complexity · A08

Finds when confusing screens are a symptom of how the product is organised rather than a list of separate bugs.

## Prompt

```text
Map this application's pages, navigation and URLs against the jobs its users actually do. Find pages that should merge, become a tab or panel, or go away; navigation systems that compete for the same destinations; and jobs users have to assemble by hand across screens. Say whether the structure itself causes the problems, and if it does, name the end state it should reach.
```

**What it returns:** A verdict per page (keep, merge, demote, retire) with the evidence for each, the two to five causes behind the symptoms, and today's site map next to the proposed one.

**Skip it when:** Products with a handful of pages, or right after a navigation redesign nobody has used yet.

**Tools:** Repository; the app running locally with test accounts for the browser checks.

**Watch for:** Agents propose a redesign for every complaint. Ask whether one structural cause explains two or more findings; if none does, the structure is sound and the fixes are local.

**Changes:** Changes nothing

**Sessions:** Look first, then fix in a new session

## Related

- [Old design choices that now cost you](https://atlasscope.dev/prompts/old-design-choices-that-now-cost-you): Separates old design choices that now cost real time or bugs from ones that are only out of fashion.
- [Lost place: Back, refresh and shared links](https://atlasscope.dev/prompts/lost-place-back-refresh-and-shared-links): Finds the everyday friction where Back closes the wrong thing, a filter resets, or a pasted link opens the wrong view.
- [Meaning drift across the stack](https://atlasscope.dev/prompts/meaning-drift-across-the-stack): Shows where one word (a task, a fund, a run) means slightly different things in different parts of the app.

Source: https://atlasscope.dev/prompts/screens-that-fight-how-people-work