Diagnosing adoption opportunity and work context · Lesson 9

Diagnose access barriers to AI-assisted work

17 min read

Lesson objectives

  • Diagnose device, source, language and support barriers, selecting repair tests preserving decision quality and personal privacy.
Reading tools

Management asks everyone to use the service assistant and publishes a low-use list. Near the bottom are an employee working by phone, a screen-reader user and an evening team facing source outages. Before interpreting names as resistance, ask each person to perform the same task in their ordinary environment. Differences may begin before anyone types a prompt. Account access, document availability, understanding the condition and approving an outcome all require effective access. This lesson diagnoses barriers preventing task completion and selects adjustments that support correct work. The purpose is to connect adoption policy with people’s ability to benefit and distinguish tool performance from access conditions. A better diagnosis can change your choice from a usage campaign to a small source, support or presentation repair.

Define access at the decision point. A license shows a seat was allocated; the employee may still be unable to open the source or understand why access failed. Map device and connectivity, account and permissions, task interface and source, then assistance and escalation. Specify an observable action at each stage. Can the login link be reached? Can the policy passage be read? Is the approval control understandable? Does an error explain what to do next? Test the whole task with the person instead of asking generally about ease of use. Record where the breakdown occurs, when and how work continues. Staff may turn to unapproved copies when the official path is blocked. Understanding that workaround helps repair its underlying need while investigating any resulting data exposure.

Separate reading permission from readability. Someone may be authorized to view a document yet receive a scanned image their screen reader cannot interpret. They may see text but struggle with the order of rule and exception. Ask them to locate a specific fact and explain the action it supports. Distinguish opening failure, extracting content and understanding wording. Repairs differ: correct permission, provide a suitable text version or clarify instructions with the policy owner. Preserve meaning when changing presentation, particularly negation, dates and exceptions. Test the revision with someone who actually uses the relevant assistive method and compare it with the authoritative source. Effective access lets a person judge the source, reject a wrong suggestion and seek correction when visible information is insufficient for safe resolution.

Treat language as part of the task. An employee may understand an English button label but interpret an exception term differently from a colleague. Ask for an explanation in the language of work, applied to a case. Application shows understanding more clearly than “do you understand?” Use one consistent term per concept and explain new meanings before relying on them in a consequential decision. For a source in another language, assign equivalence review and establish the authoritative resolution route under organizational policy. Short interface messages should explain the next available action and assistance. Repairs may involve task-specific language training, reviewed translation or step sequencing. Measure correct work afterward; satisfaction with language alone leaves accurate condition application unresolved.

Observe in a way that respects privacy. Ask how the person prefers to perform the task and what assistance helps rather than requesting an unnecessary medical diagnosis. Knowing that they use text enlargement, keyboard navigation or a screen reader may be sufficient. Explain who sees notes and what enters aggregate reporting. A synthetic case can replace sensitive real detail. Learn from one participant without generalizing their preference to everyone sharing a characteristic. Two screen-reader users may navigate differently. Gather varied feedback and preserve differences instead of designing around a stereotype. Meanwhile, the service owner should maintain a reasonable alternative so requesting help does not silently interrupt the employee’s work or delay customer service.

Examine access over time. Controls may work in the morning while the knowledge source disappears for night maintenance. The assistant may remain online after the only exception approver leaves. Create a service schedule showing source, support and authority availability for each shift. Missing links need a fallback, waiting message and case-transfer rule. Rehearse a short synthetic evening shift without relying on the morning team. Record who responds, response time and available authority. A contact in a directory may not be operationally available if they cannot act on the service. This prevents evening underuse from being attributed to motivation and exposes support cost in an adoption decision covering all working hours.

Balance fast adaptation with meaning protection. Shortening a long message should preserve eligibility, escalation rights and decision source. Split text into steps, show an example or make further explanation available when needed. Have the policy owner compare original and revised versions using an exception case. A changed decision means the adaptation needs repair before field testing. The team can maintain one outcome standard while permitting keyboard, touch or spoken access. Interaction costs differ while correct-response criteria and affected-party rights stay constant. Allow suitable learning and review time rather than requiring everyone to match one expert user. This evaluates task performance under fair conditions and distinguishes appropriate access from weakening safety.

Keep repair measures few and interpretable: successful opening of the correct source among eligible attempts, correct escalation to its owner and time to complete a correct case. Split by device, shift or interaction method when useful, protecting identifiable small groups. If capability improves, examine simultaneous changes in cases or assistance. The organization can welcome observed improvement while remaining cautious about its cause. If use stays low after access works, move to value, incentives and skill hypotheses. Diagnosis progresses by removing a demonstrated barrier and then asking the next question. Source and decision protection continue throughout instead of turning access reporting into a numeric target disconnected from correct service.

When an adjustment works for one person, preserve the barrier-and-repair description rather than copying their settings to everyone. Larger text can help one employee while hiding workflow elements on another small screen. Test content reflow instead of assuming one universal fix. The service owner can define common requirements, such as an accessible source and clear approval step, while allowing different interaction paths. Keep obtaining alternatives easy and explicit. Multiple approvals for a text version of an already-authorized guide can create a new barrier in the accommodation process itself. Measure support delivery time and whether correct work resumes. Institutional learning repairs shared causes while preserving individual interaction choice and monitoring outcomes.

Include supervisors in access training. A supervisor may interpret longer review as low productivity while the employee performs a check others skip. Train comparisons of correct, equivalent work and respectful questions about barriers. Reporting access difficulty should not require personal disclosure to the whole team. When specialist internal support is needed, define referral and follow-up ownership. Keep sensitive support records separate from general usage dashboards. Adoption meetings can report process repairs, such as restored evening links or readable documents. This supports trust, reduces fear that might suppress reports and keeps management focused on barriers rather than categorizing people from a single usage count.

The NIST AI RMF addresses use context, users and affected parties; its guidance discusses uneven technology access and interaction difficulties. It supports attention to people within the work setting. This lesson’s diagnosis and testing steps are teaching applications whose details depend on organizational policy and relevant support expertise. Tomorrow, take a task your team calls easy and observe authorized completion on a different device or shift. Watch source access, escalation and outcome. Repair one demonstrated barrier and verify correct completion with the person. Record learning about the process instead of labeling the person a weak adopter. Management then has a practical basis for an adoption policy people can carry out, and assistance becomes part of daily service quality. OECD AI Principles connect AI with fairness, privacy, inclusion and respect for labor rights. They support attention to access, while particular accommodations remain local decisions requiring appropriate review.

Before inviting participants, choose realistic conditions without exposing people or data to harm. Use a synthetic document matching the guide structure and a case requiring an explicit exception. Let participants use their usual interaction method and ask whether the test represents their work. Record facilitator help and its timing. Explaining a rule differs from repairing a login failure. Combining both into one completion score obscures product changes versus training needs. Retain limited notes and summarize actionable repairs. Return after adjustment to verify that it removes the same barrier rather than moving effort elsewhere. Worker involvement provides an explanation closer to actual need and reveals solutions a single interaction perspective may miss.

Report the barrier, repair and task result. For example, state that reading position was restored and correct condition reading and escalation were verified. Keep names and support methods outside general reporting when the process description suffices. If a specialist needs further information, define need and authority. Recheck after updates because a small change can reintroduce an old navigation defect. Preserve synthetic cases for support to use after consequential changes. Assign someone to follow the access report until correct work resumes. That ownership turns repair into an ongoing service and lets the organization spot recurrence before misinterpreting it as reluctance.

Lesson summary

Diagnosis links effective access to correct work, separating process barriers from motivation with testable support and interaction options.