3 ms·
I think Dropbox would benefit from bringing in a competent PR person to advise them on making this kind of announcement and communicating with customers. (whic
by rdl 15y ago
I think Dropbox would benefit from bringing in a competent PR person to advise them on making this kind of announcement and communicating with customers. (which is saying a lot, since I generally disdain PR people). Commenting on a problem you've caused people without actually apologizing is kind of a dick move. Even the US military does a better job when it accidentally kills people!
The statements should come from the top, but should probably only be written by founders if they're actually good at this kind of thing.
There are a lot of companies who are relatively good at crisis communications with affected parties. Network carriers are often good (at least when talking to other networking professionals), although they often try to restrict the spread of information via NDA.
There are some reasons to limit disclosure immediately after an incident (if you think the vulnerability still exists and might put you at risk, especially for a security threat and not a regular outage). You absolutely want to include "why this won't happen again" in your message (which Arash kind of did this time), but you also want to accept blame at an emotional level -- you can do this in ways which make you look perfectionist and hyper-professional, vs. weak.
I don't actually care that much about Dropbox security myself, but if anyone in the cloud computing space fucks up badly enough and frequently enough to make users distrustful of cloud resources, it makes life harder for everyone else in the space. That is a problem for me, and for other startup founders.
- ra 15y agoif anyone in the cloud computing space fucks up badly enough and frequently enough to make users distrustful of cloud resources, it makes life harder for everyone else in the space That's exactly how I felt after the AWS outage. There was a slew of (incorrect) media reports about why cloud computing was inherently bad for your business.
- gjm11 15y ago> Even the US military does a better job when it accidentally kills people! What does the US military do when it perpetrates a boneheaded security screwup that might or might not have compromised a small amount of data belonging to a few people? (No question, Dropbox's response to this screwup is totally inadequate, but comparing it to how another organization responds when it has killed people is a bit silly.)
- rdl 15y agoI kind of view it the other way. Shooting someone for speeding toward your checkpoint who turns out to have actually been deaf or in a hurry to rush a sick kid to the hospital is sad, really bad for everyone, should be avoided if at all possible, etc. There are also a lot of liability and cultural concerns. If you're willing/able to make a real apology for that, it should be really easy to do so for something comparatively minor.