Launching a new upgrade is generally a stressful time for software companies. It can be very easy to forget some of the necessary steps or simply forget to communicate something to another department. Creating an effective plan is a key part of any release.
The role of a Chief Automation Officer (CAO) for businesses was first espoused a few years ago as reporters, analysts, and automation vendors started to see the growing burden on the CIO and the need for more IT executive leadership positions. Here at the IT Automation Blog, we’ve considered the need for a CAO in previous blog posts and in conversations with automation users. Today, I want to revisit the idea of the CAO and see just how predictions about the rise of the CAO are shaping up with the reality of businesses’ organizational structure today.