Digital economy boundaries and measurement · Lesson 4
Diagnose inclusion barriers
4 min read
Lesson objectives
Diagnose inclusion barriers using an evidence matrix rather than a single access rate.
Reading tools
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
Locate the stage where users leave a service journey, then distinguish device or connection barriers from cost, skill, language, service design and trust. One registration rate cannot diagnose a cause. Evidence should separate discovery, starting, completing and continuing a task.
If one group registers less often than another, assuming it “does not want technology” is unwarranted. A shared phone may not support an app update; a form may use more data than a prepaid allowance; an identity document may be unavailable at the point of application; or instructions may use unfamiliar terms. Build a matrix with user groups as rows and device access, task starts, completions and assistance as columns. Attach each value's source. Protect privacy by collecting the least personal information needed to understand friction. Do not record a sensitive trait merely because it is available when a behavioural measure or usability test could diagnose the service problem.
A barrier matrix links each stage of a request journey to evidence that can test it. Device shortage calls for a supported device or assisted route; weak connectivity for a low-data route; language friction for clear Arabic and a task test; verification failure for error logs that do not store secret codes. Where possible, change one component in a bounded trial, recording completion, time and error type under the same denominator before and after. Voluntary comments nominate hypotheses but cannot measure their prevalence among all eligible users. If completion among site entrants improves while fewer eligible people start, do not call the service universally better. Record who never reached the form so their absence from the log is not mistaken for satisfaction.
Lesson summary
Apply Diagnose inclusion barriers to the case data and distinguish the result from an assumption before deciding.