๐—ช๐—ต๐—ฒ๐—ป ๐—ฎ๐—ป ๐—˜๐—บ๐—ฎ๐—ถ๐—น ๐—ก๐—ฒ๐—ฒ๐—ฑ๐—ฒ๐—ฑ ๐—ฎ๐—ป ๐—˜๐—บ๐—ฎ๐—ถ๐—น ๐˜๐—ผ ๐—”๐—ฝ๐—ฝ๐—ฟ๐—ผ๐˜ƒ๐—ฒ ๐˜๐—ต๐—ฒ ๐—˜๐—บ๐—ฎ๐—ถ๐—น!

I have seen a lot of things in the IT service landscape but the communication hurdles during business-critical issues tops the chart. Especially, when you are working across multiple time zones.

Imagine that you need an approval from a whole chain of people just to send an urgent mass communication email to key stakeholders and impacted business users. The one person with the “golden approval stamp” is peacefully asleep in another time zone. Meanwhile, you are wide awake and scrambling to notify users and get the issue fixed. Ultimately, finding yourself tangled in even more confusion as communication delays pile up. The BU IT teams (well-meaning as always) jump in to send out their own emails to their local users. This ends up as a chaotic mess of messages with different tones, varying details, and sometimes wildly different levels of urgency. It is like a “game of telephone” gone wrong. No one knows who is in the loop OR what exactly they know. And impacted party – business – is clueless when the services will restore!

Clearly, we had to break through the red tape. So, I took matters into my own hands and led a process change that gave the major incident manager the ability to approve mass communications and a quick sign-off from the regional service manager. This way, the approvals were happening closer to the incident and cutting out the time zone delays. As an outcome by shifting approval rights closer to where incidents were happening, we cut out those pesky time zone delays and ensured that all stakeholders received timely and consistent updates.

The key to effective incident communication in a multi-geography IT environment is simplicity and speed. So, ask yourself whether your workflows make things easier OR do they just add more layers of complexity?

๐˜—๐˜š: ๐˜š๐˜ฐ, ๐˜ธ๐˜ฉ๐˜ฆ๐˜ฏ ๐˜๐˜› ๐˜ธ๐˜ข๐˜ด ๐˜ฃ๐˜ถ๐˜ด๐˜บ ๐˜ธ๐˜ช๐˜ต๐˜ฉ ๐˜ข๐˜ฏ ๐˜ฆ๐˜ฎ๐˜ข๐˜ช๐˜ญ ๐˜ฏ๐˜ฆ๐˜ฆ๐˜ฅ๐˜ฆ๐˜ฅ ๐˜ข๐˜ฏ ๐˜ฆ๐˜ฎ๐˜ข๐˜ช๐˜ญ ๐˜ต๐˜ฐ ๐˜ข๐˜ฑ๐˜ฑ๐˜ณ๐˜ฐ๐˜ท๐˜ฆ ๐˜ต๐˜ฉ๐˜ฆ ๐˜ฆ๐˜ฎ๐˜ข๐˜ช๐˜ญ, ๐˜ต๐˜ฉ๐˜ฆ ๐˜ฃ๐˜ถ๐˜ด๐˜ช๐˜ฏ๐˜ฆ๐˜ด๐˜ด ๐˜ถ๐˜ด๐˜ฆ๐˜ณ๐˜ด ๐˜จ๐˜ฐ๐˜ต ๐˜ต๐˜ฉ๐˜ฆ ๐˜ค๐˜ฐ๐˜ฎ๐˜ฎ๐˜ถ๐˜ฏ๐˜ช๐˜ค๐˜ข๐˜ต๐˜ช๐˜ฐ๐˜ฏ ๐˜ถ๐˜ฑ๐˜ฅ๐˜ข๐˜ต๐˜ฆ๐˜ด ๐˜ง๐˜ข๐˜ด๐˜ต๐˜ฆ๐˜ณ ๐˜ต๐˜ฉ๐˜ณ๐˜ฐ๐˜ถ๐˜จ๐˜ฉ ๐˜ต๐˜ฉ๐˜ฆ ๐˜ค๐˜ข๐˜ณ๐˜ณ๐˜ช๐˜ฆ๐˜ณ ๐˜ฑ๐˜ช๐˜จ๐˜ฆ๐˜ฐ๐˜ฏ๐˜ด! ๐Ÿ˜‰

#ITManagement #TechLeadership #ITHumour #ITGovernance #ITServiceEnablement #OperationalExcellence #JSTalks


Leave a comment



No comments on ๐—ช๐—ต๐—ฒ๐—ป ๐—ฎ๐—ป ๐—˜๐—บ๐—ฎ๐—ถ๐—น ๐—ก๐—ฒ๐—ฒ๐—ฑ๐—ฒ๐—ฑ ๐—ฎ๐—ป ๐—˜๐—บ๐—ฎ๐—ถ๐—น ๐˜๐—ผ ๐—”๐—ฝ๐—ฝ๐—ฟ๐—ผ๐˜ƒ๐—ฒ ๐˜๐—ต๐—ฒ ๐—˜๐—บ๐—ฎ๐—ถ๐—น!