Library / Human Capability Development Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:00:09 UTC

HCD.8:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsRepair
“Train the trainers”The missing provider task and current competent providers disappear behind a generic intervention.Name one missing contribution and compare obtain with build.
“The assessor passed the course”Completion does not show consistent judgement on the target cases.Preserve attempts, resolve criterion-level disagreement, and test another case.
“The lab has been designed”A description does not establish safe access, reset, load, or operation.Obtain direct-owner results and run a bounded operating test.
“We bought the platform”Acquisition does not establish configuration, capacity, provider work, or recipient access.Test the exact service contribution and handoffs.
“Every builder needs a builder”The map becomes an infinite programme rather than a located dependency.Stop when a compatible qualified contribution is available or return the first unsupported result.
“The specialist will enable it”The specialist’s result, timing, authority, and relation to the provider task are hidden.Request the exact domain result and preserve its conditions.
“One calibrated answer is enough”Memorized reproduction can conceal inability to discriminate a changed case.Use another representative case and observe disagreement handling.
“The service test proves the programme works”Provider operation is not learner receipt, learning, transfer, or retention.Route those questions to HCD.9 and HCD.11–HCD.13.