Essentially, projects are the target for
doom, not day-to-day activities.
If you keep the focus of disaster recovery planning to a day-to-day activity (I believe
it should be an ongoing job role of a DBA), the likelihood that it will have the gravity to
attract the attention of a doomsayer is low. Keep the process iterative, and reduce any specific
requests for resources (whether personnel or financial) to a minimum. Doomsayers
probably won??™t see a risk to productivity (or at least other risks will take precedence).
Should a doomsayer be directly involved in disaster recovery planning and declare
a mark of doom, you must react in two ways. First, don??™t argue or downplay the objection
raised (unless it??™s without merit, in which case this isn??™t a doomsayer that you??™re dealing
with, but a simple miscreant). Acknowledge that the objection is valid. Second, start a
dialog about how the objection should be handled. Shutting things down completely is
only one approach. When beginning that dialog, say to the doomsayer, ???That??™s an excellent
point. What would you suggest we do instead???? Doomsayers are rational, albeit a bit
defeatist in their viewpoints.
Pages:
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553