OARBED is a test for what happens in the first ten seconds after something goes wrong. Above the line sit Ownership, Accountability and Responsibility. Below it sit Blame, Excuses and Denial. It is not a personality test and it is not a way of sorting your team into good ones and bad ones — it is a test you apply to a sentence, including your own.
Something breaks, and one of two things starts happening in the room. Either people begin working out what to do, or people begin working out whose fault it is. That fork is the whole of the model, and the person who decides which way it goes is you.
What the six words mean
Above the line: Ownership, Accountability, Responsibility
Ownership. I treat the outcome as mine, whether or not the cause was mine. This is the one people find hardest, because it separates fault from responsibility for the fix.
Accountability. I answer for it. I will tell you what happened, including the uncomfortable part, without being asked twice.
Responsibility. I do something about it. Ownership without action is a nicer-sounding kind of stuck.
Below the line: Blame, Excuses, Denial
Blame locates the cause in a person. It is often factually accurate and almost never useful, because you cannot fix a person retrospectively.
Excuses locate the cause in circumstances — the supplier, the weather, the client, the market. Those are frequently true as well.
Denial decides there is no real problem. It is the quietest of the three and the most expensive, because nothing gets addressed at all.
Note that below the line is not the same as lying. Most of what gets said down there is accurate. It is simply pointed at explaining the past rather than at changing the future.
Why it matters more to the owner than to anyone else
Your team works out which side of the line this business runs on by watching your reflex, not by reading a values poster. If the reflex is “who did this”, people will spend the ten seconds before they tell you preparing their defence. Information starts arriving late, filtered and slightly optimistic. That is how an owner ends up being the last person in the building to hear about a problem everyone else has known about for a month.
Owners are frequently the worst offenders, too. Blaming the market, the staff, the bank, the last recruitment agency. All of it may be perfectly true, and none of it changes anything, because every one of those explanations puts the steering wheel outside the building.
One thing is worth saying plainly, because it gets lost. Ownership is not self-blame. “It is all my fault” is not above the line — it is blame pointed inward, and it is just as useless. The above-the-line question is never who caused this. It is what do I do now.
How to use it
Catch your own first sentence
Next time something goes wrong, notice what you say in the first ten seconds and write it down afterwards. That sentence is your culture, far more accurately than anything on the wall.
Change one default question
Replace “who did this?” with “what have we got?” for a week. It is a very small change and people notice it within days.
Run one debrief properly
Take a job or a month that went badly. Establish the facts and the figures before anybody offers an opinion, work out which parts you actually control, find the specific decision point, and end with one rule that changes something. Above the line is not the softer option — it is more exacting, because it finishes with a named person doing a specific thing.
Say the words out loud when you drop below
“That was an excuse, let me start again.” Doing that in front of the team is worth more than any explanation of the model.
Separate cause from fix, explicitly
Allow ten minutes for what happened, then say out loud that you are moving on to what we do. Below-the-line conversations are usually just conversations that never got moved on.
Use it on yourself for a month before you use it on anyone else
If you introduce the language as a policy, it will be used as a stick within a fortnight.
The mistake most owners make
Using the model as a weapon. Once a team learns the vocabulary, “that’s below the line” becomes the fastest way to shut somebody down mid-sentence. It is a clever move and it is itself blame, dressed up in coaching language. Do that for a fortnight and people stop raising problems at all, which means you have made things worse with a model designed to make them better.
The related error is treating the line as a moral boundary. Everyone drops below it. You will drop below it this week, probably about something small, probably in the car. That is not a failure of character. The measure is not whether you go below, it is how quickly you climb back, and good teams notice within a minute and say so without it being a big deal.
The third mistake is skipping the facts in order to get above the line quickly. Ownership that is not grounded in what actually happened is just enthusiasm. Establish what it cost first. Then decide.
Coaching questions to sit with
- Out of 10, how quickly do you find out about problems in your business? What does that score say about which side of the line people think you sit on?
- What is the explanation you reach for most often when results disappoint, and how much of it is genuinely outside your control?
- Who in your team has stopped bringing you bad news, and when did that start?
- Think of the last thing that went wrong. Did anything actually change as a result, or did the conversation simply end?
Everyone drops below the line. The only question that matters is how fast you climb back — and your team calibrates that from you, in the first ten seconds, every single time.
This sits at the centre of the work in Leadership Coaching. Once problems are being named early, The Performance Matrix is the tool for deciding what to do about the person at the centre of them — and The Performance Zone explains why an owner under sustained load drops below the line far more often than they think.
Get the next one in your inbox
One practical, plain-English guide for business owners each week. No spam, unsubscribe any time.
Common questions
Is ownership the same as taking the blame yourself?
No, and confusing the two is the most common way this model gets misused. Blame asks who caused it. Ownership asks what I do now. An owner who responds to every problem with it is all my fault has simply pointed blame inward, and that produces the same result as pointing it outward: a long conversation about the past and nothing decided about the future. Ownership means treating the outcome as yours to resolve regardless of who caused it. You can hold somebody accountable for a mistake and own the fix at the same time. In practice the two together are what a calm, quick debrief actually looks like.
How do I introduce OARBED to my team without it becoming a stick?
Use it on yourself first, for at least a month, and out loud. Say when you have just made an excuse and start the sentence again. What kills this model is a manager who learns the vocabulary on Monday and starts labelling other people with it on Tuesday, because that is blame wearing coaching language and the team reads it correctly within days. Once people have watched you apply it to your own reflexes, the language spreads on its own and it spreads as a shared standard rather than a rule imposed from above. Introduce it as a policy and it will be a weapon inside a fortnight.
What if the below-the-line explanation is genuinely true?
It usually is, and that is exactly why the model exists. The supplier really did let you down. The client really did change their mind. Below the line is not a synonym for dishonest. The point is that a true explanation of the past changes nothing on its own, and a debrief that stops there simply schedules the same conversation for a few months' time on a different job. Establish the facts properly, then ask the only question that produces a different outcome: of everything that happened, which parts do we control, and what will we do differently from Monday? True and useful are two separate tests.