How do you define a resilient IT culture – and how are you working to build resilience on your own teams?
Sort by:
When we have a critical project, we always have someone serving as a major and a minor. For example, I might be the major on a systems integration project, but I always need to bring someone else (a minor) with me to every meeting or sometimes every other daily standup. The minor doesn’t have to have a full understanding of the project, but they need to understand the status. That way if the major gets sick, fired, resigns, whatever, the minor can step in and we can recover.
I am not saying this is completely the wrong approach, because you are doing the right thing in making yourself "not indispensable". Unfortunately this sounds like duplication of effort. From a risk perspective , what if you were both injured on your way to a meeting and then out of action for 3 months? From a People and Processes perspective, communication and proper documentation (stored in the correct place and available to stakeholders) are also key. All personnel have to be trained and coached in these and other processes and mindsets to ensure business continuity.
Resilient IT culture can be characterized as an environment where the IT team or department is able to respond to and recover quickly from both planned and unplanned disruptions while maintaining continuity of operations. This resilience is built on the principles of adaptability, flexibility, and continual learning.
Therefore invest in:
- Continuous Learning
- Incident Post Mortem
- Cross-Team Collaboration
- Plan and regularly train Disaster Recovery