A deliverable comes in late. The person apologizes, commits to doing better, and two months later, on a different deliverable, the same thing happens. Diagnosed as an individual failure - someone who's bad at time management - the fix is usually another conversation about doing better, which produces another short-term improvement and another recurrence. Diagnosed as a symptom of something else - unclear ownership, an unrealistic estimation process, a dependency that reliably arrives late - the fix looks completely different, and it's the only version that actually stops the pattern.
The tell: the same problem, different people, same outcome
The clearest signal that something is a root cause rather than an individual failing is that it would produce the same result almost regardless of who was in the role. If three different people, across three different projects, have all struggled with the same specific step, the step itself is a much more likely explanation than three unrelated individual weaknesses. This is the single most useful diagnostic question available: has this exact problem shown up with someone else, in a different context, doing something structurally similar?
Pushing past the first explanation
The first answer to "why did this happen" is almost always a symptom, not a cause - it's usually the most visible, most recent event in a longer chain. "The report was late" - why? "I didn't start it until the day before" - why? "I didn't realize it was due Friday, I thought it was due Monday" - why? "The deadline was mentioned once, verbally, in a meeting I wasn't fully paying attention to, and never written down anywhere." Each answer is more useful than the one before it, and only the last one points at something actually fixable at the system level: deadlines that live only in someone's memory of a meeting are going to keep producing this exact failure, independent of who's involved.
Where this connects to accountability, not against it
This isn't an argument against holding people accountable - it's an argument for being accurate about what they're being held accountable for. Someone who missed a deadline that was genuinely only communicated verbally, once, in a meeting, has a legitimate claim that the system failed them, not just that they failed to perform. Someone who had the deadline in writing, multiple reminders, and simply didn't manage their time is a different situation entirely, and the root-cause question resolves that ambiguity rather than avoiding it. The accountability planner's system-diagnosis step exists specifically to force this question before assuming which situation you're actually in.
A quick check before you fix anything
Before addressing a recurring problem, ask: if I replaced the specific person involved with someone else, equally capable, would this same problem likely happen again? If the honest answer is yes, the fix belongs at the system or process level - a clearer written standard, an explicit deadline-tracking mechanism, a redesigned handoff - not another individual conversation asking someone to try harder at something the system was never set up to support.