Sector analysis · Five implementations
The five portals I watched fail were built for launch, not for use.
Transparency cannot be a separate task. It has to be a byproduct of doing the work. Make the five decisions yourself and watch your portal live or die across its first three years.
The five portals I watched fail were built for launch, not for use.
Transparency cannot be a separate task. It has to be a byproduct of doing the work. Make the five decisions yourself and watch your portal live or die.
Flip each decision. Watch the curve move.
A portal with none of the five survival decisions starts strong at the launch event, then collapses as soon as the funding and the goodwill run out.
An explanatory model of observed patterns, not a calibrated forecast.
Run your portal forward.
A portal with none of the five survival decisions starts strong at the launch event, then collapses as soon as the funding and the goodwill run out.
This is the curve from the decisions you set. Watch the year clock run from launch to year three.
Survivors share architecture, not a launch.
The portals that survived were fed automatically from the systems officers already use, linked end to end, and checked by an independent reviewer. Transparency cannot be a separate task. It must be a byproduct of doing the work.
A portal does not die of neglect. It dies of the decisions made before launch.
Hardwire it into the workflows officers already run. Everything else is a press release with a countdown on it.
Build your portal. Then leave it alone for three years.
Flip each decision the way real teams do. The model plays the consequence forward. Goodwill is not on the list, because goodwill is what dies first.
A portal with none of the five survival decisions starts strong at the launch event, then collapses as soon as the funding and the goodwill run out.
Survivors have the same architecture, not the same launch.
The portals I have watched survive longest were not the most visually impressive at launch. They were the ones designed around a specific user doing a specific job, fed automatically from the systems officers already use, linked end to end with OC4IDS, and checked by an independent reviewer with the authority to publish what they find.
Transparency cannot be a separate, additional task. It must be a byproduct of doing the work. Every decision above is a way of making the data flow without asking a human to remember.
Methodology and data
Drawn from five infrastructure disclosure portal implementations across Uganda and the wider East Africa region. The five survival decisions are the patterns that separated portals that stayed active from portals that went dark within three years. The CoST Independent Review is the assurance mechanism referenced. The survival curve is an explanatory model of those observed patterns, not a calibrated forecast; the weights express relative importance as observed, not measured probabilities.
| decision | relative_importance_weight | failure_if_skipped | confidence |
|---|---|---|---|
| Automate data extraction from source systems | 30 of 100 (modeled, not a survival probability) | Officers must log in and upload spreadsheets. Compliance drops to zero the moment funding ends. | Observed across 5 implementations (Uganda and East Africa, as reported) |
| Link procurement to delivery with OC4IDS | 22 of 100 (modeled, not a survival probability) | The portal stops at contract award. Citizens get a receipt, not whether the hospital has a roof. | Observed across 5 implementations (Uganda and East Africa, as reported) |
| Run the CoST Independent Review | 20 of 100 (modeled, not a survival probability) | Raw data, unverified. Governments publish optimistic figures and face no consequence. | Observed across 5 implementations (Uganda and East Africa, as reported) |
| Build for the practitioner, not the press release | 16 of 100 (modeled, not a survival probability) | Impressive at launch, useless on Tuesday. No one returns because no one had a task. | Observed across 5 implementations (Uganda and East Africa, as reported) |
| Fund the pipeline as architecture, not a project | 12 of 100 (modeled, not a survival probability) | When the grant closes, the clerks leave and the pipeline silts up. | Observed across 5 implementations (Uganda and East Africa, as reported) |
A portal does not die of neglect. It dies of the decisions made before launch.
If you want yours to outlast its launch funding, hardwire it into the workflows officers already run. Everything else is a press release with a countdown on it.