The working difficulty and the first bounded return
Mira is an engineer-manager who prepares release-review handovers. She has four months to improve that work. “Learn more patterns” is her initial idea. Her receiving need is more specific: distinguish an already adequate specialist result from a missing result, select a worthwhile further contribution, and avoid carrying a result into a changed configuration without qualification.
For this case, a qualified HCD practitioner has recovered representative later-Work demand and evidence of Mira’s present performance under the available checklist and technical reference, using the target practice’s qualified correctness criteria. Mira’s responses adequately qualified three of five receiving uses; in the two changed-configuration cases they relied on unsupported transfer. The result concerns those tasks and supports. It does not establish unaided performance, a general mastery score, or transfer to every engineering setting.
DOCA.1 bounds Mira, that later Work and the four-month horizon. She needs a first direction question by Friday. Two short discussion sessions are available, but the support owner cannot provide a qualified capacity answer this week. The existing HCD result already supports construction of conditional personal-practice and review-support directions. Mira therefore uses that result now and carries the capacity gap; another meeting would not qualify it. Reopen acquisition when an obtainable answer could change the directions or their use.
Development activity must fit within the existing thirty-eight-hour working week; at most three hours a week can be reassigned, with the displaced activity named. Protected conditions include no disclosure of restricted release data and no unsupported technical acceptance. Mira is the recipient and direction chooser; an employer’s staffing decision remains a different use.
DOCA.1.CHR replaces “become more mature” with the needed readings:
| Coordinate and scale | Current reading in this case | Intended or protected condition |
|---|---|---|
| Adequately qualified handovers, count out of the same five representative tasks; higher is better | 3/5 with the stated checklist and reference | 5/5 under the intended receiving conditions; a target, not an obtained result. |
| Unsupported technical acceptances, count in that task set; lower is better | 2/5 | Protected: zero in the claimed qualified task set. |
| Total work burden, hours per week; lower within the required output is preferable | 38 | Do not exceed 38; development displaces at most three hours of named existing work. |
| Mentor/specialist capacity, hours per week; lower consumption preserves capacity | Extra usable capacity is unknown. | Confirm the capacity before a direction or programme relies on it. |
| Additional work shifted to release colleagues, hours per week; lower is preferable | None from this proposed change, which has not begun. | Qualify who absorbs or stops the displaced work and the resulting burden; spare capacity is not assumed. |
| Information disclosure, permitted/not permitted for each recipient and purpose; prohibited use is inadmissible | The technical reference and anonymized examples are permitted | No raw restricted release data in the learning or advice service. |
| Transfer to unfamiliar configurations, qualified/unqualified/unknown for a stated task family | Unknown | Obtain HCD and target-domain evidence before claiming that transfer. |
Counts, time, permission and qualification readings answer different questions. Do not sum them into one maturity score or code an unknown reading as poor performance.