Spot the difference between comms re: cyber attacks against the world's largest oil distro and one of the world's largest food distro companies Vs a performance issue on one of the world's smallest MMOs.
Looks it's great to accept everyone large and small should strive to a high standard but nobody's losing their lives or livelihoods OR their personal data because videogame is laggy. If you think these scenarios are comparable then I'd say you've got bigger concerns like did the toaster eat your bread when you pressed the button down.
Here it is again... the "
They're just an itty bitty struggling dev studio. Don't be too hard on them." defense. They're not as small as you think. You should probably do your homework before making such claims.
Start here:
https://forums.ddo.com/index.php?th...s-and-unpacking-adjustments.21163/post-287584
Secondly, specifically in the context of incident communications, the above almost doesn't matter.
In the business world, with anything beyond an actual tiny mom-and-pop business with 1-3 employees, proper incident/crisis management isn't hard to do properly, nor does it require mass amounts of employees. It simply requires actually knowing what to do and how to do it efficiently.
I work in a 5 person internal IT team that supports multiple, separate companies. My "customers" are our endusers and the executive management teams.
I guarantee you that if a major incident occurred that spanned 6+ weeks and we only released a weekly update that amounted to, "
We're working on it, trust us bro.", we'd be getting asked some very uncomfortable questions by the executives that sign our paychecks.
Here's the basic high level process:
- Assign the appropriate personnel and resources to find and fix the problem based on it's nature.
- Designate a member of the team who is not directly involved in the finding/fixing as the communications liaison between the "fixers" and the management/customers.
- Their job is to monitor the troubleshooting progress and provide regular updates out to the appropriate audiences.
- Their job is also to translate any technical verbiage into layman's terms so said customers can understand the issue and what is being done to fix it.
- As internal updates are being provided to executive management by the designated liaison, the executives (or if a company is large enough to have them, the PR/Legal/Marketing teams) issue updates to the external customers and any relevant responses to their inquiries.
In summary, proper, effective communications during a major business incident is straightforward and simple. In most cases, it can be accomplished with only 2 additional personnel who are not directly involved in the work to find/fix the problem.
We know that not everyone on SSG's staff is a dev and/or directly involved in debugging and fixing the actual problem. Based on job titles and previous pubilc comments by various SSG staff, it's safe to assume that at a minimum Cordovan and Severlin fall into this category.
How hard should it be for the two of them to work together and provide better, more informative updates at least every few days?