- Advanced
- About 16 min
- 5 practice questions
The accountability paradox: when more checks make things worse
Analyse defensive decision-making, accountability overload and conflicting forums, and argue for accountability designs that protect honest risk-taking while catching misconduct.
If something looks wrong, please tell us.
It is natural to think that more accountability is always better. Advanced questions challenge this. Officials who fear every audit, inquiry and court case may stop deciding at all, delay files, or choose the safest rather than the best option. This lesson analyses that paradox and how to design around it.
Three ways accountability can backfire
| Problem | What happens | Example |
|---|---|---|
| Defensive decision-making | Officials avoid decisions or choose options that are easiest to justify, not best for citizens | Referring every file to a committee so nobody owns the decision |
| Accountability overload | So many forums and reports that officials spend more time accounting than acting | A school head filling dozens of returns monthly |
| Conflicting expectations | Different forums demand incompatible things | Auditors want lowest price; users want quality; courts want speed |
Jonathan Koppell described a condition he called 'multiple accountabilities disorder': organisations that try to satisfy every conflicting expectation of accountability end up serving none well. The lesson is that accountability needs design, not just addition.
Honest mistakes versus misconduct
A decision that turns out badly is not necessarily a wrong decision. If the official acted in good faith, on the information available, following a reasonable process and recording reasons, the outcome alone should not make her culpable. Accountability systems that cannot tell bad luck from bad faith punish initiative. In India, a 2018 amendment to the Prevention of Corruption Act introduced a requirement of prior approval before investigating a public servant for recommendations or decisions taken in the discharge of official functions. Supporters saw it as protection for honest decision-makers; critics worried it could shield the corrupt. That debate is itself an example of the paradox.
Design principles
- Judge the process, not hindsight: ask whether the decision was reasonable when made.
- Protect recorded good faith: reasons written at the time are the official's best defence and the forum's best evidence.
- Rationalise reporting: fewer, more useful reports; one data entry used by many forums.
- Clarify priorities among forums: tell officials which goal wins when expectations conflict.
- Keep strong sanctions for bad faith: protection for honest error must not become impunity.
Worked example 1: the delayed medicine purchase
During an outbreak, a district health officer could buy medicines quickly from a reliable supplier at a slightly higher price, or wait weeks for a fresh tender. Fearing later audit objections, she waits, and patients suffer shortages. Analysis: defensive decision-making caused by fear of hindsight audit. Better design: emergency procurement rules with clear conditions, recorded justification, and an audit standard that asks whether the decision was reasonable at the time. She should then use the emergency route and record her reasons fully.
Worked example 2: the overloaded school head
A school head spends a large part of each week filling returns for different offices, many asking for the same data. Teaching supervision suffers. Analysis: accountability overload. Fix: one data platform where information is entered once and shared with all offices; removal of reports no one uses; time freed for academic supervision, which is the purpose of her post.
Accountability should catch bad faith, not punish honest judgement; it should be designed, prioritised and proportionate, not simply multiplied.
Key takeaways
- More checks can produce defensive decisions, overload and conflicting demands.
- Koppell's 'multiple accountabilities disorder' names the problem of conflicting expectations.
- Judge decisions by the process and information available at the time.
- Protection for good faith must not become impunity for bad faith.
Check your understanding
-
1. An officer refers every decision to a committee so that no one can be blamed. This is an example of:
- Defensive decision-making
- Outcome accountability
- Social audit
- Proactive disclosure
Show answer
Answer: A. Avoiding ownership of decisions out of fear of blame is defensive decision-making.
-
2. 'Multiple accountabilities disorder' was described by:
- Andreas Schedler
- Dennis Thompson
- Jonathan Koppell
- Max Weber
Show answer
Answer: C. Koppell used the term for organisations that try to satisfy conflicting accountability expectations and serve none well.
-
3. A fair standard for judging a decision that turned out badly is:
- Whether the final outcome of the decision turned out to be good
- Whether the official concerned is popular with the public and the press
- Whether the media and the opposition approve of the decision afterwards
- Whether the decision was reasonable given the information and process at the time
Show answer
Answer: D. Judging by hindsight punishes honest risk-taking; reasonableness at the time is the fair test.
-
4. Entering school data once on a platform shared by all offices addresses:
- Accountability overload
- Collective responsibility
- Judicial review
- Bad faith
Show answer
Answer: A. Rationalising duplicate reporting reduces overload.
-
5. The main risk of strong protection for decision-makers against investigation is that it:
- Increases transparency and public trust in the decision-makers
- May shield corrupt officials if it is not limited to good faith
- Reduces audit objections to zero in the whole department
- Removes all discretion from officials taking decisions
Show answer
Answer: B. Protection for honest decisions must be designed so that it does not become impunity for bad faith.
Sign in to keep track of the lessons you finish.