Take Responsibility

Introduction

When bad news must be communicated, one of the most defining choices a leader makes is whether to take responsibility for their role in the situation. This choice often happens implicitly rather than explicitly. The leader does not consciously decide whether to acknowledge their contribution; the acknowledgment is either present or absent in how they communicate. And the difference between communication that includes appropriate responsibility-taking and communication that does not is one of the most consequential differences in how bad news lands and what effects it produces over time. Teams notice when leaders take responsibility. They notice when leaders do not. They draw conclusions about what kind of leader they are working with based on these patterns, and those conclusions shape working relationships in ways that persist long after individual communications are forgotten.

There is something specific about taking responsibility that distinguishes it from related concepts that are sometimes confused with it. Taking responsibility is not the same as accepting blame. Blame implies fault, often in a way that locates causation primarily in one person and treats the situation as having a clear villain. Responsibility is broader. It involves acknowledging your role in a situation without requiring that you be the sole or even primary cause. A decision that did not work out involves responsibility from those who made it even when the failure was not entirely their fault. A team outcome involves responsibility from the team leader even when many factors beyond their control contributed. Taking responsibility means acknowledging this role honestly, without either deflecting it or overstating it. It means being clear about what you did, what you decided, what you committed to, and how those choices contributed to the situation you are now communicating about. It does not mean accepting blame for things that were not actually your responsibility.

There is another aspect of taking responsibility that often gets missed. Taking responsibility is not primarily an act of communication; it is an act of leadership that gets expressed through communication. A leader who takes responsibility approaches situations differently from the start. They examine their role honestly. They distinguish what they could have influenced from what they could not. They consider what they would do differently if they could go back, not as self-flagellation but as honest reflection. They prepare to communicate about their role as part of communicating about the situation. By the time they get to the actual communication, the work of taking responsibility has largely already happened internally; the communication is the expression of that internal work. Leaders who try to take responsibility only at the moment of communication, without the prior internal work, often produce something that sounds like responsibility-taking but lacks substance. Recipients usually sense the difference even when they cannot fully articulate it.

There is one more thing about taking responsibility that matters before exploring the practice in detail. The pressures against taking responsibility are substantial and operate continuously. The instinct to protect oneself. The concern about how acknowledgment will affect standing. The fear that taking responsibility will be taken as accepting full blame for situations that had many contributors. The cultural patterns in some organizations that punish responsibility-taking by treating it as evidence of weakness. All of these create pressure to deflect, minimize, or omit responsibility from communication. Working against this pressure requires both understanding why it operates and developing the capacity to take responsibility despite it. The leaders who do this work consistently develop a particular kind of standing that other leaders cannot match: the standing of someone whose acknowledgment of their role can be trusted because it is offered honestly rather than only when circumstances force it.

This article explores taking responsibility in bad news communication. What responsibility-taking actually involves and what distinguishes it from accepting blame, performing humility, or other patterns that sometimes look similar but operate differently. The specific pressures against taking responsibility and how they shape communication when not addressed. What appropriate responsibility-taking looks like in different kinds of bad news situations, including decisions you made, situations you contributed to, and circumstances where your role was limited but not absent. How to distinguish appropriate responsibility-taking from inappropriate over-claiming of responsibility you did not actually have. What responsibility-taking does for recipients and for the working relationship beyond the immediate communication. How to develop the practice as a consistent capacity rather than something you do only when situations make it unavoidable. And how taking responsibility connects to the other practices of bad news communication addressed in this chapter. By the end of this article, you should have a clearer understanding of what taking responsibility actually requires, how to practice it well in different situations, and how to develop the capacity for honest acknowledgment of your role as one of the consistent practices of leaders who communicate bad news well.

Simple Meaning: What Does It Mean to Take Responsibility?

Taking responsibility in bad news communication means honestly acknowledging your role in the situation being communicated, including decisions you made, actions you took, judgments you exercised, commitments you set, or aspects of the situation you could have influenced but did not. It is different from accepting blame, which implies fault and often suggests sole or primary causation. Responsibility is broader and more accurate: it acknowledges your contribution without requiring that you be the only or even main cause of what happened. Taking responsibility means being clear about what you did and did not do, what you decided and did not decide, what you committed to and how those commitments did or did not get fulfilled. It means doing this without either deflecting your actual role or overstating it. And it means doing this even when pressures push toward minimizing your role, because acknowledgment offered honestly produces something that deflection cannot: trust that you can be relied on to be accurate about your own contribution in ways that allow effective working relationships to continue.

Taking responsibility is one of the practices that most distinguishes leaders who communicate bad news well from leaders who do not. It is also one of the most difficult to do consistently because the pressures against it are continuous and substantial. Every leader experiences impulses to protect their role, to frame situations in ways that locate causation elsewhere, to acknowledge contribution only in ways that do not implicate them in difficulty. Working with these impulses requires both understanding why they operate and developing the capacity to take responsibility despite them. Taking responsibility is not the same as accepting blame. This distinction matters significantly because many leaders who would resist accepting blame are willing to take responsibility, and clarifying the difference allows them to do the latter without falling into the former. Blame implies fault and often suggests that the person being blamed is the cause or main cause of what went wrong. Responsibility is acknowledgment of role and contribution without requiring exclusive or primary causation. A decision that did not work out involves responsibility from those who made it even when many factors contributed to it not working out. A team that missed a target involves responsibility from the team leader even when many causes including ones beyond the leader's control led to the miss. Taking responsibility for these situations means acknowledging your role honestly without claiming to be the sole cause. It also means not deflecting from your role by emphasizing only the other contributing factors. The discipline is being accurate about your contribution, neither inflating nor minimizing it. Taking responsibility serves several purposes that other practices cannot serve. It produces trust because recipients see that the leader is willing to acknowledge their role rather than only acknowledge other people's roles. It prevents the leader from appearing to be above the situations they are communicating about, which can create a sense of distance and inauthenticity that damages working relationships. It models accountability that the leader is implicitly asking from others by communicating bad news; if the leader cannot acknowledge their own contribution, why should team members acknowledge theirs? It addresses what recipients often want to know, which is whether the leader will be honest about their own role rather than only honest about other things. And it builds the leader's standing over time as someone whose acknowledgment of contribution can be relied on. Taking responsibility is not the same as performing humility. Performed humility is when leaders make statements that sound like responsibility-taking but lack substance. "I should have done better." "This is on me." "I take full responsibility." These statements, when not connected to specific acknowledgment of what was done and what should have been different, can come across as theatrical and actually undermine trust rather than building it. Genuine responsibility-taking is specific: it names what you did, why you did it, what you would do differently if you could go back, and what you are committing to going forward. The specificity is what makes it genuine rather than performative. The pressures against taking responsibility include self-protection, concern about standing, fear of being held to blame for situations with many contributors, cultural patterns that punish responsibility-taking, and the immediate discomfort of acknowledgment. These pressures operate continuously and require active work to manage rather than just intention to take responsibility. The leaders who manage these pressures successfully and take responsibility consistently develop a particular kind of standing that other leaders cannot match. They become known as people whose acknowledgment of role can be trusted because it is offered honestly rather than extracted by circumstances. This standing accumulates over time into something extremely valuable: the reputation for being a leader whose communication includes the leader rather than only excluding them, whose accountability is real rather than performed, whose engagement with difficulty includes their own contribution rather than only other people's contributions.

Taking responsibility can be understood through four essential dimensions:

The Pressures Against Taking Responsibility

Understanding the pressures against taking responsibility helps explain why it is so often avoided and what work is required to do it consistently.

Self-Protection

The most fundamental pressure is self-protection. Acknowledging your role in difficult situations exposes you to consequences: criticism, reduced standing, loss of trust, possible career implications. The instinct to protect yourself from these consequences is normal and operates continuously. Working with this pressure does not require eliminating the instinct but recognizing it when it is operating and deciding whether to act on it.

Concern About Standing

Closely related is concern about how acknowledging your role will affect your standing with the team, with peers, with senior leadership, and with the broader organization. The fear is that taking responsibility will be seen as evidence of weakness or incapability, leading to reduced standing in ways that affect future opportunities and effectiveness. This concern is sometimes warranted in organizational cultures that genuinely punish responsibility-taking, but it is often overstated. In most contexts, leaders who acknowledge their role with appropriate accuracy gain standing rather than losing it over time.

Fear of Being Held to Inappropriate Blame

Another pressure is the fear that taking responsibility will be interpreted as accepting blame for the entire situation, even when many factors beyond your control contributed. This fear is sometimes warranted in environments where acknowledgment is treated as full blame. Working with this fear involves both distinguishing responsibility from blame in how you communicate and developing the resilience to communicate with appropriate acknowledgment even when others may interpret it as more than you intend.

Cultural Patterns That Punish Acknowledgment

Some organizational cultures explicitly or implicitly punish responsibility-taking, treating leaders who acknowledge contribution to problems as more culpable than leaders who deflect. In these environments, the rational response can seem to be deflection because acknowledgment produces visible costs. But the calculation is more complex than it appears. Even in cultures that punish acknowledgment in some ways, leaders who consistently take responsibility usually build the kind of standing that protects them over time, even when individual instances of acknowledgment produce short-term costs.

The Discomfort of Acknowledgment

Acknowledging your role in difficult situations is uncomfortable in itself, separate from any external consequences. It involves admitting what you would prefer not to have done or not to have decided. It involves examining your judgment in ways that may surface limitations. It involves being seen as the kind of person who makes the mistakes you are acknowledging. All of these are uncomfortable, and the discomfort itself motivates deflection.

The Difficulty of Examining Your Own Role Honestly

Beyond the discomfort of communicating about your role is the difficulty of examining it honestly to begin with. Honest self-examination is hard. Patterns of self-justification operate continuously, often below conscious awareness. What looks to others as your contribution may look to you as primarily external factors. The work of honest self-examination is foundational to taking responsibility because you cannot accurately acknowledge what you have not honestly examined.

The Asymmetry Between Effort and Recognition

There is also an asymmetry that creates pressure against responsibility-taking. When leaders take responsibility for situations that did not go well, the acknowledgment is visible and often costly. When leaders deflect and let situations be attributed to other factors, the deflection is often invisible and goes uncriticized. This asymmetry can make deflection feel like the rational choice in the moment, even when it produces worse outcomes over time.

Patterns of Avoidance Above

When senior leadership in an organization models avoidance of responsibility, the pattern propagates downward. Leaders learn that responsibility is not what is rewarded or even expected. They adapt by also avoiding it. Working against these patterns requires recognizing them and deliberately choosing different patterns even when the surrounding context suggests they are not necessary.

What Appropriate Responsibility-Taking Looks Like

Recognizing what appropriate responsibility-taking actually involves in different situations helps you practice it well rather than performing something that looks like it.

When You Made the Decision

When the decision being communicated was made by you, appropriate responsibility-taking involves being clear about your decision-making. "I decided to prioritize this approach." "The choice to commit to this timeline was mine." "I made this call based on the information I had at the time." This is not difficult in principle but is often avoided through framings that locate causation elsewhere even when the decision was actually yours. Acknowledging your decisions clearly is foundational responsibility-taking.

When You Were Part of Making the Decision

When the decision was made through collective processes you were part of, appropriate responsibility-taking involves acknowledging your role in those processes. "I was part of the conversations that led to this decision." "I supported this direction at the time it was being decided." "I had reservations but did not push back as strongly as I now think I should have." These acknowledgments take responsibility for your contribution to collective decisions without claiming to have been the sole decision-maker when you were not.

When You Supported the Decision Even Though You Disagreed

Sometimes you disagreed with a decision but supported it once made. Appropriate responsibility-taking involves acknowledging both elements. "I had concerns about this direction but agreed to support it as a leader of this team." "I disagreed with parts of this but went along with the overall decision." This kind of acknowledgment is more honest than either pretending you fully supported the decision or distancing yourself from it entirely.

When Your Action or Inaction Contributed

When your specific actions or inactions contributed to the situation, appropriate responsibility-taking involves naming them. "I should have raised this concern earlier." "My decision not to allocate resources here contributed to where we are." "I delayed addressing this and that delay made things worse." These specific acknowledgments are more meaningful than general statements of responsibility because they identify what specifically you did or did not do.

When Your Judgment Was Wrong

When your judgment turned out to be wrong, appropriate responsibility-taking involves acknowledging the judgment and what you now think. "I judged that this approach would work, and looking back, that judgment was wrong." "My read of the situation turned out to be incorrect." "I underestimated how much this would matter." These acknowledgments are not exercises in self-criticism but honest engagement with what your judgment was and how it has been validated or not.

When Your Role Was Limited but Not Absent

Sometimes your role was limited but not absent. You did not decide the matter but had some influence on it. You were not the primary actor but contributed in some way. Appropriate responsibility-taking acknowledges the limited role accurately. "I was not part of making this decision, but I did influence the conversation in these ways." "My role here was secondary, but I did contribute." This is more honest than either claiming no role or claiming a larger role than you actually had.

When You Are Communicating a Decision Made Elsewhere

When you are communicating a decision that was made entirely elsewhere, your responsibility shifts. You may not be responsible for the decision itself, but you are responsible for how you communicate it. "I was not part of making this decision, but I am part of how it gets communicated, and I am committed to making sure the communication is honest about what is happening." This kind of acknowledgment maintains accuracy about your role while taking responsibility for what is actually yours.

When Acknowledgment Involves Multiple Levels

Many situations involve multiple levels of responsibility to acknowledge. Your role in specific decisions. Your role in shaping the conditions in which decisions were made. Your role in not catching problems earlier. Your role in how things were communicated. Your role in how the situation is being addressed now. Appropriate responsibility-taking often involves acknowledging multiple levels rather than only the most obvious one.

Common Patterns of Failed Responsibility-Taking

Several patterns that look like responsibility-taking but actually fail at it deserve specific attention because they are common and often unrecognized as failures.

The Generic Statement

One pattern is generic statements that sound like responsibility-taking but lack specificity. "I take responsibility for this." "This is on me." "I own this." Without specifics about what you actually did and what you would do differently, these statements often come across as performative rather than genuine. Specificity is what makes acknowledgment real.

The Conditional Acknowledgment

Another pattern is acknowledgment with conditions that essentially negate it. "I take responsibility, although the circumstances were unusual." "I should have done better, but given the information I had, this was reasonable." "I made the call, but everyone agreed at the time." The conditions in these statements often undermine the acknowledgment, leaving recipients with the sense that the responsibility being taken is being simultaneously deflected.

The Acknowledgment That Shifts to Others

Another pattern is acknowledgment that quickly shifts attention to others' contributions. "I made this decision, but the situation we were in made it very difficult." "I should have addressed this earlier, but I was getting conflicting signals from senior leadership." "This is on me, although many people contributed to the conditions." The shifts in these statements often dilute the acknowledgment, leaving recipients with the impression that the leader is acknowledging their role primarily as a setup for talking about other contributions.

The Theatrical Acknowledgment

Another pattern is theatrical acknowledgment that emphasizes the emotion of taking responsibility without substantive content. "I am deeply sorry that this happened." "I feel terrible about this." "This has been very difficult for me." These statements may be sincere expressions of feeling, but they substitute emotional display for substantive acknowledgment of what was actually done. Recipients often want to know what happened and what would be different, not primarily how the leader feels about it.

The Acknowledgment That Defers to System

Another pattern is acknowledgment that locates causation primarily in systems rather than in personal choice. "The processes we had in place did not catch this." "The information flows in our organization made this hard to see." "The decision-making structure contributed to where we are." These observations may be accurate and worth making, but they should not substitute for acknowledgment of personal role. When systems shape outcomes, leaders still have responsibility for their choices within those systems.

The Belated Acknowledgment

Another pattern is acknowledgment that comes only when circumstances force it. The leader did not acknowledge their role when communication first occurred but does so later when pressure mounts. This belated acknowledgment can be useful but lacks the credibility of acknowledgment offered when not required. Building the practice of acknowledging your role from the start, rather than only when circumstances force it, is part of genuine responsibility-taking.

The Acknowledgment That Avoids Specifics

Another pattern is acknowledgment that uses general language to avoid specifics that would be more pointed. "Mistakes were made." "Things did not go as planned." "There were some issues." These passive or generalized constructions avoid the specifics of who did what. They sound like acknowledgment but actually obscure the role that more specific language would identify.

The Acknowledgment Followed by Defensiveness

Another pattern is acknowledgment that is immediately followed by defensiveness when others engage with what was acknowledged. The leader acknowledges their role in opening communication but then defends, explains, or pushes back when team members raise the role in subsequent conversation. This pattern undermines the initial acknowledgment by demonstrating that the leader is not actually willing to engage with their role beyond the initial statement.

What Taking Responsibility Does

Understanding what taking responsibility actually does helps motivate the practice when pressures against it are operating.

It Produces Trust

When recipients see that you are willing to acknowledge your role honestly, trust develops in your overall communication. They sense that if you are honest about your contribution, you are probably also honest about other things. This trust extends beyond the specific communication to the broader working relationship.

It Models Accountability

Communicating bad news often implicitly asks team members to be accountable for what comes next, for adjustments they need to make, for their reactions and adaptations. When you take responsibility for your role, you model the accountability you are implicitly asking from others. When you do not, you ask for accountability without modeling it, which is often noticed and resented.

It Prevents the Appearance of Being Above the Situation

Leaders who communicate bad news without acknowledging their role can appear to be above the situations they are communicating about. They communicate as observers of difficulty rather than as participants in it. This appearance creates distance from the team and the situation that can undermine effectiveness. Taking responsibility prevents this distance by demonstrating that you are part of what is being addressed.

It Addresses What Recipients Often Want to Know

When recipients receive bad news, one of the things they often want to know is what role the leader had. Was this something the leader contributed to or something that happened to the leader? Did the leader see it coming? Could the leader have done something different? Honest acknowledgment of your role addresses these questions directly, while deflection leaves them open and often produces speculation that is unfavorable to the leader.

It Allows the Situation to Be Addressed Honestly

When responsibility is not acknowledged, conversations about what to do next operate in a kind of pretense that the leader's role does not need to be considered. This pretense distorts subsequent conversations. Taking responsibility allows what comes next to be addressed honestly, including the leader's role in addressing it.

It Builds Standing Over Time

Over many situations, leaders who take responsibility consistently build the kind of standing that other leaders cannot match. They become known as people whose acknowledgment can be trusted because it is offered honestly rather than extracted by circumstances. This standing accumulates into a reputation that is one of the most valuable assets a leader can have.

It Makes Other Practices More Effective

Taking responsibility makes other practices in bad news communication more effective. Accuracy is more credible when the leader is honest about their own role. Care is more believable when the leader includes themselves in what is being addressed. Commitments to future action are more trusted when the leader has acknowledged their role in the situation that produced the need for action. Taking responsibility is foundational to other practices working as intended.

It Demonstrates Capacity for Honest Self-Examination

Taking responsibility demonstrates that you have the capacity for honest self-examination, which is itself reassuring to team members. They want to work with leaders who can examine their own role honestly rather than leaders who can only see externally located causes. The demonstration of this capacity supports working relationships in many ways beyond the immediate communication.

How to Avoid Inappropriate Over-Claiming

Just as important as avoiding deflection of responsibility is avoiding inappropriate over-claiming of responsibility you did not actually have.

Why Over-Claiming Is Also a Problem

Over-claiming responsibility for situations that were not actually your responsibility creates its own problems. It can come across as performative humility rather than honest acknowledgment. It can obscure actual causation, which makes it harder to address the situation effectively. It can be unfair to others whose actual responsibility is being obscured by your over-claiming. And it can compromise accuracy, which is the foundation that other practices depend on.

Distinguishing What Was Yours From What Was Not

Practicing responsibility-taking well requires distinguishing what was actually yours from what was not. What did you decide? What did others decide? What did you influence? What was beyond your influence? What did you know and when? What was outside your knowledge? This distinction work is part of preparing to communicate honestly about your role.

Acknowledging Limited Role When the Role Was Limited

When your role was genuinely limited, acknowledge that honestly rather than claiming more responsibility than you had. "I was not part of making this decision, though I did communicate it." "My influence on this situation was limited; the main factors were beyond my control." These honest acknowledgments of limited role are more accurate than over-claiming.

Not Claiming Responsibility to Appear Humble

Some leaders claim responsibility they did not actually have because doing so appears humble or because it deflects attention from others whose role was more central. This pattern is well-intentioned but produces inaccuracy. Genuine humility involves accurate acknowledgment of role, not inflation of role to appear humble.

Not Shielding Others Inappropriately

Sometimes leaders over-claim responsibility to shield others from acknowledgment that should rightly be theirs. This protective impulse is sometimes appropriate but often is not. When others' responsibility is being obscured by your over-claiming, the obscuring can interfere with addressing the situation effectively and can be unfair to those whose contribution is now being attributed elsewhere.

Being Specific About Your Actual Role

The discipline that prevents both deflection and over-claiming is being specific about your actual role. Specifics make it harder to claim too little or too much. They require you to articulate exactly what you did, what you decided, what you influenced. This specificity supports accuracy in both directions.

How to Develop the Practice

Developing the practice of taking responsibility involves both internal work and consistent application over time.

Practice Honest Self-Examination

The internal work begins with practice in honest self-examination. When situations arise, examine your role honestly, before any need to communicate about it. What did you decide? What did you do? What did you know? What could you have done differently? This examination, practiced regularly, develops the capacity to acknowledge your role when communication is required because the acknowledgment is already grounded in honest self-knowledge.

Notice Self-Justification Patterns

Notice the patterns of self-justification that operate in your thinking. Most people have patterns where causation is located primarily outside themselves, where their role is framed as reasonable given circumstances, where contributions to problems are minimized. Noticing these patterns when they are operating allows you to question whether they are accurate or whether they are protecting your sense of yourself.

Practice Acknowledgment Without External Pressure

Practice acknowledging your role in lower-stakes situations where external pressure to do so is minimal. Each acknowledgment, even of small contributions, develops the capacity for larger acknowledgment when more is required. Leaders who practice acknowledgment only when forced to find it harder when situations require it than leaders who practice consistently.

Build the Specificity Discipline

Build the discipline of being specific when acknowledging your role. What exactly did you decide? What exactly did you do? What exactly would you do differently? The specificity is what distinguishes genuine acknowledgment from performative statements, and developing it requires deliberate practice.

Examine Past Communications

Look at past communications where you communicated bad news. Where did you take responsibility appropriately? Where did you deflect? Where did you over-claim? What patterns can you see in your own communication of your role? This retrospective examination develops awareness of patterns that operate in real-time.

Seek Feedback on How Your Role Comes Across

Seek feedback from people you trust about how your role comes across in your communications. Do you acknowledge your contributions honestly? Do you deflect more than you realize? Do you over-claim? Feedback from others can surface patterns you cannot see in yourself.

Work With Discomfort Rather Than Around It

Develop the practice of working with the discomfort of acknowledgment rather than around it. The discomfort is real and does not disappear with practice. But the capacity to act despite discomfort develops over time, and acting consistently despite discomfort is what makes the practice reliable.

Build the Practice Over Time

Build the practice over time through consistent attention. Each situation is an opportunity. Each communication is a chance to practice. Each reflection is an opportunity to develop further. Over many situations, the practice becomes more natural, though the underlying pressures against it continue to operate and require ongoing management.

Practical Workplace Scenario

Scenario

A team lead named Vinay had decided six months earlier to allocate the majority of his team's resources to a specific project he believed had strategic importance. Other work had been deferred or de-resourced to make this possible. Now, six months in, the project was clearly not working out as he had hoped. The strategic conditions he had been counting on had changed. The technical approach was proving more difficult than anticipated. The deferred work was now needed urgently. Vinay needed to communicate to his team that the project was being scaled back significantly and that resources would be reallocated to other priorities.

How He Thought About His Role

Vinay spent some time examining his own role honestly before drafting his communication. The decision to prioritize this project had been his. He had made it based on his read of strategic conditions and his judgment about the technical approach. Some senior leaders had raised concerns at the time, but he had argued for the prioritization and they had agreed to let him proceed. He had monitored the project as it developed and had been slower than he should have been to recognize signals that it was not working out. By the time he was now communicating, several months had been lost to a direction that had not produced what he had committed to.

Examining his role honestly was uncomfortable. He noticed impulses to frame the situation in ways that located more causation in external factors: the changing strategic conditions, the technical difficulty, the team members who had not surfaced concerns more strongly. He noticed impulses to minimize his judgment by emphasizing that others had agreed with him. He noticed impulses to soften his role through general statements about how decisions had been made collectively. Each of these would have made the communication easier to deliver but would have compromised accuracy about his role.

How He Communicated

Vinay communicated to his team and took responsibility specifically. He explained the situation: the project was being scaled back, resources would be reallocated, the deferred work would be addressed. He acknowledged his role specifically. "I made the decision six months ago to prioritize this project. I based that decision on my read of strategic conditions and my judgment about the technical approach. Both of those have not worked out as I expected. I should have been quicker to recognize the signals that this was not going as planned, and I want to acknowledge that the delay in addressing this is on me."

He continued: "Some of you raised concerns at various points that I weighed but ultimately did not act on as I now think I should have. I want to acknowledge that as well. And I want to be honest that the decisions about reallocation that we are now making are partly addressing situations I created through my earlier decisions. I am not trying to make this seem like it just happened. It happened because of choices I made, and I am responsible for those choices."

He talked about what he was committing to going forward: making different decisions about when to escalate concerns about projects he had led, building in more regular check-ins on judgment calls like this, being more responsive to signals from the team about project health. He invited questions and was prepared to engage with whatever team members wanted to raise.

How the Team Responded

The team responded better than Vinay had expected. Some team members were frustrated, particularly those whose work had been deferred and was now being prioritized after months of delay. Some had questions about specific decisions and the reasoning behind them. Some had concerns about how to manage the transition. But the overall tone was different from what it would have been if Vinay had communicated in ways that deflected his role. Team members engaged with what came next rather than spending energy on whether they were getting the full picture. One team member said afterward: "It was hard to hear that we are pivoting, but I appreciated that you were direct about your role. We can work with that. What is much harder is when leaders make decisions and then act like the consequences just happened."

What He Reflected On Afterward

Vinay reflected on the communication after it was done. Taking responsibility had been uncomfortable. The specific acknowledgments had been harder to deliver than more general statements would have been. The willingness to be vulnerable about his judgment had felt risky. But all of these were part of what made the communication land as honest engagement with the situation rather than as performance. And the team's response confirmed that the honesty was received as honesty, even when the content was difficult. Vinay noticed that he felt different about his own standing afterward than he had expected. He had worried that taking responsibility would reduce his standing. Instead, it seemed to have strengthened it. The team's trust in him appeared to be greater after the communication than before.

Learning

Vinay's experience illustrates that taking responsibility, while uncomfortable in the moment, often produces outcomes that deflection would not produce. The specific acknowledgments demonstrated honest engagement. The willingness to name his judgment and its limits demonstrated capacity for self-examination. The combination produced communication that the team could trust and could work with, even when the content was difficult. The fear that taking responsibility would damage his standing turned out to be largely unfounded; the actual effect was strengthening rather than weakening. This pattern, of fears about responsibility-taking being more substantial than the actual costs, is common, and recognizing it is part of developing the practice.

Take Responsibility Checklist

Self-Reflection Questions

Use these questions to examine your own practice of taking responsibility.

1. Looking at recent bad news communications I have delivered, how well did I acknowledge my own role?
2. What patterns of deflection do I notice in my own communication?
3. What pressures against taking responsibility operate most strongly in me?
4. When have I noticed myself making generic statements that sounded like responsibility-taking but lacked specifics?
5. How honestly do I examine my own role before communicating about difficult situations?
6. What self-justification patterns do I notice in my thinking about my contributions?
7. How do I tend to handle the discomfort of acknowledging my role in difficult situations?
8. What were the actual consequences when I have taken responsibility in the past? How did they compare to my fears?
9. How do I tend to handle situations where my role was real but limited?
10. If I imagined a year of deliberate practice in taking responsibility, what might change in how I communicate bad news?

Key Takeaways

• Taking responsibility in bad news communication means honestly acknowledging your role in the situation, including decisions you made, actions you took, judgments you exercised, and aspects you could have influenced.
• Taking responsibility is different from accepting blame. Responsibility involves role-acknowledgment without requiring sole or primary causation. Blame implies fault. Distinguishing these matters because many leaders willing to take responsibility resist accepting blame.
• Taking responsibility has four essential dimensions: honest acknowledgment of role, accuracy without inflation or minimization, specificity rather than performative statements, and willingness to acknowledge despite pressures against it.
• The pressures against taking responsibility include self-protection, concern about standing, fear of inappropriate blame, cultural patterns that punish acknowledgment, discomfort of acknowledgment, difficulty of honest self-examination, asymmetry between effort and recognition, and patterns of avoidance above.
• Appropriate responsibility-taking looks different in different situations: when you made the decision, when you were part of making it, when you supported decisions you disagreed with, when your action or inaction contributed, when your judgment was wrong, when your role was limited but not absent, when you are communicating decisions made elsewhere, and when acknowledgment involves multiple levels.
• Common patterns of failed responsibility-taking include generic statements, conditional acknowledgment that negates itself, acknowledgment that shifts to others, theatrical acknowledgment focused on emotion, deferral to systems, belated acknowledgment forced by circumstances, vague language that obscures role, and acknowledgment followed by defensiveness.
• Taking responsibility produces trust, models accountability, prevents the appearance of being above the situation, addresses what recipients want to know, allows the situation to be addressed honestly, builds standing over time, makes other practices more effective, and demonstrates capacity for honest self-examination.
• Avoiding inappropriate over-claiming of responsibility is as important as avoiding deflection. Over-claiming can come across as performative, obscure actual causation, be unfair to others, and compromise accuracy.
• The discipline that prevents both deflection and over-claiming is being specific about your actual role. Specifics make it harder to claim too little or too much.
• Developing the practice involves honest self-examination, noticing self-justification patterns, practicing acknowledgment without external pressure, building specificity discipline, examining past communications, seeking feedback, working with discomfort, and building the practice over time.
• Taking responsibility, while uncomfortable in the moment, often produces outcomes that deflection would not produce. Fears about responsibility-taking are often more substantial than the actual costs. The practice usually strengthens rather than weakens standing over time.
• This article addresses one of the practices that most distinguishes leaders who communicate bad news well. Subsequent articles will address listening and answering questions, saying what will happen next, and following through on commitments. Each becomes more effective when taking responsibility is established as a reliable practice.

Conclusion

Taking responsibility is one of the practices that most distinguishes leaders who communicate bad news well from leaders who do not. It is also one of the most difficult to do consistently because the pressures against it operate continuously. Every leader experiences impulses toward deflection, self-protection, and framing that locates causation away from themselves. Working with these impulses requires both understanding why they operate and developing the capacity to take responsibility despite them. The leaders who do this work consistently develop something other leaders cannot easily replicate: the standing of someone whose acknowledgment of role can be trusted because it is offered honestly rather than only when circumstances force it.

A leader who has developed strong capacity for taking responsibility brings something specific to bad news communication. They examine their role honestly before communicating, working through their own contribution to what is being communicated. They acknowledge that role specifically, including what they decided, what they did, what they would do differently. They distinguish their actual responsibility from both deflection and over-claiming, being accurate about what was theirs and what was not. They avoid the patterns of failed responsibility-taking that produce communication sounding like acknowledgment but lacking substance. They take responsibility despite the pressures against it, which gives their acknowledgment a credibility that easier acknowledgment cannot match. And they continue developing the capacity through consistent practice across many situations, with each acknowledgment building both their skill and their standing.

The most important lesson of this article is this: Taking responsibility is an act of leadership that expresses through communication, not just a communication technique. The leaders who take responsibility well have done the internal work of examining their role honestly before they communicate. The communication is the expression of that internal work, not a substitute for it. Leaders who try to take responsibility only at the moment of communication, without the prior internal work, often produce something that sounds like responsibility but lacks substance. Distinguish responsibility from blame. Responsibility acknowledges role; blame implies fault. You can take responsibility for your contribution to a situation without claiming to be the sole or primary cause. This distinction matters because it allows acknowledgment that would otherwise be resisted out of concern that taking responsibility means accepting blame for everything. Practice specific acknowledgment. Generic statements about responsibility, however well-intentioned, often come across as performative. Genuine acknowledgment names what you specifically did, what you specifically decided, what you would specifically do differently. The specificity is what makes the acknowledgment real. Recognize the pressures against taking responsibility. Self-protection. Concern about standing. Fear of inappropriate blame. Cultural patterns. Discomfort itself. These operate continuously and below conscious awareness. Naming them when they arise allows you to choose whether to act on them rather than being moved by them automatically. Avoid both deflection and over-claiming. Deflection compromises accuracy by understating your role. Over-claiming compromises accuracy by overstating it. Both fail to serve the recipients of communication and both damage your standing over time. The discipline that prevents both is specificity about your actual role. Take responsibility appropriately in different kinds of situations. When you made the decision. When you were part of making it. When you supported decisions you disagreed with. When your action or inaction contributed. When your judgment was wrong. When your role was limited but not absent. When you are communicating decisions made elsewhere. Each calls for different specifics of what your role actually was. Recognize what taking responsibility produces. Trust. Modeling of accountability. Prevention of distance from the situation. Addressing of what recipients want to know. Honest engagement with what comes next. Building of standing over time. Effectiveness of other communication practices. Demonstration of capacity for honest self-examination. These outcomes accumulate over many situations into something extremely valuable. Build the practice through consistent attention. Practice honest self-examination regularly. Notice self-justification patterns when they operate. Practice acknowledgment in lower-stakes situations. Build the specificity discipline. Examine past communications. Seek feedback. Work with discomfort rather than around it. Each situation is an opportunity to develop. Recognize that the fears about responsibility-taking are usually larger than the actual costs. Most leaders who take responsibility appropriately find that their standing strengthens rather than weakens over time. Teams trust them more. Peers respect them more. Senior leadership values them more. The costs that fears anticipate often do not materialize, while the benefits of consistent practice accumulate. Develop the practice across the long arc of your career. Each instance of taking responsibility builds capacity for the next. Each acknowledgment adds to your standing as a leader whose acknowledgment can be trusted. Over many years, this practice becomes one of the defining qualities of how you communicate bad news, the foundation on which other practices can rest effectively. Begin from where you are. Notice patterns in your own communication. Recognize where you have deflected and where you have taken responsibility. Practice deliberate examination of your role before communicating. Build the discipline over many situations. Develop the capacity over time. And let taking responsibility become one of the consistent strengths you offer the teams you lead, communication by communication, year by year, across the long arc of your career as a leader whose acknowledgment of role can be trusted because it is offered honestly rather than only when circumstances force it. This is the work. It is uncomfortable. It is essential. Engage with it directly, and let the capacity you develop become foundational to your broader practice of communicating bad news well. Subsequent articles will address other practices that build on this foundation. Each becomes more effective when taking responsibility is established as a reliable pattern. Each becomes problematic when responsibility is consistently deflected. Begin here. Build well. And let your willingness to take responsibility become one of the practices that distinguishes you as a leader who can be trusted with difficult communication, the kind of leader teams want to work with through the inevitable difficulties that real work and real organizations produce.