> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/operations/frameworks/nexus-leadership-system-nls/vii.-leadership-plan.md). # VII. Leadership Plan Nexus Leadership System (NLS) guide to the Annual Leadership Contribution Plan (ALCP), proposal-based leadership, institutional outcomes, evidence, plan maturity, and scale readiness. **Where this fits:** all six sectors · [Nexus Universe](/organization/programme/universe.md), [Risk Academy](/organization/programme/academy.md) · The Global Risks Forum (GRF), with GCRI Canada as Consortium Secretariat · the programme year (quarterly NLC alignment; the Year-One Gateway) · systems [NXS-HUB](/organization/systems/nxs-hub.md), [NXS-RLS](/organization/systems/nxs-rls.md), [NXS-NSF](/organization/systems/nxs-nsf.md), [NXS-CMD](/organization/systems/nxs-cmd.md), [NXS-DSS](/organization/systems/nxs-dss.md) · framework page (NLS). **In brief.** This Nexus Leadership System (NLS) guide explains the Annual Leadership Contribution Plan (ALCP). This page belongs to the Nexus Leadership System (NLS), read as the leadership method of the operating model: it describes how leaders selected in a personal capacity contribute through the National Leadership Council (NLC), alongside the Helix councils of the National Nexus Consortium (NNC) and the National Working Groups (NWG). Selection precedes payment. Council standing does not buy office, employment, a Board seat or restricted data, and an employer does not own a personal seat; no council decides for a public authority. The method aligns with international practice ([ISO 2018](https://www.iso.org/standard/65694.html); [OECD 2014](https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405)). {% hint style="info" %} **Read with the current model (21 October 2026).** The "Leadership Councils" of this framework correspond, at national level, to the [National Leadership Council (NLC)](/organization/governance-in-operation/nlc.md), the leadership pillar of [National Nexus](/organization/governance-in-operation/national-nexus.md); the regional and global leadership councils are the councils of the GRF council architecture, in formation ([Councils](/organization/governance-in-operation/councils.md)). Institutions take part through the six Helix councils of the [NNC](/organization/governance-in-operation/nnc.md) (SPC, IOC, ARC, CMC, CIC and the FIR pathway); expert work runs through [NWG](/organization/governance-in-operation/nwg.md) assignments, with the six CERTs under them. Earlier labels are mapped in running text: Competence Cells are the atomic units of the NWG fabric, formed at institution, community or agency level; a Competence Cell can serve as a CERT, Investors Councils are the Financial Institutions and Regulators (FIR) pathway, `Nexus Grid` is the `Nexus Network` and [NXS-NET](/organization/systems/nxs-net.md), Protocol Authority is NXS-NSF ([Reference](/organization/reference.md)). Leadership work follows [the programme year](/organization/programme/the-programme-year.md): mandate at G0, quarterly alignment, Action Week, renewal at G7. {% endhint %} ## 7. THE ANNUAL LEADERSHIP CONTRIBUTION PLAN This Nexus Leadership System (NLS) guide explains the Annual Leadership Contribution Plan (ALCP). It covers proposal-based leadership, institutional outcomes, stakeholder and decision mapping, evidence-based review, Plan maturity, and the path from leadership contribution to institutional capability. ### 7.1 Proposal-Based Leadership #### 7.1.1 Why Nexus uses proposal-based leadership We organize NLS around **proposal-based leadership** because senior leaders do not create value through one standardized form of participation. The capabilities of an infrastructure executive, systems scientist, public-sector leader, technology specialist, finance professional, university leader or community institution are materially different, and those differences are precisely what make a plural Leadership Council useful. A leadership system that assigns identical tasks to every member may achieve administrative consistency while wasting much of the distinctive human capital it has assembled. The Annual Leadership Contribution Plan, or **ALCP**, allows us to preserve a common institutional architecture without forcing substantive uniformity. Every member works through the same basic disciplines of purpose, context, outcomes, institutional relationships, dependencies, evidence, review and maturity, but the actual contribution can be shaped around the member's expertise, geography, Council, professional environment and the needs of the Nexus system. Proposal-based leadership therefore asks a more demanding question than conventional participation models. It does not ask only what activities a member is willing to undertake. It asks **where that person's distinctive capability can strengthen an institution, system, country or region in a way that is material, realistic and capable of being learned from**. *** #### 7.1.2 From generalized willingness to bounded contribution Experienced leaders often enter a new institution with broad willingness to help. That willingness is valuable, but it is not yet an operating proposition. Without further definition, it can generate a long sequence of introductions, discussions and opportunities that consume significant time while creating little cumulative institutional learning. The ALCP converts generalized willingness into a bounded leadership contribution. It identifies the area in which the member intends to concentrate meaningful effort, the conditions surrounding that effort and the institutional support required to make it useful. This bounding function should not be confused with reducing ambition. Some of the most consequential leadership contributions may concern highly complex National or Regional systems. The objective is to define a sufficiently coherent portion of that complexity that the institution can organize around it, test assumptions, preserve evidence and determine what should happen next. A leader can therefore retain a broad strategic horizon while operating through a focused annual proposition. *** #### 7.1.3 Contribution should follow comparative leadership advantage We seek to identify what might be described as the member's **comparative leadership advantage** within Nexus. This is the intersection between what the leader knows unusually well, which institutions or systems they understand, where their judgment carries legitimate value, what relationships or experience they bring, and what the Nexus system currently needs. A highly accomplished person may have many areas in which they could contribute. The Plan should not attempt to capture all of them simultaneously. It should identify the combinations in which the member can add distinctive value that would be difficult to reproduce through another leader or ordinary programme capacity. This also allows Council composition to become more intelligent. Instead of expecting every member to contribute broadly across the entire Council agenda, NLS can develop a portfolio of complementary leadership contributions whose combined value is greater than the sum of disconnected individual activities. *** #### 7.1.4 Proposal-based leadership is not individual freelancing The member proposes a contribution, but the ALCP does not become an entirely self-directed personal project detached from the Council or Nexus architecture. A credible Plan must connect individual leadership ambition with institutional purpose. It should reflect the needs of the relevant National, Regional or Global Council, the broader Nexus mission, material National or Regional priorities, the maturity of relevant Working Groups and Portfolios, and the actual support capacity of the system. Proposal-based leadership therefore combines **member agency with institutional coherence**. The leader has meaningful authorship over the contribution. Nexus retains responsibility for ensuring that the proposed work fits the wider architecture and can be supported responsibly. The objective is co-designed leadership, not centralized assignment and not unrestricted individual initiative. *** #### 7.1.5 The Plan as a compact between capability and context The ALCP should ultimately describe the relationship between four things: the capability of the leader, the need of the system, the institutional environment in which the work must occur, and the evidence required to understand whether the contribution is developing successfully. A Plan becomes weak when one of these dimensions dominates the others. A highly ambitious contribution may fail if the institutional environment cannot support it. A strong institutional opportunity may not fit the leader's actual expertise. A technically mature proposition may lack a credible route into National or Regional institutions. A well-connected leader may generate activity without a sufficiently defined outcome. Proposal-based leadership forces these dimensions into one coherent frame. This is why the ALCP is more than a personal objective-setting document. It is a compact between **human capability and institutional context**. *** ### 7.2 Leadership Contribution Questionnaire #### 7.2.1 The Questionnaire as the diagnostic entry point We use the **Leadership Contribution Questionnaire** as the principal diagnostic instrument through which an initial contribution thesis is developed into a more structured basis for the ALCP. The Questionnaire is not intended to examine the member's credentials again after admission. Selection has already established sufficient leadership fit to begin the NLS relationship. Its purpose is to understand how the member's experience, interests, institutional context, systems perspective and development objectives may translate into a serious contribution. We therefore use the Questionnaire to surface questions that may not be visible in a biography or conventional onboarding conversation. What systems does the member understand deeply? Which institutional environments have shaped their judgment? Which unresolved problems do they believe are important? Where do they see opportunities that others may be overlooking? Which capabilities would they like to develop? Which relationships or institutional interfaces may matter? What conditions could constrain their contribution? The answers provide structured material for dialogue rather than a final Plan generated by form completion. *** #### 7.2.2 The Questionnaire should reveal the leader's theory of contribution Every experienced leader carries an implicit theory about how change occurs. Some emphasize institutional relationships. Others begin from technology, evidence, policy, markets, community capability, governance or organizational design. The Questionnaire should help make that theory visible. We want to understand not only what the member wants to do, but why they believe the proposed contribution might create value. What causal relationship do they see between their intervention and the desired outcome? Which actors must respond differently? Which system conditions must change? Which assumptions are embedded in the proposition? Making this reasoning explicit is valuable even where it later proves incomplete. The purpose of diagnosis is not to demand perfect foresight. It is to create enough visibility that assumptions can become objects of learning rather than invisible determinants of the Plan. *** #### 7.2.3 Professional identity and institutional context The Questionnaire should also allow the member to describe their professional identity in a way that goes beyond title. Two people holding similar senior positions may have substantially different capabilities because their careers, institutional environments and exposure to complex systems differ. The relevant questions therefore concern the kinds of problems the member has led through, the institutions they understand, the decisions they have had to make, the systems in which they possess deep experience and the forms of leadership they wish to exercise within Nexus. This provides NLS with a more meaningful foundation for contribution design than a conventional curriculum vitae alone. *** #### 7.2.4 Contribution appetite and contribution capacity The Questionnaire should distinguish between **contribution appetite** and **contribution capacity**. A leader may have substantial interest in several Nexus domains while possessing realistic capacity to concentrate on only one or two during the annual cycle. Another may have limited recurring time but be capable of providing highly valuable strategic interventions at particular moments. A third may have the capacity to lead a sustained Working Group or National formation effort. NLS should therefore understand both what the member wishes to contribute and what form of participation their professional circumstances can support credibly. This distinction protects the leader from overcommitment and protects the Council from constructing Plans around unrealistic expectations. A smaller Plan delivered with depth is generally more valuable than a broad Plan whose commitments cannot be sustained. *** #### 7.2.5 The Questionnaire as the beginning of co-design The Questionnaire should conclude not with an automatically generated Plan, but with a structured dialogue between the member and NLS. The member's responses provide one perspective. The relevant Council, National or Regional context, Nexus priorities, systems evidence and institutional capabilities provide others. The ALCP emerges through the interaction among them. This is why we describe the Plan as member-led but institutionally co-designed. The member should recognize their own leadership proposition within it, while the institution should be able to explain how the contribution connects to wider Nexus work. The Questionnaire therefore begins the design process. It does not complete it. *** ### 7.3 The Annual Leadership Contribution Plan #### 7.3.1 The ALCP as the principal work-design instrument The **Annual Leadership Contribution Plan** is the principal work-design instrument of the Nexus Leadership System. It translates the member's experience, institutional context and contribution thesis into a coherent annual proposition that can be understood by the leader, Council, NLS support team and other relevant Nexus environments. The Plan establishes what the member intends to strengthen, why that contribution matters, which systems and institutions are relevant, what meaningful progress would look like, what dependencies must be addressed, what evidence should be generated and what support Nexus must provide. The ALCP therefore creates a shared object around which reciprocal responsibility can organize. Without such an object, the institution may understand that a member is talented and engaged while remaining unable to explain what the relationship is designed to produce. *** #### 7.3.2 The Plan is a living institutional instrument We do not treat the ALCP as a static annual contract whose original language must be defended regardless of what the year reveals. Systems change. Institutions respond differently than expected. New evidence emerges. A Working Group may expose a hidden dependency. A member's professional environment may change. A National priority may become Regionally significant. A technical proposition may prove less important than the institutional problem surrounding it. The Plan must therefore be capable of amendment. This adaptability does not weaken accountability. It improves it. A Plan that changes transparently because the evidence changed demonstrates stronger institutional discipline than a Plan that remains formally unchanged while the reality around it has moved. The relevant standard is not fidelity to the first draft. It is fidelity to the purpose of the contribution and the evidence informing its development. *** #### 7.3.3 Annual does not mean short-term The term **Annual** describes the review cycle of the Plan rather than the maximum duration of the underlying ambition. Many systemic-risk challenges cannot be resolved within twelve months. National institutional development, Regional federation, infrastructure resilience, technology transitions, leadership succession and complex programme formation may require several years. The ALCP therefore identifies the portion of a longer leadership journey that can be advanced meaningfully during the current year. A multi-year contribution should be capable of being decomposed into annual learning and capability increments so that the institution can understand what changed during each cycle. Annual planning provides discipline to long-term ambition. It does not reduce long-term ambition to short-termism. *** #### 7.3.4 The Plan should be outcome-led and learning-led A strong ALCP begins with the institutional change the leader seeks to help create, not with a long activity list. The desired change may concern a stronger National capability, a more mature Working Group, an improved evidence base, a functioning institutional relationship, a tested technology proposition, a Regional framework, a leadership-development outcome or another material result. The Plan should then identify what must be learned before the institution can determine whether that result is becoming realistic. This dual orientation toward **outcome and learning** is critical. Where uncertainty is high, learning may be the most important first-year outcome. The institution may need to understand whether a proposition is viable before attempting to deliver it at scale. A Plan should therefore be capable of creating value even where its original ambition is ultimately narrowed or discontinued. *** #### 7.3.5 The Plan as a Council object Although the ALCP belongs principally to the member, it should also be intelligible within the Council. A Council should be able to understand broadly where its members are concentrating their contributions and where important complementarities or gaps exist. This allows individual Plans to form a leadership portfolio. Several Plans may converge around a National infrastructure priority. Others may create a Regional Working Group. One member's research contribution may support another member's institutional programme. A senior leader's mentoring Plan may strengthen the succession pathway required by the Council as a whole. The ALCP therefore creates a bridge between **individual agency and collective Council capability**. *** ### 7.4 Leadership Outcomes #### 7.4.1 Outcomes describe the institutional change sought We use **Leadership Outcomes** to define the meaningful change the member intends to help create through the Plan. An outcome should describe something more substantive than participation itself. It should explain how an institution, relationship, body of knowledge, programme, leadership cohort, National system or other relevant object may become stronger because of the contribution. This does not mean that every outcome must be large or publicly visible. A significant outcome may consist of clarifying a previously poorly understood institutional problem, creating a functioning cross-sector relationship, establishing a durable Working Group, improving the quality of a National Portfolio priority or developing a successor capable of sustaining an important leadership function. Leadership outcomes should be judged by institutional consequence, not spectacle. *** #### 7.4.2 Outcomes should remain proportionate to the leader's role A Leadership Council Member may materially influence a programme without being its executive owner. The ALCP should therefore define outcomes in a way that reflects the member's actual contribution. Where the leader's role is strategic challenge, the outcome might concern improved programme architecture or a decision-quality improvement rather than delivery of the entire programme. Where the member creates an institutional relationship, the outcome may be a functioning collaboration pathway rather than every result later produced through that relationship. This discipline prevents leadership Plans from claiming responsibility for outcomes controlled by other actors. It also allows substantive non-executive contribution to be recognized accurately. *** #### 7.4.3 Outcomes may be developmental, institutional or programmatic NLS recognizes several legitimate classes of outcome. Some Plans primarily strengthen the **leader**, for example by developing systems-leadership capability required for future Council service. Some strengthen the **Council or institution**, such as improving Council formation or succession. Some strengthen a **National or Regional system**, for example through a Portfolio contribution or new institutional interface. Others may support a more defined **programme, research or technical proposition**. A mature Plan may combine several of these dimensions. The important requirement is that the outcome logic remain coherent. The Plan should not become a collection of unrelated ambitions simply because each one is individually worthwhile. *** #### 7.4.4 Outcomes and Four-Way Value We use the Four-Way Value Framework to examine whether the proposed outcomes create a sufficiently balanced institutional relationship. The contribution should ideally create meaningful value for Nexus, for the relevant country, region or system, for the leader's institution and for the leader personally. The value will not necessarily be equal in every dimension or every year. The purpose of the framework is to test sustainability. A Plan that benefits only Nexus while imposing continuous unrewarded demands on the member may be difficult to sustain. A Plan serving only the member's personal interests does not create a credible public-good leadership proposition. A Plan generating institutional visibility without strengthening the relevant National or Regional system may be strategically weak. Four-Way Value helps keep the contribution reciprocal without turning it into a transaction. *** ### 7.5 Geography and Institutional Context #### 7.5.1 Geography is part of the contribution, not a label attached afterward Every ALCP should identify the geographic context within which the contribution operates because systemic conditions are shaped by place. A water-security proposition has different implications in different hydrological, institutional and economic environments. An AI-governance proposition encounters different data infrastructures, public institutions, languages and technological capabilities. A Regional supply-chain programme must understand the specific countries, corridors, infrastructure and institutions involved. Geography therefore belongs inside the substantive design of the Plan. It affects evidence, stakeholders, operating constraints, institutional relationships, implementation possibilities and the scale at which the contribution should be understood. *** #### 7.5.2 National Plans require National grounding Where a Plan is National, the contribution should be connected to the country's actual systems and institutional conditions rather than merely applying a global theme within a country label. A credible National Plan should increasingly understand the relevant National risk docket, institutional actors, physical systems, infrastructure, economic context, evidence environment and National Nexus maturity. The leader's professional experience may provide some of this context. Other parts may need to come from the National Desk, National Model, Portfolio, GCRI evidence or other local knowledge. National grounding therefore becomes an epistemic discipline as much as a geographic designation. *** #### 7.5.3 Regional Plans require a genuine cross-border unit of analysis A Regional ALCP should not merely describe work occurring in several countries independently. Regional relevance exists where relationships among the countries are themselves part of the problem or opportunity. A shared watershed, power system, infrastructure corridor, trade network, digital environment, ecosystem or institutional mechanism may create a genuine Regional unit of analysis. The Plan should therefore identify what becomes visible or actionable only when the countries are examined together. This protects Regional leadership from becoming an enlarged National programme without genuine cross-border additionality. *** #### 7.5.4 Global Plans require global substance The same discipline applies to Global leadership. A Plan should not be described as Global merely because the member possesses international experience or wishes to engage broad audiences. Global scope should arise because the contribution concerns multiple Regions, global systems, international institutions, frontier technologies, globally shared methods or another problem whose structure genuinely exceeds a single Regional frame. This distinction allows Global leadership to remain substantive. It also protects National and Regional systems from being treated as secondary merely because Global language appears more prestigious. *** #### 7.5.5 Place-based knowledge and institutional context Geographic analysis should include forms of knowledge that may not appear readily in formal data. Local operators, communities, subnational authorities, professional institutions and people with long experience of a place may understand system conditions that are poorly represented in aggregate National datasets. The ALCP should therefore recognize when place-based knowledge is material to the proposition and identify appropriate ways for that knowledge to enter the work. This is particularly important where a Plan concerns infrastructure, ecological systems, local resilience or communities whose experience of risk differs materially from national averages. Geographic context is not complete until the lived system has been considered alongside the formal one. *** ### 7.6 Domain and Strategic Context #### 7.6.1 The Plan should identify the system, not merely the professional sector Every ALCP should identify the principal domain in which the member intends to contribute, but Nexus requires the leader to go further than conventional sector classification. A Plan may begin in water, energy, health, biodiversity, infrastructure, AI, cyber, finance or another domain. The design process should then examine the adjacent systems whose dependencies materially affect the proposition. The purpose is not to make every Plan encompass the entire Nexus risk universe. It is to establish the **minimum sufficient system boundary** required to understand the contribution responsibly. A narrowly bounded Plan can therefore remain systemic if it identifies and manages the dependencies that matter beyond its immediate domain. *** #### 7.6.2 Strategic context links the Plan to the wider Nexus agenda The member's contribution should connect to the strategic context of the relevant Council and Nexus programme. At National level, this may mean a National risk priority or Portfolio need. At Regional level, it may concern shared cross-border systems. At Global level, it may concern a frontier risk, common method or institutional challenge relevant across several Regions. This strategic context prevents the ALCP from becoming a personal project hosted inside Nexus merely because the member finds the topic interesting. Personal intellectual interest is welcome. Institutional relevance is still required. A strong Plan aligns the leader's distinctive capability with a real Nexus need. *** #### 7.6.3 Domain depth should remain credible Systems leadership does not justify superficial treatment of specialized fields. Where a Plan enters a technical, scientific, financial, legal, operational or other specialized domain, it should connect to appropriate expertise and evidence rather than relying on broad systems language as a substitute for disciplinary competence. The member may possess the required expertise personally. Where they do not, the Plan should identify the capability required around them. This principle protects Nexus from a common failure of interdisciplinary programmes, in which breadth of ambition gradually replaces depth of knowledge. NLS seeks **systems breadth built upon credible disciplinary depth**. *** #### 7.6.4 Strategic context should include the time horizon The Plan should identify the time horizon relevant to the contribution. A programme may need an immediate operational intervention, a multi-year institutional transition or a long-horizon resilience strategy. These are materially different leadership problems. The ALCP should therefore distinguish what the current annual cycle is expected to accomplish from the longer-term transformation the leader may be helping to support. This allows the institution to avoid evaluating a long-term programme as though twelve months should produce final outcomes while still maintaining accountability for meaningful annual progress. *** ### 7.7 Stakeholder and Relationship Architecture #### 7.7.1 Stakeholders are part of the operating system A Leadership Plan becomes institutionally credible only when it understands the people and organizations whose participation, knowledge, decisions, implementation or lived experience materially affect the proposition. We therefore treat the stakeholder environment as a **relationship architecture**, not a contact list. The Plan should ask what role each material actor plays in the system, what they know, what they need, what incentives shape them and how their participation affects the viability of the contribution. This produces a more useful picture than conventional stakeholder enumeration. A stakeholder matters because of the function they perform within the system. *** #### 7.7.2 Institutional relationships should have purpose Senior leaders often possess extensive networks. The ALCP should not treat the size of those networks as a contribution by itself. The relevant question is which relationships are materially connected to the Plan and what institutional function those relationships may perform. One relationship may provide evidence. Another may create access to a National operating institution. Another may enable a Working Group. Another may provide specialist technical knowledge. Another may reveal community concerns that materially change the proposition. The Plan should therefore distinguish strategic relationships from generalized networking. The objective is to convert relational capital into institutional capability where appropriate. *** #### 7.7.3 Relationships should become more durable than the connector Where the member helps establish a valuable relationship, the long-term objective should ordinarily be for that relationship to become institutional rather than permanently dependent on the member. A personal introduction may be the beginning. A mature relationship should eventually acquire a clearer purpose, relevant institutional participants, working history and continuity sufficient to survive changes in individual people. This is an important leadership outcome. A member does not lose value when the institution no longer requires them to mediate every interaction. In many cases, that transition demonstrates that the relationship has matured successfully. *** #### 7.7.4 Relationship architecture should include missing voices The Plan should also ask which materially affected or knowledgeable actors are absent. Senior institutional networks naturally overrepresent organizations with established access and underrepresent actors whose knowledge is less formally organized. A systems-leadership proposition should therefore consider whether communities, local institutions, smaller operators, researchers, specialists or other relevant actors possess information that the existing network does not capture. The purpose is not to create indiscriminate consultation. It is to identify knowledge or institutional perspective whose absence would materially weaken the work. *** #### 7.7.5 Relationship quality should be distinguished from relationship volume A small number of high-trust, purpose-aligned institutional relationships may create more value than a large volume of introductions. The ALCP should therefore avoid defining relational outcomes through simple counts wherever those counts conceal quality. A relationship becomes strategically important when it changes the capability of the system. It may create access to evidence, improve coordination, enable a Working Group, strengthen National institutional continuity or remove a critical barrier. Relationship architecture is therefore about **function, trust and durability**, not accumulation. *** ### 7.8 Institutional and Decision Map #### 7.8.1 The Plan must understand how the relevant system actually moves Many strong ideas fail because their proponents understand the problem but not the institutional route through which action must occur. The ALCP should therefore develop an **Institutional and Decision Map** sufficient to identify the organizations, decision environments, dependencies and sequencing relevant to the contribution. The purpose is not to produce a generalized map of every institution in a country or sector. It is to understand the route that matters to the Plan. Which institution can advance the work? Which institution must provide evidence? Which actors must cooperate? Where can a proposition be tested? Who must sustain the capability if it becomes operational? These questions move leadership from concept toward institutional viability. *** #### 7.8.2 Decision points should be distinguished from influence points Not every actor who influences a proposition is responsible for determining its next state. A Council may shape strategic understanding. A Working Group may develop evidence. A National Desk may coordinate. A technical team may test. A public institution or operator may later determine whether a programme proceeds within its own context. The ALCP should preserve these distinctions. Otherwise, influential relationships can be mistaken for institutional control, and contribution claims can become inflated. A mature leader understands where they can shape the system and where another actor legitimately carries the next decision. *** #### 7.8.3 Institutional sequencing matters Complex institutional work frequently fails because the right actions occur in the wrong sequence. Technical design may advance before the relevant institutions have agreed on the problem. A financing discussion may begin before programme readiness exists. A public launch may occur before evidence has matured. Regional activity may begin before sufficient National capability is present. The Institutional and Decision Map should therefore identify **sequence** as well as actors. What must be understood first? Which dependency must be resolved before another step becomes meaningful? Which activity can proceed in parallel? Which step should not begin yet? Systems leadership is partly the discipline of timing institutional action. *** #### 7.8.4 The map should remain dynamic Institutions change during the life of a Plan. Personnel move. Programmes are reorganized. priorities shift. New partners emerge. A previously critical institution may become less relevant while another becomes central. The Institutional and Decision Map should therefore remain reviewable throughout the annual cycle. Its value comes from helping the Plan remain aligned with reality, not from preserving a static diagram. Quarterly review should update the map where material changes affect the viability or sequencing of the contribution. *** ### 7.9 Resources and Dependencies #### 7.9.1 Leadership contribution depends on an enabling system A strong leader does not operate in an institutional vacuum. A Plan may require evidence, research, technical expertise, programme coordination, data, institutional relationships, finance-readiness analysis, Working Group support, Foundry capability, Nexus Universe participation or resources held outside Nexus. The ALCP should therefore make the enabling system visible. This prevents the institution from attributing an unrealistic outcome entirely to the member while leaving critical dependencies unacknowledged. Leadership accountability becomes more credible when the conditions required for success are explicit. *** #### 7.9.2 Distinguishing member resources from institutional resources The Plan should distinguish what the member personally brings from what Nexus or other institutions must provide. The member may contribute time, expertise, judgment, relationships, strategic leadership or specialist capability. Nexus may need to provide evidence, technical infrastructure, Secretariat support, Working Groups, programme management, access to particular institutional environments or other resources. This distinction creates reciprocal accountability. If an outcome depends on institutional support that was never provided, Year-One Review should not treat the resulting limitation solely as member underperformance. Conversely, if NLS provides the agreed support and the member does not engage sufficiently, that state should also remain visible. A mature leadership institution evaluates the **whole contribution system** rather than only the individual. *** #### 7.9.3 Dependencies should be classified by consequence Not every dependency requires equal attention. Some are useful but substitutable. Others are essential. Some can be resolved within the annual cycle. Others may determine whether the contribution can proceed at all. The ALCP should therefore distinguish material dependencies according to the consequence of their absence. A critical data source, institutional sponsor, infrastructure operator, technical capability or long-term programme owner may represent a gating dependency. Another relationship may improve quality without determining viability. This distinction helps the member and NLS allocate attention intelligently. *** #### 7.9.4 Hidden dependencies are a major source of institutional risk Many programmes appear viable because important dependencies remain invisible during early design. A technology proposition may assume data availability. A National programme may assume institutional coordination. A Regional initiative may assume countries share the same priorities. A financial-readiness proposition may assume the underlying programme has reached a level of maturity it has not actually reached. The ALCP should therefore actively search for hidden dependencies. One of the most valuable functions of Council challenge, Working Groups and systems analysis is to identify conditions the initiating leader did not know needed to be considered. Dependency discovery is therefore an expected part of Plan maturation. *** #### 7.9.5 Resource needs should mature with the proposition A concept-stage Plan should not require the same resource precision as an active delivery programme. Resource requirements should become more detailed as the Plan matures. During formation, broad capability needs may be sufficient. During testing, specific technical, institutional or research requirements should become clearer. Before scale, the system should possess a much stronger understanding of the operating resources required to sustain the proposition. This maturity principle prevents unnecessary administrative burden in early stages while ensuring that ambition becomes increasingly connected to operational reality as commitment grows. *** ### 7.10 Risks, Constraints and Safeguards #### 7.10.1 Every serious Plan contains uncertainty and risk A credible ALCP should make its risks and constraints visible rather than presenting only the argument for why the contribution should succeed. Systemic work occurs in environments shaped by uncertainty, competing institutional incentives, technical limitations, scarce resources, political and economic change, social consequences and physical constraints. A Plan that contains no visible risk is more likely to be incomplete than unusually safe. We therefore expect leaders to identify the material conditions that could weaken, delay, distort or invalidate the contribution. This is not pessimism. It is professional readiness. *** #### 7.10.2 Constraints should shape design Constraints are not merely issues to be listed after a preferred approach has already been chosen. They should influence the architecture of the Plan. If the member has limited time, the contribution should be designed accordingly. If institutional access is uncertain, early work may need to focus on relationship development. If evidence is weak, the first objective may need to be research rather than programme formation. If technical readiness is low, a controlled Lab test may be more appropriate than public demonstration. A mature Plan incorporates constraints into its method. This prevents planning from becoming an exercise in describing ideal conditions that do not exist. *** #### 7.10.3 Risks should be related to the scale of commitment The more consequential the next step, the stronger the institution's understanding of material risk should become. A concept discussion can tolerate substantial uncertainty. A small controlled test can proceed with uncertainty if the test itself is designed to reduce it. A large National programme, major infrastructure initiative or public institutional commitment requires a substantially stronger evidence and readiness profile. The ALCP maturity model therefore links risk understanding to progression. As the proposition moves toward scale, assumptions that were acceptable at concept stage should increasingly become evidence, controlled constraints or explicit unresolved risks. *** #### 7.10.4 Safeguards should be designed into the contribution Where a Plan creates material institutional, technological, environmental, community or other risk, relevant safeguards should be considered as part of design rather than added after the proposition has matured. The appropriate safeguards will depend on the contribution. A technology Plan may require privacy, security, human oversight or data-governance measures. A community-facing programme may require appropriate participation and protection of sensitive local knowledge. An infrastructure intervention may require safety, continuity and environmental considerations. The ALCP should remain proportionate to the scope of the work. The purpose is to ensure that risk reduction is part of the leadership proposition itself. *** #### 7.10.5 Risk ownership and leadership contribution A Leadership Council Member may identify and help reduce risk without becoming the formal owner of every risk associated with a programme. The Plan should therefore distinguish where the member contributes to risk understanding from where operating institutions must carry ongoing responsibility. This is consistent with the non-executive nature of Council membership. The member's role may be to improve the system's ability to see a risk, question an assumption or connect the relevant institution. Another actor may later be responsible for managing that risk operationally. Accurate role definition is part of responsible leadership. *** ### 7.11 Evidence and Success #### 7.11.1 Evidence should be designed into the Plan The ALCP should identify from the beginning what forms of evidence will allow the member and institution to understand whether the contribution is progressing. Evidence should not be reconstructed only at annual review. If the Plan concerns institutional formation, evidence may include functioning Working Groups, persistent records, repeatable processes and demonstrated participation. If it concerns research, the relevant evidence may be methodological outputs, reviewed analysis or institutional use of the resulting knowledge. If it concerns a programme proposition, evidence may concern readiness, stakeholder response, technical testing or movement into a more mature institutional state. The form of evidence should follow the nature of the outcome. The common requirement is that progress should be interpretable rather than asserted. *** #### 7.11.2 Success should not be defined as activity volume NLS does not equate more activity with more success. A Plan containing dozens of meetings, introductions and events may produce less institutional value than a Plan that resolves one critical dependency. Success should therefore be connected to **material change**. Did the institution understand the problem better? Did a Working Group become capable? Did a National Portfolio priority become more mature? Did an institutional relationship become functional? Did a test reveal something important? Did the leader develop a capability that materially improves future contribution? The ALCP should define success at the level of institutional consequence. *** #### 7.11.3 Evidence should preserve negative and inconclusive results A credible evidence system records what happened, not only what supports continuation. A test may fail. A relationship may not develop as expected. An institution may decline to participate. A technology may prove unsuitable. A proposed Regional issue may turn out to be better addressed Nationally. These results can be valuable. They prevent the Leadership System from investing further in weak assumptions and improve the quality of future decisions. The ALCP should therefore create no incentive to hide negative or inconclusive evidence merely because the member originally supported the proposition. Learning is a valid outcome. *** #### 7.11.4 Success belongs to the appropriate contributor Leadership outcomes are frequently collective. The member may initiate an idea, another leader may strengthen it, a Working Group may develop it, GCRI may provide evidence, a Desk may organize the institutional pathway and another organization may eventually implement the programme. The Plan and Leadership Ledger should preserve these contributions proportionately. Recognition should be accurate enough that people can understand what the leader genuinely added without converting collective institutional work into a personal achievement claim. This protects both individual credibility and the collaborative culture of Nexus. *** #### 7.11.5 Success should include institutional learning A Plan that produces a valuable programme but leaves the institution unable to explain why it worked has produced less durable value than one that also preserves reusable learning. We therefore ask whether successful contribution generates knowledge, methods, relationships, records or successor capability that can support future work. This does not mean every Plan must become replicable globally. It means the institution should preserve what it learned at a level appropriate to the significance of the contribution. Institutional memory is part of success. *** ### 7.12 Plan Review and Amendment #### 7.12.1 Review is a core operating function The ALCP should be reviewed throughout the year because the Plan is an active instrument operating in a changing environment. Quarterly review provides the primary recurring rhythm, but material events may justify amendment between scheduled reviews. The purpose of review is to compare the original proposition with current evidence and ask whether the Plan remains the best representation of the contribution. This protects NLS from a common planning failure in which the document becomes increasingly detached from the work it was created to guide. *** #### 7.12.2 Amendment should follow evidence, not convenience alone The Plan should be flexible, but flexibility should not become an excuse for avoiding accountability. Material amendments should have a reason. The underlying cause may be new evidence, changed institutional conditions, a discovered dependency, altered member capacity, a revised National priority or another legitimate factor. Where the Plan changes substantially, the leadership record should preserve enough context to understand why. This creates a history of learning. The institution should be able to distinguish disciplined correction from repeated movement caused by lack of focus. *** #### 7.12.3 Narrowing can indicate maturity Leadership culture often rewards expansion and treats narrowing as loss of ambition. NLS should resist that assumption. A broad Plan may become more valuable when evidence reveals the smaller number of issues where the member can produce genuine leverage. A Regional concept may become a stronger National programme. A large technical proposition may reduce to one foundational capability that must be proven first. Narrowing can therefore be evidence of better systems understanding. The relevant question is not whether the Plan became larger. It is whether it became more credible. *** #### 7.12.4 Expansion should also be evidence-led The same discipline applies when a Plan expands. A National contribution should not become Regional merely because wider scope appears attractive. A successful pilot should not become a large programme merely because early reception was positive. A Working Group should not become a permanent institution solely because participants enjoyed the process. Expansion should follow evidence of real additionality, readiness and institutional capacity. This protects the leadership system from momentum-driven scale. The ALCP should therefore make expansion a consequence of maturation rather than aspiration alone. *** #### 7.12.5 Plan changes should preserve continuity When the ALCP is amended, the previous state should not simply disappear from institutional memory. The Leadership Ledger and Plan history should preserve enough information to show the evolution of major objectives and assumptions where that history matters. This is particularly valuable for multi-year contributions. Future members and operating teams should be able to understand not only the current Plan but how the institution arrived there. Correction becomes more useful when it remains traceable. *** ### 7.13 Plan Maturity #### 7.13.1 Why NLS uses a maturity model We use a maturity model because leadership propositions do not move directly from idea to institutionalized capability. Between those states are important differences in evidence, readiness, institutional support and operating consequence. If the system describes every interesting proposition as an active programme, it loses the ability to distinguish aspiration from actual maturity. If it requires full certainty before any work begins, it prevents controlled learning. The maturity model therefore provides a common language through which leaders can understand the current state of a contribution without overclaiming what has been achieved. The public ALCP maturity chain is: > **Concept → Designed → Approved for Testing → Testing → Tested → Pre-Scale → Validated → Scale-Ready → Active Delivery → Demonstrated → Replicated → Institutionalized** *** #### 7.13.2 Concept A **Concept** is a leadership proposition that appears potentially valuable but remains insufficiently developed for structured testing. At this state, the member may have identified a problem, opportunity or contribution thesis, but important questions concerning system boundaries, institutions, evidence, dependencies or intended outcomes remain open. Concept status should be treated as legitimate. Every mature programme begins with some form of hypothesis. The discipline lies in not representing that hypothesis as though it were already a validated institutional proposition. *** #### 7.13.3 Designed A Plan becomes **Designed** when the proposition has been developed sufficiently to describe the intended contribution, relevant context, outcomes, institutional relationships, principal dependencies, evidence needs and proposed method. Designed does not mean proven. It means the proposition is coherent enough that others can understand what is being proposed and what would need to be learned next. This is an important transition because the work has moved from an individual idea into an institutional object capable of structured review. *** #### 7.13.4 Approved for Testing **Approved for Testing** means that the proposition has reached a level of coherence and relevance sufficient to justify a controlled evidence-producing activity. The significance of this state is often misunderstood. Approval for testing is not approval for full implementation. It means the institution has determined that the question is worth examining under bounded conditions. The test should therefore be designed around a clear uncertainty, assumption or capability question whose answer can change the next institutional state. *** #### 7.13.5 Testing A proposition is in **Testing** while the relevant controlled activity is underway. Testing may involve Council challenge, research, Working Group analysis, Foundry, Labs, scenario work, Nexus Universe, stakeholder engagement or another appropriate environment. The purpose is to expose the proposition to evidence rather than to demonstrate that the initiating leader was correct. A credible testing state therefore allows the possibility that the proposition may narrow, change or stop. *** #### 7.13.6 Tested A proposition becomes **Tested** when the planned testing activity has concluded and sufficient evidence exists to interpret what the test established. Tested does not automatically mean successful. The evidence may support continuation, reveal significant weaknesses, remain inconclusive or indicate that the proposition should not proceed in its current form. The important institutional achievement is that the original hypothesis has encountered a structured evidence environment and the result has been preserved. *** #### 7.13.7 Pre-Scale A proposition enters **Pre-Scale** when testing has produced enough positive evidence to justify deeper analysis of whether the work can operate under more consequential conditions. This state should focus increasingly on institutional readiness, resource requirements, ownership, sustainability, technical capability, financial readability where relevant and the dependencies that become more important as scale increases. Pre-Scale is therefore the bridge between a promising tested proposition and a validated institutional pathway. Many ideas that perform well in controlled environments reveal their most important weaknesses here. That is precisely why the state exists. *** #### 7.13.8 Validated A proposition becomes **Validated** when the available evidence supports the conclusion that the underlying contribution is credible enough to justify consideration of a deeper operating state within its defined context. Validation should remain bounded to what has actually been established. A National proposition validated in one institutional environment is not automatically validated in another country. A technical capability validated under one test condition is not automatically appropriate for every deployment environment. NLS therefore treats validation as context-specific evidence of credibility rather than universal proof. *** #### 7.13.9 Scale-Ready A proposition is **Scale-Ready** when the system possesses not only a validated underlying concept but a sufficiently mature understanding of the institutional, technical, human, resource and continuity conditions required for expanded delivery. This is a demanding state. A proposition may be validated and still not be scale-ready because the operating owner is unclear, resources are insufficient, National Desk capacity is weak, institutional partners are not prepared or another critical dependency remains unresolved. Scale readiness therefore belongs to the **whole system around the proposition**, not the idea alone. *** #### 7.13.10 Active Delivery **Active Delivery** begins when the proposition moves from readiness into substantive implementation or programme operation through the appropriate institutional environment. At this stage, the leadership role may change. The member may continue to provide strategic oversight, Council connection, specialist contribution or institutional stewardship while an operating team carries day-to-day delivery. The transition should preserve role clarity. NLS should recognize the member's contribution without treating non-executive leadership as operational ownership unless a separate role has been established appropriately. *** #### 7.13.11 Demonstrated A proposition becomes **Demonstrated** when active delivery has generated sufficient real-world evidence to show that the capability or institutional model works meaningfully within the context for which it was designed. Demonstration is more demanding than testing because the proposition has encountered real operating conditions. The evidence should therefore concern actual performance, institutional use, continuity, outcomes or other relevant indicators rather than only controlled assumptions. Demonstration allows the system to ask a new question: whether the capability is transferable. *** #### 7.13.12 Replicated A proposition becomes **Replicated** when its essential capability has been reproduced successfully in an additional relevant context with appropriate adaptation. Replication is not copying. A programme that succeeds only when every original condition remains unchanged may not possess a transferable institutional model. Nexus therefore treats replication as evidence that the underlying architecture can survive contextual change while retaining its essential function. This is particularly important to the 2027 and 2028 institutionalization stages of the wider Nexus programme. *** #### 7.13.13 Institutionalized A proposition becomes **Institutionalized** when the capability has become sufficiently embedded in the relevant institution or system that it no longer depends primarily on the founding leader, temporary project, exceptional sponsorship or original implementation team. Institutionalization should be visible through continuity. The relevant institution knows how to operate the capability. Records exist. Responsibilities have been integrated. Successors can continue the work. Annual cycles or other recurring processes sustain it. Necessary resources and support structures have become more durable. This is one of the highest maturity states because it demonstrates that leadership contribution has become institutional capability. *** #### 7.13.14 Maturity is not a prestige hierarchy The maturity chain describes the state of a **contribution or proposition**, not the personal worth of the leader. A member with a Concept-stage Plan may be an exceptionally accomplished leader. Another member may inherit an already mature institutional programme and therefore operate immediately around Active Delivery. NLS should never turn maturity states into status labels for people. The value of the model lies in making work intelligible. Its purpose is to prevent overclaiming, improve resource allocation and identify the correct next test or institutional state. *** ### 7.14 From Validated Plan to Scale #### 7.14.1 Validation changes the leadership question Once a Plan has become genuinely validated, the leadership question changes. Earlier stages ask whether the proposition is coherent, whether its assumptions survive testing and whether the member-system relationship is creating value. After validation, the central question becomes whether the wider institutional environment can carry the contribution responsibly into a more consequential state. This shift is significant. Scale depends less on the attractiveness of the original idea and more on the maturity of the **system around it**. The member's role therefore often evolves from proposition development toward institutional orchestration, stewardship or specialist support. *** #### 7.14.2 Scale requires an operating owner No validated proposition should be treated as scale-ready simply because the Leadership Council supports it. The system needs to know where persistent delivery will sit. A National programme may require a competent public institution, operator, enterprise, programme organization or other implementation environment. A Regional proposition may require participating National systems and a sufficiently mature Regional coordination capability. A technical system may require an operating team capable of maintaining it after initial development. The ALCP should therefore identify the likely **operating owner or operating environment** before scale. Without that condition, the proposition may remain validated but institutionally homeless. *** #### 7.14.3 Scale requires continuity beyond the member The member may be essential to forming and validating the contribution. That does not mean the contribution should remain permanently dependent on them. Before scale, the Plan should consider what must become transferable: knowledge, relationships, methods, documentation, Working Group capability, operating processes, leadership succession or another form of institutional memory. A proposition that cannot survive the temporary absence of its initiating leader remains fragile. We therefore interpret reduced dependence on the founder of a contribution as a sign of maturity rather than loss of influence. *** #### 7.14.4 Scale requires support architecture Validated propositions frequently fail during transition to scale because the institutional support required for larger operation was not developed at the same rate as the idea itself. The next state may require stronger programme management, new technical infrastructure, more substantial evidence systems, National Desk capacity, finance-readiness work, additional institutional relationships, workforce development or other capabilities. Scale readiness should therefore be assessed across the complete support architecture. A validated idea surrounded by immature infrastructure is not yet scale-ready. This distinction protects Nexus from accelerating propositions faster than the institution can sustain them. *** #### 7.14.5 Scale requires stronger evidence discipline As consequence grows, evidence standards should become more demanding. A Concept may proceed on a plausible hypothesis. A controlled test may operate with known uncertainty. Active delivery affecting larger systems requires a more mature understanding of evidence, risk, operating conditions and monitoring. The evidence architecture should therefore grow with the proposition. What was sufficient to justify testing may be insufficient to justify replication. What was sufficient to demonstrate one National use case may be insufficient to support Regional scaling. NLS links evidentiary maturity to institutional consequence. *** #### 7.14.6 Scale requires an explicit learning architecture Scaling should not end the learning process. In many cases, larger operation reveals dependencies and consequences that controlled testing could not reproduce. The Plan should therefore preserve feedback mechanisms through which evidence from Active Delivery, Demonstration and Replication returns to the Council, Portfolio, Foundry, Leadership Ledger and subsequent annual Plans. This creates a recursive rather than linear model of scale. The proposition grows while continuing to learn. That discipline is particularly important in systemic-risk environments because the intervention itself can change the system it was designed to address. *** #### 7.14.7 Replication requires adaptation A contribution validated in one environment should not be copied mechanically into another. Replication should begin by identifying which features of the original success were structural and which depended on local conditions. Institutional structures, infrastructure, laws, culture, capacity, evidence and political economy may differ materially. The transferable object is therefore rarely the exact original programme. It is more often the **method, architecture or capability logic** capable of being adapted responsibly. This is how Nexus can scale without erasing context. *** #### 7.14.8 Federation creates another form of scale Not every mature contribution needs to become a larger centralized programme. Some capabilities scale through federation. A National method may remain nationally owned while becoming legible enough for peer countries to adapt. A Regional network may connect several independent National programmes. A common Foundry capability may support multiple institutional users while preserving differentiated ownership of the underlying work. NLS therefore treats federation as a distinct scaling logic. Scale can mean **more connected capability**, not only a larger organization. *** #### 7.14.9 Institutionalization is the long-horizon test The deepest test of a mature ALCP is whether the contribution eventually becomes capable of existing beyond the Plan itself. An institutionalized capability should no longer require an annual leadership document merely to prove that it exists. The Plan may shift toward stewardship, improvement, replication or a new contribution while the original capability becomes part of the relevant institution's normal operating system. This is the point at which leadership has succeeded in becoming infrastructure. The member helped create something that the institution can now carry. That is a more consequential outcome than permanent dependence on the leader who initiated it. *** #### 7.14.10 The ALCP as a pathway from leadership potential to institutional capability The complete Plan architecture can therefore be understood as a transformation. At entry, the member brings **leadership potential** in the form of experience, judgment, relationships and expertise. Through the Questionnaire and diagnosis, that potential becomes a **contribution thesis**. Through Plan design, the thesis becomes a **structured institutional proposition**. Through testing, the proposition encounters **evidence**. Through pre-scale validation, the system determines whether the proposition has become **credible**. Through scale readiness and delivery, the contribution becomes **operating capability**. Through demonstration, replication and institutionalization, that capability becomes progressively more **durable and transferable**. The ALCP is the instrument that allows NLS to preserve the continuity of that transformation. Its purpose is therefore not merely annual planning. It is to create a disciplined pathway through which human leadership can become durable institutional capability. *** ## PART VII FRAMEWORK PRINCIPLES **7.A Proposal-based leadership.** We organize leadership contribution around the member's distinctive expertise, institutional context and the real needs of Nexus rather than assigning identical work to every Council Member. **7.B Comparative leadership advantage.** A strong Plan identifies where the member can create distinctive institutional value that is difficult to reproduce through ordinary programme capacity. **7.C Member-led, institutionally co-designed.** The member retains substantive authorship of the contribution while NLS ensures that the Plan is connected to Council purpose, institutional context, evidence and available capability. **7.D Questionnaire as diagnosis.** The Leadership Contribution Questionnaire surfaces the leader's systems experience, theory of contribution, institutional context, capacity, development interests and material assumptions as the starting point for co-design. **7.E Plan as the organizing object.** The Annual Leadership Contribution Plan is the principal institutional object through which leadership purpose, outcomes, support, evidence and review are connected. **7.F Annuality without short-termism.** The Plan governs one annual learning and contribution cycle while allowing the underlying leadership mission to extend over multiple years. **7.G Outcome and learning orientation.** We design Plans around meaningful institutional change and the learning required to determine whether that change is becoming credible, rather than around activity volume. **7.H Proportionate outcomes.** Leadership outcomes should reflect the member's actual non-executive contribution without attributing implementation or institutional consequence that belongs to other actors. **7.I Four-Way Value.** We examine contribution through its value to Nexus, the relevant country, region or system, the member's institution and the member personally so that the leadership relationship remains reciprocal and sustainable. **7.J Geographic grounding.** National, Regional and Global Plans should reflect the real geographic structure of the problem rather than using geographic scope as a prestige label. **7.K System boundary.** A Plan may remain bounded while still identifying the adjacent systems and dependencies required for credible systems leadership. **7.L Disciplinary depth.** Systems breadth should complement rather than replace the specialist depth required by technical, scientific, institutional or financial questions. **7.M Relationship architecture.** We assess stakeholders and relationships according to the institutional function they perform within the contribution rather than the size of the member's network. **7.N Durable relationships.** Where personal leadership helps establish useful cooperation, the desired long-term state is an institutional relationship capable of surviving beyond the original connector. **7.O Institutional and decision mapping.** A mature Plan identifies the institutions, influence points, decision environments and sequencing required for the proposition to move coherently. **7.P Dependency visibility.** We distinguish what the member contributes from what Nexus and other institutions must provide, and we identify critical dependencies before treating the proposition as ready for scale. **7.Q Constraint-informed design.** Material constraints should influence the design and sequencing of the Plan rather than being recorded only after an approach has already been fixed. **7.R Safeguard-by-design.** Relevant safeguards should be incorporated as the proposition develops, proportionate to the scale and consequence of the work. **7.S Evidence by design.** The Plan should establish from the beginning what evidence will allow the institution to distinguish activity, learning, outcome and maturity. **7.T Negative evidence.** Failed, inconclusive or limiting results are legitimate institutional evidence and should inform correction rather than disappear from the leadership record. **7.U Proportionate attribution.** NLS recognizes what the member actually contributed while preserving the collective character of work created across Councils, Working Groups, Nexus institutions and implementation actors. **7.V Review and amendment.** Plans remain living institutional instruments and should be amended where evidence, conditions or dependencies materially change the best contribution pathway. **7.W Evidence-led narrowing and expansion.** Reducing or expanding the scope of a Plan should follow stronger understanding of institutional value and readiness rather than assumptions that larger always means better. **7.X Maturity discipline.** We distinguish Concept, Designed, Approved for Testing, Testing, Tested, Pre-Scale, Validated, Scale-Ready, Active Delivery, Demonstrated, Replicated and Institutionalized states so that leadership propositions are represented according to their actual maturity. **7.Y Maturity belongs to the proposition.** Plan maturity describes the institutional state of the work and should never be used as a hierarchy of personal leadership worth. **7.Z Institutionalization.** The highest long-horizon outcome of an ALCP is a useful capability sufficiently embedded in the relevant institution or system that it can continue beyond the initiating leader and annual Plan. *** ## OPERATING RELATIONSHIP Part VII establishes the Annual Leadership Contribution Plan as the central work-design and learning instrument of the Nexus Leadership System. The Plan is the mechanism through which the capabilities of an individual leader become connected to a real institutional need, a defined system, a geographic and strategic context, an architecture of relationships, a decision environment, a set of dependencies and an evidence-producing pathway. We begin with proposal-based leadership because NLS is designed to use the diversity of its members rather than standardize it away. The Leadership Contribution Questionnaire helps make the member's experience, contribution thesis, systems perspective, capacity and development interests visible. The ALCP then converts that material into a bounded annual proposition capable of being understood, supported and reviewed by the institution. The Plan defines outcomes at the level of institutional consequence rather than activity volume. It grounds the contribution geographically, situates it within the relevant risk or strategic domain, maps the institutions and relationships required around it, identifies decision pathways, makes resources and dependencies explicit, incorporates material constraints and safeguards, and defines how evidence will allow the institution to understand what is actually changing. The ALCP remains adaptable throughout the year. Quarterly review and other evidence-triggered amendments allow narrowing, expansion and correction where stronger information changes the best path. This flexibility is governed by an explicit maturity architecture so that change does not become ambiguity. The maturity chain from **Concept → Designed → Approved for Testing → Testing → Tested → Pre-Scale → Validated → Scale-Ready → Active Delivery → Demonstrated → Replicated → Institutionalized** provides NLS with a common language for distinguishing promising ideas from tested propositions, validated contributions from scale-ready systems, and active programmes from genuinely institutionalized capability. The deepest purpose of the Plan is therefore not annual administration. It is transformation. The ALCP provides a governed pathway through which **individual leadership capability can become evidence, evidence can become institutional learning, learning can become operating capability, and operating capability can become durable institutional infrastructure**. The next Part turns from the individual contribution Plan to the wider system Nexus places around its leaders so that they can perform at the level this architecture requires. ## NEXT ## PART VIII: HOW WE EQUIP NEXUS LEADERS ### Reciprocal Leadership Value, Leadership Intelligence, Systems Capability, Strategic Foresight, Risk Intelligence, Technology, Finance-Readiness, Governance, Trust, Peer Development and Applied Leadership Part VIII will establish the capability environment NLS provides around Leadership Council Members. It will define the reciprocal leadership proposition and Four-Way Value architecture; explain Leadership Intelligence as a personalized strategic operating layer rather than a stream of information; establish the systems-leadership, foresight, risk-intelligence, technology, finance-readiness, governance and institution-building capabilities expected of mature Nexus leaders; and define Leadership Circles, mentoring, Missions, research, authorship and the wider conditions through which NLS seeks to create stronger leaders as well as stronger institutions. ## Sources 1. ISO (2018). ISO 31000:2018 Risk management — Guidelines. Geneva: International Organization for Standardization. [www.iso.org/standard/65694.html](https://www.iso.org/standard/65694.html) 2. OECD (2014). Recommendation of the Council on the Governance of Critical Risks. OECD/LEGAL/0405. [legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405](https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405) 3. UN General Assembly (2024). The Pact for the Future, with the Global Digital Compact. A/RES/79/1. [undocs.org/A/RES/79/1](https://undocs.org/A/RES/79/1) **Standards that apply.** Masters: [Communities, Learning and Contribution](https://nexustandards.com/communities/) (PLANNED); [Governance, Security and Society](https://nexustandards.com/society/) (PLANNED). Standards: [NS-0](https://nexustandards.com/standards/ns-0/) (PROPOSED), [NS-1](https://nexustandards.com/standards/ns-1/) (PROPOSED), [NS-2](https://nexustandards.com/standards/ns-2/) (PROPOSED), [NS-3](https://nexustandards.com/standards/ns-3/) (PROPOSED), [NS-3b](https://nexustandards.com/standards/ns-3b/) (PROPOSED), [NS-4](https://nexustandards.com/standards/ns-4/) (PROPOSED), [NS-5](https://nexustandards.com/standards/ns-5/) (PROPOSED), [NS-8](https://nexustandards.com/standards/ns-8/) (PROPOSED), [NS-9](https://nexustandards.com/standards/ns-9/) (PROPOSED), [NS-10](https://nexustandards.com/standards/ns-10/) (PROPOSED), [NS-11](https://nexustandards.com/standards/ns-11/) (PROPOSED), [NS-12](https://nexustandards.com/standards/ns-12/) (PROPOSED), [NS-13](https://nexustandards.com/standards/ns-13/) (PROPOSED). Statuses are registry statuses on nexustandards.com, never adoption or certification. **In the GitBook.** [Programme](/organization/programme.md) · [Governance in operation](/organization/governance-in-operation.md) · [Systems](/organization/systems.md) · [Reference](/organization/reference.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.therisk.global/organization/operations/frameworks/nexus-leadership-system-nls/vii.-leadership-plan.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.