Meta: course=fellowship · module=1 · lesson=1.1 · ~70 min · keywords: pilotitis, institutionalization, NASSS, designed-for-scale, alignment, strategic persistence, leadership stance, digital health platform Objectives:
- Articulate why digital health leadership is an institutional discipline, not a technology discipline.
- Diagnose pilotitis and the structural reasons initiatives fail to scale.
- Apply "alignment with the national architecture" as the decisive strategic filter.
The African digital health landscape is littered with technically sound projects that worked — and then ended. They ended when the grant ended, when the champion was transferred, when the server bill arrived, when the NGO closed its country office. The field's defining pathology, pilotitis, is the gap this Fellowship exists to close. A Fellow's first reorientation is therefore one of stance: scale is not an event but an institutional condition — a system is at scale when its functioning no longer depends on any particular project, person, or donor. Everything in this program serves that single, demanding definition.
The evidence on why pilots stall is mature. The NASSS framework — nonadoption, abandonment, and challenges to scale-up, spread, and sustainability — locates failure not in technology but in accumulating complexity across the condition, the technology, the value proposition, the adopters, the organization, and the wider system; initiatives die when that complexity is ignored rather than managed. The mHealth-specific diagnosis is blunter still: pilots are typically designed as pilots — financed, staffed, and architected for demonstration, not for absorption — so scale would require a redesign nobody budgeted. The corrective, repeated by the MAPS toolkit and PATH's scale frameworks alike, is to plan for scale from day one, across management, financing, technology, partnerships, and integration, or to accept that the pilot is the product.
The single most powerful lever a leader holds is alignment. An intervention inside the national architecture and strategy inherits financing channels, governance cover, and scale pathways; an intervention outside them inherits isolation, however elegant its design. This is why DHIS2 national HMIS programs and Ethiopia's eCHIS became "simply how the health system works" — owned where they operate, surviving staff turnover and donor cycles — while a thousand bespoke pilots are remembered by no one. For the Fellow, alignment is not bureaucratic deference; it is the highest-return strategic decision available, made before a single line of requirements is written.
The reward justifies the patience. Reaching the institutional condition of scale takes, in the honest experience of the programs this book draws on, the better part of a decade of strategic persistence — problem-first design, coalition maintenance, architecture discipline, costed honesty, financing domestication, and evidence-steered adaptation, sustained across political and funding cycles. Each system that crosses from pilot to platform permanently raises the floor for everything built after it. That is how health systems are transformed: not by a thousand flowers blooming, but by a few deep roots holding. The Fellowship trains gardeners of roots.
Key terms:
- Pilotitis — the endemic failure pattern in which projects launch as small pilots and terminate when project funding ends, never integrating into national systems.
- Institutionalization — the deliberate transfer of every life function of a system (budget, staffing, maintenance, governance, data ownership) from project to government institution.
- NASSS framework — a model locating scale failure in accumulating complexity across condition, technology, value, adopters, organization, and wider system.
- Alignment — placing an intervention inside the national architecture and strategy so it inherits financing, governance, and scale pathways.
Knowledge check: Q: What is the precise definition of "at scale" a Fellow should hold? A: A system is at scale when its functioning no longer depends on any particular project, person, or donor — an institutional condition, not a user-number milestone.
Q: Why is "designing a pilot as a pilot" a structural cause of failure? A: Because pilots financed, staffed, and architected only for demonstration require an unbudgeted redesign to absorb into national systems — so scale never happens.
Q: Why is alignment with the national architecture the decisive strategic filter? A: An aligned intervention inherits financing channels, governance cover, and scale pathways; an unaligned one inherits isolation no matter how elegant its design.
Summary: Digital health leadership is an institutional discipline aimed at one condition — independence from any single project, person, or donor. Pilotitis is structural and avoidable; the antidotes are designing for scale from day one and aligning relentlessly with the national architecture, sustained across years.