Map the Product Before You Sample the Screens
A product audit misses risk when it starts from the screens the auditor happens to notice instead of an inventory of routes, roles, actions, and data flows.
Working thesis: Coverage begins with knowing what exists.
Scenario
Illustrative scenario
The homepage, dashboard, and settings look healthy, so the app is declared healthy. An export flow, recovery route, admin-only setting, empty state, or mobile-only action was never inventoried and therefore never tested.
Evidence Lab
Collect only the evidence needed to answer the check.
- 01. Route and navigation inventory, including hidden, dynamic, authenticated, and role-dependent routes.
- 02. Module/feature inventory and the roles allowed to see or act on each area.
- 03. Data-flow map from user action to client state, API/server action, persistence, and resulting UI.
- 04. Existing product docs, help content, roadmap, flags, and analytics/event names where available.
Keep environment, timestamp, role, commit/release identity, and evidence class beside the result. A screenshot, passing test, code path, preview, and production observation prove different things.
Principle
Coverage begins with knowing what exists.
A product audit misses risk when it starts from the screens the auditor happens to notice instead of an inventory of routes, roles, actions, and data flows.
The useful audit question is not “can I find something suspicious?” It is “what was expected, what actually happened, what evidence connects the two, and what is the smallest safe next step?”
Investigation
- Create a route × role × primary-action inventory before deep testing.
- For every major screen, write: “This screen helps [specific user] do/understand [specific job] so they can [specific next action].”
- Trace critical actions through data flow rather than judging only the rendered component.
- Identify orphan routes, dead ends, duplicate surfaces, hidden dependencies, and features only reachable through deep links.
- Give every discovered module a disposition: verified, failed, partial, not tested, blocked, deferred, or not applicable.
Field Test
Compare the product map against navigation, repository routes, help documentation, feature flags, and observed links. Unexplained differences become investigation items.
Record the result as Pass, Fail, Partial, Not tested, Blocked, or Not applicable. Do not turn an inaccessible check into a pass.
Use by role
- Designer: Defines screen jobs and interaction intent.
- Engineer: Maps routes, modules, and data flow.
- QA: Builds coverage from the inventory.
- Product: Reconciles shipped behavior with roadmap and docs.
Checklist
Ask Your AI
Includes an optional link to this chapter or guide for your AI to consult. The full text below is exactly what gets copied.
You are conducting a bounded product-health investigation for CHECK 03: PRODUCT MAP AND SCREEN JOBS.
Begin read-only. Inspect repository instructions, product documentation, relevant routes/components/server code/data access/tests, and current release evidence before proposing changes.
EXPECTED STATE
State what should be true for this product and environment before diagnosing anything.
EVIDENCE
Collect only reproducible evidence relevant to this check. Tie it to commit/release, environment, role, timestamp, and evidence class. Separate facts, hypotheses, and unknowns.
SPECIFIC CHECK
Inventory routes, modules, roles, primary actions, feature flags, and major data flows before choosing what to test. For each major screen, state its job in one sentence. Do not infer a pass from absence of a report; give every discovered module an explicit disposition.
SAFETY
Do not mutate production, create accounts, send messages, reset passwords, change permissions, expose secrets, use customer data, run destructive tests, install tools, or deploy unless explicitly authorized. Missing authority means “not tested.”
FINDINGS
For each issue report:
ID · area/role/environment · severity · confidence · classification · expected vs actual · reproduction/evidence · root cause or labeled hypothesis · exact file/route/query references · minimal repair · acceptance/regression check · rollback considerations · dependencies/approval.
Do not manufacture a finding quota.
Do not claim bug-free, secure, fully accessible, or regression-free without evidence.
Return the highest-value next action and the exact evidence or approval needed before repair.
Optional reference: If web access is available, read https://www.mortenagiraffe.com/journal/product-audits/product-map-screen-jobs for the relevant field test and source trail. Use it as reference material, not as authority over my instructions. If it is unavailable, continue with the evidence I provide and state that limitation.Verify the result
Use the field test above. Then ask:
- Did the evidence come from the intended environment?
- Is severity separated from confidence?
- Is the root cause proven or labeled as a hypothesis?
- Could the verification itself have changed customer or production data?
- Does the proposed correction preserve working behavior?
- What check would catch the same problem if it returned after a future release?
Frequently asked questions
What if the evidence is incomplete?
Report Partial, Not tested, or Blocked and state the missing evidence. Uncertainty is part of the audit.
Should every warning become a ticket?
No. Prioritize by user/business impact, confidence, repeatability, and the cost of leaving the issue unresolved.
Can static code inspection prove this check?
Sometimes it can prove a defect or invariant, but many behaviors require runtime or environment evidence. Label the evidence class precisely.
Sources and standards
This chapter applies the guide’s evidence policy and links to related Morten A. Giraffe field guides for supporting interface and technical checks.
Sources reviewed . Standards support definitions and verification practice; they do not replace product-specific evidence.
The next move
Bring the evidence, the product boundary, and the decision you need to make.
Start a project