Mar 23, 2026 11:49 PM
Replying to Imran Afzal
...
I think a charter can be helpful — but only to a point.
The real issue isn’t the absence of guidelines. It’s how decisions get made when those guidelines meet real-world ambiguity.
Most AI use cases won’t sit cleanly inside predefined boundaries. They’ll involve trade-offs:
• speed vs. risk
• innovation vs. compliance
• local efficiency vs. enterprise impact
A charter can define principles, but it can’t resolve those trade-offs in practice.
Where I’ve seen organizations struggle is assuming that documenting “acceptable use” will remove the gray areas — when in reality, it often just shifts them into interpretation.
The more important question becomes:
How do we make
those trade-offs visible and discussable at the right level of the organization?Without that, a charter risks becoming:
• a compliance artifact
• something teams reference selectively
• or something that gives a false sense of control
The organizations that seem to be navigating this well aren’t relying on static charters alone — they’re pairing them with
clear decision pathways and forums where ambiguity can be surfaced and resolved.
A charter can set direction.
But it’s the decision system around it that determines how AI is actually used.