What do you do when you approve a change?
Another email arrives in your inbox. It's a request to approve a change. The change is to patch the firmware on a network switch. A service that you're responsible for is dependent on this network switch. But then so are many other of your IT services too.
Do you wait until a few other people you trust have given the thumbs up and then give your seal of approval?
Do you assume the change management team has scheduled the change to be carried out at a time that won't affect your customers, and so approve the change?
Do you pore over every detail and use the wisdom you've accumulated over time to look for obvious mistakes in the implementation plan and ensure the post-implementation tests will be rigorous enough to confirm your service is no longer affected?
Do you assume that the technical people on the approval list are the Subject Matter Experts (SMEs) and only approve to show you are aware of the change happening?
What do you do when you approve a change?
- Previous: But I already told you that
- Next: Iterative planning
