An AI Council needs to help the work move forward. Bring the people who understand the process and the person who can make the decision into the same conversation.
Put the right people in the room.
Include an executive sponsor, the relevant department champions and the people who own active pilots. Bring IT or other specialists when the decision needs their judgment. Keep membership connected to the work.
Start with a short view of progress.
Review the baseline, current use and what has changed. Separate measured outcomes from estimates and potential opportunities. A large projected saving should not appear as a completed result.
Name the blocker.
Make the issue concrete. Is access missing? Is the output unreliable? Is no one available to test it? Does the team need a policy decision? Describe what is preventing the next step.
Make one focused decision.
A useful agenda gives the group a question it can answer. For example: should this pilot move to another team, what review is required before release, or which of two opportunities gets capacity next?
Leave a record someone else can use.
Record the decision and why it was made. Add the owner and due date for the next action. The record should help the next person understand the work without reconstructing a meeting.
- Decision and date
- Who approved it
- Reason and relevant evidence
- Where the decision applies
- Next action, owner and due date
Match the cadence to the work.
An active pilot may need frequent decisions. A stable program may need a different rhythm. Set the cadence around delivery and keep it useful. If meetings repeatedly produce no decisions or actions, revisit the agenda and who attends.