Actionable reports
BEFORE
Static documentation
Site maps, flows, and IA docs go stale as soon as the product changes. Generation makes that gap worse.
A designer opens last days’ flow diagram.
- It no longer matches the shipped routes.Engineering added screens the map never captured.
- Nobody can name the golden path with confidence.Reviews argue from screenshots, not from a shared product model.
Empty, error, and permission states stay invisible until users hit them.
- Complexity accumulates with no record of what changed.Recommendations start before anyone agrees what exists.
- Easy to ship more UI. Harder to understand the product.Leadership sees output, not architecture.
Result: Documentation that cannot keep up with generation.
AFTER
Living map
Cartographer reads the product as it exists: routes, screens, navigation, and how they connect.
- It writes a product map, screen inventory, flow map, and state coverage.“Hero diagnosis: what the experience actually is, in one sentence.”The card shows evidence labels and screens, routes, and flows (Observed, Inferred, or Unknown).
Reports answer different jobs without changing the facts:
Designers: where the experience is incoherent.
PMs: which journeys are incomplete or high-risk.
Engineering: which states and routes are missing.
Teams see Map / Evidence / Unknown before anyone edits.
- Proposed changes are shown before implementation.Product evolution tracks what changed since the last map.
- Understanding stays current as the product moves.
Result: A living atlas instead of a stale deck, with visible confidence and a fix queue.
Cartographer features
Product map
Product areas, surfaces, relationships, and complexity.
Screen inventory
Screens, routes, purposes, status, and evidence.
Navigation intelligence
Wayfinding, dead ends, orphans, and mental-model fit.
Flow map
Goals, paths, entry points, success, failure, and recovery.
State coverage
Loading, empty, error, success, disabled, and permission states.
UX health report
Diagnosis, score, findings, risks, and what to fix first.
Fix queue
Actionable fixes with acceptance criteria, after the diagnosis.
Product evolution
What changed, where complexity grew, and what drifted.
Jobs to be done
Product designers
Understand what the product actually does and how it is organized.
See where users are likely to fail before a redesign starts.
Product managers and owners
Prioritize from incomplete flows and UX health, not the loudest screenshot.
Name structural risk and missing states before proposing a rebuild.
Engineers
See which flows are incomplete and which states are missing from the shipped product.
Researchers
Ground research in observed journeys, not assumed ones.
See what is Unknown so research time is not spent re-proving the obvious.
How a run works
Map the product, inventory screens, audit navigation, generate flows, audit states, score UX health, then write a fix queue. Diff only when a prior map exists. Creates Cursor prompts for every suggested fix. Browser view for more visual users, Cursor agent chat view for backend workflows.
