Our AI policy is a shrug wearing a lanyard
The studio has approved experimentation. Nobody has defined the experiment.
Office politics
A new stakeholder appears precisely when the project is ready to leave.
In our fictional presentation, the work is approved until someone mentions that Gary has not seen it. Gary has been absent from every previous conversation. Gary has thoughts.
Late feedback is easier to manage when the approval process was agreed at the beginning. Ask who needs to review the direction and who can give final sign-off. These may be different people; knowing that early is useful.
Bring the necessary reviewers in while the choices are still cheap to change. A rough direction invites discussion. A finished production file invites a very particular kind of headache.
When somebody new joins late, explain the decisions already made and the requirements behind them. Assess their comments against that context rather than treating every preference as a new instruction.
If a change reopens approved work, show what it affects before promising a date.
Gary may have spotted something important. He may also simply prefer blue. It helps to establish which before cancelling the weekend.