Core Competencies · Protecting · Component
The embedding record
What has been done to hold each competence in the organisation rather than in individuals — and what that has cost.
The deliverable
What it is
Embedding trades flexibility for durability. A competence written into a process is harder to lose and harder to change, and both halves of that are real.
The record exists because embedding work is invisible once complete, which makes it the first thing cut in the following year’s planning.
One level in
What it is made of
Each element is a constituent part of the component. Follow one to see the attributes it carries.
The embedding work
What was done — documentation, cross-training, process, tooling — and when.
3 attributes: Method · Completed · Cost
LearnThe coverage
How much of the competence has actually been embedded.
3 attributes: Coverage · Not covered · Confidence
LearnThe freshness
Whether the embedded version still matches how the work is actually done.
3 attributes: Last verified · Status · Review trigger
Learn
Documentation captures the standard case and leaves the exceptions, which is where the capability actually lives. State the coverage honestly.
The other components in protecting
The dependency map
What each competence actually rests on — the people, systems, relationships and knowledge without which it stops working.
LearnThe erosion watch
The indicators that would show a competence weakening, checked by someone, before the loss becomes obvious.
Learn