In the technology industry, everything depends to some degree on our machines and software. We'd be lost without our computers. And when you get down to it, it's astonishing how many parts of a business can fit inside 100 sq. inches of polycarbonate and aluminum. You have applications, stored data, and time-sensitive projects that depend on a functioning system. So what happens when that system isn't working right?
Step 1: Get to the doctor
We're Mac users through and through. One of the (many) perks to that is our access to Apple techs and AppleCare plans. As half our company has been employed by Apple in the past, there's a lot we can troubleshoot and fix in-house. Sometimes it isn't worth the time though, and sometimes we just don't know what's up with the hardware.
Step 2: Find yourself a temp
And I don't mean the Ryan Howard type (although, sure, why not... do that too). But if your computer repair is going to take a couple days, you probably need a temporary computer. You have partners, clients, and a team depending on you. Calling off and watching The Office won't be an option.
If you're a small business like we are, you can't just phone staff to order a new MacBook. So what do you do? Get back into your survival mindset. Can you get by with a barebones machine for a day or two by altering your approach? If you don't have a viable system to borrow, it may be possible to buy one with the intention to return it when yours is good to go again. Get creative. Be scrappy if you need to be. Just please don't steal anything, you animals.
Step 3: Transfer your backups
We back our data up with Backblaze. Wherever you store a copy of your data, make sure its accessible in a crunch. Probably preaching to the choir here too, but make sure you have a copy in the cloud. Nothing worse than having your only backup on an SSD and then watching that glitch out at the same time as your machine.
By way of example, a graphics card malfunctioned on one of our laptops recently. After taking it in, finding a temporary replacement, and syncing it up with Backblaze, our developer was only behind by half a day. That's pretty ideal.
Step 4: Communicate on shifting timelines
Shit happens. Most people understand this. If you're going to miss a deadline because of equipment failure, be candid with your partners about that. Explain the situation and how you've remedied it to the best of your ability. Reset expectations and then get to work however you can for the time being.
The Bottomline:
As great as it would be if everything came right down the center of the plate, technology throws the occasional curve ball. Be prepared for it, roll with it when it comes, and try to connect with a solution that involves transparent communication about realistic adjustments. Ultimately, it's just one curveball, and probably not the end of the world.
