[HN Gopher] Communicating to Users During Incidents
       ___________________________________________________________________
        
       Communicating to Users During Incidents
        
       Author : rozenmd
       Score  : 24 points
       Date   : 2022-01-17 10:32 UTC (12 hours ago)
        
 (HTM) web link (onlineornot.com)
 (TXT) w3m dump (onlineornot.com)
        
       | bloodyplonker22 wrote:
       | I worked for a startup where the lead/founding engineer would
       | always panic and think of excuses and sneaky things to try to
       | slither away from responsibility whenever there was an incident.
       | Not only responsibility to the customer, but responsibility to
       | our team. This is when I knew that I needed to start looking for
       | another job.
        
       | cube00 wrote:
       | _> As soon as you 're aware of an incident, tell your users!_
       | 
       | These days you'd be lucky to get any information about an
       | incident on a status page let alone being communicated with.
        
       | 692 wrote:
       | at almost every place that I've worked at, it's been the task of
       | the manager/ senior managers to keep the stake holders, general
       | staff/ users at bay, to keep the techies happy and free of
       | harassment during severity one incidents
       | 
       | and that includes making coffee, tea and bringing sandwiches/
       | pizzas
        
         | cube00 wrote:
         | I need to work at better places. Our managers are the ones who
         | schedule the "quick chats" to "see where we're at". In
         | particularly stressful situations I've been blunt in saying
         | we're not going to be able to solve the problem during this
         | meeting so please let us get back to work.
        
       ___________________________________________________________________
       (page generated 2022-01-17 23:00 UTC)