Application return to a programme and instrument designer

The specified FoundationsProgramme is a 34-week design with 340 learner hours, 240 teaching hours, 16 topics and 49 practiced patterns. Its two intended outcomes are checked performance of complete selected work tasks and lower effort to learn a previously untaught Method while preserving correctness. The release-review and support-workload cases illustrate the first; the proposed new-Method instrument below addresses the second. The quantities and outcomes describe a design, not observed learner gains. HCD can qualify programme, practice and evidence questions; the Learning Product owner still designs and resources the actual programme, tasks and instrument.

Before particular learners are known, the present decision concerns a learning product for a future audience. HCD.2 therefore returns the design values or candidate fragments needed for that product rather than inventing a personal recommendation. PSD can compare the author’s A/B/C learning-product options. Once one person becomes current, a personal HCD.2 comparison needs that same holder’s later Work, qualified target or profile, starting attempt, support conditions, feasible candidates and finite resources. It still stops before programme choice, commitment or launch.

At the original ten learner-hours per week, the three A/B/C compositions are 340-hour candidates. If participant time falls to six hours a week, the 34-week limit becomes 204 hours. All three original designs then require revision. The author must identify which 136 hours are removed or replaced, what complete-task practice and evidence are preserved, and whether both intended outcomes remain attainable. The three over-budget candidates do not establish that a suitable 204-hour programme exists.

This is a constraint on the whole proposed combination. In the original design, A allocates 202/96/42 learner hours to general/domain/joint application, B allocates 88/204/48, and C allocates 136/136/68; each totals 340. The usefulness of an individual topic, exercise or pair of contributions does not establish that all selected contributions fit the same learner’s 204 hours. Each revised candidate must account once for its complete learner effort and show that the required preparation, whole-task attempts, feedback, correction and evidence can coexist within that limit. The teacher’s separate contribution has its own limit and timing test below.

HCD.2’s useful immediate return is a comparable fragment for one complete task family. The author can retain C’s available detail and develop the smallest missing A/B fragment with the same output, audience assumptions, practice, help and evidence opportunity. HCD.5/.6 explain the different development contribution; HCD.7 tests the corresponding provider demand; HCD.8 enters only for an exact gap that must be obtained or built. The resulting comparison can expose a useful substitution or a remaining constraint. It still leaves the existence of a full 204-hour programme open. Changing an intended output is a separate target decision, as illustrated by HCD.2:5.2’s narrower 170-hour offer.

Teaching capacity is another contribution account. For twelve participants, 32 × 6.5 + 2 × 16 = 240 teaching hours and 240 / 12 = 20 hours per participant are planning allocations, not twenty hours of individual teacher contact. HCD.7 must establish the actual modelling, feedback, assessment, specialist, tool, AI and checking contributions at their working times and peak load. With twenty-four participants, the same per-person checking demand either doubles the checking work or requires an explicit split or changed service design; the 240-hour label cannot simply be reused.

The new programme-and-practice Methods make the design chain inspectable without turning it into a mandatory sequence. HCD.5 selects a Method from the target action, starting attempt, mechanism, task, provider, risk and evidence need. For a future audience it supplies conditional choices and the entry evidence needed to apply them. HCD.6 designs representative action-and-refusal contrasts, including compatible FW8 evidence and 24- versus 22-hour resource cases where the changed limit should change the answer. HCD.7 establishes the sources, tables, calculator, AI conditions, assessor competence, capacity, human checking and fallback. HCD.8 is used only if one exact contribution remains missing and obtaining or building it has to be decided.

For example, assessor preparation can use three contrasting answers: a supported ten-change proposal under 24 hours, an unsupported twelve-change promise under the same limit, and a justified request when the firmware evidence is absent. Independent judgements and criterion-level disagreement resolution are preparation. Consistent and timely judgement on a changed 22-hour case is the bounded operating test; it does not establish general assessor capability, whole-window service operation or a learner effect.

HCD.9 then keeps the learner’s first attempt, actual help, criterion-bearing feedback, correction, targeted retry and next focus separate. HCD.10 can vary a decision-bearing condition, return to the target after an interval, interleave a competing Method family, or change support or challenge. None of these designs by itself establishes improved capability, transfer, retention or causal effectiveness.

Its planned delayed visits concern six selected patterns: F.1, F.0.1, C.16, B.5.2, A.10.1 and C.11.

Weeks 8, 17, 25 and 34 are an HCD.10 spacing design only because they are separated returns to selected contributions with intervening practice made visible. HCD.13 owns any later inference about retained performance or support dependence. Calendar dates alone establish neither retrieval nor retention.

The thirty-minute final core contains one fifteen-minute no-AI fragment; supplied tables and a calculator remain available. The main task retains ordinary pattern and AI access. The fragment tests recovery of the configuration and time constraints, rejection of an unsupported release, and a valid next proposal. It is not a compressed closed-book examination of the whole course. An additional six-to-eight-week follow-up outside the programme needs separately agreed time, assessor and access.

The proposed Q2 unfamiliar-Method instrument remains a distinct design task:

These sixty minutes replace the existing one-hour task; they do not add an hour to the 340-hour design. The designer must still show that the tasks fit. A proposed ME.14 task must test its new practical-disposition contribution against current alternatives; a SYSE.23 task must distinguish target-system change from enabling-platform change and test the anticipated future benefit. Familiar cost arithmetic or reused C.11 comparison alone cannot demonstrate acquisition of either whole contribution.

Retain recognition, first and corrected performance, new-source contribution, help, time, material errors and unfinished attempts separately. “Faster learning at unchanged correctness” needs actual comparable observations; different Methods at weeks 17 and 34 do not isolate a training effect. The three-to-five-hour instrument-authoring estimate is not the cost of a learner experiment. These specifications supply no Q2 result, pilot extension or actual learner trial.