Difference between revisions of "Meteor-proofing"
| Line 1: | Line 1: | ||
| − | 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. | + | 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. Specifically, the terms specifically refers to the distribution of tasks and responsibilities among human resources. |
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. | 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. | + | A meteor-proof organization needs to include redundancy and transparency in its design. |
| − | Redundancy may be achieved in many ways, | + | ==Redundancy== |
| + | |||
| + | Functional redundancy may be achieved in many ways, among them: | ||
*Cross-training | *Cross-training | ||
*Rotation of duties | *Rotation of duties | ||
*Trusting critical responsibilities to teams, rather than individuals. | *Trusting critical responsibilities to teams, rather than individuals. | ||
| + | |||
| + | ==Transperancy== | ||
Transparency is critical when the situation does not allow for a redundant solution. When the work cannot be shared, the knowledge regarding how to do that work is. | Transparency is critical when the situation does not allow for a redundant solution. When the work cannot be shared, the knowledge regarding how to do that work is. | ||
Revision as of 19:22, 12 April 2009
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. Specifically, the terms specifically refers to the distribution of tasks and responsibilities among human resources.
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 in its design.
Redundancy
Functional redundancy may be achieved in many ways, among them:
- Cross-training
- Rotation of duties
- Trusting critical responsibilities to teams, rather than individuals.
Transperancy
Transparency is critical when the situation does not allow for a redundant solution. When the work cannot be shared, the knowledge regarding how to do that work is.
It is also important that work done by members of the organization be apparent. Work carried out "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.