TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I think you ought to prepare a disaster recovery plan the same you carry out any technical writing task -- except that this time you get to design the product too:
Identify the audience -- the people who will have to implement
your plan.
Identify the key systems they need to restore. Find a balance
between what you'd like and what you can afford.
Figure out what preparations you need to make in advance
for restoration to be possible:
- What to prepare.
- How often to update it.
Analyze the tasks
- to carry out the advance preparations.
- to recover using the prepared materials.
Write a first draft of the plan.
Test the plan in a simulated disaster on your intended audience.
Iterate until you're happy.
Put the plan into practice with ongoing monitoring and frequent
review. Be alert for new systems or the obsolescence of formerly
important ones.
I hope that helps. ...RM
Richard Mateosian <srm -at- cyberpass -dot- net>
Review Editor, IEEE Micro Berkeley, CA
