CM-201a · Module 2

The High-C Stakeholder

4 min read

The compliance officer, the auditor, the careful IT director who has a list of seventeen questions before approving anything — this is the High-C stakeholder. They are not your adversary. They are a stakeholder with a legitimate job: making sure things that get deployed are actually safe to deploy.

Let me be clear: High-C stakeholders who become blockers are almost always High-C stakeholders who were not briefed early enough. They learned about the AI initiative in the approval process rather than the design process. Now they are discovering risks in a context where they have no authority to fix them — only to block.

The High-C-skeptic-to-validator conversion is one of the highest-value interventions in change management. A High-C who has reviewed the governance framework, contributed to the risk assessment, and signed off on the security architecture is not a blocker. They are the organizational stamp of approval that the rest of the organization — especially other High-C profiles — needs to see before they will move.

The intervention is straightforward: brief the High-C early, give them access to the technical documentation, bring them into the governance design, and let them identify and help resolve their own concerns. They become the person who designed the safety framework rather than the person who blocked the deployment. That is a fundamentally different identity, and it produces fundamentally different behavior.

Do This

  • Brief High-C stakeholders before the announcement, not in the approval process
  • Provide complete documentation: security review, data governance, audit trail design, compliance mapping
  • Give them a role in designing the governance framework — they become owners, not critics
  • Let them ask all seventeen questions. Answer each specifically. Do not summarize.
  • Use their concerns to improve the design rather than treating them as obstacles

Avoid This

  • Tell a High-C "this is approved, we just need your sign-off" — that is an invitation to a detailed review of everything
  • Send a summary deck to a stakeholder who needs primary source documentation
  • Rush a High-C — they will either refuse to move or miss something important
  • Treat High-C concerns as bureaucratic friction rather than legitimate quality gates