← Guide libraryWebsite experience, enquiries and handoffs · Resolution guide

Abrasim problem-resolution guide

Navigation and Internal Search Prevent Users Reaching the Right Answer

Improve on-site findability for important user tasks.

By Tafadzwa BoriwondoPublished 29 August 2026Evidence reviewed 29 August 2026

For: Product Owner, UX Lead or Web Manager
Decision to make: Use task, path, query and failed-search evidence to choose labels, hierarchy, links and search changes.
Scope boundary: On-site navigation and search for defined tasks, not a cosmetic redesign.

Downloadable working pack · ZIP

On-Site Findability Test Workbook

Fill in the workbook as you follow the guide. Keep each decision linked to its evidence, responsible owner, live-site checks and review date.

Download working pack

Start Here
Set the investigation scope, decision question, accountable owner, dates and working rules before changing anything.
Evidence Register
Capture each source, observation, date, owner, confidence limit and evidence gap without turning an assumption into a fact.
Diagnosis
Compare possible causes, record the evidence for and against each one, and identify which failed check needs action.
Action Plan
Assign an owner to each agreed action. Record dependencies, acceptance criteria, release controls and rollback conditions.
Verification
Record production proof, live tests, expected reporting lag, guardrails and the result against the original baseline.
Decision Log
Record the decision to proceed, change, investigate again or stop. Name who authorised it, the remaining risks and the next review date.

Before Section 1
Open Start Here. Name the exact problem, affected scope, decision owner and safe working boundary before gathering or changing evidence.
While working through Sections 1 and 2
Use Evidence Register for source facts and Diagnosis for competing explanations. Keep observations, interpretations and unknowns separate.
During Section 3
Move only the accepted cause into Action Plan. Assign an owner, dependency, acceptance test and rollback condition to every change.
During Section 4
Use Verification to compare the released result with the baseline. Record technical proof and later search or commercial movement as separate evidence.
During Section 5 and close-out
Use Decision Log to record what will proceed, change, reopen or stop. Name who will prevent the problem returning and when they will review fresh evidence.

Working rule: The workbook is a structured investigation record, not a pre-completed diagnosis or performance promise. Keep source evidence, uncertainty and decision authority visible throughout.

Start here

Agree what you need to find out.

Use this guide when you are responsible for resolving the problem described by “website navigation and internal search users cannot find content”. Check the cause before changing content, technology or the way the work is done.

Before you start

A representative user task, entry page and device context, plus a control journey that is known to work.
Access to analytics, form or call handling, CRM and operational response evidence where those systems are in scope.
Named owners for the page experience, conversion mechanism and downstream response handoff.

What you leave with

A dated evidence record for the problem described by “website navigation and internal search users cannot find content”.
A decision that answers: Use task, path, query and failed-search evidence to choose labels, hierarchy, links and search changes.
An action plan with a responsible owner, live-site evidence, acceptance criteria and a follow-up date. State when to roll back the change or investigate again.

How to run every step

01Record the observation, source, date, scope and evidence owner before drawing a conclusion.
02Classify the statement as VERIFIED, INFERRED, PROPOSED or REQUIRES VALIDATION; do not silently promote an assumption.
03Name the result you need and who is responsible for each step. Record the decision it supports and any question still unanswered.
04After a change, record the live result and acceptance test. Keep source-code, preview and live-site evidence separate.
05Monitor search recovery and business results separately. If a check still fails, investigate that check again before repeating the whole method.

Accountable owner: Product Owner, UX Lead or Web Manager
Operating action: follow the user from the page promise through the action and response. Check whether the problem is usability, technical failure or a missed handoff
Decision gate: Before making a change, check that the evidence supports this decision: Use task, path, query and failed-search evidence to choose labels, hierarchy, links and search changes.
Acceptance evidence: a representative user can complete the task, and the enquiry or action reaches the correct workflow and responsible person. Keep evidence of both
Rollback or reopen when: completion falls, accessibility regresses, duplicate records are created or a working downstream path is interrupted
Scope boundary: On-site navigation and search for defined tasks, not a cosmetic redesign.

What the problem looks like and why it matters

Use labels and routes that help people find the answer they need. Test whether navigation reflects their tasks and whether site search returns current, relevant results. More menu items may make an unclear structure harder to use.

Use visitor tasks, internal search queries and failed searches to identify information people cannot find. Check the labels, results and destination pages together, then test whether people can reach the right answer without relying on the team's internal vocabulary.

What evidence distinguishes the real cause

Evidence	What to capture	Control
E-01	Priority user tasks and start points across desktop, mobile and assistive use	Record source, date, scope, owner and confidence.
E-02	Navigation hierarchy, labels, link purpose and crawlable destinations	Record source, date, scope, owner and confidence.
E-03	Internal-search queries, zero results, refinements and selected results	Record source, date, scope, owner and confidence.
E-04	Path analysis, failed tasks and qualitative observations	Record source, date, scope, owner and confidence.
E-05	Content ownership, duplicates, stale items and inaccessible destinations	Record source, date, scope, owner and confidence.

Classify evidence as VERIFIED, INFERRED, PROPOSED or REQUIRES VALIDATION. Keep consent, privacy, accessibility and unavailable-data limitations visible.

How to fix it step by step

Step 1: Define top tasks

Choose evidence-backed market and support tasks rather than stakeholder favourites.

Step 2: Run findability tests

Ask representative users to locate answers from common entry points without coaching.

Step 3: Audit labels and hierarchy

Compare user language with menus, breadcrumbs, hubs and internal links.

Step 4: Analyse site search

Classify zero-result, low-click and reformulated queries; protect privacy in query logs.

Step 5: Fix content ownership first

Resolve duplicates and stale destinations before tuning ranking or menus.

Step 6: Redesign the smallest path

Change labels, grouping, contextual links or search synonyms based on observed failures.

Step 7: Verify all interaction modes

Test mobile, keyboard, screen reader, direct URL and crawler access.

For each action record owner, approver, dependency, production proof, acceptance test and rollback trigger. Test the complete route rather than approving a screen in isolation.

How to verify recovery

Accept when priority tasks reach the correct current answer within the agreed path, search results are relevant and controls are accessible. Roll back changes that hide a high-value route, create ambiguous labels or make keyboard order unpredictable.

Use successful, failed and out-of-scope scenarios. Implementation acceptance, user recovery and commercial recovery are separate gates.

How to prevent the problem returning

Track top tasks and failed searches continuously. Review navigation when content ownership or services change. Require descriptive crawlable links for critical destinations.

Primary guidance reviewed at the 29 August 2026 source cutoff includes Google Search Central documentation and W3C technical standard. These standards guide testing but do not prove an outcome for a particular organisation.

Where the journey crosses search, content, experience, technology and sales ownership, Discuss navigation and site search. The six value paths cross functional budgets, evidence and ownership; diagnosis therefore needs cross-functional authority, access and independent challenge, whether led internally or externally.

Use the method with AI

Use this prompt to organise your analysis. Share only evidence you are authorised to provide to that model. A person must remain responsible for the decision, privacy limits and final action.

Copy and adapt

You are helping me apply the Abrasim problem-resolution guide: “Navigation and Internal Search Prevent Users Reaching the Right Answer”.

Situation: website navigation and internal search users cannot find content
Decision to make: Use task, path, query and failed-search evidence to choose labels, hierarchy, links and search changes.
Scope boundary: On-site navigation and search for defined tasks, not a cosmetic redesign.

Use only the evidence I provide. Do not invent facts, benchmarks, sources, outcomes, customer research or legal conclusions. Keep VERIFIED, OBSERVED, INFERRED, PROPOSED and UNKNOWN separate. Ask focused questions when the evidence or authority is missing.

Help me work through this method by returning:
1. An evidence table with claim, source, date, confidence and limitation.
2. The strongest competing explanations, including what would disprove each one.
3. Decision options with trade-offs, dependencies and the cost of waiting where evidence supports it.
4. The next smallest evidence-gathering action, its accountable owner and acceptance test.
5. A proceed, change, validate, defer or stop recommendation that a named human decision-maker can review.

Treat the attached Abrasim working pack as a blank working record. Do not fill missing rows with plausible data. Flag privacy/POPIA, security, accessibility, safety and authority issues. Cite primary sources for external claims and show uncertainty. End with the conditions that would make us change course or stop.

My organisation-specific evidence and constraints:
[Paste evidence, links, dates, decisions and limitations here]

Working rule: AI can help organise evidence and expose questions; it cannot establish truth, approve risk, make the business decision or replace qualified legal, privacy, security or accessibility review.