Accountability has two faces. Organizations see one. My work reveals the other.

Organizations typically treat accountability as procedure—compliance, documentation, audit. That’s one face, and it’s essential. But accountability also operates through a discretionary regime—the institutional conditions surrounding the procedural regime that determine whether an organization can recognize when a situation exceeds what its procedure can resolve, and act on that recognition. When organizations integrate automation technologies, the procedural regime expands and the discretionary regime gives way to the signals procedure implicitly produces. This displacement is most acute in critical infrastructure—cybersecurity, financial services, healthcare, energy, defense—where automated decisions often carry consequences that procedural compliance alone cannot manage.

The result looks like governance on the surface. Below it, the capacity to recognize and act when procedure cannot is being crowded out.

Accountability Engineering is the deliberate design of governance architectures—and of the questions leaders ask about them—that sustain both regimes.