The Compliance Oracle
Consulted after the fact, consulted too late
The Compliance Oracle is the person everyone consults when a workflow is already in use but the compliance question is still undefined. The tool touches sensitive data, makes recommendations that feel risky, generates summaries someone may act on, or stores information in a way nobody has fully understood. Someone remembers, usually a little late, that compliance should probably have an opinion.
Symptom
The Oracle is always consulted after the workflow is live. Their guidance is thoughtful but arrives when the cost of changing course is already high enough that the organization would rather absorb the risk than redo the work.
Why It Matters
The Compliance Oracle's late involvement is not their failure — it's the organization's. By the time they're consulted, the question has shifted from 'should we do this?' to 'how do we justify that we already did?'
What the Chapter Gives You
Why late consultation is not consultation, how to bring compliance in before the cost of change makes compliance advisory, and the organizational pattern that guarantees the Oracle is always too late.
Want the full chapter? Grab the free cheat sheet, read an excerpt, or get the book.
Recognize this one in your codebase?
Free cheat sheet, excerpts, and interactive diagnostics.