# Peer Accountability: What to Say When a Teammate Drops the Ball Canonical URL: https://headwayskills.com/knowledge/teamwork/peer-accountability/ Markdown URL: https://headwayskills.com/knowledge/teamwork/peer-accountability.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 Peer accountability means raising a missed commitment with a teammate, not your manager. When it's your place to speak up - and what to actually say. ## Key facts - Title: Peer Accountability: What to Say When a Teammate Drops the Ball - Category: Teamwork - Primary skill: Teamwork - Related skills: Communication, Influence - Primary keyword: peer accountability - Source page: https://headwayskills.com/knowledge/teamwork/peer-accountability/ ## What this page covers - Peer accountability means raising a missed commitment with a teammate, not your manager. When it's your place to speak up - and what to actually say. - Practical guidance for peer accountability - How this topic connects to Teamwork ## Detailed explanation A teammate said they would have it done by Tuesday. It is Thursday. You have thought about saying something four separate times and said nothing, and now you are wondering whether it is even your call. Peer accountability is the willingness to raise a missed commitment or a harmful behavior directly with a teammate, rather than waiting for a manager to notice. It runs sideways, between equals. And the hesitation is the normal part, not the disqualifying part. ## What is peer accountability? Peer accountability is what happens when people on a team hold each other to their commitments instead of routing everything through a manager. Patrick Lencioni, whose Five Dysfunctions of a Team model anchors most of the writing on this subject, defines it as the willingness of team members to call their peers on performance or behaviors that might hurt the team. The load-bearing word is *peers*. This is a lateral obligation between colleagues, not a management task quietly delegated downward, and the reasoning is practical: a manager sees a fraction of what teammates see, so a team that waits for the manager to notice moves at the speed of the person with the least information. Some fields have stopped leaving this to individual courage: the National Wildland Fire Coordinating Group publishes peer accountability as formal doctrine for US wildland firefighters, who are expected to flag a hazard regardless of who outranks whom. ## Is it my place to say something if a teammate isn't pulling their weight? In most cases, yes — with one honest caveat. You often cannot see the whole picture. Discussion threads on this topic surface the same objection repeatedly: it is genuinely hard to judge whether someone is pulling their weight when you do not do their work and cannot see what got dropped on them last week. That objection is fair, and it should change how you open the conversation. It should not stop you from having it. What makes it your place is not seniority. It is that you have a stake in the outcome. If their commitment feeds into yours, you are not commenting on their performance in the abstract — you are asking about something you depend on. That is a narrower and far more defensible claim than "you are underperforming," and it is almost always the true one. ## How do I hold a coworker accountable when I'm not their boss? You do not, in the way the phrase suggests. You have [no authority](/knowledge/influence/influence-without-authority/) to require anything from a peer, and any approach that pretends otherwise lands badly. What you have is a request, a working relationship, and a shared interest in the work landing. That changes the shape of the conversation more than its difficulty. In practice it means four things: keep it private, raise it soon, [name something observable](/knowledge/self-awareness/constructive-feedback/), and open with a question rather than a verdict. The goal is not to extract an admission. It is to get a new, specific commitment you can both plan around. ## What do I actually say to a teammate who missed a deadline? The most consistent piece of tactical advice across practical sources — Integris Performance Advisors put it most plainly — is to open by asking how you can help, before assuming neglect. It sounds soft. It is actually the accurate move, because you are usually missing information, and an accusatory opening that turns out to be wrong is expensive to recover from. From there, name the specific thing rather than the general pattern. Consultancies working on team performance, including Monkhouse & Company and Arootah, make the same point about expectations: when the standard is explicit and observable, the conversation stays about a commitment. When it is implicit — "you're not contributing enough" — it becomes a conversation about character, and people defend their character much harder than they defend a missed date. So the difference is between "the draft was due Tuesday and I haven't seen it — what's going on?" and "you keep letting the team down." One of those has an answer. The other has only a fight. Then close it properly. Ask for a specific new date or handoff, and say what you will do if it slips again. A small, concrete win beats a general promise to do better. ## How do I bring it up without seeming like I'm attacking them or being a tattletale? Go directly, and go early. Those two choices do most of the work. Direct means to them, not around them. The advice here is unusually unanimous: raising it with other teammates first, or going straight to the manager, is what actually damages your standing. The Muse frames the cost bluntly — a leader often reads a complaint about a peer as evidence that you cannot manage the working relationship yourself. Early means before it becomes a pattern. Sources from Integris to Arootah converge on addressing a missed commitment promptly rather than accumulating incidents, and the reason runs against instinct, because waiting feels considerate. But when you finally raise three months of examples at once, you are presenting a case you have evidently been building, and it lands that way. One recent, specific thing is a conversation. Six old ones is an accusation. ## When should I go to my manager instead of handling it myself? Escalation is legitimate; the point is to make it the second step rather than the first. Go to your manager when you have already raised it directly at least once and nothing changed; when the issue sits outside peer scope entirely, such as conduct, safety, or a policy breach; or when it puts a commitment your manager owns at risk and they need the information to replan. When you do go, bring what you tried, not just what you observed. "I raised the Tuesday deadline last week, we agreed on Friday, and it slipped again" is a different conversation from "they never deliver" — and it makes you the person handling it, not the person complaining about it. ## What if they get defensive or it goes badly? Some defensiveness is normal and does not mean you got it wrong. The useful discipline is to stay on the commitment and refuse to be pulled onto motive. If the conversation turns to what kind of person either of you is, you have both left the topic that had a solution. Return to the specific thing, ask what would make the new date realistic, and end it there. It is also worth being honest about the more common failure, which is not a conversation gone wrong. It is the conversation that never happens. If you recognize yourself in the four separate occasions you almost said something, the difficulty is probably not this particular teammate — it is friction in general, and how you tend to handle it. That is a learnable pattern rather than a fixed one, and it is worth getting a read on [where your work skills stand](https://assessment.headwayskills.com/) before you decide it is just how you are. ## Why does peer accountability need trust first? Because it sits on top of trust structurally, not just sentimentally. In Lencioni's model, accountability is the fourth of five layers, resting on trust, on the willingness to have real disagreements, and on genuine commitment to decisions. Skip the lower layers and the top one does not hold: on a team where [people do not trust each other](/knowledge/teamwork/building-trust-in-a-team/), being called on a missed deadline reads as an attack, because there is nothing underneath it to interpret it charitably. That gives you a practical direction if your team has none of this yet. You do not start by holding others accountable. You start by being visibly reliable about your own commitments, and by asking a teammate to hold you to one — a low-risk opening move that earns the standing to do the same in return. The reframe Lencioni is best known for follows from the same place, and the Global Leadership Network's summary of his work states it directly: holding a colleague to a standard is an act of care rather than aggression. It says you take them seriously enough to have an uncomfortable conversation instead of quietly writing them off. Silence is not the kind option. It is just the easier one. ## What if I'm the one being held accountable? You will be, eventually, and how you take it decides whether anyone tries again. [Hear it out before responding](/knowledge/self-awareness/how-to-receive-feedback/), separate the missed commitment from your worth as a colleague, and give a real new date rather than an apology. A team where this travels in one direction only has one person policing everyone else. ## The skills underneath a conversation like this Read back across those answers and the same few capabilities keep surfacing, none of them really about accountability as a concept. Knowing it is your place to speak. Finding words that land as a question instead of a verdict. Getting someone to move when you cannot make them. **Teamwork** is where this obligation actually lives. Holding each other accountable — addressing it when a teammate misses a commitment, without delay and with specifics — is part of what membership on a team involves, alongside being reliable about your own commitments and willing to disagree constructively. That is the answer to the permission question you started with: it is not an escalation you have to justify, and the trust you build by delivering your part is what makes it possible. **Communication** covers the mechanics that decide how it lands. Raising a missed commitment sits with the genuinely tricky situations — giving feedback, expressing disagreement, working through conflict — and the choices are concrete. Choosing a conversation over a written message when the topic is sensitive. Being clear and direct without being blunt. Wanting to understand what happened before deciding what happened. **Influence** is what you are left with once you accept that you cannot require anything. Influence between equals starts with understanding what the other person is actually dealing with, then aims at something achievable — a renewed commitment on one deliverable rather than wholesale change. Your own track record is what gives the ask any weight, which is why credibility and accountability turn out to be the same project. Three of the twelve work skills in this framework, then, converge on one difficult conversation — and the free Work Skills Test will show you [which skills to build first](https://assessment.headwayskills.com/) rather than leaving you to guess. ## Where this goes from here Some of this may already describe how you operate. If you are the one noticing the missed commitment, you are usually also the one keeping yours. What is missing is not character — it is a handful of behaviors you have not had much reason to practice yet, and behaviors are learnable without becoming someone else. This also gets weightier rather than lighter. The further into a career you go, the more of your work depends on people you have no authority over, and the more often a project lands or quietly fails on whether somebody said the awkward thing early. You have already done the part most people skip: you went looking for how to do this properly instead of firing off an annoyed message on Thursday afternoon. ## See where your skills stand The only thing left is to find out which of these are already solid for you and which are worth some attention. The Work Skills Test is a **free** self-assessment of your skills across all twelve areas this framework covers — teamwork and communication among them — and it gives you a clear read on where each one currently sits, so you can put your effort into the two or three that will make the most difference rather than trying to work on everything. It takes about 7 minutes, and there is nothing to prepare beforehand. **Take the test** *Free, no sign-up, and about 7 minutes from start to your results.* ## 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? Peer accountability means raising a missed commitment with a teammate, not your manager. When it's your place to speak up - and what to actually say. ### Which Headway skill does this connect to? This guide connects primarily to Teamwork. It also relates to Communication, Influence. ### 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/influence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/teamwork/peer-accountability/ Preferred summary: "Peer accountability means raising a missed commitment with a teammate, not your manager. When it's your place to speak up - and what to actually say." ## Change log - 2026-07-07: Content collection version published.