• If I was worried about disk space then I'd be asking how I could determine the amount of disk space required through automated means. Similarly could I predict locking/blocking impact mechanically?
    I would design a good process, automate as much of it as possible, document it both as an operational playbook and separately as an educational piece.
    In my experience change review boards have a nasty habit of descending into ego stroking committees for yesterday's men. The worst of them add bureaucracy and distraction that actually increases the likelihood of a failed change.