The symptom is always the same
Across nearly every AI steering committee I observe, in discussion, at conferences, in the case studies that surface from the field, the same scenario repeats: the technical function arrives with a detailed use-case roadmap, and the executive committee discovers the governance stakes during the meeting, never before.
This isn't a competence problem. It's a sequencing problem, and sequences get fixed faster than most people expect.
Three signals that never lie
- Governance questions, risk, compliance, accountability, are raised after the use cases are presented, never before.
- Leadership approves a budget before settling on acceptable risk thresholds.
- Technical and business teams don't share the same vocabulary for "risk," which makes trade-offs illegible to the committee.
What sets the organizations that fix it apart
They made a simple choice, almost trivial on paper: reverse the agenda. Governance and risk thresholds are settled before use cases are presented, not in reaction to them.
That's where a bit of pragmatism changes the outcome. The organizations that correct course fastest aren't chasing the perfect AI governance theory: they test a minimal framework, adjust it at the next committee, and iterate. It's a logic close to what my immersion in the Chinese business ecosystem taught me: less doctrine, more execution, adjust as you go rather than wait for the perfect framework.
What to take away
This isn't a competence change. It's an agenda change, within reach of any executive committee starting with its next meeting.
Related topics