Accountability as a System
Core Principles from How Did That Happen?
Roger Connors & Tom Smith
Author: Shashank Heda, MD
Location: Dallas, Texas
Organization: Raanan Group
Classification: Management & Organizational Design
Who Is This For — And Why It Matters
Who Should Read This
- Leaders who have inherited broken teams and sense that the fracture is structural, not personal—but lack a diagnostic framework to prove it
- Managers caught in the blame cycle, where missed targets produce finger-pointing instead of root-cause inquiry, and the same failures recur quarter after quarter because the system was never examined
- Founders scaling beyond personal oversight who recognize that what worked when they could see every deliverable will collapse the moment the organization outgrows their line of sight
- Anyone who has asked “How did that happen?” in genuine bewilderment—not as an accusation, but as an honest diagnostic question—and received only alibis in return
Why It Matters
- Because accountability is the most misdiagnosed concept in organizational life. It is treated as a personality trait when it is actually an architectural problem. This article reframes it as system design
- Because the cost of ambiguity compounds silently. Unclear expectations don’t produce visible crises; they produce slow erosion—missed deadlines rationalized, mediocre output normalized, and capable people quietly disengaging because they were never told, with precision, what excellence required
- Because the alternative to designed accountability is not freedom—it is drift. And drift, in organizations, is the precursor to irrelevance
Sometime around 2011—I was still in the thick of portfolio management consulting at the time, working across dependent programs for a large financial services client in the Northeast—I sat through a post-mortem that changed how I understood organizational failure. The project had missed its deadline by six weeks. When the senior sponsor opened the room with “How did this happen?”, what followed was forty-five minutes of elaborate blame redistribution. The vendor. The requirements team. The holiday schedule. A resignation in middle management nobody had backfilled. Every explanation was individually plausible. Collectively, they formed a perfect alibi—and revealed absolutely nothing about the mechanism of failure.
That room is where I first understood, viscerally, what Connors and Smith articulate with clinical precision in How Did That Happen?: accountability is not a human trait. It is a system property. You either design for it or you inherit its absence.
The Diagnostic: What Actually Goes Wrong
The book opens with three axioms that function less as philosophy and more as operational triage. First, the Accountability Assumption: most people want to deliver. They are not indolent or venal by default. Second, the Accountability Fallacy: when results disappoint, the instinct to assign blame is the wrong first move—it treats symptoms while the structural disease progresses unchecked. Third, the Accountability Truth: the diagnostic question begins with the self. “How did I let that happen?” Not as performative humility. As genuine root-cause discipline.
This is not soft thinking. This is the organizational equivalent of what pathologists do before they sign out a diagnosis—rule out your own contribution to error before attributing the finding to the specimen. If I may propose a parallel: the physician who blames the staining technician for a missed cancer has committed the same architectural failure as the executive who blames “poor execution” without examining whether the expectations themselves were ever coherent.
The Architecture: Building Expectations That Can Be Met
Connors and Smith construct their framework around two concentric operational rings. The Outer Ring governs expectation-setting. The Inner Ring governs failure diagnosis. Most organizations skip the Outer Ring entirely and live permanently in the Inner Ring, wondering why the same conversations recur.
The Outer Ring operates through four sequential steps—and the sequence matters. Form. Communicate. Align. Inspect. Each step is a gate; skip one and the system degrades downstream.
Form requires that expectations be Framable, Obtainable, Repeatable, and Measurable. The acronym is convenient; the discipline behind it is not. Most organizational expectations fail the “Framable” test alone—they exist as ambient assumptions, never articulated with enough specificity to be falsifiable. I have seen entire teams operate for months under expectations that, when finally surfaced, turned out to be mutually contradictory across two senior leaders who had never compared notes. That is not an execution failure. That is an architecture failure.
Communicate anchors the task in Why—What—When—and the ordering is deliberate. Why comes first. Not as corporate rhetoric. As structural necessity. My experience across consulting, hospitality, and even pandemic response with CovidRxExchange confirms this—that compliance without comprehension produces brittle execution. The moment conditions shift, people who understood only what to do, but not why, freeze or improvise dangerously. The “Why” is load-bearing.
Align goes beyond intellectual agreement. The book demands emotional alignment—genuine commitment, not nodding in a meeting. This is where most leaders under-invest. Alignment takes time. It requires dialogue, not broadcast. It requires the leader to listen, genuinely, for misunderstanding, hesitation, or unspoken objection. I did not fully appreciate this distinction until I watched it fail repeatedly in cross-continental volunteer teams during COVID—brilliant physicians who intellectually agreed with evidence-based protocols but emotionally resisted changing established practice. Intellectual alignment without emotional buy-in is a Maginot Line: it looks protective until tested.
Inspect closes the loop through the LOOK model: Listen, Observe, Objectify, Know. Not surveillance. Kartavya—duty-driven oversight that treats monitoring as care, not control.
The Diagnostic Ring: When Expectations Are Not Met
When results fall short—and they will—the Inner Ring provides four diagnostic levers: Motivation, Training, Personal Accountability, and Culture. Not four accusations. Four levers. The distinction is the entire point.
Motivation is addressed not through pressure but through narrative. Connors and Smith argue that leaders activate, sustain, reinforce, and regenerate motivation by connecting tasks to identity and meaning. This resonates with something I have observed across domains: people endure extraordinary difficulty when they understand why their contribution matters. They abandon well-compensated positions when that connection breaks. The sequelae of meaningless work are not just disengagement—they are organizational atrophy.
Training follows the discipline of Demonstrate, Do, Debrief, Repeat. Straightforward on paper. Rarely executed with discipline in practice, because organizations confuse information transfer with capability building. Telling someone the standard is not training them to meet it.
Personal Accountability introduces the “Above the Line” framework—See It, Own It, Solve It, Do It—and the recursive question: “What else can I do?” This is where the book shifts from organizational architecture to individual epistemic discipline. The question is not rhetorical. It is operational. And it must be asked without the expectation that someone else will provide the answer.
The Cultural Substrate: Where Accountability Lives or Dies
The deepest layer—and this is where the book moves from competent management literature to something approaching governance philosophy—is culture. Connors and Smith identify three pillars: Follow Through (do what you commit to), Get Real (speak the truth without political filtering), and Surface Issues (identify problems before they metastasize). Three pillars. Not decorative values printed on a lobby wall. Operational norms that either exist in daily practice or do not exist at all.
The most important insight is structural: high-performing organizations create bottom-up accountability flows. Not top-down enforcement. Bottom-up ownership. People raise issues. People own outcomes. People hold themselves accountable before the system needs to intervene. This is the difference between governance that requires constant policing and governance that sustains itself—between an organization that merely functions and one that can absorb, adapt, recalibrate, and self-correct under pressure.
The Deeper Architecture
What Connors and Smith have built—perhaps without fully naming it in these terms—is a governance architecture for human systems. Accountability, in their formulation, is not a value statement. It is an operating model: designed, inspected, diagnosed, and continuously recalibrated. The Outer Ring is preventive architecture. The Inner Ring is diagnostic architecture. The cultural substrate is the immune system that determines whether the architecture heals itself or requires perpetual external intervention.
I recognize this pattern because it maps directly onto what I have spent two decades building across very different domains—from molecular oncology to cloud governance to hospitality experience design. The structural absence is always the same: the missing governance layer between intention and outcome. Connors and Smith have identified that absence in the specific domain of people management and built the scaffolding to fill it. The question that remains—and I leave it genuinely open, because I have not resolved it—is whether organizations that lack this architecture can install it retroactively, or whether the installation itself requires a quality of leadership that the absence has already selected against.
That is not a criticism. It is a boundary condition. And boundary conditions, as any diagnostician knows, are where the real learning begins.
Obeisance to the Almighty and my Celestial Gurus.
If I may err, I seek pardon.
I welcome your thoughts.
Author: Shashank Heda, MD
Location: Dallas, Texas
Organization: Raanan Group