HCD.1 — Derive Human Capability Demand from Representative Later Work
Type: Human Capability Development practitioner method pattern Status: Stable
HCD.1:0 - Use This When
Use this pattern when someone asks what a named person must be able to contribute in later Work and the available request is still expressed as a job title, competency list, course request, platform score, MethodDescription, or technology rollout. Begin with the person and representative cases of their later Work.
The first useful result is a human capability-demand account. State what the person must contribute in the particular planned job or across the recurring work being considered, under which configuration and conditions, over what horizon, and which question or decision the account will support. If the account of future Work is grounded but evidence of current performance is insufficient, return a prospective demand hypothesis and the observations that could qualify it. Use an applicable result already available for specialist judgement, assignment, access, tools or nonhuman capability. If another practice still needs to answer or decide a question, give it the question and available evidence. If its source is unknown, identify the contribution needed. State which conclusions still need evidence and what would support them.
The demand identifies what a later diagnosis or profile comparison should examine. Use HCD.3 when the demand is known and the question is which changeable human limitation, if any, is supported. Use HCD.4 when the demand is known and simultaneous capability claims must be compared. A separate programme comparison (HCD.2) may use the account; deriving demand does not select a programme.
Use the relevant professional practice and authority for clinical, curriculum, provider, employment, safety and release decisions or a judgement of target-domain correctness.
HCD.1:0.1 - Working Terms
| Name in this pattern | What it denotes |
|---|---|
| human holder | One identified person whose capability demand is being considered. For a population question, use separately identified member accounts or representative accounts. |
| later Work | The work in which this person will need to act. Name the intended task if the demand concerns one occasion. For a demand across recurring situations, state what the jobs share and which differences matter. |
| representative case | A case selected to examine a material variant of later Work, such as unfamiliar content, changed support, or a specialist interface. Its suitability depends on the conditions it represents and the conclusion for which it is used. |
| human capability demand | The contributions this person needs to be able to make under the named later-Work conditions. A demand account records those requirements; it does not establish the person’s current capability. |
| demand claim | A statement that this person needs to be able to make a specified contribution under the named later-Work conditions, with the grounds for that requirement, remaining uncertainty and scope. |
| prospective demand hypothesis | A provisional account of future demand grounded in a supported future-Work frame. It states which demand claims remain provisional and which observations could qualify or revise them. |
| demand-evidence-blocked | A result that names each missing input, the conclusion it blocks, and the condition for retry. It also distinguishes available material from the missing input when that material could mislead the receiver. |
| outside-HCD return | The question and available evidence returned to the practice that can answer or decide it. If that practice is unknown, identify the contribution needed. |
The account records what later Work requires of the person. Use evidence and a method suited to the separate question about present capability, causes, learning or intervention effectiveness.
HCD.1:1 - Problem Frame
Human development is often commissioned on the strength of a course catalogue, certification, role framework, AI platform, assessment dashboard, or manager’s request. Those sources can be useful, but none identifies by itself what a particular person must contribute in later Work.
The same named task can require different contributions when the product configuration, Method, information access, AI support, time, authority, specialist interface, or critical-error boundary changes. Assisted performance may also conceal which contribution belongs to the person and which belongs to a tool, another Agent, or an organization.
Demand therefore has to be recovered from representative Work and its intended result. Current observations are valuable, but future planning sometimes precedes an actual Work occurrence. State what the future arrangement suggests and what observations would establish current demand.
HCD.1:2 - Problem
A role-first or course-first description bundles unlike things. It can call a missing Method, inaccessible source, broken tool, absent specialist result, poor assignment, unsafe workload, or organizational constraint a human skill gap. It can also average across a population and then assign the average to one person.
The reverse mistake is to refuse any demand account until the exact future Work has occurred. An account of the planned arrangement can already identify a provisional human contribution and an observation that would test it. The practitioner needs a result that distinguishes what can be framed now, what is qualified now, what belongs elsewhere, and exactly what evidence blocks the stronger conclusion.
HCD.1:3 - Forces
- A short role label is easy to communicate, while the consequential demand usually depends on case variants, interfaces, and error boundaries.
- A MethodDescription can describe how the Work should be done. Ground a claim about a particular performance or result in that occurrence. For a claim about representative work, use evidence from cases that fit the claim.
- Current task success is visible, while later transfer and unfamiliar variants must be established rather than presumed.
- AI and other supports can improve the joint result, while assisted output is not automatically human capability.
- Population summaries help allocation, while a person-specific decision requires a person-specific holder and compatible evidence.
- Evidence can be insufficient for a current demand while a useful prospective hypothesis may still guide observation.
- HCD can organize demand evidence, while target-domain correctness, specialist judgement, assignment, safety, release, and employment authority stay elsewhere.
HCD.1:4 - Solution
Derive each required human contribution from representative later Work. Distinguish observed cases from plans, stipulations and assumptions. Identify which contributions the person must make, what others or the environment must supply, and how strongly the available evidence supports each requirement.
HCD.1:4.1 - Pattern-Use Unfolding
- Fix the use boundary and holder. Identify the person, the question or decision the account will serve, the planned task or range of later work, subject configuration, effective horizon, and evidence window. If the question concerns a population, identify the separately observed members or representative accounts; do not manufacture one aggregate holder.
- Recover the later-Work basis. For every case, distinguish what was observed from what is planned, stipulated, or assumed. Explain which later Work and material conditions the case represents, and why its evidence is suitable for the intended conclusion. Recover the intended result, quality and critical-error predicates, Work products, and stopping conditions.
- Recover Methods and direct-owner inputs. Identify applicable target Methods or MethodDescriptions, specialist results, assignments, authority, access, environment, tools, and supports. State any missing external condition or contribution and what depends on it.
- Select representative cases. Cover the variants that can change demand. Depending on the Work, these may include familiar and unfamiliar situations, allowed and withdrawn assistance, time or workload limits, AI-output challenge, coordination interfaces, specialist-return conditions, and material quality or critical-error boundaries.
- Derive human demand claims. For each case, state which contribution the named person must be able to make for the intended result under the protected conditions and why the evidence warrants that requirement. Contributions may include, for example, noticing a signal, handling an object, coordinating a specialist return, or justifying a decision. Record required tools and supports as conditions of the contribution. Keep each contribution distinct from the Method, task, tool output, team result, or personal trait.
- Bind evidence and uncertainty. Relate each demand claim to the cases, observations, work products, inference rule, uncertainty and any observation still needed. Keep instruction events, learner events, learning outcomes, later transfer, and job performance distinct; one does not establish the next by label alone.
- Return a conclusion-specific disposition. Return
qualified current demand,prospective demand hypothesis,outside-HCD return, ordemand-evidence-blocked. Different questions may lawfully receive different dispositions in one use—for example, a prospective hypothesis for future framing and a blocker for qualified current demand.
HCD.1:4.2 - Record the Result
A human capability-demand account contains these result positions:
| Result position | Required content |
|---|---|
| use boundary | Human holder, receiving question or decision, planned task or range of later work, configuration, effective horizon, evidence window, and direct owners whose results or authority matter. |
| later-Work basis | Cases, what was observed or remains planned, stipulated, or assumed, and the later Work and conditions they represent; reasons the evidence is suitable for the conclusion; intended result, quality and critical-error predicates, Work products, and stop conditions. |
| protected conditions | Allowed or required tools, AI posture, information access, time, environment, assignment, authority, supports, and specialist interfaces. |
| demand claims | Statements of the human contributions required in the named later Work, including material interfaces among simultaneous contributions. Derive these requirements from the cases rather than assigning capability from job labels or traits. |
| evidence account | Evidence and inference for every demand claim, uncertainty, incompatible evidence, and any observation or case still needed. |
| external gaps | Missing Method, description, specialist return, assignment, authority, access, environment, or nonhuman capability with the work or conclusion that depends on it and its responsible source where known. |
| disposition | One conclusion-specific qualified current demand, prospective demand hypothesis, outside-HCD return, or demand-evidence-blocked. |
| continuation | Compatible inputs that HCD.3, HCD.4, or a future programme comparison may consume, plus scope limits and reopen conditions. |
For each input that a conclusion needs and still lacks, explain what it would establish and what would allow reconsideration. Use the following fields where they apply.
| Missing-value field | Required content |
|---|---|
| missing kind | For example later-Work-occurrence-missing, later-Work-result-claim-missing, result-record-missing, representative-observation-evidence-missing, or a named external supplier result. |
| blocked conclusion | The exact conclusion that cannot be supported without this value. |
| available non-substitute, when relevant | If available material could plausibly be mistaken for the missing input, name it and explain why it cannot fill this gap. |
| retry condition | The input that must become available or be confirmed before reconsidering the named conclusion. State its required connection to the person, Work, and conditions, using only qualifiers that affect that conclusion. |
Use qualified direct observations when they suffice. If the claim depends on a result record, establish its connection to the Work and the result.
HCD.1:4.3 - Population and Reuse Boundary
A population use may return a distribution over separately identified member or representative demand accounts. It does not create one person’s demand by averaging, and it does not turn the population into a capability holder. A population whole qualifies as a holder only through the independent-System condition of E.23.CDI, outside this one-human-holder pattern.
For another use, check that the person, configuration, later-Work conditions, horizon and evidence window support the new question or decision. Carry over the applicable limits. HCD.3 may consume the account as evidence input; HCD.4 may consume it as a scope and result frame. Programme comparison (HCD.2) may use the same frame. Deriving demand requires no programme-comparison result.
HCD.1:4.4 - What Changes in Practice
Ask “What must this person contribute in which later Work, under which conditions, and what evidence makes that demand current?” The answer either supports a bounded demand, makes a future hypothesis testable, returns the question to its owner, or exposes the exact missing evidence.
HCD.1:5 - Archetypal Grounding
HCD.1:5.1 - Constructed Positive Case: ImpactReview-17
ImpactReview-17 is a constructed case. Its answer key, ImpactReview-17-Domain-Oracle-v1, supplies the engineering correctness and criticality criteria for PumpWorks-Config-Baseline-42 and AI-Assist-M4. The review events and evidence below are stipulated case data.
The human holder is Engineer-P14. The later-Work family is independent review of AI-proposed change-impact claims for mixed physical/software pump-controller changes before separate integration, assurance, and release decisions. The constructed 2026-Q4 conditions include the named configuration and AI assistant, current source access, a forty-five-minute case limit, recoverable audit records, and bounded safety and maintenance specialist returns. Final integration, safety, release, and employment authority remain with their direct owners.
The stipulated work permits a routine reminder to construct and test an alternative configuration hypothesis. The engineer must supply the case-specific hypothesis and test, then decide whether to reject the AI claim. Remembering to initiate the operation without a reminder is a separate, stronger question.
The evidence packet stipulates eight representative review occurrences: four familiar and four unfamiliar variants; four include a plausible but wrong AI dependency claim; two require a specialist return; and every case requires a recoverable audit record. HCD.1 returns this human capability demand for Engineer-P14:
- recognize when the independent-review Method applies;
- trace each release-affecting claim to the current source and configuration;
- independently develop and test an alternative explanation before accepting a plausible AI claim;
- define the specialist contribution needed, obtain it when it is missing and retain the applicable result;
- return auditable evidence; and
- detect every seeded safety-critical omission within the protected time and authority boundary.
Within this example, the stipulated criteria and observations support qualified current demand for Engineer-P14. The case shows how to derive required human contributions from representative Work; demand does not establish the person’s current capability. For an operational conclusion, use applicable domain criteria, any necessary specialist or safety inputs, and representative evidence for the person and Work in question.
HCD.1:5.2 - Missing Case: ReleaseWork-R9
For Engineer-E27, the accepted architecture supports a prospective demand hypothesis for 2026-Q4 ReleaseWork-R9: AI-output challenge, configuration-impact reasoning, evidence return, specialist coordination, critical-error detection, and adaptation across unfamiliar mixed physical/software variants may be required. The proposed requirements identify what to observe.
The stronger conclusion is blocked by distinct absent values:
| Missing value | Blocked HCD.1 use | Non-substitute and retry |
|---|---|---|
XRI-21-supplier-result-missing | Any demand claim that consumes current engineering-culture enactment, its bounded practice-change decision, retained alternatives, or evidence gaps. | The current SYSE.21 MethodDescription and its constructed PumpWorks demonstration can shape questions but are not the actual supplier result. Retry with a compatible actual SYSE.21 result—or a receiver-permitted qualified direct substitute—for Engineer-E27, the Method, Work, period, and evidence use. |
later-Work-occurrence-missing | Treating ReleaseWork-R9 itself as current later-Work evidence. | A plan, architecture, MethodDescription, or constructed occurrence does not establish enactment. Retry when an admitted performed Work occurrence identifies Engineer-E27, configuration, period, and actual performer. |
later-Work-result-claim-missing | Any demand claim whose evidence consumes the occurrence-produced result, quality, error, or consequence. | A planned result or demonstration result is not the occurrence’s result. Retry with the produced result or a supported direct claim tied to the admitted occurrence. |
result-record-missing | Any record-dependent inference about that occurrence or result. | An orphan document would not establish the Work or result. Retry when a current result record links the admitted Work occurrence to its produced result; omit this requirement where qualified direct observations are sufficient. |
representative-observation-evidence-missing | Upgrading the prospective hypothesis to qualified current demand. | A target repertoire, curriculum, course completion, platform score, or constructed case is not representative observation evidence. Retry with holder- and condition-compatible observations or a named qualified representative case set covering performed Method, configuration, work products, quality and critical errors, AI/support posture, specialist returns, variants, and evidence window. |
Recovering one input permits reconsideration of the conclusions that depend on it.
HCD.1:5.3 - Unlike Case: Clinical Ownership
Return an adult’s request for treatment of social anxiety to a qualified clinical specialist as an outside-HCD return. HCD.1 may address a separately posed, legitimate question about that person’s non-clinical participation in later Work, supplied by the person or qualified clinical owner. Diagnosis, treatment choice, provider competence, safety, consent, and clinical outcome interpretation remain with the qualified clinical route.
HCD.1:6 - Bias-Annotation
| Recurring bias | Likely drift | Repair |
|---|---|---|
| training-solution bias | The requested course or certification is treated as the demand. | Recover the human holder and representative later Work before considering any learning product. |
| role-average bias | A job-family profile is assigned to one person or one population average is reified as a person’s demand. | Keep holder-specific accounts and report population distributions separately. |
| current-arrangement bias | Today’s Method, tool, or division of labour is assumed to be the only future demand. | Name the effective horizon, alternatives, supports, and configuration; preserve prospective uncertainty. |
| technology bias | AI-assisted or tool-supported output is attributed to the human holder. | Separate human, tool, specialist, team, and organization contributions and test material support conditions. |
| evidence-convenience bias | Completion, self-report, platform prediction, MethodDescription, or visible document substitutes for later-Work evidence. | Trace each demand claim to representative cases, observations, inference, uncertainty, and remaining evidence. |
| human-deficit bias | Missing access, authority, assignment, Method, environment, specialist result, or nonhuman capability is called a skill gap. | Identify the missing condition and its responsible source if known. |
| occurrence maximalism | No future question is allowed until the exact Work occurs. | Return a prospective demand hypothesis with observations-to-obtain, while blocking only the stronger current conclusion. |
HCD.1:7 - Conformance Checklist
- The person whose contribution is in question is identified; any population use preserves member or representative accounts.
- The planned task or range of later work, configuration, effective horizon, evidence window, and receiving question or decision are explicit.
- Each case distinguishes observed facts from plans, stipulations, and assumptions, and explains which later-Work conditions it represents and why its evidence is suitable for the conclusion.
- Intended results, quality and critical-error predicates, protected conditions, tools, supports, and specialist interfaces are recoverable.
- Each demand claim names a human contribution supported by representative Work rather than a job label, trait, task, MethodDescription, or course.
- Human, AI, tool, specialist, team, organization, assignment, authority, and environment contributions or gaps remain distinct.
- Each demand claim states its grounds, their limits, remaining uncertainty and any observation still needed.
- Each conclusion has its own disposition. A supported prospective hypothesis can be returned while current demand remains unestablished.
- Every blocker names the missing input, blocked conclusion, and retry condition; available material is distinguished from that input when it could mislead the receiver.
- Before reusing the demand account, check that the holder, configuration, conditions, horizon and evidence window fit the receiving question or decision.
- The first result selects no curriculum, provider, intervention, assessment programme, treatment, safety action, release action, or employment action.
HCD.1:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Why it fails | Repair |
|---|---|---|
| “The role requires these competencies” | The role label hides case variants, conditions, and the exact holder. | Derive claim-sized contributions from representative later Work for the named person. |
| “The course objective is the capability demand” | A course objective does not by itself establish what this person’s later Work requires. | Derive the demand from later Work. Compare programmes for meeting it if a comparison is requested. |
| “The MethodDescription proves the Work” | A description makes claims about a Method; it does not establish enactment, result, or observation. | Use the description to frame the question. For a particular occurrence, use evidence tied to that occurrence. For a representative demand claim, use qualified cases. State what remains unknown. |
| “The tool score is the person’s capability” | The score may describe joint or model-dependent performance. | State support conditions and recover direct task evidence and inference limits. |
| “One missing record means no evidence exists” | Direct observations may support the conclusion without a record, while an orphan record may support nothing about the occurrence. | Name the evidence actually consumed and require a record only for a record-dependent use. |
| “The average employee is the holder” | Aggregation erases person, condition, and evidence identity. | Keep individual accounts or an explicit distribution; use E.23.CDI before treating a population whole as holder. |
| “HCD.2 must come next” | Numbering is mistaken for a lifecycle and invites premature programme design. | Route independently to HCD.3 or HCD.4 when their qualified inputs exist. Compare programmes when the question calls for it and the inputs support it. |
| “Poor outcome means training” | Method, tool, assignment, access, organization, nonhuman capability, or specialist causes may dominate. | Identify the supported cause or remaining gap. Refer a question that needs another participant’s contribution to that participant. Use HCD.3 if a diagnostic question remains. |
HCD.1:9 - Consequences
The demand account gives its recipient grounds for diagnosis, profile comparison, evidence collection or a later programme comparison. A supported hypothesis can guide planning before the work begins. When evidence is missing, state which stronger conclusion it would support.
The cost is more careful case selection and relation keeping. Demand may vary across configurations, supports, horizons, and holders; some visible requests will return outside HCD. Evidence collection may reveal that the main constraint is not human capability.
HCD.1:10 - Rationale
Beginning from representative later Work shows how the intended results and conditions constrain the required human contributions. Use cases relevant to the named person to establish what their work requires. A role or cohort average alone cannot establish that demand or their present capability.
A prospective hypothesis can guide planning. Naming the missing evidence tells the recipient which current conclusion must wait and what could support it. Keeping external gaps under their own kinds prevents HCD from taking authority over target Methods, specialist results, assignments, safety, release, or employment.
HCD.1:11 - SoTA-Echoing
How should a practitioner derive a human capability demand that is useful for later development decisions and still warranted by later-Work evidence?
Representative-work analysis uses the workplace-instruction distinctions summarized by Kraiger and Ford’s 2021 review (COG-10): instructional events, learner events, learning outcomes, transfer, and job performance must be distinguished, and claims about each need corresponding evidence. Transfer must be established under material learner, design, opportunity, support, and work-environment conditions. Direct target-domain evidence supplies what counts as correct, safe, critical, or useful in the actual Work. Where AI assistance is material, Dell’Acqua and colleagues’ Navigating the jagged technological frontier (AI-03) supplies a bounded cue to test independent error detection under the named task and model conditions. It establishes neither a universal AI-task boundary nor this person’s engineering capability.
A serious operational alternative is a role-first competency framework or training-needs inventory. A shared role inventory can cost less to publish than individual demand accounts and can help communicate across the workforce. Check whose work it covers, which case variations, tool and specialist interfaces and critical errors it represents, and whether it distinguishes learning outcomes from later performance. Use those inventories to find candidate requirements, then derive and qualify each demand claim from representative Work.
For ReleaseWork-R9, the proposed architecture and the evidence in §5.2 support a future hypothesis. Obtain domain grounds for the correctness claims on which an operational demand depends. Reopen a demand claim when its holder, Work family, Method, configuration, support posture, quality or critical-error predicate, effective horizon, evidence window, direct source, or receiving decision changes. A later stronger source reopens only the claims whose move or limit it changes.
HCD.1:12 - Relations
A.15.1and current Work ontology: keep Method, Work occurrence, performer, result, and result episteme distinct.E.23.CDI: governs whether a population whole is an independent System capable of holding capability; HCD.1 otherwise stays at one-human-holder granularity.E.23.CAE: supplies capability-evidence boundaries for downstream observations; evidence does not itself authorize intervention or employment action.COG-10: supplies the event-to-transfer distinction and the requirement to qualify workplace opportunity, support, and environment.- Dell’Acqua and colleagues, Navigating the jagged technological frontier (
AI-03): supplies the bounded independent-error-challenge cue where assisted Work makes that contribution material. - Target-domain Methods and results: determine correctness, quality, criticality, and specialist boundaries. Use the applicable domain result to judge the required contribution.
SYSE.21/XRI-21: a compatible result may supply evidence of later enactment and its limits. Reuse an actual practice decision or retained alternatives when such results exist and the demand question needs them. A MethodDescription or constructed demonstration can frame an inquiry.HCD.3: may consume a compatible HCD.1 account when examining a possible human limitation or another source of difficulty.HCD.4: may consume a compatible HCD.1 account to define the scope and required results of a profile comparison under stated conditions.- Programme comparison (
HCD.2): may consume the demand account and evidence requirements when comparing programmes. - Clinical, safety, legal, employment, specialist, organization, provider, and release owners: retain their direct decisions and authority.