n.V7-2.02| Divisions, Groups, Circles
01| Three things at IkoCiti are permanent and one is not. The permanent three are divisions, groups and operators. The temporary one is the Circle. Almost every structural mistake an organization makes is a mistake about which category something belongs in, so it is worth being exact before going further.
02| A division is a domain of the platform and a home for the people who work in it. There are ten. Each is led by a Division Leader who sits in the Global Management Team, and each holds a budget, a headcount and a permanent responsibility that does not expire. What a division does not hold is any outcome that crosses its own boundary. That limitation is not an oversight. It is the reason Circles exist.
03| A group is a permanent capability team inside a division — five to seven of them per division, around sixty-five across the platform. The group is the real unit of capability at IkoCiti. When we say the platform can do something, we mean a specific group can do it, has done it before, and will still be able to do it next year. Below the group, operators run the day-to-day: the standing work that has to happen on Tuesday whether or not anything interesting is going on.
04| Every division and group carries a number. Divisions run 1000 to 10000, groups run x010 to x070. Government Coordination is 4030. The PI Exchange is 7030. This looks like bureaucratic decoration and it is not. An organization operating in several countries, in several languages, with local partners who have never met each other, needs to be able to name a thing unambiguously. 4030 means precisely the same thing in Medellín and in Nairobi, and it will still mean it after the group has been renamed twice. Addressability is cheap. Ambiguity is not.
05| Then there is the Circle: a temporary team that forms across a boundary, takes ownership of a project, and dissolves when the project is finished or judged unsalvageable. It is sized to the work — a Division Circle across groups inside one division, an Iko Circle across divisions, a CITI Circle where Global and local people build something together — and it borrows its people from the divisions rather than owning them.
06| The distinction that matters is this: capability is permanent, work is temporary. Most organizations know this and act as though they don't. When the work changes they reorganize the permanent structure to match it — new departments, new reporting lines, a fresh chart every eighteen months — and each reorganization destroys accumulated capability in order to serve a project that will be over in a year. We separate the two so that we never have to make that trade. The work reshapes itself constantly through Circles. The capability underneath sits still and gets better.
07| A Circle runs through five functions and they are worth naming because each one is a way Circles fail elsewhere. Formation gives it a charter that fixes purpose and scope, staff matched to the skills required, and a shared workspace before it starts. Leadership owns it — scope, direction, the contributed staff, and the call on whether a struggling Circle continues, restructures or terminates. Delivery drives the project to done: handoffs between contributing groups, blockers flagged and cleared, one shared view of where every part stands. Monitoring watches two different things — health, meaning is the Circle functioning at all, and performance, meaning is it worth the staff time it consumes. Reporting turns that record into an account for platform leadership, so the coordination layer is judged on results rather than assumed useful.
08| Termination deserves its own sentence. Someone must be able to close a Circle, and it must be easy. Temporary structures that cannot be killed are how organizations acquire permanent structure without ever deciding to.
09| One power sits deliberately outside the Circle. The escalation right — the ability of qualified Ikosi to lift a major decision to a higher body — is not a Circle function, because a leadership cannot own the mechanism that checks it, and because the right runs platform-wide rather than Circle by Circle. Inside a Circle, leadership leads. It leads under an external check it does not administer.
10| Two clarifications on ownership. Circles are staff-only: they never include Maveriqs, and they share no boundary with the Kikundi, the Maveriq teams that design PI projects. The two run on separate layers and do not touch — Kikundi build impact projects in the barrio, Circles coordinate the platform's own internal work. And the craft of building a Circle sits with group 5020, which matches people, manages Circle Captains and monitors team health; the Circle then runs its own project. 5020 builds the vehicle. The Circle drives it.
11| Divisions to house capability. Groups to hold it. Operators to keep it running. Circles to spend it on something that crosses a line. Everything else in this book part is an application of those four words.
THE END
