Why the Same Problems Keep Happening in My Company

Accountability is one of the most frequently discussed and least practiced concepts in business. Every leadership team wants it. Most leadership decks include a slide about it. Roughly half the performance review systems I have seen are built around it.

And yet, if you walked into most of the companies I work with and asked the leadership team who is accountable for the organization's most pressing problems, you would get a version of the same answer: a lot of thoughtful analysis about external conditions, market dynamics, team performance, legacy decisions, and structural limitations. Very little finger pointed at the mirror.

That is the accountability gap. And it is not a system design problem. It is a human problem. Specifically, it is what happens when the people leading an organization have learned, usually very early and very completely, that being the reason something went wrong is not safe.

What does real ownership look like at the top?

Radical accountability is a concept built on two components that sound simpler than they are. Radical acceptance and radical responsibility.

Radical acceptance comes from dialectical behavior therapy. It is not resignation. It is not approval. It is the willingness to acknowledge the present reality completely, without fighting against the fact of it. The deal is lost. The hire was wrong. The strategy did not work. The market changed. These things are true. Fighting the truth of them, which is what most organizations do in the early stages of any setback, consumes resources and produces nothing.

Radical responsibility goes further. It says that even in situations where external conditions contributed to the outcome, the leader's choices, responses, interpretations, and behaviors are in scope. Not as punishment. As data. If the market shifted and the business was not positioned to respond, who made the decisions that left the business unpositioned? If the hire was wrong, who hired them, what criteria were used, what signal was ignored?

The combination of these two is what makes accountability functional: seeing what actually happened, fully, without editing for comfort, and then tracing the thread of personal agency through it without stopping the trace at the point where it becomes uncomfortable.

Most accountability conversations stop well before they get there.

Why do smart leaders blame outside conditions for their results?

The accountability gap exists for reasons that are psychologically precise and worth understanding.

Accountability requires self-awareness at a level that is actively uncomfortable. You have to be willing to see yourself as the cause of outcomes you do not want to claim. That triggers something very fundamental in human psychology: the attribution bias, which is the well-documented tendency to attribute our successes to our own abilities and our failures to external circumstances.

This is not weakness. It is a feature of how the human brain protects self-concept. The brain that could look at a failure and immediately and accurately trace it to its own choices without any defensive processing would also be unable to maintain the confidence required to act under uncertainty. Some degree of protective interpretation is probably adaptive.

The problem is when the protective interpretation becomes the primary mode of operating. When the founder who has missed their growth targets for three consecutive years is still primarily focused on the market conditions and the team composition and the macroeconomic environment without once sitting in the room with the question: what did I do that contributed to this, and what am I doing right now that is making it continue?

The longer that question goes unasked, the wider the gap gets. And the gap does not just cost the founder. It costs everyone working in an organization whose leader has not yet located themselves in the problem.

How does a victim mindset show up in executives?

Victim posture in business does not usually look like self-pity. That would be too visible. It shows up in subtler ways that are easier to defend because they are partially true.

It looks like the founder who is primarily articulate about what their team cannot do, their market does not understand, their investors do not appreciate, and their competitors do not play fair. The analysis is often accurate. The incompleteness of it is the problem. An accurate description of external constraints that does not include an accurate description of internal constraints is not a diagnosis. It is a defense.

It looks like the CEO who in every board presentation has a sophisticated account of why the quarter missed and an equally sophisticated account of why the next quarter will be different, without any sustained examination of what pattern they are running that has produced the same result multiple times.

It looks like the leadership team that is very good at explaining why execution is hard and very bad at asking whether strategy is wrong, because asking whether strategy is wrong means asking who made the strategy.

It looks like the organization that has institutionalized blame at every level. Marketing blames product. Product blames engineering. Engineering blames sales for setting wrong expectations. Sales blames marketing for bad leads. Everyone has a defensible position. Nobody has a solution. The CEO sits at the top of a blame structure and wonders why nothing changes.

What do problems with no owner cost the company?

When problems do not have owners, they persist. That is not a motivational statement. It is a mechanical one.

A problem with an owner has at least one person whose job it is to understand the problem accuratly, develop responses, test those responses, and iterate. The owner has skin in the game. The outcome is connected to their sense of themselves. Even if the owner is also partially the cause of the problem, ownership creates the conditions for resolution.

A problem without an owner just degrades. It gets described, categorized, analyzed, included in presentations, and left in the same condition it was in three quarters ago. Because nobody's internal identity is attached to whether it resolves.

The accountability gap produces organizations full of unowned problems. Everybody can describe the problems. Many people have opinions about whose fault they are. Nobody has claimed them as theirs to fix.

The founder who says "I am responsible for that" and means it, not performatively, not in a way that is really designed to seem humble before redirecting blame somewhere else, but actually and operationally, that founder changes the organization's relationship to its problems. Because if the founder can own their role in something that went wrong, it becomes possible for others to own theirs. And then the problems start moving.

Is holding myself accountable the same as blaming myself?

This is the place where a lot of founders get stuck. They hear accountability and they hear judgment. And so they either reject it, because they are not going to sit in front of their team and be punished for every strategic miss, or they overcorrect into a performance of self-criticism that is also not accountability, just a different kind of defensiveness.

Radical accountability is neither of those things. It is the clinical and specific identification of which choices, behaviors, and patterns you contributed to an outcome, combined with the full intention to make different choices going forward. That is it. No flagellation. No theater. Just precision.

A founder I worked with had a pattern of building and then abandoning internal initiatives. He would get excited about a new direction, communicate the excitement to the team, get them organized around it, and then quietly stop prioritizing it when the next thing captured his attention. Three or four cycles in, the team had stopped believing any new initiative would last. They participated perfunctorily while the founder was excited and waited for the cycle to complete.

When I named this to him, his first response was to explain the external factors that had shifted his focus each time. The explanations were true. They were also completely irrelevant to the organizational damage the pattern was causing. The second time we talked about it, he said: I have done this to them four times and they have no reason to believe I will not do it again. That is accountability. It is not theater. It is not self-punishment. It is a precise and accurate recognition of his role in a pattern that was costing him organizational trust.

That recognition was the beginning of the change. Not the conversations with the team. Not the new initiative structure. The moment he could see himself clearly in the problem without running from it.

How do I build accountability without a blame culture?

Accountability and blame are not the same thing and they require different architecture.

Accountability is prospective and operational: who owns this, what does that ownership require, and what happens when the outcome is not what we aimed for. Blame is retrospective and relational: who caused this and what does that mean about them.

Organizations that run on blame are full of people managing their exposure to being blamed. They make conservative decisions. They over-document. They build strong cases for why what they did was reasonable. They do not take risks because risk creates exposure to a bad outcome and a bad outcome creates exposure to the blame machine.

Organizations with real accountability run differently. People own things. When something goes wrong, the owner traces what happened accurately, including their own contribution to it, and uses that information to do something different. The organization is oriented toward resolution, not toward the allocation of fault.

The founder builds that culture by doing it first and doing it visibly. Not by declaring it in a values document. By doing it in a meeting, in front of the team, when something they own has gone sideways. That moment is worth more than any culture initiative in the history of the company.

Why do the same problems keep happening in my company?

Pick the thing in your business that is most frustrating to you right now. The thing you talk about most in leadership team meetings. The thing you have the clearest and most sophisticated explanation for why it is happening.

Now ask: what is my role in this? Not a token answer. A complete trace. Every decision that contributed to the current state. Every behavior that is maintaining it. Every thing you know you should be doing differently that you are not doing.

Write it down. Not for anyone else. For you. And see if the version you write down is actually complete, or whether it stops before it gets to the part that is uncomfortable.

That stopping point is where the accountability gap is. And everything that is not working in your business lives on the other side of it.

How does ownership work differently in nonprofits?

Accountability in nonprofit organizations gets complicated by the emotional weight of mission. When the work matters deeply and the resources are scarce and the need is real, owning a failure feels like failing the mission and failing the people it serves.

That weight makes the accountability gap wider in nonprofit leadership, not narrower. Because the stakes feel too high to be wrong, and being wrong feels like something worse than a business mistake.

But the cost of the gap is the same. Programs that are not working stay funded. Leaders who are not right for the organization stay in roles. Strategies that are not producing outcomes stay in strategic plans. And the people the mission is supposed to serve continue to receive resources that are consumed by an organizational system that cannot tell the truth about itself.

Accountability is not a betrayal of the mission. It is the mechanism that keeps the mission honest.

Frequently asked questions

What is radical accountability, and how is it different? Radical accountability combines two components: radical acceptance, the complete acknowledgment of current reality without fighting against the facts of it, and radical responsibility, the willingness to trace personal agency through any outcome, including uncomfortable ones, without stopping the trace at the point of maximum discomfort. Standard accountability practices often focus on systems and structures. Radical accountability addresses the psychological pattern underneath the system: the tendency to locate the cause of problems in conditions outside personal control.

Why do the same problems keep recurring in my business? The accountability gap is the distance between what a leader says about accountability and what they actually practice when things go wrong. It shows up most visibly in how leaders narrate setbacks: sophisticated accounts of external conditions and team limitations that are accurate as far as they go but incomplete because they stop before they reach the leader's own choices and behaviors as contributing factors. The gap is not usually intentional. It is the result of deeply human attribution patterns that protect self-concept at the cost of organizational accuracy.

How does a victim mindset show up in executives? In an executive context, victim posture rarely resembles self-pity. It looks like precision about external constraints without equivalent precision about internal ones. The CEO who has a sophisticated explanation for every miss without examining their own pattern across multiple misses. The leadership team that can map every external obstacle without examining whether the strategy requires a different kind of leader to execute. It is the organizational tendency to explain performance gaps through conditions rather than through choices.

Can I hold people accountable without a blame culture? Yes, and the distinction matters. Accountability is prospective and operational: it is about ownership of outcomes and learning from what happens. Blame is retrospective and relational: it is about attributing fault in a way that has social consequences. Organizations that run on blame create cultures of defensive decision-making where people manage their exposure to fault rather than their contribution to outcomes. Accountability-based cultures run on ownership: someone's job is to understand what happened, trace their contribution to it, and do something different.

What's the first step to owning my part in the pattern? Take the thing in the business that is generating the most sophisticated external explanation and trace it backward through personal agency. Not as a performance of humility but as a genuine operational exercise: what decisions contributed to this state, what behaviors are maintaining it, and what is being avoided that is keeping it from changing. The stopping point in that trace, the place where it becomes uncomfortable to keep following the thread, is where the gap is. That is the work.

Take this if it serves you. Much Respect, -bryan