Leadership Accountability Can Improve Team Reporting After Business Failures

A missed deadline can reveal more than a planning failure. The way a leader responds can determine whether the next problem surfaces early or stays hidden until it becomes more costly. For business owners, accountability works best when it starts with an examination of the environment they shaped, then addresses the choices individual employees made.

Christopher Myers, CEO of B:Side Capital and B:Side Fund and an entrepreneurial leadership professor at Arizona State University’s W.P. Carey School of Business, describes a familiar reaction to a serious miss: leaders scan for the person responsible. That instinct may identify who made the final decision, but it can also make employees cautious about sharing what happened. Myers says the silence after he looked for someone to blame stayed with him longer than the slipped deadline itself.

His experience points to an operating risk. When employees expect punishment before inquiry, they may delay reporting weak signals or leave out context. Managers then receive a less accurate account of the failure, making it harder to fix the process that contributed to it. Leaders may need to address individual performance, but the order of that conversation shapes what the organization learns.

Start with the conditions behind the miss

Myers argues that leaders should write down the conditions that preceded a mistake before naming the person who made it. That means examining priorities, staffing, incentives and the information available to the employee responsible for acting. These are areas where leaders often have more influence than the people closest to the breakdown.

The questions are practical: What did leadership prioritize? Was the person given enough authority and support? What behavior did the incentive structure reward? Which warning signs were missed or never passed along? Answering them can reveal whether a failure grew out of an individual decision, a flawed process or a combination of the two.

Consider a restaurant delivery that arrives late. The employee receiving it may have missed a step, but a schedule without time for receiving could have made the delay more likely. In a software company, an outage may follow a release process that employees understand is not consistently enforced. In each case, examining the operating conditions gives leaders a clearer basis for deciding what to change.

That distinction matters because a postmortem is also an information-gathering exercise. If the first response is a verdict, employees have reason to shape their accounts around what they think a manager wants to hear. If leaders first ask how the work was set up, they can get a fuller picture while still reserving judgment about the choices people made.

Pair leadership ownership with individual accountability

Looking upward does not remove responsibility from the person who made a decision. Myers’s point is about sequence: first establish what the organization and its leaders made possible, rewarded or overlooked; then assess the individual action. That approach can preserve a clear standard without pretending that senior leaders control every choice.

In a review, a manager might state both parts directly: “Here is what I set up that made this more likely. Here is the decision that still belongs to you.” The wording separates the leader’s contribution from the employee’s agency. It also gives the discussion a useful structure: acknowledge the conditions, identify the choice, and decide what needs to change.

The same method can apply across very different operations. A franchise owner reviewing a poor weekend shift can look at staffing and training while addressing an employee’s conduct. A clinic owner investigating a billing error can check whether the process and information were clear before judging how a worker handled the claim. A manufacturer responding to increased scrap can review equipment, targets and procedures alongside the decisions made on the floor.

Without that distinction, teams can fall into two unhelpful patterns. Leaders may single out a convenient employee and leave a weak system intact, or they may talk so broadly about “the process” that no one is responsible for a specific decision. A sound review needs both levels of accountability. Seniority should bring greater responsibility for the conditions people work in, while each person remains accountable for choices within their control.

Make candid reporting useful to the business

Myers connects this approach to employee engagement. Gallup reports that managers account for at least 70% of the variance in team engagement, while 20% of employees worldwide were engaged in 2025. Those figures put managers’ influence in context: the people who shape priorities and daily communication also affect how willing staff may be to speak up.

For owners, the economic value of earlier reporting is straightforward. A warning that arrives while a problem is small gives a business more time to investigate and respond. A culture that makes reporting feel risky can push those signals later, when the disruption may be harder to contain. Trust is built through repeated evidence that employees can describe a problem without having the account used against them automatically.

That does not require leaders to avoid difficult conversations. It requires them to distinguish between an honest account of a failure and an effort to evade responsibility. A careful review can surface both: the process defects that leadership should address and the decisions that an employee needs to own. The goal is a more accurate explanation and a clear response, not a performance of blame or an excuse for poor judgment.

Build a repeatable review after meaningful misses

Myers recommends making the discussion a routine rather than waiting for a crisis. After a meaningful failure, leaders can hold a 10-minute debrief with the people closest to the work. The leader speaks first about the conditions; employees then explain their choices. The group finishes by naming one system change and one clear expectation for the person involved.

That format is short enough to repeat and specific enough to produce action. If the room still feels guarded, Myers suggests treating that caution as information. Employees may be holding back details about unclear expectations, past reactions or incentives that made the safer choice seem to be silence. Leaders can ask what was left out of the first account and use the answer to improve the next review.

A practical starting point is to revisit a recent failure that still concerns the business. Write four lines about the conditions leadership created and one line about the decision that belonged to someone else. Discuss both with the employee involved, then ask what parts of the story were difficult to share initially. The test is whether future concerns reach management sooner and with enough detail to act.

For a business, accountability is not only a way to assign consequences. It is also a way to keep information moving through the organization. Leaders who own their part of the operating environment can set a higher standard for candor while still drawing a clear line around individual responsibility. After the next miss, what matters is whether the organization learns enough to prevent a repeat—and whether people feel able to tell the truth in time.