Accountability begins the day you agree to hear what you had no wish to read
In a project, it is relatively easy to communicate about what went well.
You set out the activities carried out, the objectives reached, the number of people served and the results obtained.
But what about criticism?
What do we do with complaints?
What do we do when the people we serve tell us that our work does not really answer their needs?
That is precisely where accountability begins.
“Accountability begins the day you agree to hear what you had no wish to read.”
Accountability is not only about reporting
Accountability is often reduced to the duty of presenting results to funders, partners or authorities.
But it goes well beyond producing reports.
It also means putting in place arrangements that let the people affected by a project:
give their opinion;
voice their concerns;
report a problem;
make a complaint;
suggest improvements;
receive an answer.
In other words, the people a project serves should not be treated only as recipients, but as interlocutors able to help make it better.
Listening does not always mean agreeing
One of the challenges of accountability is accepting that the feedback received will not always be what the team hoped to hear.
A satisfaction survey may reveal shortcomings.
A complaints mechanism may bring an unexpected problem to light.
A community consultation may call into question an approach the project team thought entirely sound.
This information can be uncomfortable.
But it is valuable.
Negative feedback, properly analysed, can correct a problem before it becomes a much larger one.
A complaint is not necessarily a failure
A complaint can be seen as a threat to an organisation's image.
And yet it can also be an important source of information.
When someone takes the time to report a problem, they are potentially supplying information that no standard monitoring tool would have surfaced.
The question should therefore not be only:
“How many complaints did we receive?”
But rather:
“What did we learn from those complaints, and what did we do next?”
It is that second question that gives accountability its meaning.
Accountability must lead to action
Setting up a suggestion box, a free telephone line, a complaints form or a satisfaction survey is not enough.
The feedback received must also be followed up.
An effective accountability mechanism has to move through:
Listen → analyse → answer → act → follow up
For example, if several people report the same difficulty, the organisation must be able to spot the pattern, analyse its cause and decide whether the project needs adjusting.
Otherwise the mechanism turns into a mere administrative formality.
Accountability also takes organisational courage
It is easy to ask communities for their opinion.
It is much harder to accept that this opinion may call some of your decisions into question.
A genuine culture of accountability therefore requires a certain openness:
“We can be wrong.”
And above all:
“If we are wrong, we must be able to acknowledge it and put it right.”
That attitude is what turns feedback into a real instrument of learning.
An organisation that listens learns
Accountability should not be seen as one more constraint imposed on teams.
It can become a genuine tool for improvement.
Feedback from the people served can help to:
improve the quality of services;
identify operational problems;
understand needs better;
adapt activities;
build trust with communities;
improve the design of future projects.
So listening is not a weakness.
It is an organisational capability.
Conclusion
Accountability does not begin when an organisation publishes its final report.
It begins when it genuinely agrees to listen to the people its work affects — including when their answers are hard to hear.
Because an organisation that listens only to the information confirming that it is doing well is likely to miss the very problems that call for its attention.
Listen to criticism. Understand the problems. Answer. Act. Learn.
That too is accountability.
