The Leader's Compass: Cultivating Responsibility and Ethical Awareness
Responsible leadership means owning your share of outcomes, keeping commitments and holding others to account without hunting for culprits. It is built through language, blame-free reviews and a team climate where mistakes can be raised.
8 min readUpdated on

Building a sense of responsibility as a leader means recognizing your own share in your team's results, keeping your commitments and holding others to account without hunting for someone to blame. It rests on first-person language, blame-free reviews and a climate in which people can report a mistake without fear.
Responsibility is often reduced to answering for results. It goes further: it is a stance, the way a leader connects their decisions to what those decisions do to the team, the project and the organization. During a transformation, when reference points shift and setbacks pile up, that stance shapes how the team talks about what is not working.
Responsibility vs accountability: what is the difference for a leader?
For a leader, a sense of responsibility is the ability to recognize and own the consequences of their choices, actions and words. It does not mean carrying the weight of everything alone; it means understanding your role in a wider system. Accountability is the other side of the coin: the obligation to answer to someone for a specific commitment. You can be accountable without feeling responsible, delivering what is asked without owning the outcome. Our article on responsibility versus accountability in leadership explores the distinction.
In practice, a responsible leader facing a failure does not start by asking who got it wrong. They look at their own contribution first: were the instructions clear? Were the resources adequate? Could the team raise a problem in time? The question shifts from "who is at fault?" to "what made this failure possible, and which part of it is mine?"
This stance does not stifle initiative. When a leader visibly owns their mistakes, it becomes safer for others to make a call and stand by it. That is the link between responsibility and personal initiative: one makes the other less risky.
Why do so many executives avoid holding people accountable?
Owning your share does not exempt you from asking others to own theirs, and this is where many leaders back off. Writing in Harvard Business Review (Darren Overfield and Rob Kaiser, 2012), two leadership consultants call accountability the single most shirked responsibility of executives: even leaders who talk tough about performance step back when the conversation gets uncomfortable.
That retreat carries a quiet cost. When a missed commitment is never discussed, the team learns that commitments are negotiable, and those who keep theirs end up carrying everyone else. On the other hand, accountability experienced as punishment teaches people to hide problems. A sense of responsibility means holding both ends: naming the gap plainly, and examining it without humiliating anyone.
How a leader's responsibility makes mistakes discussable
Team research sheds light on this mechanism. In a 1999 paper in Administrative Science Quarterly, Amy Edmondson (Harvard) defines psychological safety as a belief shared by team members that the team is safe for interpersonal risk taking. Her study covered 51 work teams in a manufacturing company. Psychological safety was associated with learning behavior, and learning behavior in turn linked safety to team performance. She concludes that team structures, including contextual support and coaching by the team leader, shape outcomes alongside shared beliefs.
For a leader, the implication is immediate: how you react to the first mistake someone reports sets the rule for every one after it. Look for a culprit, and the next mistakes surface later, or not at all. Start by acknowledging your own part, and reporting becomes less costly. This is also what strategic humility is about: admitting what you do not know without losing authority.
Some organizations have written this principle down. The engineering handbook of Google (Site Reliability Engineering) describes the blameless postmortem: a written review expected after any significant undesirable event, which identifies contributing causes without indicting any individual or team, and assumes everyone acted with good intentions on the information they had. As the book puts it, you cannot fix people, but you can fix systems and processes.
Five everyday practices that build a sense of responsibility
Responsibility grows through observable behavior, not through a general resolution. Here are five practices you can put in place, on your own or with support.
- Define what responsibility means to you. Leading by example, keeping your word, protecting the team, raising issues early: your own definition becomes a reference point when a decision is hard.
- Speak in the first person. Replace "the team missed the deadline" with "I did not check progress often enough to see the delay coming" or "I never said this deadline came before the others." The rewording does not deny outside causes; it brings into view what is still within your reach.
- Make commitments explicit. Who does what, by when, and how success will be judged. You can only hold someone to account for a commitment both sides understood the same way.
- Set up a non-punitive review ritual. A regular slot where everyone, the leader included, presents one decision, its effect and what they take from it. The principle is the blameless postmortem: look for causes in the situation, not in the person.
- Follow the review with real change. Amy Edmondson (Harvard Business Review, 2011) notes that teams running after-action reviews and postmortems often drew little real change from them, because managers were thinking about failure the wrong way. A review that changes nothing discourages the people who took the risk of speaking up.
During a transformation, these practices are best put in place before the first difficulties arrive. Our article on leadership and change management looks more broadly at managerial posture in those periods.
What leadership coaching can work on, and what it does not do
A coach does not make you responsible; they help you look at how you exercise responsibility. The core competencies of the International Coaching Federation (ICF) put this work at the center of the profession: helping clients take ownership of their development by encouraging them to set clear goals and commit to specific actions, then supporting them in turning insights into action steps, with respect for their autonomy.
In practice, sessions often start from real situations: a recent failure reread through the lens of your own contribution, an accountability conversation to prepare, a team ritual to design. The coach asks questions, reflects back and returns to the commitments you made from one session to the next. They do not decide for you and do not promise outcomes. A difficulty that is a health matter, such as exhaustion or persistent anxiety, calls for a health professional, not a coach.
To find support, you can browse leadership coaches, or executive coaches if you run an organization. If the issue concerns a whole team, the leadership and team management page describes that kind of engagement. Our article on becoming a leader coach explains how a manager can bring some of these practices to their own team.
Frequently asked questions
What is the difference between responsibility and accountability?
Responsibility is a stance: recognizing your share in what happens and acting on it, even when nobody asks. Accountability is an obligation: answering to someone for a specific commitment. A leader needs both, owning their part and asking others to answer for theirs, without confusing the review of a gap with a sanction.
Does taking responsibility mean covering for my team's mistakes?
No. Owning your share means examining what depended on you: how clear the instructions were, what resources you provided, whether people could flag a problem. It does not erase anyone else's part. A responsible leader acknowledges theirs first, which makes it easier for others to acknowledge theirs, without the discussion turning into a trial.
How can I hold people accountable without creating a climate of fear?
Start from an explicit commitment, describe the gap in facts, then look together for causes in the situation before talking about people. That is the blameless postmortem principle described by Google. Opening with your own contribution shows the exercise is not about naming a culprit; ending with a concrete decision shows it serves a purpose.
Can a sense of responsibility be developed as an adult?
Yes, because much of it rests on habits: how you frame a problem, make a commitment or react to a mistake. Those habits change through practice, self-observation and feedback from others. Coaching provides a structure for that work without guaranteeing results: what changes depends on what you put into practice between sessions.
Sources
- Edmondson, A. (1999), Psychological Safety and Learning Behavior in Work Teams, Administrative Science Quarterly
- Edmondson, A. (2011), Strategies for Learning from Failure, Harvard Business Review
- Overfield, D. and Kaiser, R. (2012), One Out of Every Two Managers Is Terrible at Accountability, Harvard Business Review
- Google, Site Reliability Engineering, Postmortem Culture: Learning from Failure
- International Coaching Federation, Core Competencies
Sources
Ready to take action?
Find the coach who matches your goal
Hand-picked certified coaches. Free first discovery session, no commitment.


