Building Team Accountability: Why People Stop Performing (It’s Not What You Think)
You’ve got someone on your team who used to be great. Now they’re missing deadlines, dropping balls, and you’re picking up the slack. You’ve had “the conversation” twice. Nothing changes. So you’re doing one of two things: avoiding them entirely, or building a case for termination.
Here’s what most leaders miss about building team accountability: the problem usually isn’t the person. It’s the system—or lack of one—around them. After 25 years of operations leadership, I can tell you that 80% of “performance problems” are actually clarity problems wearing a different costume.
That employee who’s “not performing”? They often have no idea what success actually looks like in their role. They’re guessing. And when people guess, they guess wrong.
Expectations vs. Agreements: The Accountability Divide
Most companies run on expectations. The boss expects things to happen a certain way. Employees try to figure out what those expectations are. Everyone’s frustrated.
Expectations are one-sided. They live in your head until they’re violated, at which point they explode outward as disappointment or anger. Your employee had no idea they were supposed to update the CRM within 24 hours of a client call—until you lost it on them in the Monday meeting.
Agreements are different. An agreement is a two-way commitment. Both parties discuss it, understand it, and explicitly commit to it. The employee knows exactly what they’re agreeing to. You know exactly what you can count on.
Here’s the uncomfortable truth: if you never made an explicit agreement, you can’t hold someone accountable for breaking it. You can only express disappointment that they didn’t read your mind.
For professional services firms, this shows up when partners assume associates understand “client service standards” that were never defined. For trades companies, it’s the foreman expecting crews to clean job sites to a standard that exists only in his head.
Why People Actually Stop Performing
When someone’s not delivering, leaders default to character judgments. They’re lazy. They don’t care. They’ve checked out. Sometimes that’s true. More often, it’s one of these four things:
Unclear Roles, Accountabilities, and Responsibilities
This is the big one. In most organizations, job descriptions are HR artifacts that bear little resemblance to what someone actually does. The employee’s understanding of their role doesn’t match yours. They think they’re doing great because they’re excelling at things you consider secondary.
Clear RARs—Roles, Accountabilities, and Responsibilities—eliminate this gap. The role defines the seat and who it reports to. Accountabilities are the outcomes this seat must produce (5-7 max). Responsibilities are the key activities that produce those outcomes.
No Measurable Targets
If “do a good job” is the standard, no one knows if they’re hitting it. Your service manager might think running 15 calls a week is impressive while you expected 22. Without agreed-upon numbers, accountability becomes subjective—and subjective accountability isn’t accountability at all.
Competing Priorities
When everything’s a priority, nothing is. Your employee is drowning in requests from three different people, all “urgent.” They’re not underperforming—they’re paralyzed by a system that gives them no way to win.
Broken Feedback Loops
The person genuinely doesn’t know they’re off track. They haven’t had meaningful feedback in months. By the time you address it, the gap between your perception and theirs is a canyon.
Turning Expectations Into Agreements
The fix isn’t complicated, but it requires discipline. Here’s how to convert vague expectations into real agreements:
Start with RARs. Sit down with each direct report and define their seat’s accountabilities—the 5-7 outcomes they’re responsible for producing. Not tasks. Outcomes. For a project manager, it might be “Projects delivered on time and within budget” and “Client satisfaction scores above 8.5.” For a lead technician: “First-time fix rate above 85%” and “Daily job documentation completed before leaving each site.”
Attach numbers. Every accountability needs a measurable target. What’s the number? What’s the timeframe? What’s the source of truth? No ambiguity.
Get explicit commitment. “Does this seem reasonable? Can you commit to this?” If they hesitate, dig in. Maybe the target’s unrealistic. Maybe they need resources. Maybe they’re not the right person for this seat. Better to know now.
Document it. If it’s not written down, it didn’t happen. Use whatever system works—Ninety.io — try it free for 30 days makes this seamless with built-in accountability charts—but the tool matters less than the documentation.
Making Accountability Visible with Scorecards
Here’s where most accountability efforts die: confrontation. Managers hate uncomfortable conversations. Employees hate feeling attacked. So everyone pretends things are fine until they’re catastrophically not fine.
Scorecards solve this by making accountability about data, not personality. Each seat has 3-5 KPIs with weekly targets. Every week, the numbers are green (hit), yellow (close), or red (missed). The scorecard doesn’t judge. It just reports.
In your Weekly Team Meeting, you review scorecards. When someone’s number is red, you don’t need to lecture them about commitment. You just ask: “What happened? What’s the plan to fix it?” The conversation is about the number, not the person’s character.
For a trades company, this might be: jobs completed per week, callback rate, average ticket size, safety incidents. For a professional services firm: billable hours, proposal close rate, client retention, project margin.
The magic is consistency. When the team sees these numbers every single week, accountability becomes ambient. It’s just how things work here. No drama required.
The 90% Rule
How do you know if someone’s truly accountable? Aim for 90% agreement fulfilment. When your team commits to things—whether Rocks, To-Dos, or scorecard targets—they should hit them at least 90% of the time.
Below 90%, you’ve got an accountability problem. Either commitments aren’t being taken seriously, or people are agreeing to things they can’t deliver. Both are fixable.
Above 90% consistently? You’ve built something rare: a culture where commitments mean something.
When Someone Consistently Misses
Even with clear agreements and visible scorecards, some people don’t deliver. After you’ve verified that RARs are clear and targets are reasonable, consistent misses come down to one of three things: competency, commitment, or capacity—what we call the Three Cs.
Competency: Do they have the skills? Can they be trained, or is this a fundamental gap? If your HVAC tech doesn’t have the technical chops for commercial systems, no amount of accountability will fix it.
Commitment: Do they actually want to do this job? Are they bought in? Sometimes great people are just in the wrong seat—or the wrong company.
Capacity: Do they have the time and resources? Maybe they’re overloaded. Maybe they’re dealing with personal circumstances. Maybe the job has grown beyond what one person can handle.
Diagnose which C is the problem before taking action. The solution for a capacity problem (redistribute work) is very different from the solution for a commitment problem (hard conversation about fit).
Trust and Accountability Are the Same Thing
Here’s what took me years to understand: accountability isn’t the opposite of trust. It’s the foundation of it.
When you hold someone accountable—clearly, consistently, without drama—you’re telling them their work matters. You’re saying, “I believe you can do this, and I’m paying attention.” That’s respect, not micromanagement.
Teams with high accountability have high trust. When everyone delivers on their commitments, you stop wondering if things will get done. You can focus on growth instead of babysitting. The anxiety in the building drops.
Teams with low accountability have low trust—no matter how “nice” the culture feels. People cover for each other, step on each other’s toes, and quietly resent the colleagues who coast while they carry the load.
Signs Your Accountability System Is Broken
- You know someone’s underperforming but haven’t had a direct conversation in over 30 days
- People routinely commit to deadlines they miss, with no consequences or adjustments
- You couldn’t describe the top 5 accountabilities for each of your direct reports without checking notes
- Your team would give different answers if asked “What does success look like in your role?”
- Performance conversations only happen during annual reviews—or when you’ve finally had enough
- High performers are frustrated, while mediocre performers seem comfortable
Where to Start
Pick one direct report. Schedule 45 minutes with them this week. Review their current job description—if one exists—and ask: “Is this actually what you do? What’s missing? What’s on here that you don’t really do?”
Then define 5-7 accountabilities together. Attach numbers where you can. Get their explicit commitment. Write it down.
Do this with every direct report over the next month. Then implement a simple weekly scorecard review—even if it’s just 15 minutes in your team meeting.
You’ll be amazed how many “performance problems” solve themselves once people actually know what winning looks like.
Ready to Build Real Accountability?
If this article hit close to home, you’re not alone. Accountability is the thing most leaders know they need but struggle to implement without it feeling punitive. A 30-minute call costs nothing and could be the clearest conversation you’ve had about what’s actually causing your team’s performance gaps.
We use Ninety.io to run our own accountability systems—Scorecards, RARs, the whole framework. If you want to see what it looks like in practice, try it yourself.
