Meteor-proofing - Revision history

Tonyc at 04:43, 12 December 2013

2013-12-12T04:43:01Z

Mkille at 22:17, 24 September 2013

2013-09-24T22:17:17Z

Kathey at 01:19, 17 June 2009

2009-06-17T01:19:16Z

Tonyc: /* Transparency */

2009-04-13T21:47:27Z

Transparency

Tonyc at 07:06, 13 April 2009

2009-04-13T07:06:06Z

Tonyc at 06:53, 13 April 2009

2009-04-13T06:53:59Z

Tonyc: /* Transperancy */

2009-04-13T04:58:51Z

Transperancy

Tonyc: /* Transperancy */

2009-04-13T02:24:58Z

Transperancy

Tonyc at 02:22, 13 April 2009

2009-04-13T02:22:37Z

Tonyc at 23:28, 12 April 2009

2009-04-12T23:28:24Z

← Older revision		Revision as of 04:43, 12 December 2013
Line 1:		Line 1:
−	~~{{Delete}}~~
−
−
	This expression refers to 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 term refers to the distribution of tasks and responsibilities among human resources.		This expression refers to 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 term refers to the distribution of tasks and responsibilities among human resources.

← Older revision		Revision as of 22:17, 24 September 2013
Line 1:		Line 1:
		+	{{Delete}}
		+
		+
	This expression refers to 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 term refers to the distribution of tasks and responsibilities among human resources.		This expression refers to 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 term refers to the distribution of tasks and responsibilities among human resources.

← Older revision		Revision as of 01:19, 17 June 2009
Line 23:		Line 23:
	Moreover, when invisible work suddenly stops being done, it only becomes apparent when something fails catastrophically.		Moreover, when invisible work suddenly stops being done, it only becomes apparent when something fails catastrophically.

−	[[Category:Memes]]	+	[[Category: Memes]]
		+	[[Category: Big Picture]]

@@ Line 21: / Line 21: @@
 It is also important that work be visible. Work carried out "behind-the-scenes" hides the true cost of operations. This could cause a shock to the system when a worker suddenly disappears, and that worker's unknown contribution must be replaced, incurring an unbudgeted expense.
-Moreover, when invisible work suddenly stops being done, it will only become apparent when something fails catastrophically.
+Moreover, when invisible work suddenly stops being done, it only becomes apparent when something fails catastrophically.
 [[Category:Memes]]

@@ Line 1: / Line 1: @@
 This expression refers to 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 term refers to the distribution of tasks and responsibilities among human resources.
-The specific term is a more far-fetched (and therefore more palatable) version of being "hit by a bus."
+The term is a more far-fetched (and therefore more palatable) version of being "hit by a bus."
 Another way to describe this concept in Geek language 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.

@@ 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. Specifically, the terms specifically refers to the distribution of tasks and responsibilities among human resources.
+This expression refers to 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 term 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.
+The specific term is a more far-fetched (and therefore more palatable) version of being "hit by a bus."
 A meteor-proof organization needs to include redundancy and transparency in its design.
@@ Line 7: / Line 9: @@
 ==Redundancy==
-Functional redundancy may be achieved in many ways, among them:
+Redundancy of human resources could be achieved in many ways within an organization, among them:
 *Cross-training
-*Rotation of duties
+*Rotation of critical duties (similar to cross-training)
 *Trusting critical responsibilities to teams, rather than individuals.
 ==Transparency==
-Transparency is critical when the situation does not allow for a redundant solution.
+When the work, itself, cannot be shared, the knowledge regarding how to do the work should be. In general this is accomplished through documentation.
-When the work, itself, cannot be shared, the knowledge regarding how to do that work should be.
+It is also important that work be visible. Work carried out "behind-the-scenes" hides the true cost of operations. This could cause a shock to the system when a worker suddenly disappears, and that worker's unknown contribution must be replaced, incurring an unbudgeted expense.
-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.
+Moreover, when invisible work suddenly stops being done, it will only become apparent when something fails catastrophically.
 [[Category:Memes]]