The Accountability Gap - Part One: It Was Just a Small Mistake

There are few moments more exciting for a young graduate than receiving that employment email.

After months of applications, assessments, interviews and the occasional “we will get back to you,” Adewale finally got his break. He had completed NYSC only a few months earlier and was employed as a junior communications officer in the digital communications team of one of Nigeria’s largest corporate groups. He called his mother immediately.

Bisi had a similar story. She had also just completed NYSC and had been employed by the same organisation as a junior social media executive. Her first week was a mixture of excitement and nervousness. The company was not one people casually ignored. Its name was on buildings, trucks, products, television adverts and newspapers. Millions of Nigerians knew the brand.

For both of them, the first few weeks felt like proof that the hard work had finally started to make sense. Then came a Tuesday afternoon.

The communications team had prepared a social media post celebrating an important corporate milestone. It was a routine assignment, or so it appeared. The copy had been written, the graphic had been designed, and the post was scheduled for publication. Adewale was responsible for one of the final checks before publication.

He looked at the graphic. He read the caption. He checked the date. Everything seemed fine. He approved it.

Bisi, who was responsible for publishing the post, saw the approval and pushed it live, Within minutes, the post began receiving engagement. Then someone noticed something.

A major figure in the graphic had been identified with the wrong title, Not a missing paragraph. Not a broken link. Not some complicated technical failure, One small line.

But the company was a highly reputable organisation, and the person whose title had been incorrectly stated was a nationally recognisable figure, within an hour, screenshots were circulating, People were laughing, others were criticising the company, a few media platforms picked it up.

By evening, the mistake that had taken less than five minutes to create had become a public conversation about the competence of the company's communications team.

The next morning, the Head of Communications called the team into a meeting. “Who approved this?” Adewale explained that the information had come from the material supplied to the team, Bisi explained that she had only published the post after it had been approved, Someone else pointed out that the original brief had been unclear.

Another employee mentioned that the team had been under pressure to publish quickly, Everyone had an explanation, And almost every explanation was true. That was the problem. The room was full of explanations, but the mistake was still sitting on the internet. This is where the accountability gap begins.

Accountability is not the refusal to explain what happened. Explanations matter. Organisations need to know whether an error came from poor information, inadequate checking, unclear instructions, system failure, workload or human error.

But explanation answers one question: “What happened?”

Accountability asks another: “What are we going to do about it?”

Research on workplace error response makes this distinction particularly useful. Fischer and Weißmüller’s 2024 study examined how employees respond to errors and specifically considered the difference between reporting and correcting mistakes versus ignoring or hiding them to avoid blame. The important lesson is that the value of identifying an error lies partly in what happens after the error has been recognised, Imagine that Adewale had noticed the mistake five minutes after publication, The accountable response would not have been to sit quietly and hope nobody noticed.

It would have been:

“Sir, I have identified an error in the post we published at 2:15 p.m. The title is incorrect. I have taken the post down, prepared the corrected version and sent it for urgent review. I am also checking whether the same information appears in any other scheduled materials.” That is a different professional posture, the mistake has not disappeared, but the employee has moved from explaining the problem to managing the problem.

This distinction becomes especially important for young employees because the instinct to defend oneself is understandable. You have just entered the organisation. You want to appear competent. You do not want your first major mistake to become the story people tell about you.

So you begin building a defence. “The designer made the graphic.” “The information was in the brief.” “I was only following instructions.” “I thought someone else had checked it.” “The deadline was tight.”

Sometimes these statements are completely accurate, they are also sometimes completely irrelevant to the immediate task of containing the damage, a company does not need an employee who can win a courtroom argument about why the mistake was not technically his fault, it needs an employee who can recognise that something has gone wrong and help stop the problem from becoming worse. That does not mean accepting blame for everything. Accountability should not become scapegoating. A junior employee should not be expected to carry responsibility for decisions outside his authority or failures created by the organisation itself.

But within one's area of responsibility, there is a significant difference between saying, “This was not entirely my fault,” and saying, “Here is what I am doing about it.”

The first may be a defence. The second is accountability. Adewale and Bisi had both entered the organisation with certificates, enthusiasm and enough technical knowledge to perform their assigned duties.

Their first serious professional lesson was not about social media. It was about responsibility. Because in a large organisation, a mistake rarely remains the size of the mistake that created it.

A wrong word can become a screenshot, A screenshot can become a post, A post can become a news story, A news story can become a reputation problem.

And somewhere in that chain, someone eventually has to stop explaining and start solving.

That is what the organisation is looking for when it asks an employee to take accountability.