5 ms·
Not sure this is something I’d be bragging about. What happens when you do eventually have a major outage and need to rapidly provide reassurance and tailored
by urbandw311er 4y ago
Not sure this is something I’d be bragging about. What happens when you do eventually have a major outage and need to rapidly provide reassurance and tailored support to hundreds of people. Like when Atlassian deleted thousands of JIRA tickets by mistake and seemed completely unprepared to scale up their support.
- trevor-e 4y agoIs that something you can reasonably prepare for as a company? Like just keep a bunch of extra support people on payroll in case there's a catastrophic event?
- speakfreely 4y agoIt's about not optimizing for a single variable. If you're trying to reduce headcount (and payroll cost) as a single goal, your business becomes a brittle shell subject to disruption by any number of circumstances. Investing in some redundancy is responsible to your shareholders and respectful to your customers.
- urbandw311er 4y agoWhat a great question. Perhaps the answer is “not entirely” but draw up some best effort contingency plans (pool of contractors, insurance cover, etc). I still wouldn’t be highlighting how few support staff I have per customer like this in either case!
- trevor-e 4y agoHa I definitely agree with you there. While impressive from the company's standpoint, I'm not sure it's something I'd highlight either. If anything, learning this would steer me away as a prospective client.