Plan for things to go wrong
Nathan Connors avatar
Written by Nathan Connors
Updated over a week ago

You’ve got to have one. A plan in place for sh*t going wrong. It’s not so much a plan, but a bit of common sense when it comes to working with technology.

And sh*t can be any number of things. It could be the way you’ve set something up not working as you had imagined/planned, a bug in the technology, a site going down. There are any number of things that can crop up unplanned, but what you can do is give yourself some room.

Our advice. Test, test and test some more, and give yourself, as well as your technology supplier some wriggle room.

Launching a major project at 5pm on a Friday is not the greatest idea and doesn’t get anyone into a Zen state for the weekend if something does go wrong.

Did this answer your question?