Getting People To Actually Follow Through When They've Already Failed You
Most people read the book and then immediately try to apply all four tools in a single conversation. That never works. I learned that the hard way around 2019 when I was managing a team of twelve on a software rollout. A senior developer had missed three consecutive sprint commitments. My first attempt involved pulling him into a conference room, laying out the entire MBTI framework, walking through master status, and demanding a new commitment. He shut down completely. We spent forty-five minutes going in circles and he left saying he'd "think about it." He didn't. The actual practice of these tools requires a specific sequence and a lot less energy than the book makes it sound like. Here's how it actually plays out.
Crucial Accountability Tools For Resolving Violated Expectations Broken Commitments And Bad Behavior Second Edition
The book breaks accountability down into four distinct tools, but the order matters more than most people realize. The correct sequence is: master status first, then walk the talk, then make it safe, and finally get agreement. You cannot start at step three. I've seen managers try to create psychological safety before establishing clear expectations, and it produces exactly the wrong result — the person feels safe to keep doing what they've been doing. Master status is the foundation and the part most people botch. You state the expectation clearly, then you ask if the person agrees with your understanding of the expectation before you ever discuss performance gaps. This sounds obvious until you see someone say "I think the deadline was last Friday" and the manager immediately jumps to consequences instead of confirming whether they're even talking about the same thing. The gap between what the manager expected and what the employee understood is where most accountability conversations collapse. You establish master status by saying something like "I understand the commitment was X by date Y. Is that accurate?" Only after they confirm do you move forward. Walk the talk means acknowledging your own contribution to the problem. This is the tool people dread because it feels like admitting fault. In practice, it's the fastest way to defuse defensiveness. When that developer kept missing deadlines, I eventually realized I'd been changing the scope mid-sprint without formal acknowledgment. Instead of leading with his failures, I opened with "I know I've been moving the goalposts on this project and that's part of why the commitments got missed." His entire posture changed in about thirty seconds. He stopped being defensive and started being honest about what was actually blocking him.
Making it safe has two components: mutual purpose and mutual respect. You need the other person to believe you're not trying to humiliate them or push them out. And they need to feel that you respect their competence even while addressing the failure. The typical mistake here is focusing only on the task and ignoring the relationship. If someone feels attacked, no amount of logical argument about missed deadlines will fix the behavior. I learned to explicitly state the purpose before critiquing: "I'm bringing this up because I want you to succeed here and I need the team to be able to rely on these timelines." It's transactional language but it works because it removes ambiguity about your intentions. Getting agreement is where most conversations end prematurely. The agreement needs to be specific enough that you can verify it later. "I'll do better" is not an agreement. "I'll commit to completing the authentication module by Wednesday end of day and flag any blockers by 10am that morning" is an agreement. The book emphasizes the difference between commitment and agreement, and honestly that distinction saves a lot of wasted follow-up. An agreement means both parties have agreed on what success looks like. A commitment is one-sided and usually gets forgotten.
Get the Full Details
The Parts The Book Doesn't Cover Well
One thing the second edition gets right but doesn't emphasize enough is the concept of bad behavior versus missing a commitment. These require different tool sequences. If someone is consistently late, rude, or deliberately withholding information, that's bad behavior and you address it differently than a missed deadline caused by poor estimation. The book treats them somewhat interchangeably in early chapters, which confuses people. Bad behavior requires the safety tools first and master status second. Missed commitments follow the opposite order because the expectation was already established — you just need to close the gap between what was promised and what was delivered. Another counter-intuitive point: sometimes the right outcome is no agreement. If someone genuinely cannot meet the expectation given their current capacity, workload, or constraints, pushing for agreement is just performative accountability. I had a situation where a team member agreed to a commitment she knew she couldn't deliver. She said yes because she didn't want to look like the problem. Three days later she was behind again and now she'd also lost trust because she'd lied to me. The workaround was to explicitly ask "Do you have what you need to hit this, or do we need to adjust the scope or timeline?" That question surfaced the real issue — she was simultaneously running two projects with no visibility from either manager. Fixing the accountability problem required fixing the resource allocation, not having a harder conversation about commitment. The book also underplays the consequence framework. You need to know what happens when agreements are broken before you have the conversation, not after. Without pre-established consequences, accountability becomes arbitrary and managerial credibility erodes. I recommend writing down the consequence escalation path before you ever need to use it. "First violation: conversation and revised plan. Second violation: formal performance improvement document. Third violation: reassignment or separation." People respond better to consistent systems than to surprise punishments, and having it documented prevents you from escalating prematurely or failing to escalate when you should.
Where This Approach Fails Completely
Accountability tools don't work on people who are actively looking for reasons to leave. I've had situations where someone was three months into a notice period and still missing commitments. Having a full conversation using all four tools in that scenario wastes everyone's time. The person has already decided to disengage. In those cases, the only productive move is to reduce their exposure — reassign their work, limit their access, and protect the team from further disruption. The book mentions this briefly but doesn't give it the emphasis it deserves. Similarly, these tools require managerial authority. If you're trying to hold peers or direct reports from other teams accountable, the framework falls apart quickly. You can establish master status and walk the talk, but without the ability to meaningfully influence outcomes, getting agreement is mostly aspirational. In matrix organizations where I've worked, the workaround was to bring the person's actual manager into the conversation from the start rather than trying to build accountability from scratch. It's less elegant but it actually works. One more limitation: this system assumes the person wants to improve. Chronic accountability avoiders who have learned that things eventually resolve themselves without consequence will game the process. They'll agree to commitments they never intend to keep because they've seen that managers prefer agreement over follow-through. I dealt with one of these people for eleven months before realizing the pattern. The workaround was stopping the conversation cycle entirely and moving directly to documented performance management with measurable milestones. Accountability tools are for people who are genuinely stuck, not for people who are strategically avoiding responsibility.
Practical Implementation
The book includes worksheets and templates that most people skip. I recommend using them, specifically the commitment agreement form from chapter seven. Writing down the exact expectation, the verification method, and the consequences for non-performance takes about five minutes and prevents an enormous amount of follow-up confusion. I keep a shared document where each team member's current commitments are recorded with dates, deliverables, and review points. When someone misses a commitment, the conversation starts with "Here's what we agreed. Here's where we are. What changed?" instead of "Why didn't you do this?" The shift from emotional to documentary framing changes the entire dynamic. For self-assessment, the accountability inventory in the appendix is worth filling out honestly. It took me about twenty minutes and revealed that I was consistently skipping the master status step because I assumed I knew what the other person committed to. Once I started verifying expectations explicitly before discussing gaps, the number of misaligned commitments dropped significantly within two sprints. The physical book is still available through major retailers and the PDF version circulates widely. There's no official free digital copy from the publishers, but if you can't purchase it, the core framework — master status, walk the talk, make it safe, get agreement — is accurate enough that you can start applying it without the supplementary material. The tools are simple. The difficulty is in the execution and in knowing when not to use them.
