Accountability in the Workplace
What It Actually Requires at Director Level

The key insight:

Delegation is handing work over. Feedback is telling someone how it went. Accountability is the standing expectation that sits between them, with nobody there to enforce it.

Accountability is one of the two or three things a director is most often told to work on, and it is one of the hardest to turn into an actual development objective, because most of what gets written about it describes a skill when accountability is a standing disposition instead.

Clear it away from two things it gets confused with first, because the confusion is where most advice on this goes wrong. Delegation is handing work over: deciding what leaves your desk and whose it becomes. Feedback is telling someone how it went: the conversation after the fact about what worked and what did not. Accountability is the standing expectation that sits between them, quietly, with nobody there to enforce it in the moment. You can delegate cleanly and give excellent feedback and still have no real accountability in a team, because accountability is not an event. It is what a person does, or does not do, when no one is watching and nothing is due yet.

That distinction matters because it changes what you are actually trying to build. A delegation framework tells you how to hand work over well. A set of feedback scripts tells you how to say things so they land. Neither one builds the standing expectation that someone owns the outcome whether or not anyone checks, and conflating the three is why so much accountability advice feels true and does nothing.

Accountability without a formal lever

Below director level, accountability usually rides on hierarchy. You are accountable to your manager because your manager can affect your pay, your role and your next move, and that is a real lever even when nobody says it out loud.

At director level, most of the accountability that actually matters runs sideways, not down. You need a peer in another function to deliver their half of a shared commitment, and you have no formal authority over them at all. You need a matrixed report, someone who sits on another leader's org chart and works with you on a dotted line, to treat your priority as a real one. Neither relationship has a lever in it.

What holds in practice is not authority. It is three things, stated in order because they genuinely work in this sequence.

The standard has to exist before the work starts, not after it goes wrong. Vague alignment in a meeting is not a standard. A standard is specific enough that both sides could independently describe what done looks like and by when, stated out loud, and ideally confirmed in writing somewhere both people can find it later.

The consequence has to be real and known in advance. It is very rarely disciplinary at peer level, because you do not have that lever and pretending you do reads as a threat you cannot back. It is almost always reputational and relational: what you will say, to whom, and how directly, if the commitment slips. People who are reliably accountable to their peers are not more senior than the people who are not. They are simply predictable about what happens next, and predictability is what lets a peer trust the arrangement without a hierarchy underneath it.

You have to follow through without drama, every time, including the first time it is inconvenient. One quiet exception teaches everyone watching that the standard was conditional. This is the part that most senior leaders quietly fail, because the first exception is usually made for someone they like, under time pressure, with a reasonable-sounding excuse, and it is never framed to anyone as the moment the standard became optional. It was.

Being held accountable for outcomes you do not fully control

The second half of director-level accountability runs the opposite direction, and it is the part that actually changes at this altitude. Below director, you are mostly accountable for things you can directly control: your own output, your own deadlines, your own decisions. Above it, you are accountable for things you only partly control, because the outcome now depends on other people's execution, on functions you do not own, and on market conditions nobody owns.

This is where accountability and responsibility pull apart most sharply, and the distinction is worth stating precisely because most of what gets written about accountability collapses the two.

Responsibility is assigned. It is the task on the job description, the line in the org chart, the thing that is formally yours to do. Accountability is owned. It is the standing answer to who carries the outcome when it lands well or badly, and crucially, it does not require that you personally did the work. A director can be fully accountable for a missed revenue number without having personally touched a single sale, because the result sat inside their remit. The research from the Center for Creative Leadership on building a genuine culture of accountability makes the same point from the organisational side: accountability has to be chosen, not compelled, which is exactly why it cannot be delegated downward the way a task can.

A useful test for whether you are confusing the two: if the honest sentence in your head is "that was not my fault," you are reasoning about responsibility. If the honest sentence is "that happened on my watch," you are reasoning about accountability. Senior leaders who stall are very often technically correct on the first sentence and still wrong to say it out loud, because the room is listening for the second one.

SHRM's research on building employee accountability found that the leaders who build it most reliably do so through trust rather than enforcement: congruence between what they say and do, openness about the real state of things, acceptance of people rather than judgement of their character, and reliability over time. The same four behaviours are what let a director credibly own an outcome they did not personally produce. Nobody trusts a leader's claim to accountability if it only shows up when things go well.

The ninety-day objective that actually works

Accountability shows up on more development plans than almost anything else, and fails to show up in the ninety-day review more often than almost anything else, because "be more accountable" cannot be assessed. It is not a behaviour. It is a verdict about behaviours that were never specified.

A version that actually survives a review names a concrete behaviour and a visible, checkable outcome. Not "improve accountability", but something close to: close every open commitment from the leadership steering group within the agreed window, without being chased, for the full quarter. That single sentence contains a standard (the agreed window), a consequence structure (visibly chased versus visibly not), and a result anyone on the steering group could confirm without asking the person being assessed.

The same sentence works for the sideways kind too: respond to every cross-functional request with either a committed date or an explicit decline within 48 hours, with zero silent misses for the quarter. It is specific enough to fail cleanly, which is the actual test of whether a development objective was worth writing. If a reasonable observer could not tell you, at the end of ninety days, whether it happened, it was never a real objective.

This is the part a written plan genuinely helps with, because the discipline of stating the behaviour precisely is most of the work. Our individual development plan examples show the same level of specificity applied to other common senior objectives, if you want more worked versions before writing your own. If you want a structured version of this against your own profile rather than building one from scratch, the Development Plan Builder on AssessYou turns a skills gap into milestones with this level of specificity attached, and a free account gets you started on it.

Where this sits next to delegation and feedback

Once the three are separated, it is easier to see how they actually connect rather than overlap. Delegation is the decision about what leaves your desk. Feedback is what you say about how it went once it has happened. Accountability is the quiet, standing expectation that holds in the gap between those two moments, when nothing is due and nobody is checking, and it is the one of the three that cannot be scripted, because it is tested by what you do, not what you say.

If you want to see how your own profile reads on the dimensions that predict whether this holds under real pressure, the free Leadership Psychometric on AssessYou takes 10 to 15 minutes and gives you a read before you write your own development objective. You can see what the assessment covers first on the Leadership Psychometric landing page if you want the detail before signing up.

The same gap between visible activity and real accountability shows up at board level too. How a board actually discovers whether its top HR seat built genuine succession accountability rather than simply hiring quickly is a governance-level version of the same problem: the operational metrics a chief people officer is measured on day to day reveal nothing about whether a credible bench actually exists, and the gap is only exposed when a senior departure forces the question.

Key takeaways

• Accountability is a standing disposition, not an event. Delegation is handing work over; feedback is the conversation afterwards; accountability is the expectation that holds between them with nobody enforcing it.
• Accountability without formal authority runs on three things: a standard stated before the work starts, a real and known consequence, and consistent follow-through without exception, especially the first inconvenient one.
• Responsibility is assigned; accountability is owned. A director can be accountable for an outcome they did not personally produce, and the honest tell is reasoning in terms of "that happened on my watch" rather than "that was not my fault."
• A development objective on accountability only survives a ninety-day review if it names a concrete behaviour and a checkable outcome. "Be more accountable" is not assessable; "close every open commitment within the agreed window, unchased, for the quarter" is.

JOH Partners Intelligence

Get the fortnightly brief on GCC careers, salaries, and market moves.

No spam. Unsubscribe any time.