How do you navigate the fine line between providing the technical explanation for the cause and being perceived as 'making excuses' - strikes me as a no-win situation.
i don't think it's that binary. they're different conversations. my concern is that technical answers are being provided when people express concern about things like product failure, business continuity, exception handling, and so on.
basically, it's the same as if your cars caught fire (Hi, Ford) and when clients raised concerns, the discussion devolved onto the difficulties of solving particular engineering problems related to which side of the motor it's best to run flammable pipes. it's the wrong response. the correct response relates to what you're doing about product and service continuity, how you're addressing client concerns, and - critically - why i should be confident that you're defended against future such events.
i have just been reading the client communications from the September outages. i don't feel like re-typing them (they're images) but a sample is below.
this was on the 27th September. so was this:
basically, if you're going to position yourself as a community brand, and highlight particularly the value and strength of your "word-of-mouth referrals" and customer engagement, then when the word you start hearing from mouths is
"we're concerned", you have some kind of obligation to take it seriously.
(also, totally subjectively, i don't like the social good lever - we sponsor a lot of schools - because i find that manipulative. i'm glad you do that, and it counts in your favour if i have to choose between CI and someone else, but it's immaterial when you fail to deliver. but that's personal. YMMV.)