- Whether to mention a pregnancy in a job interview
- A possible meeting protocol
- What are an end-user's responsibilities?
- Another take on opening PCs, or not
- Getting some process going
- Selling a more open environment to management
- Running an effective meeting
- Licensing rules for virtual machines
- The ROI of metrics
- Legal challenges to virtual machines
November 15, 2006 | Comments: (0)
Collapse and chaos theory
I don't normally post twice in one day, but I didn't want to lose the thought.
The past three Keep the Joint Running columns have been based on Jared Diamond's Collapse: How Societies Choose to Fail or Succeed (see "Collapsible business lessons," 11/6/2006). A friend, reading them, suggested that usually, negative feedback loops will act to prevent collapse.
That's when it occurred to me: The mathematics of negative feedback covers the Collapse effect nicely. It works like this: If you take the basic logistics equation (x at time (n+1) = max(rx(1-x),0)) and play with the parameters, you'll find that for a wide variety of conditions (so long as x is a fraction and r is less than 2.2 or so) you'll end up with a stable system.
Now, delay the feedback (make it x at time (n+2) or (n+3) = the formula). The result is that the system destabilizes - it grows unpredictably and wildly, then crashes to zero.
This is exactly what happens in Collapse situations: The factors that should lead to moderation of population growth don't happen immediately, and so they go unrecognized. The feedback is delayed, and the result is chaos and collapse.
The lesson is clear, really pretty obvious, and applies to a wide variety of situations: Make decisions based on current information, not what was true a year or two ago. Situations change, and if you don't notice the change, what you "know" is what used to be true, not what's true right now.
- Bob
Posted by Bob Lewis on November 15, 2006 06:42 AM
RATE THIS ARTICLE:
-

- COMMENTS
This is more or less the lesson of "Only the Paranoid Survive" by Andy Grove (of Intel). Over and over again he shows examples where the critical error is the failure to recognize a disruptive change as disruptive, and essentially makes the argument that you have to assume every change is disruptive, because if you wait for the evidence, it's too late.
Posted by: John Stork at November 15, 2006 11:29 AMThe problem with this approach is captured in the following classic line, where one pundit was speaking of another: "XXX has predicted 21 of the last 16 recessions."
Posted by: Joe Gwinn at November 15, 2006 12:35 PMAs you stated, for values of r2.2 (when there is a lot of financial pressure on the management team, for one example) the constant over-reactions can drive a business into the ground with overspending, over supply, under supply, etc. The effect on the business looks the same to those undergoing the swings. Mathematically, one business may survive one type of swing and and the same business will not survive the other, but it really doesn't matter - especially when public trust (brand loyalty, etc.) and investor confidence act as a forcing function.
Posted by: Anonymous at November 15, 2006 01:33 PMFrom study of negative feedback systems for an engineering degree, I learned the following:
To ensure a stable system, not only does the information you act upon have to be *current*, but your reaction to this information should not be *over-reactive*. This is because the information upon which you make decisions is NEVER perfect in the real world. It is always a bit out-of-date or contains errors.
Posted by: Mr. Ashley Jacobs at November 15, 2006 03:26 PMFrom study of negative feedback systems for an engineering degree, I learned the following:
To ensure a stable system, not only does the information you act upon have to be *current*, but your reaction to this information should not be *over-reactive*. This is because the information upon which you make decisions is NEVER perfect in the real world. It is always a bit out-of-date or contains errors.
Posted by: Mr. Ashley Jacobs at November 15, 2006 03:27 PMIn General System Theory, the conservation of a System is an Entrophy problem, in other words the interchange with the environment, in Social Systems (read Luhmann), is not only a problem of information or decision making is also a problem of Control and the selection of the variables to stablish a measure. The decision making is not the final step, the final step is the solution of the problem, and the generation of a new problem less bigger than the original.
Posted by: Mario Mayor at November 17, 2006 09:06 AMOkay, I'm feeling really behind the curve.
I've read "Collapse" and know a little something about feedback loops. If this educator and musician wanted to get more up-to-speed on the topics mentioned above, what's a good resource? Web sites? Book list? Major thinkers?
This area of thought seems important to my current job (process development, especially software development) and desired future job (public policy work), so I'm glad to spend some time on it.
Anyone?
|
Three books. Three ways to change the world, your life, or at least Bob Lewis' bank account. Leading IT: The Toughest Job in the World distills the world of IT leadership into eight learnable skills and gives you concrete, practical techniques for each one of them. Bare Bones Project Management: What you can't not do makes project management manageable, even for first-time project managers with no formal training in the discipline. ManagementSpeak: What managers say/What they mean … well, it won't help your career, and won't make you a better manager. Mostly, it will make you chuckle, guffaw, and maybe even chortle. Make friends - it's the perfect gift for anyone who has ever suffered through one of those meetings. Order your copies today! |
TOP STORIES
ADDITIONAL RESOURCES

- Virtualization: A Step by Step Approach to Success
- Dialing up Agility with Business Transformation
- 5 Things You Need to Know About Storage Virtualization

- Is your smaller organization ready for High Availability?
- Is system maintenance doing more harm than good?
- Virtual Test Lab Automation: Manage development infrastructure





