Disclosure systems / Institutional incentives
Nobody is rewarded for finding a problem
Build the perfect portal. Every field published, every record fresh, every dataset machine-readable, every API awake. Turn all six build levers to maximum, and the accountability outcome barely moves, because the levers that decide it are bolted to a wall you do not control.
The diagnosis everyone reaches for
The missing-information theory of failure
When a public project goes wrong and somebody asks why nobody caught it, the answer almost always arrives in the same shape: the information was missing. The data was not published. The record was stale. The format was unusable. The portal was down.
That diagnosis is attractive because it is tractable. Missing information has an owner, a budget line, a vendor and a delivery date. You can procure your way out of it. So we do: another portal, another standard, another integration, another dashboard.
And it is often correct. Plenty of failures really are information failures, and fixing them really does help. That is the whole case for disclosure infrastructure, and it is a good case. I have spent years making it.
But it is not the whole account, and treating it as the whole account is how a well-built portal ends up sitting on top of a system that keeps failing in exactly the same way. So here is the test. Build the portal perfectly and see what happens.
The instrument
Turn every lever you own to maximum
These six levers are the ones a disclosure programme actually controls. Push them as far as you like. The meter on the right is not the portal's health; it is whether a problem that exists gets found, named and acted on by someone who can change it.
Your panel: what architecture buys
Six build levers, 0 to 100. Every one of them is a real, fundable line item.
The portal reads
Patchy
Problems found, named and acted on
6 / 100
Start moving the levers. Watch how far the outcome follows the build.
| Build levers | The portal reads | Problems found and acted on |
|---|---|---|
| All at 0 | Absent | 2 of 100 |
| All at 20 | Patchy | 6 of 100 |
| All at 60 | Solid | 14 of 100 |
| All at 100 | Flawless | 20 of 100 |
How this model works, stated plainly so you can argue with it: the six build levers are capped at a combined 20 of 100, because architecture removes the friction of finding out and nothing else. The remaining 80 sits with the six institutional levers below, which this panel cannot reach. The weighting is an argument from field experience, not a measured coefficient. No dataset here. Disagree with the split and the shape of the claim survives: the ceiling exists even if you move it.
What the meter is telling you
A flawless portal is a 20
You built it. Every field published, every record same-day, clean JSON, full uptime, standard-compliant, searchable. The portal reads Flawless. The outcome reads 20.
Not zero. That 20 is real, and it is worth having: it is the difference between a problem being unknowable and a problem being knowable. Every serious accountability story starts from a record someone could get to.
But knowable is not the same as found, and found is not the same as fixed. The remaining 80 lives with six forces that were never on your panel, and none of them is an information problem.
Architecture can reduce friction. It cannot manufacture institutional demand for accountability.
The far panel
Six levers you cannot procure
Each of these survives a perfect portal untouched. For each one, the same question: what would actually have to change, and who has to change it.
LEVER 01
Officials have no incentive to expose problems
The person best placed to spot the fault is the person whose unit gets blamed for it. Publishing it is a career cost paid by them and a benefit collected by someone else. Perfect data does not change that arithmetic; it only makes the cost easier to incur.
Moves when: finding a problem early is what gets you promoted. Owner: the ministry's own performance and appraisal rules.
LEVER 02
Decision-makers lack the authority to act
The officer reading the red flag cannot suspend the payment, vary the contract or remove the contractor. The person who can is three levels up and reading something else. A signal with no matching power is just information arriving at the wrong desk.
Moves when: a named role can halt a payment on the evidence. Owner: whoever writes the delegation of authority.
LEVER 03
Agencies protect jurisdiction
The problem sits across a boundary: the roads authority sees the works, the finance ministry sees the money, the audit office sees it a year later. Each is right within its mandate and none owns the whole picture. Integration at the data layer does not merge the mandates.
Moves when: one body is answerable for the joined-up view. Owner: cabinet or the statute that split the mandates.
LEVER 04
Political priorities outrank evidence
The record says the project is failing. The project is also the one that was announced, ribbon-cut and promised before an election. Evidence does not lose the argument here; it never gets to have the argument. This is the lever that most often decides the others.
Moves when: cancelling a bad project costs less than defending it. Owner: the political principal, not the programme.
LEVER 05
Budgets end when the donor project ends
The portal was built on a three-year grant. The data pipeline, the analyst who read it and the unit that chased the findings were all on the same grant. The system does not fail on the last day; it goes quietly stale, and the failure is only visible years later.
Moves when: the recurrent budget carries the running cost before the grant closes. Owner: the finance ministry, at the next budget cycle.
LEVER 06
Nobody is punished when the system goes stale
Publication stops. Nothing happens. No hearing, no finding, no consequence for the accounting officer. The absence of a penalty for silence is itself a rule, and it teaches everyone what the disclosure regime is really worth.
Moves when: failure to publish is an audit finding with a named officer. Owner: the supreme audit institution and the regulator.
The trap this creates
Why the fix is always another portal
Look at the six levers again and notice what they share. Every one of them requires someone powerful to accept a cost: a ministry to be appraised on bad news, a principal to lose a project they announced, a finance ministry to take on a recurrent line, an audit office to name an officer.
The build levers require none of that. They need a budget, a vendor and eighteen months. That asymmetry is the whole explanation for the pattern: we keep fixing the tractable thing because it is the one nobody has to lose an argument over.
This is not a case against disclosure infrastructure. I build it, and the 20 is worth having. It is a case against the substitution: shipping architecture and reporting it as accountability, then being surprised when the same failures repeat on a better platform.
The honest version is narrower and more useful. A portal makes a problem knowable. Whether it gets found, named and acted on is decided somewhere else, by people whose incentives you can describe and, sometimes, change.
What to do with this
Ask the question the portal cannot answer
Before the next disclosure system is scoped, ask who is rewarded for finding a problem in it. Not who can access the data: who benefits, personally and institutionally, from surfacing something bad. If the answer is nobody, you already know what the system will produce, however well it is built. Ask it again at the mid-term review, when the grant that pays for the analyst is halfway gone.
Architecture can reduce friction. It cannot manufacture institutional demand for accountability.