Abrasim customer and buyer persona guide
One “Typical User” Is Hiding Important Access Needs
Represent access needs hidden by the typical-user profile.
By Tafadzwa BoriwondoPublished Evidence reviewed
- For
- Service Owner, Product Lead or Accessibility Lead
- Decision to make
- Add access, capability, environment, support and failure contexts to research and decisions without stereotyping.
- Scope boundary
- This guide is not a substitute for WCAG testing or qualified accessibility expertise.
What the problem looks like and why it affects the business
The persona represents a confident user with reliable connectivity, standard input methods, fluent language and uninterrupted attention. People who need assistive technology, support, more time or a different channel appear only as edge cases.
A typical-user model can turn foreseeable access barriers into service failure, avoidable support cost and exclusion while giving the team false confidence in a single journey.
Start with the decision this research needs to support. Represent access needs hidden by the typical-user profile. The budget owner is normally Service Owner, Product Lead or Accessibility Lead; involve research, analytics, sales, service, product, accessibility and privacy specialists where their evidence or authority is needed. The symptom alone does not establish its cause.
This guide helps the owner decide whether the current persona evidence may support that decision, needs correction, should be narrowed, must be validated or should be stopped. It does not choose the organisation's priority customer segment. Use Customer Evidence and Segment Priority Standard when the unresolved decision is whom the organisation should prioritise.
What to expect in the working pack
Start the working pack before research begins. Update its eight sheets as you follow the method:
- Start here: Explain the decision, sequence, evidence labels and stop conditions before the reader begins.
- Decision charter: Bound the decision the persona must support and the authority required to act on it.
- Evidence register: Keep observed facts, participant statements, interpretations, inferences and unknowns distinguishable.
- Research and coverage: Plan research questions, participant contexts, access needs, consent and coverage gaps.
- Persona hypotheses: Represent only evidenced jobs, needs, behaviours, contexts and barriers that may change the decision.
- Roles and journey: Map changing user and buying roles, tasks, criteria, handoffs and unresolved conflicts.
- Activation and tests: Connect persona evidence to a changed decision, an accountable test and observable acceptance evidence.
- Review and change log: Govern versions, approvals, evidence changes, review triggers, replacement and retirement.
Use stable IDs when one sheet refers to another. Replace the illustrative seed rows with authorised organisation-specific evidence. Do not enter names, contact details, recordings or unnecessary personal information into the workbook; link to a controlled source reference instead.
What evidence distinguishes the real cause
Build one dated evidence set before rewriting the persona, launching research or changing a customer journey.
| Evidence set | Question it must answer | Minimum control |
|---|---|---|
| Context inventory | Which capability, environment, device, language and support contexts affect the task | Observed context, source, consequence and coverage |
| Barrier evidence | Where the current experience prevents or burdens progress | Step, interaction, content, assistive technology, workaround and outcome |
| Research coverage | Whether people with relevant access needs were included | Recruitment criteria, accommodation, consent, method and gap |
| Service evidence | What assisted channels and support teams observe | Contact reason, volume boundary, handling evidence and limitation |
| Standards and specialist review | Which requirements or expertise govern the decision | Relevant WCAG check, specialist owner, test evidence and unresolved risk |
Classify each material statement as VERIFIED, INFERRED, PROPOSED or REQUIRES VALIDATION. Within the evidence register also distinguish an observed fact, a participant statement, an organisational interpretation, an inference and an unsupported assumption. These labels answer different questions and must not be collapsed during synthesis.
Research permission is part of evidence quality. Record purpose, participant information, consent or other authorised basis, access, sharing, retention, withdrawal and deletion routes before collecting personal information. The Protection of Personal Information Act is a primary South African legal source; the guide is not legal advice, and the organisation's Information Officer or qualified adviser retains legal authority.
Stop and re-charter when the decision is unnamed, participation would be coercive, the team cannot protect participant data, the sample cannot answer the question, a preferred outcome controls the method, or no receiving owner can act on the result.
How to fix it step by step
Throughout the eight steps, record each material item's source, population or participant context, date, owner, permitted use and confidence. Keep contrary evidence and unresolved questions visible. Label unknowns, participant statements, internal interpretations and examples separately from verified customer facts. Save source references with the receiving owner, next handoff and conditions for stopping or reopening the work.
Step 1: Charter the decision and exposure
Accountable owner: Service Owner, Product Lead or Accessibility Lead.
Charter the named service or product decision and identify whose success and failure it affects.
Use in the working pack: Start here and Decision charter.
Check before continuing: Check that the decision, accountable owner and business consequence are clear. Record who receives the result and any authority gap that prevents the next step.
Step 2: Separate claims from evidence
Accountable owner: Research lead with the decision owner.
Audit the current persona for hidden assumptions about capability, environment, language, support and technology.
Use in the working pack: Evidence register.
Check before continuing: A reviewer should be able to trace the recorded claims or inputs to their sources. Keep evidence types, confidence and contrary findings visible before drawing a conclusion.
Step 3: Define coverage and authority
Accountable owner: Research lead with privacy, accessibility and relationship owners.
Map access contexts to tasks, barriers, workarounds, consequences and existing evidence.
Use in the working pack: Research and coverage.
Check before continuing: Record the coverage, classification and permission limits relevant to this task. Identify what is still missing and whether that gap prevents the next step.
Step 4: Test the competing explanation
Accountable owner: Research and analysis lead.
Review research coverage and distinguish missing representation from a conclusion that needs are rare.
Use in the working pack: Evidence register and Persona hypotheses.
Check before continuing: Retain the assumptions, competing explanations and unresolved questions this step exposed. Explain which evidence would change the current interpretation and who will review it.
Step 5: Run the bounded evidence round
Accountable owner: Research lead and participant-access owner.
Run accessible, permissioned research with actual or likely users and provide requested accommodations.
Use in the working pack: Research and coverage.
Check before continuing: Keep the evidence collected or reviewed at this step, its permitted use and important exclusions. Record any remaining gap before treating the result as customer evidence.
Step 6: Synthesise without hiding conflict
Accountable owner: Research lead with cross-functional observers.
Add decision-relevant access contexts without stereotyping individuals or creating one disability persona.
Use in the working pack: Persona hypotheses and Roles and journey.
Check before continuing: Separate the retained observations from your interpretation. Link the result to sources, preserve conflicting cases and show what the receiving team can safely use.
Step 7: Change and test the decision
Accountable owner: Accountable decision owner with receiving teams.
Test the affected choice with users, accessibility checks and service guardrails.
Use in the working pack: Activation and tests.
Check before continuing: Record the decision change or test, its owner and what remains uncertain. An authorised reviewer must be able to follow the evidence before the next commitment.
Step 8: Approve, defer or reopen
Accountable owner: Service Owner, Product Lead or Accessibility Lead.
Approve ownership, escalation, review triggers and transfer to qualified accessibility remediation where required.
Use in the working pack: Review and change log.
Check before continuing: Record the authorised decision, sources, unresolved limits and next handoff. State when to review, stop or reopen the work so approval cannot be mistaken for permanent certainty.
Worked method example
An application persona assumes desktop use and confident reading. Research with actual users shows that shared mobile devices, screen magnification and help from an intermediary change task order and privacy risk. The team adds these contexts to the decision model and routes interface conformance issues to the accessibility owner.
This is a method illustration, not an Abrasim client result. The reader must replace it with current, permissioned evidence and record any limitation that would change the decision.
How to verify the persona improves the decision
Accept the work when material access contexts are evidenced and visible, research coverage and gaps are explicit, the persona does not stereotype disability, relevant decisions change, and WCAG or specialist testing remains separately owned.
Run four tests:
- Traceability test: select a material persona claim and trace it to the evidence, participant context, permission, interpretation and confidence record.
- Decision-difference test: present the old and revised evidence to the accountable owner and record whether a real content, product, service, research or commercial choice changes.
- Contrary-case test: apply the decision to a credible negative, excluded or exception case and confirm that the model exposes rather than hides the difference.
- Outcome-learning test: after the accepted observation window, record what happened separately from implementation completion and reopen if the expected behaviour or customer outcome does not appear.
Adding one fictional disabled persona does not make the model inclusive when research, accommodations, standards testing and service ownership remain absent.
Roll back or contain a decision when it increases exclusion, service failure, privacy exposure, unsupported targeting, customer burden or irreversible investment without stronger evidence. A completed interview, workbook or persona card is implementation evidence; it is not proof of a customer or commercial outcome.
How to keep the problem from returning
- Include access and support contexts in every relevant research plan.
- Require accessibility specialists and affected users in consequential reviews.
- Keep persona evidence distinct from conformance testing and legal conclusions.
Review the persona when the decision, market, offer, customer context, research coverage, evidence source, regulation or operating model changes materially. Retire it when no active decision uses it or when a replacement has an approved migration and evidence-retention route.
Use the preceding guide before this method when its evidence boundary is unresolved. Continue to the next guide when you have the evidence it requires. Compare the adjacent guide before commissioning overlapping work: The existing guide owns search-journey accessibility diagnosis; this guide owns research representation.
Primary sources reviewed at the 30 August 2026 source cutoff include w3c people use web, gov find participants, gov user needs, popia act. These sources inform the method; they do not prove a condition, prevalence or outcome for a particular organisation.
Where the problem crosses functional budgets, evidence and ownership, Assess the service and operating consequences. 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
A prompt to help you work through this guide
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 customer and buyer persona guide: “One “Typical User” Is Hiding Important Access Needs”.
Situation: Represent access needs hidden by the typical-user profile.
Decision to make: Add access, capability, environment, support and failure contexts to research and decisions without stereotyping.
Scope boundary: This guide is not a substitute for WCAG testing or qualified accessibility expertise.
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.