A design firm, Friday evening
The weekend restore
The challenge. On Friday at six, the firm’s file server stops opening drawings and a note appears on the screen. The partners call the IT provider, who is willing but asks who is allowed to approve shutting down the network, whether the backups are good, and whom the firm has to tell. Nobody has the answers written down.
The insight. A bad weekend is mostly a question of decisions made in advance. Recovery speed depends on three things: backups that have been restored on purpose, a short list of who decides what, and a record of which systems matter most and in what order they come back.
The decision. After the weekend, the partners decided to write the plan, test it, and give it a yearly date, rather than hope the next one would go better.
The action. We listed the firm’s systems in the order the business needs them, set a recovery time for each and wrote one-page roles for the partners, the IT provider and the office manager. The IT provider moved a backup copy somewhere the network cannot change it and ran a full restore, which we timed and recorded. We then ran a two-hour tabletop with the partners using a made-up Friday evening, and fixed the six places where the plan was unclear.
The result. The firm now knows how long its drawings take to come back, who calls whom first, and which notices it owes under its contracts and the law. The plan is shorter than before and has been used in rehearsal.