CIO Screw up Log
Some might say that this is the unofficial name for the help desk ticketing system. And to some extent they are right.
But screw up is an unkind phrase for a failure. But failure is a key element in self development. As mentioned in an earlier post, failure is crucial, mistakes are unacceptable.
I encourage CIOs to keep a log of anything that takes place during the day that doesn’t conclude in a positive manner. These might include:
- The mis-launch of a new IT service.
- The strained meeting with the CFO.
- The heated exchange with the key supplier.
- The new innovation budget allocated to the CMO, which includes a substantial allocation for technology spend (that is not under the CIO’s control).
All of these came about because of something the CIO didn’t do correctly. So rather than go on to make the same mistakes day after day, they need to be logged. Assigning severity scores to the log entries will provide the information needed to prioritise the CIO’s personal development.
If the CIO is unwilling to do this, then HR might take on this responsibility. The log can then be used as either a development tool or exhibit A in the firing process.