n.V5-7.03 | THE SCOREBOARD AND THE SEVEN FUNCTIONS

01| In most organizations, leaders manage people. They hire, fire, direct work, evaluate performance, and sit at the top of a chart with names underneath. We reject that model — not as a softer alternative, but as a different one. Our leaders coordinate work, judge quality, and facilitate collaboration. Hiring, firing and team formation happen through other mechanisms entirely.

02| Two ideas hold it together, and both are uncomfortable. Performance is measured, ranked, and made public. Leaders coordinate without controlling.

03| The principle is blunt: you are as good as your ranking. Not as good as your last deliverable — that is too volatile and rewards noise. Ikosi earn points for activities and are ranked in league tables that reflect accumulated performance, with recent work weighted more heavily and the full track record visible. The tables are public. GMT members, Division leaders and Pro.Crowd teams are all on them.

04| Why rankings instead of credentials? Because inside a coordination platform, diplomas and titles predict very little. What someone achieved at another organization, under other constraints, with other people, tells us less than what they are delivering here this quarter. The ranking captures that. The credential cannot, which is precisely why credentials are so popular: they are permanent, and performance is not.

05| This is not meritocracy, and we should stop using the word. Meritocracy assumes equal starting points, which have never existed anywhere. This is performance measurement with full transparency. Starting points differ. The scoring rules do not, and everyone can see them.

06| The reason the standards are non-negotiable is structural rather than moral. In coordination infrastructure, a weak link breaks the chain for everyone. One underperforming Division becomes a bottleneck for every other Division. One Pro.Crowd team delivering poor work damages the platform's reputation with stakeholders who never met them. Performance standards are not punishment. They are how everyone gets protected from the cost of failure somewhere they cannot see.

07| The GMT answers for one question: did the platform deliver what it promised? That splits in two. Were the promised tools delivered — infrastructure, AI, support mechanisms, learning resources, coordination systems? If they are broken, slow or missing committed features, that is the GMT. Was the promised experience delivered — ease of use, responsiveness, support quality, clarity? If Ikosi are fighting friction the platform created, that is the GMT. What the GMT does not answer for is ground results in the barrio. If the tools are adequate and the impact does not arrive, that is a Maveriq question with a support response, not a GMT failure. Keeping that line clean is what prevents both blame-shifting and blame-hoarding.

08| Division leadership is measured on five dimensions: domain results specific to the Division; integration with other Divisions; the quality of the Pro.Crowd teams the leader assembled through the market; innovation contribution; and budget efficiency. All metrics are public and updated regularly. There are no private scorecards and no results shared "just internally." Poor performance is visible immediately, and so is strong performance.

09| The most important task any platform professional performs is filling out the monthly survey. That sounds like an overstatement and it is not. Honest reporting on platform health, team dynamics, leadership quality and emerging problems is the mechanism by which coordination infrastructure stays alive. Without it, problems compound in silence until something breaks in public.

10| The design details are what make it work. The surveys go to independent outside analysts — not internal HR, not the GMT. The questions demand substance rather than satisfaction ratings. Individual responses stay anonymous; aggregate trends go public under the transparency rule; analysed results reach the Board and the GMT, and patterns trigger action — leadership changes, reallocation, process fixes. Monthly, because quarterly lets problems compound between cycles and weekly produces fatigue and shallow answers. Outside, because internal analysis gets filtered: people protect colleagues and soften uncomfortable truths, usually without noticing they are doing it. Our appetite for honest feedback is only as large as the channel that carries it.

11| Consequences come in three categories, and confusing them is how organizations become either cruel or useless. Capability gaps get patience: someone struggling with a new challenge gets training, time and support; someone whose context shifted gets goals reassessed; someone in a skill mismatch gets moved. None of that is failure — it is the normal work of building teams. Effort gaps get escalation: coasting and repeated non-delivery without valid reason gets a warning, then an improvement plan, then exit. Integrity violations get immediate action: fraud, corruption, abuse of teams or staff, hiding or falsifying data — investigated at once, removed if confirmed. Different decision-makers handle different categories. Pro.Crowd teams face market consequences and simply stop being selected. Staff and leaders are handled by an outside HR team working from performance data and survey analysis. GMT members are handled by the Board Chairman with majority Board support.

12| So if leaders do not hire, fire, assign work, command teams or control the marketplace — what is the job? Seven functions. Break work into projects and tasks, which is strategic rather than administrative, because how work is chunked determines what is possible. Distribute work through the market, setting scope, timeline, standards and compensation, and letting teams compete on track record rather than price. Form collaboration circles, because the valuable work happens at intersections and those do not organize themselves. Keep collaboration productive by removing obstacles and realigning incentives when turf battles start, not by issuing orders. Judge the quality of output — not whether people tried, but whether the work meets the requirement. Judge how the building blocks fit together, which is the most important function and the easiest to neglect, because individually excellent pieces fail at the seams. And develop others to decide better, so that over time teams need less input. The measure of a leader here is not indispensability. It is how dispensable they manage to become.

13| The prohibitions are explicit. Leaders cannot hire or fire directly. They cannot override the market for team selection. They cannot hide decisions or performance data. They cannot dictate how a Pro.Crowd team organizes itself. What they can do is ask the outside HR team to review an underperformer, set the standards that filter who qualifies, escalate to the GMT or Board, and shape outcomes through project design and criteria. The limits exist because concentrated power kills decentralization every time it is left unattended: control hiring and you build an empire, override the market and accountability collapses, command teams and self-organization dies. The limits are what let the architecture survive contact with normal organizational gravity.

14| Two lighter pieces complete it. Any leader may keep a personal advisory panel — three to five trusted people, informal, no meetings unless useful, optional. It exists so leaders can test their judgment without us building an advisory bureaucracy that becomes its own problem. And the long-term direction underneath everything: AI eventually running the large majority of platform operations, with humans holding strategic oversight, exception handling, integration and quality judgment. That is direction, not current reality, but it shapes today's choices — build what can be automated, document decisions so the patterns are learnable, set clear criteria for routine calls. If a design requires constant human intervention to function, the design is wrong.