Andy Osborne's blog from last week was truly timely: I've just been assigned a new task by my boss: Take a recovery management plan done for one company site, and sinter it down into a suitable "template" for other "small" company sites. The task has already shown indications of Andy's experience: the work done by predecessors causing more work. It's not that wrong things were written, but the document doesn't "flow" like a plan should. I beieve a "plan" is like a recipe, only longer and without the rewarding aroma to savor at the end. ;-)
Of the many kinds of plans I've seen over my years in this profession, few really read like a recipe, rather more like a cross between a dictionary with a mixture of random essays. No flow. But this time, I feel much better about the prospects, because the plan I'm to use as the starting point has, on one of the early pages after the Table of Contents, a FLOW CHART!!! It has been my contention since my earliest months in this business, that recovery is a process, meaning it must flow - start at Square One and start marching until you're done.
Perhaps, if you've found yourslef feeling like your plan lacks something, maybe it needs some improvement in its flow. Developing recovery plans can't (easily) effect a timely recovery without flow, because no matter how many people you throw at the disruption, the lack of flow will have them bumping into one another.