People Management
A New Workplace Process Is Not Being Used: Diagnose Adoption Before Adding More Training
Use a completed architecture-review booking case to distinguish understanding gaps, unusable requirements, and conflicting management expectations. Three bounded intervention records show what improved, what remained blocked, and what a short pilot cannot prove.
When a new workplace process is not being used, inspect a recent eligible task before scheduling another training session. Establish what should have happened, what actually happened, and where the person stopped or chose another route. Lack of understanding, an unusable step, missing support, and conflicting management expectations call for different fixes. The same low usage count can reflect several barriers; it does not identify their cause.
This LandOffer.ai guide contains a completed adoption diagnosis and three small intervention records for one fictional architecture-review booking process. All people, interviews, work records, counts, approvals, and results are invented teaching material. They are not a real organizational study or a tested productivity claim. Sources were checked October 27, 2026; no employee was contacted and no workplace system or policy was changed.

Define the work opportunity before counting adoption
“Only four people used the form” is hard to interpret without knowing who needed it. Start with the work event the process is meant to support, its applicable period, and its exceptions. A person who had no eligible task does not belong in the nonuse count. Someone who opened the form but could not finish has supplied different evidence from someone who completed the intended handoff.
In the fictional case, process owner Farah introduced a queue to book the first substantial architecture review involving two or more engineering teams. A usable request needs a permitted design-document link, the decision needed, affected teams, and a proposed review window. The queue is for scheduling and preparation; it does not grant design approval or release authority. Routine document edits without a new cross-team decision are excluded. A revision that introduces a new cross-team dependency is eligible; urgent production incidents use the existing incident route.
Farah reviews the twelve eligible requests from October 19–23. Four reached the queue with the required information before scheduling; eight were handled elsewhere or abandoned. That gives a baseline of four usable submissions out of twelve opportunities, approximately 33%. It does not show that eight employees resisted: one employee can have several requests, and the process itself may be the obstacle.
APQC's process-adoption guidance connects adoption with clear ownership, accessible documentation, practical support, two-way feedback, and ongoing measurement. Its process-management recommendations support looking beyond launch communications. They do not establish the cause of Farah's eight missing entries or prove that the process deserves to survive unchanged.
Check the purpose as well as the compliance count, so you do not improve the number while leaving the original work blocked. Here the intended benefit is a review with the necessary people and decision context, rather than an empty meeting followed by another booking. More form entries would be a poor result if reviewers still lacked the question, or if people had to maintain several duplicate records to secure a slot.
Walk through the last task without diagnosing the person
Ask a user to reconstruct a recent eligible request using permitted material: what started it, which instructions they found, the step attempted, what prevented completion, and how they got the work done. Ask an existing user what made the process workable too. Keep the inquiry about the workflow rather than soliciting private explanations or asking coworkers to rate one another's attitude.
Farah speaks with Sana, Beck, Tariq, and regular queue user Uma in the invented case. She explains that the purpose is to repair the process, takes limited task notes, and uses sanitized request examples. She does not collect private messages or infer motives from absence of a form. A participant account is recorded as an account until another permitted artifact supports it.
| Completed diagnosis record | Evidence available in the fictional case | Working interpretation and what it does not prove |
|---|---|---|
| Sana used chat for three eligible requests | Sana describes treating preliminary concepts as outside scope; the introductory guide only shows a near-release example | Applicability is unclear. This is not proof that Sana rejects cross-team review |
| Beck could not submit three requests | A walkthrough of the authored form stops at required Release ID; all three concept proposals have no release yet | The form excludes legitimate work. Repeating the same instructions cannot supply a nonexistent identifier |
| Tariq booked two reviews by direct message | Tariq reports that the chair prioritizes messages; chair Drew confirms accepting those bookings outside the queue | Management behavior rewards a competing route. This is not established by Tariq's report alone |
| Uma submitted four usable requests | Those requests have release references and familiar reviewer contacts | The process works for this path. It does not establish usability for concepts or an occasional requester |
The primary categories account for all twelve baseline requests: three scope misunderstandings, three blocked submissions, two bypass bookings, and four usable entries. They are a convenient case summary, not evidence that every request had only one cause. Farah retains possible overlap, including whether people knew where to get help and whether preparing a request fit their workload.
Prosci's discussion of change barriers, updated September 24, 2026, distinguishes understanding how to change from being able to do it with adequate time, tools, and support. It also discusses reinforcement and alignment with performance measures. Those distinctions inform the diagnosis here; Farah does not administer a proprietary assessment, score an employee's willingness, or turn a missing entry into a personality judgment.
Match the repair to the evidence and authority
For a knowledge gap, give an example at the point of work and ask the person to explain or demonstrate the next step. For an unusable requirement, have its authorized owner change the requirement or provide a valid alternative. For a support or capacity gap, name who will help and which work will make room. For an incentive conflict, the manager or sponsor must reconcile the competing expectations.
Do not remove an important control merely to increase submission counts. Farah can change the scheduling form, but she cannot authorize wider document access or bypass architecture decisions. Beck's example justifies making Release ID optional for concept reviews; it does not justify removing the decision question or sharing a restricted design document with everyone.
Drew accepts responsibility for routine bookings rather than leaving Tariq to persuade other reviewers. The chair will direct those bookings through the queue and stop treating an unsolicited chat request as a faster approved scheduling lane. Urgent incidents retain their separate route. An assisted entry remains available when a requester is blocked, so the change does not become “no form, no help.”
Capacity is agreed before the pilot: Farah receives two twenty-minute triage windows per week in place of the old forty-five-minute scheduling reconciliation. She uses a separate approved thirty-minute setup slot for the form and guide revision. Sana and Uma each receive ten minutes within their existing review-preparation time for the scope walkthrough. These are accepted allocations, not a claim that setup work is free or that the process saves time.

Three completed interventions with different results
Farah limits the first pilot to November 2–6 and reviews it with Drew on November 9. The following records are completed within the fictional story. They describe three responses to the diagnosed barriers, not experiments executed by this publisher or proof that any intervention caused an improvement.
| Barrier and intervention | Prediction and agreed observation | What happened in the authored pilot | Completed decision |
|---|---|---|---|
| Unclear applicability: Farah adds concept-stage and exception examples; Sana and Uma discuss four classification cases | Each person can explain the routing rule; then check usable submissions among the next three eligible concept-review requests | The joint walkthrough reaches four correct classifications out of four after correction; independent individual understanding is not established. Two of three subsequent eligible requests are usable; one revised design with a new dependency is incorrectly treated as an excluded routine edit | Keep the short guide, add the unresolved revision boundary, and check independent use again. Completion of a walkthrough is not adoption |
| Unusable step: Farah makes Release ID optional for concept reviews while retaining the decision and permitted document link | The next three eligible concept requests can be submitted without an invented release identifier; preserve access restrictions | Two of three submit usable requests. The third still stops because a supporting attachment is too large; the requester cannot assume an alternative document link grants reviewers permission | Keep the identifier repair. Farah owns clarifying the approved attachment/link path with its service owner; access and size problem remain open |
| Competing scheduling lane: Drew directs routine bookings through the queue and uses it for triage | The next three eligible requests are recorded before scheduling; note any duplicate work rather than only counting entries | All three are usable. One requester still posts the same details in chat because an old calendar invitation asks for them there | Drew corrects the invitation and retires its duplicate instruction. Queue use improved in this small group, but the duplicate burden has not yet been rechecked |
The classification exercise is a teaching observation, while the three actual-work opportunities in that row are the fictional adoption observation. Keep those denominators separate. Similarly, making the release field optional is a completed repair, but the failed attachment shows that the full path is not yet reliable. A promising intervention can expose another obstacle without making the original finding wrong.
The Institute for Healthcare Improvement's testing guidance describes small local tests with a prediction, observations, reflection, and a decision about modification. It also emphasizes unexpected effects and testing under different conditions. This article adapts that learning discipline to an internal workplace process; it does not reproduce a clinical case or imply that one short pilot justifies organization-wide implementation.
Farah's three changes occur during the same week with different request groups. She can describe each observed path in this authored case, but cannot isolate a causal effect from the overall count. No control group, comparable long-term series, or stable mix of requests supports a claim that “training increased adoption” or that the form revision alone explains the result.
Check useful handoffs, downstream work, and extra burden
The nine eligible pilot requests produce seven usable queue submissions, approximately 78%. Two remain unusable: the incorrectly excluded revision and the attachment-blocked request. Farah reports seven of nine, rather than announcing that every trained person adopted the process or dropping difficult cases from the denominator.
She also checks what happened after submission. Five of the seven usable requests received triage within the agreed two-window weekly arrangement; two were late. Four reviews have taken place, two are waiting for reviewer availability, and one request was closed as a duplicate. A completed review is not an accepted design, and a booking record cannot establish a quality or delivery improvement.
The old calendar instruction caused one known duplicate chat entry. The pilot has not measured total preparation time, so Farah makes no time-saving claim. She records the incomplete attachment path and late triage as process-owner work, alongside the scope-example revision. The additional support is not silently assigned to Uma because she is the most comfortable user.
Farah's November 9 decision note reads:
Keep the concept-stage Release ID correction and the scope examples for another bounded cycle. I own adding the revised-design example and obtaining the approved attachment route. Drew owns correcting the obsolete invitation and confirming reviewer availability. We will check the next six eligible requests at the November 16 review, including late triage and duplicate work. No expansion is approved today. The attachment route, two late triages, and reviewer capacity remain unresolved.
The next review has not occurred. The note assigns actions its named owners accepted; it does not record future success. Where the process depends on another service owner's permission or capacity, Farah must obtain that agreement rather than treating an escalation as a completed fix.
Decide what to keep, revise, or stop
More training is appropriate when a person needs knowledge or practice and can use it in the real workflow. It cannot supply a nonexistent field value, make a reviewer available, or reconcile a manager’s conflicting expectations. Check each barrier again after repair: circumstances and expectations can change, and the first explanation need not remain the main obstacle.
If a step adds work without serving the stated purpose, ask its authorized owner whether to simplify, replace, or stop it. Preserve required controls and record the decision. Do not demand that employees invent evidence of use to protect a launch announcement.
Take one recent eligible task, reconstruct the actual path, and ask the authorized owner to agree on a repair, capacity, a bounded observation, and a review date. Use the completed records above to distinguish a learning need from a process failure. LandOffer.ai publishes this workplace guide; it does not administer your change program or promise adoption, productivity, or employment outcomes.



