II-05 — Implementation Capability: What a Carrier Can Repeatably Do
Description
This paper defines Implementation Capability, the third of four foundational concepts in the Implementation Intelligence programme. An implementation capability is a set of repeatable routines that a carrier can deploy to act on an implementation object. The concept's purpose is to record what an actor can reliably do — as evidenced by what it has repeatedly done — as distinct from what it knows, what the setting supplies, and what forms it has adopted. The paper establishes that capability is bounded by three conditions taken together — repeatability, deployability, and person-independence — that distinguish a genuine capability from a lucky performance, a favourable circumstance, or a single individual's skill. It establishes that capability is carrier-borne, residing in members, tasks, tools, and the networks among them, and portable only to the degree its carrier can be relocated, which makes portability graded rather than binary and predicts which capabilities transfer well. It establishes that capability is non-monotonic: it can be degraded, rather than strengthened, by demand placed on it before it is established, a documented failure the paper terms premature load-bearing. It describes a sub-type, Dynamic Implementation Capability, directed at the development of an actor's own routines and adopted from the dynamic-capabilities literature. Throughout, the concept is built to resist a specific error — mistaking the visible forms of capability (teams, plans, boards, charters) for capability itself — by defining capability as demonstrated routine rather than adopted form and specifying observation through documentary, self-report-resistant indicators. The paper distinguishes capability from capacity, knowledge, and organisational structures and states open questions on which the concept depends, foremost the separability of Capability from Implementation Knowledge under shared carriers, which the programme holds as its most consequential open empirical question.
Files
Yun Consultancy II-05 Implementation Capability - What a Carrier Can Repeatably Do.pdf
Files
(872.9 kB)
| Name | Size | Download all |
|---|---|---|
|
md5:e0f7870d9608fd09adc2fd5843196f3f
|
872.9 kB | Preview Download |