Failover: Do you have redundant systems in place if a disastrous event occurs in a particular geozone and you need to failover? And if your systems, AI, and automation become totally inoperative, does the company have on staff employees who can revert to manual processes if needed?
Developing a resilient IT roadmap
Understandably, CIOs can only develop future-facing technology roadmaps with what they see at a present point in time. However, they do have the ability to improve the quality of their roadmaps by reviewing and revising these plans more often.
Today, the shortcoming at many companies is that leadership writes strategic plans and roadmaps as an annual exercise only. Given the rate of change of technology, putting away an IT roadmap for 12 months without periodic review and revision to adjust for disruptive change is no longer viable. CIOs should revisit IT roadmaps quarterly at a minimum. If roadmaps must be altered, CIOs should communicate to their CEOs, boards, and C-level peers what’s happening and why. In this way, no one will be surprised when adjustments must be made.
