The Oz Principle: The Accountability Ladder Explained

By Tara Minh · Updated Oct 10, 2026

The Oz Principle is an accountability model from Roger Connors, Tom Smith and Craig Hickman. It draws a line through workplace behavior. Below the line, people blame, wait and protect themselves. Above it, they follow four steps: See It, Own It, Solve It, Do It. The goal is to move from explaining why results didn't happen to making them happen.

The book first came out in 1994, and the model has outlasted most management fads of that decade. People often call it the "accountability ladder" because it asks a simple question about any stuck situation: which rung am I on right now? This article covers the line itself, the six below-the-line habits, the four steps up, how to use the model with a team, and where it sits next to similar frameworks.

What is the Oz Principle?

The title borrows from The Wizard of Oz. In the story, the Scarecrow, Tin Man and Lion each wait for the Wizard to hand them brains, a heart and courage, and each already has what they need. The book uses that story to argue that most people have the power to affect results and spend too much energy looking for someone else to supply it.

Roger Connors, Tom Smith and Craig Hickman published the book in 1994. The consulting firm they built around it, Partners In Leadership (now Culture Partners), says the book has sold more than a half-million copies and is the basis of its Accountability Workshop.

The model has two parts:

• The line. A dividing line between two ways of responding to a missed result.
• The Steps to Accountability. Four moves that sit above the line.

One definition is worth holding onto because it changes how you use the word. Culture Partners separates accountability from responsibility. Responsibility covers defined duties and roles, while accountability is described as a proactive, forward-facing process of using your own agency to reach a goal. You can be responsible for a task and still be below the line about its result.

The line: Above vs Below

Culture Partners describes the line like this. Below the Line is where people avoid accountability, focus on things they can't control, play the blame game, and react instead of act. Above the Line is where they focus on what they can control, work proactively and treat the need for change as their own.

Partners In Leadership's own white paper adds a useful test. Below the Line, people tell a story about why they can't deliver, and Above the Line they tell a story about what they did to overcome the obstacles. The same paper points out that the line applies to individuals and to whole organizations, and that it's relative to a specific result. A team can be above the line on a product launch and below it on a late invoice.

Two points keep the model honest:

1. Going below the line is normal. Everyone does it under pressure. The skill is noticing it and climbing back quickly.
2. The line is about a result, not a person. Nobody lives permanently on one side. You're above it on one goal and below it on another, sometimes in the same hour.

The six-stage victim cycle (below the line)

The book calls the below-the-line behaviors the victim cycle. Partners In Leadership's white paper lists six habits, each with the phrases you'd hear in a meeting. These are the originator's own examples, lightly trimmed.

Look at the pattern. Every phrase is reasonable on its face, which is why the cycle survives. Nobody says "I refuse to be accountable." They say they're waiting on a decision, or that they sent a warning, or that the instructions weren't clear. The white paper notes that these habits can become so accepted in a culture that people stop noticing how pervasive they are.

The cost is energy. The paper's argument is that time spent explaining and justifying why a result didn't happen is time not spent producing it.

The four Steps to Accountability (above the line)

Climbing out takes four moves, in order. Culture Partners' description of each step is a good starting point.

1. See It. Acknowledge that something needs to change and look honestly at the causes. That includes asking others for candid feedback about what you can't see yourself. This is the step most skipped, because it's uncomfortable. It's also the direct counter to Ignore/Deny.

2. Own It. Take ownership of your contribution to the result instead of looking for someone to blame. Culture Partners adds that you should expect setbacks and keep the goal in view, and that everyone shares accountability for the result.

3. Solve It. Build a plan by asking "What else can we do?" The point is to think differently, not just work harder. A team stuck below the line usually asks "Why didn't this work?" and gets a list of excuses. The Solve It question gets a list of options.

4. Do It. Execute and follow through. Hold each other accountable with honesty and transparency, without blame. A plan nobody is accountable for becomes a Wait and See.

The steps are a sequence for a reason. If you jump to Do It without See It, you'll execute a plan for the wrong problem. If you stop at Own It, you'll have a team that feels guilty and accomplishes nothing.

How to apply the Oz Principle with your team

You don't need a workshop to use the idea. A team can run it on one stuck result in about an hour.

1. Pick one specific result. Not "improve communication." Something like "ship the Q4 pricing page by November 15." The line is relative to a result, so you need one on the table.
2. Define the result clearly first. The white paper says nine out of ten companies have either not clearly defined results or failed to communicate them broadly. If people can't state the result in a sentence, they can't be accountable for it. Fix that before anything else.
3. Name where you are. Ask each person to say which of the six habits they've been tempted by on this result. Leaders go first. If the leader admits to a bit of Cover Your Tail, others follow. If not, you'll get silence.
4. Walk the four steps out loud. See It: what's the current reality? Own It: what's my part in it? Solve It: what else could we do? Do It: who does what by when?
5. Set a check-in date. Accountability without a date is a wish. Put the review on the calendar before the meeting ends.
6. Notice the slide. When someone says "I was waiting for approval," treat it as data, not a failure. Ask what they could have done in the meantime.

Psychological safety decides whether step 3 works at all. If people expect punishment for admitting a miss, they'll stay below the line to protect themselves. See psychological safety for how teams build the conditions where "I own this" is safe to say.

Accountability steps template

Copy this into a doc or a team wiki and fill it in for one result at a time.

Keep it to one page. If the "Own It" box only lists what other people did, you're still below the line.

Examples by business function

These are illustrations of how the six habits and four steps look in common roles. They aren't case studies.

Notice that the above-the-line version is rarely heroic. It's usually one extra question or one phone call.

Oz Principle vs similar frameworks

The model overlaps with several others on ownership and responsibility. The differences are in the scope.

In practice they combine well. Use goal setting to define the result, the Oz Principle to examine how people respond when it slips, and a feedback model to have the conversation.

What the research says (and what it doesn't)

Culture Partners publishes a Workplace Accountability Study that supports the idea that accountability is rare in practice. The study covers more than 40,000 participants, with data collected from April 2011 to June 2014 through live online polls during webinars. Among its findings:

• 85% said they were not sure what their organization is trying to achieve.
• 93% said they were unable to align their work or take accountability for desired results.
• 84% named leader behavior as the most important factor influencing accountability, but only 15% of leaders had clearly defined and broadly communicated their key results.
• 82% said that when holding others accountable, they either try and fail or avoid it.

Read these with care. The sample is self-selected: people who chose to join a webinar and answer polls, so it isn't a random sample of workers. The data is also first-party, from the firm that sells accountability training. It shows what that audience reported, not an independent measurement of how common accountability problems are in all workplaces.

That caveat applies to the Oz Principle in general. It's a practical, widely taught model built from consulting experience, not a theory validated by controlled experiments. Treat it as a useful lens for conversation and use your own results to judge whether it helps.

Do's and don'ts

Do:

• Define the result first. The line only means something relative to a specific outcome.
• Go first as a leader. Say out loud when you've been below the line. Toxic leadership is what you get when leaders only point downward.
• Ask "What else can we do?" It's the shortest route from complaint to options.
• Treat the first slip as information. Everyone goes below the line sometimes.
• Pair it with clear goals. Accountability for a vague target is just anxiety.

Don't:

• Don't use the line as a weapon. Telling a colleague "you're below the line" is Finger-Pointing with a vocabulary.
• Don't confuse ownership with taking all the blame. Own It means looking at your contribution, not absorbing everyone else's.
• Don't skip See It. Jumping to action without an honest look at reality is how teams fix the wrong thing.
• Don't micromanage in the name of accountability. Tracking every move is a different failure, covered in what is micromanagement.
• Don't treat it as a one-time workshop. The habits come back under pressure.

Key Facts

Key Facts

• The Oz Principle: Getting Results Through Individual and Organizational Accountability is by Roger Connors, Tom Smith and Craig Hickman and was first published in 1994.
• Culture Partners (formerly Partners In Leadership) says the book has sold more than a half-million copies.
• The model splits behavior at "the line." Below the Line is blame and avoidance; Above the Line is ownership and action.
• The six below-the-line habits, per the originator's white paper: Ignore/Deny, It's Not My Job, Finger-Pointing, Confusion/Tell Me What to Do, Cover Your Tail, Wait and See.
• The four steps above the line: See It, Own It, Solve It, Do It.
• In Culture Partners' Workplace Accountability Study of more than 40,000 webinar participants, 85% were unsure what their organization is trying to achieve.

Summing it up

The Oz Principle gives a team a shared vocabulary for something everyone recognizes: the moment a missed result turns into a search for someone to blame. The six victim-cycle habits make that moment easy to spot, and the four steps give you a way out that doesn't depend on heroics. Start small. Pick one stuck result, define it in a sentence, and walk the steps with your team. If you want the harder follow-up, look at how your culture treats the person who first says "that one's on me." That reaction decides whether the line gets crossed or ignored. For a leader-level companion, read Extreme Ownership.