Home

Pflogging

the never-ending quest for pragmatic solutions, useful plans, flawless execution, and designs that endure
Home

User login

  • Create new account
  • Request new password

A number of key features are only available to registered users. They include:

  • Access to the full content of top-rated material (only teasers are available to anonymous users after the material has been posted for 45 days)
  • The ability to search site content
  • The ability to access reviews of books relevant to site material
  • The ability to access key quotes relevant to site material
  • The ability to access content from partner sites
  • The ability to rate material
  • The ability to post comments
  • The ability to post new information and propose it for publication
  • The ability to request email notification when selected content is added or updated

Negative synergy

  • View
  • links
Submitted by Bryan Pflug on Sun, 02/18/2007 - 08:53

Synergy is frequently used in the context of 'the whole isĀ greater thanĀ the sum of the parts.' Obviously, this is not always true, especially on projects. For example, in the mechanical mental model that people so often have, components are replaceable, they act independently of one another, and all behavior can be scripted in simplistic terms. The world is a far more complicated place than that.

This article analyses the symptoms and trends in which 'negative synergy' can occur on projects. In such situations, not only is the whole less than the parts you don't have, it's dramatically so.

  • The terrain is not the map
  • A chain is as weak as it's weakest link
  • Belief is a tipping point
  • The architecture compartmentalizes knowledge and action
    • communications rarely occurs
    • key states and interactions ripple across systems
    • initialization and recovery behaviors
    • throughput, timing, and race conditions
    • analysis of failures
0
Your rating: None
  • Login or register to post comments