# How to Hold Someone Accountable When You're Not Their Boss Canonical URL: https://headwayskills.com/knowledge/teamwork/how-to-hold-someone-accountable/ Markdown URL: https://headwayskills.com/knowledge/teamwork/how-to-hold-someone-accountable.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving teamwork at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Holding someone accountable starts with a commitment, not a confrontation. How to raise a missed promise with a colleague — early, privately, without blame. ## Key facts - Title: How to Hold Someone Accountable When You're Not Their Boss - Category: Teamwork - Primary skill: Teamwork - Related skills: Communication, Building Confidence - Primary keyword: how to hold someone accountable - Source page: https://headwayskills.com/knowledge/teamwork/how-to-hold-someone-accountable/ ## What this page covers - Holding someone accountable starts with a commitment, not a confrontation. How to raise a missed promise with a colleague — early, privately, without blame. - Practical guidance for how to hold someone accountable - How this topic connects to Teamwork ## Detailed explanation You agreed on something weeks ago. It didn't happen. And the longer you leave it, the harder it gets to bring up at all. Here is how to hold someone accountable when you have no authority over them: point back to a specific commitment they made, ask what happened before saying what went wrong, and agree a new commitment you can both check. Do it privately, and sooner than feels comfortable. Accountability is a comparison against something agreed — not a confrontation. Which is why most of these attempts fail long before anyone opens their mouth. ## What holding someone accountable actually asks of you The phrase makes it sound like enforcement, as if you need some lever over the other person before you can use it. You don't. What you need is something they actually agreed to. That is the point almost every serious source on this returns to, and it is the one most people skip. Writing in Forbes, Margie Warrell puts it plainly: without a firm commitment, there is nothing to hold anyone to. The mechanism is straightforward once you see it. You are measuring what happened against what the person said would happen. If nothing specific was ever said, there is nothing to measure against, and the conversation collapses into your preference versus theirs. That is why so many attempts land as nagging — the other person genuinely does not recognize the obligation you are describing. ## The five kinds of accountability at work Accountability is not one thing. The sources that map it out separate it into distinct forms, and the form you are in decides what is available to you. ### Personal accountability Owning your own actions, decisions and outcomes — noticing your own misses and correcting them before anyone has to raise them. It is the only form with no second party in it, which is exactly why it matters here: it is the credibility you bring into the room. Asking someone to own a slip lands differently depending on whether you have been seen to own yours. ### Peer accountability Being held to a commitment by someone at your own level. The definition that circulates across sources on this, originally Patrick Lencioni's, is the willingness of team members to call peers on performance or behavior that might hurt the team. Notice what it does not include: any power to impose a consequence. Peer accountability runs sideways, on relationship and shared purpose, which is why sources agree it rests on [trust built beforehand](/knowledge/teamwork/building-trust-in-a-team/) — it is easier to hear something uncomfortable from someone you believe means well. This is almost certainly the form you are in. ### Team accountability The many-to-many version, where a group holds itself to its own commitments rather than each person answering upward. The obligation is to the shared purpose rather than to any one colleague, and that changes what raising a miss means socially: it becomes a normal team function instead of one person challenging another. Where a team has agreed in advance how misses get surfaced, the conversation carries much less charge. ### Professional accountability Being answerable for the duties your role carries and the standards your employer expects. It differs from the others in that the standard pre-exists — it sits in the job, not in a conversation between you and a colleague. That is useful to know, because it is the one form that does not need a prior agreement. If something is obviously [part of someone's role](/knowledge/teamwork/role-clarity/) and it is not happening, you can reference the role rather than a promise. ### Managerial accountability The downward form: a manager sets expectations, tracks performance against them, gives feedback and applies consequences. It is the only kind backed by formal authority, and it is the kind nearly all the top-ranking advice describes. If that advice has felt inapplicable, this is why. You are being handed a tool that requires a title you do not have. ## Why the kind you're in changes what you can do Strip out authority and two things are left: whether the person trusts your intent, and how you handle [one conversation](/knowledge/communication/difficult-conversations-at-work/). That is a thinner set of tools than a manager has — not a weaker one, since it is the set that changes behavior rather than producing compliance. It does mean the preparation is different. A manager can set the expectation and then enforce it. You have to work with a commitment that was probably never crisp, without pretending in hindsight that it was. If you agreed in a corridor three weeks ago that they would handle the client update, you cannot now treat that as a breached deadline. What you can do is raise it as what it is — an agreement that turned out vaguer than either of you assumed — and use the conversation to make the next one specific. That reframe is the difference between an accusation and a repair. If you find yourself stuck at this same point across different people and different situations, the obstacle is probably not this particular colleague. It is worth checking [which skills are stalling you](https://assessment.headwayskills.com/) before you assume the problem is entirely theirs — the free self-assessment will show you the pattern faster than another week of waiting will. ## How to hold someone accountable without making it worse **Raise it sooner than feels comfortable.** The instinct is that waiting is the considerate option: you are giving them room, avoiding a fuss. Warrell argues the reverse — staying quiet about a broken promise makes you complicit in it. There is a practical version of that too. Delay does not preserve the conversation, it loads it. Three weeks of accumulated irritation comes out as a verdict on the person rather than a note about one specific thing that did not happen. **Do it privately.** Crucial Learning's guidance here is unusually firm: call people in, do not call them out. Raising a miss in front of others turns a work problem into a status problem — the person now has an audience and has to defend their standing before they can even look at what went wrong. The narrow exception is a team that has already agreed how misses get surfaced, which is a different situation from yours. **Ask before you assert.** Every source that takes the conversation seriously puts a question ahead of a statement: find out what actually happened first. There may be a blocker you can remove, a dependency that never arrived, or something going on you know nothing about. Either way, you learn it before committing to an interpretation you would then have to back out of. Fred Kofman's accountability work gives this a structure worth borrowing, sometimes labeled CRIA: confirm the commitment, explore the reality of what happened, reach the insight about why, then agree an action — a new commitment built on what you both just learned. What separates it from [ordinary feedback](/knowledge/self-awareness/constructive-feedback/) is where it ends. It does not finish with an acknowledgment; it finishes with something checkable. That is the part that stops the same conversation recurring next month. **Leave shame out of it.** Practitioners including Troy L. Love and Nika White both argue that shame can shift behavior briefly but does not sustain it. Separate intent from impact: you can be completely direct about what the miss cost without implying anything about the kind of person they are. This is also the specific risk the delayed conversation carries. The longer you have held it in, the more likely it comes out as blame. ## When to escalate, and what you owe afterward Peer approaches do not always work. Sources agree the endpoint is handing the problem to whoever should own it next — the person's manager — and that this is a last resort rather than a punishment. Two things are worth adding, because most sources stop there. Escalating after one direct attempt is a different act from escalating after none. If you have raised it and nothing changed, you are passing on a documented problem. If you have not, you are asking someone else to have your conversation for you. And you will still be working with this person afterward. Telling them you are taking it further, before you do it, costs one uncomfortable sentence and protects what going behind their back destroys. ## What makes this conversation easier to have Notice what none of that required. Not authority, not a policy, not a script. It required knowing what to say when someone gets defensive, and being willing to start at all — which are practiced abilities rather than fixed features of who you are. **Teamwork** treats this as ordinary rather than exceptional. Addressing a teammate who has not met a commitment, promptly and about the specific thing, sits inside the skill rather than beyond it. It also names the groundwork: the trust that makes such a conversation survivable is built earlier, through being reliable and meaning what you say, and it is protected during the conversation by keeping the subject on the topic instead of the person. **Communication** covers the mechanics you are actually short of. Choosing a conversation over a message because the topic is sensitive. Leading with the main point instead of circling it for five minutes. Being clear and direct while still making it possible for the other person to respond well. The genuine wish to understand the other side is not a softener here — it is what stops you being direct about the wrong problem. **Building Confidence** closes the gap between knowing you should say something and saying it. Its move is deciding in advance exactly where, when and how you will raise it, rather than waiting until you feel ready; the readiness tends to follow the action rather than precede it. It also handles the aftermath. If it goes badly, asking whether this is really always, everything and you keeps one awkward exchange from becoming a reason never to try again. The free Work Skills Test measures all three of these, along with the **nine others in the same set of twelve** — so what comes back is not more advice about accountability, but [a picture of your strengths](https://assessment.headwayskills.com/) and where the thin spots sit. None of them is fixed. They are the kind of thing you get better at by doing them imperfectly a few times first. Some of this may already describe how you operate. If you have been turning the conversation over in your head rather than complaining about the person to everyone else, that is the harder instinct, and it is the one the whole thing rests on — you have been trying to protect a working relationship while fixing a problem inside it. Nothing that is left requires becoming a more confrontational person. The behaviors change; you do not. And they compound, because the commitments that go unraised get larger as your responsibilities do. That is learnable at any stage, and the sooner you know which part of it you are weakest on, the less of it you have to learn the expensive way. Which leaves a fairly small question: which parts already work for you, and which one is worth some attention. ## Find out where your own footing is The only thing left is finding out which. The Work Skills Test is a **free** self-assessment of your work skills — you answer a set of questions about how you actually handle things at work, and you get back a profile of where you stand across all twelve, including the three this article has been circling. There is nothing to prepare and nothing to score badly on; what you do with it afterward is yours to decide. If you would rather have a clearer sense of your own footing before you go and have the accountability conversation, that is a reasonable order to do it in. **[Take the test](https://assessment.headwayskills.com/)** *Free, about seven minutes, and nothing to prepare.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Holding someone accountable starts with a commitment, not a confrontation. How to raise a missed promise with a colleague — early, privately, without blame. ### Which Headway skill does this connect to? This guide connects primarily to Teamwork. It also relates to Communication, Building Confidence. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/teamwork.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/confidence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/teamwork/how-to-hold-someone-accountable/ Preferred summary: "Holding someone accountable starts with a commitment, not a confrontation. How to raise a missed promise with a colleague — early, privately, without blame." ## Change log - 2026-07-07: Content collection version published.