Sprint 8 - Staging, Orchestrating, Prototyping

Sprint Objective – To sequence the actions identified across sprint 4 to 7, develop orchestration structures (including governance) and identify prototypes to validate feasibility.

Staging Having identified the key actions across Sprint 4 to 7, we need to arrange them in implementation stages so as to gradually build momentum over time. These stages may overlap like waves, with a subsequent stage starting in parallel before the prior stage concludes.

We begin by preparing the ground for coordinated actions that create strong alignment and build trust across the ecosystem. Having primed the ecosystem to engage its potential, we co-create the next set of actions, not as a one-time process but repeated and adapted across contexts. To enable this, we take actions that enhance the ability of the ecosystem to move together towards a shared purpose.

A resilient ecosystem is not built once, it is continually renewed. As circumstances change, we listen, learn, and adapt. Towards this, we introduce feedback loops, adaptive infrastructure and innovation mechanisms that keep the ecosystem responsive over time. Sustaining progress is about nurturing an ecosystem that detects where we are falling short and responds with practical course-correction. This requires reliable data, trusted spaces for reflection, and a culture of continuous learning.

Orchestrating Since diverse ecosystem actors play different roles towards a shared goal, it is important to nurture a shared narrative of change that resonates with people, communities and actors across government, civil society and markets. While the shared narrative offers direction, moving towards it requires cohesion – aligning incentives, motivations, investments, actions and timing among and across these actors.

As we make progress, it becomes essential to leverage data and evidence to sustain momentum and course-correct as needed. While orchestrating, we set guidelines and structures to coordinate action and make space for new voices / capabilities and harmonise the response of the ecosystem.

Orchestrating needs to be scaffolded by a robust and participatory governance mechanism. Governance ensures all initiatives and actions are in service of the big question by putting in place guardrails (policies and regulations) to protect against concentration of decision-making, unintended consequences of change created and help resolve conflicts and challenges that arise along the way.

Prototyping Prototyping helps us validate new ways of solving problems – testing small yet meaningful shifts in how the actors in the network learn, act, adopt change, share, or collaborate. Prototyping enables us to:

• Validate assumptions, test hypotheses and assess feasibility

• Learn quickly in real-world settings and make improvements

• Involve institutions and participants in shaping solutions

• Reduce risks before investing into driving adoption at scale

A prototype could be a physical model, a storyboard, a digital tool, a mock narrative, or a simulation of a new process. It is not limited to technology. We can prototype a narrative (say, how a story changes mindsets), a method or process (say, a new mentoring model), a knowledge asset (say, a playbook or toolkit) or a digital or physical tool (say, a self-learning application). Prototyping is not just a phase; it is a mindset and a way of thinking by doing, of grounding in the context of people who we aim to serve.

Reimagining Education Leadership

To better appreciate the sprint journey, we are following the story of how ShikshaLokam has been developing 4.5 million education system leaders in India. For this sprint, we will illustrate the prototypes they tested and what they learnt along the way.

To address their big question, ShikshaLokam adopted a prototyping mindset. They tested small, meaningful prototypes, or experiments, that would help unbundle what enables leadership and what makes systems self-healing. Their first prototype was in the Anekal education block of Karnataka. They explored the idea of ‘Cluster as a Distributed School’ – hypothesising that if a cluster of schools could function as an interdependent unit with “For” actors working together, including head teachers, teacher leaders and block officials, then the system could begin to heal and improve itself.

This prototype helped them understand the connection between leadership and agency. They saw how school leaders, when supported to reflect and make small context-specific improvements, began demonstrating ownership and creativity. The cluster became a microcosm of a self-healing system – one that listens, learns, and adapts without waiting for external interventions. This prototype enabled the ShikshaLokam team to validate the idea that it is possible for leadership to be effective when distributed and refined the idea of agency-driven micro-improvements compounding towards systemic change.

They realised that nurturing leadership at scale required open digital infrastructure – one that could be adapted and built upon by multiple actors in the ecosystem. ShikshaLokam instantiated its platform using the open-source building blocks of Sunbird. The platform opened a shared space where civil society organisations, government and academic institutions hosted and shared reusable leadership courses, tools, and resources. Leveraging these, educators could engage in self-paced, context-specific learning.

Then ShikshaLokam set out to build and strengthen the community of social entrepreneurs who could work with government and grassroots actors to enable leadership. They launched EduMentum to nurture early-stage organisations working on education leadership. It brought together mentors, funders, and practitioners and created a community of enablers who designed contextual leadership programmes. Through EduMentum, ShikshaLokam could distribute orchestration capacity across the ecosystem.

As these prototypes matured, they began to converge into collective action models. For instance, the Punjab Education Collective, which brought together multiple NGOs and government partners to work on learning improvement and leadership in the state. These early orchestration efforts taught ShikshaLokam how to align diverse actors around a shared goal (narrative infrastructure), establish coordination mechanisms across NGOs and the state (procedural infrastructure), and build trust-based, distributed governance systems where no single actor dominates the agenda. The journey continues…

Now Let Us Prepare for This Sprint Together… Please reflect on these questions from your perspective.

• In what sequence would you like to implement the actions / initiatives identified?

• What new ideas would you like to prototype to understand their feasibility / relevance?

• What orchestration and governance mechanisms may be beneficial for the journey ahead?