Meteor-proofing

From FreekiWiki
Revision as of 15:21, 12 April 2009 by Tonyc (talk | contribs)
Jump to navigation Jump to search

Designing an organizational system so that if any one element were to be wiped out--as in hit by a meteor--the system as a whole would continue to function.

Another way to describe this concept in computer terms would be: Making the elements of a system "hot-swappable." If one element fails, it could be replaced on-the-fly without causing major disruption to the overall function of the system.

A meteor-proof organization needs to include redundancy and transparency.

Redundancy may be achieved in many ways, including:

Cross-training Rotation of duties Trusting critical responsibilities to teams, rather than individuals.

Transparency is critical when the situation does not allow for a redundant solution. When the work cannot be shared, the knowledge is.

It is also important that work done by members of the organization be apparent. Work done "behind-the-scenes" hides the true cost of the operations. Additionally, when hidden work suddenly stops being done, it becomes apparent only when something fails.