n.V4-2.06| CAPABILITY: INTELLIGENCE THAT PRODUCED SOMETHING

01| Intelligence is potential energy. Capability is work done. The distinction is the whole reason this part carries both words in its title, and it is where the argument turns from what people are to what the organization can actually deliver.

02| A capability is not a person. It is a defined area of competence that produces a specific deliverable — a community needs assessment, a trained rookie, a project quality rating, a set of accounts that balance. It normally involves several people, some machine support, and a documented way of working. Every deliverable in IkoCiti traces back to one, which is how accountability stays findable when something goes wrong.

03| We run on more than three hundred of them, across ten divisions. That number is either impressive or alarming depending on whether they are improving, and most of them, today, are not — because most of them do not exist yet outside a document.

04| Capabilities move through five stages, and knowing which stage a capability is in tells you what to do about it.

05| Initial. It happens, and quality depends entirely on who is doing it. The knowledge is in one head. When that person leaves, the capability leaves.

06| Repeatable. Somebody wrote down how it is done. Quality is still uneven but the work no longer depends on one specific person.

07| Defined. Real standards exist, the training materials work, and one Maveriq can teach another to do it. This is the stage that makes peer-to-peer teaching possible — below it, teaching just propagates whatever the teacher happened to figure out.

08| Managed. It is measured. We know its normal performance, we can see variation, and improvement is driven by evidence rather than by whoever complained loudest.

09| Optimizing. It innovates on itself, performs at a level worth copying, and could be taught to organizations outside IkoCiti. Very few capabilities ever need to get here.

10| Almost everything we have starts at stage one. The goal is not to drag three hundred capabilities to stage five — that is a fantasy and an expensive one. The goal is that none of them stay at stage one, because stage one is where knowledge dies with the person holding it, and our entire replication model assumes it does not.

11| That is the structural point and it is worth being blunt about. Viral replication amplifies whatever it finds. If a capability is at stage three and improving, peer teaching spreads the improvement. If it is at stage one, peer teaching spreads one person's habits, including the bad ones, and does it faster every generation. The trajectory of the capability becomes the trajectory of the network. This is the mechanism by which a good idea degrades into a mediocre franchise, and it does not require anybody to make a mistake.

12| What moves a capability up the stages is unglamorous. Deliberate practice — not repetition, but focused work on the specific weak component, with feedback fast enough to matter, at the edge of what the person can currently do. Feedback loops that are real: peer review, mentor observation, outcome data, and what the community actually says afterwards. Documentation that gets the knowledge out of the head and into a form somebody else can use. Communities of practice, where people doing the same job across different CITIs compare notes horizontally, without routing through the centre. And machine support that spots the gap, surfaces the relevant past case at the moment of need, and tracks whether any of it is working.

13| How do we know a capability is improving rather than just busy? Six signals. Is the output meeting standard, and better than last quarter. Is it taking less effort. Is it consistent across different people and different places. Can it handle something it has not seen before. How fast does a newcomer reach competence — the transfer rate, which is the one that matters most for replication. And is it generating new practice, or only repeating old practice well.

14| Not every capability deserves the same investment. Priority goes to three kinds: the strategically critical, the currently failing, and the high-leverage ones whose improvement cascades into many others. Spreading investment evenly across three hundred capabilities develops none of them.

15| None of these mechanisms survive a culture that resists them. Honest self-assessment, willingness to do unglamorous practice, and a teaching orientation that treats sharing capability as the job rather than as a threat to personal standing. A sophisticated system in a defensive culture produces nothing. A simple system in a learning culture produces a great deal.