17 June 2006

Yaneer Bar-Yamm - Collected Quotes

"A complex system is a system formed out of many components whose behavior is emergent, that is, the behavior of the system cannot be simply inferred from the behavior of its components. The amount of information necessary to describe the behavior of such a system is a measure of its complexity." (Yaneer Bar-Yamm, "Dynamics of Complexity", 1997)

"A dictionary definition of the word ‘complex’ is: ‘consisting of interconnected or interwoven parts’ […] Loosely speaking, the complexity of a system is the amount of information needed in order to describe it. The complexity depends on the level of detail required in the description. A more formal definition can be understood in a simple way. If we have a system that could have many possible states, but we would like to specify which state it is actually in, then the number of binary digits (bits) we need to specify this particular state is related to the number of states that are possible." (Yaneer Bar-Yamm, "Dynamics of Complexity", 1997)

"Many of the systems that surround us are complex. The goal of understanding their properties motivates much if not all of scientific inquiry. […] all scientific endeavor is based, to a greater or lesser degree, on the existence of universality, which manifests itself in diverse ways. In this context, the study of complex systems as a new endeavor strives to increase our ability to understand the universality that arises when systems are highly complex." (Yaneer Bar-Yamm, "Dynamics of Complexity", 1997)

"There are two approaches to organizing the properties of complex systems that will serve as the foundation of our discussions. The first of these is the relationship between elements, parts and the whole. Since there is only one property of the complex system that we know for sure - that it is complex - the primary question we can ask about this relationship is how the complexity of the whole is related to the complexity of the parts. […] The second approach to the study of complex systems begins from an understanding of the relationship of systems to their descriptions. The central issue is defining quantitatively what we mean by complexity."  (Yaneer Bar-Yamm, "Dynamics of Complexity", 1997)

"When the behavior of the system depends on the behavior of the parts, the complexity of the whole must involve a description of the parts, thus it is large. The smaller the parts that must be described to describe the behavior of the whole, the larger the complexity of the entire system. […] A complex system is a system formed out of many components whose behavior is emergent, that is, the behavior of the system cannot be simply inferred from the behavior of its components." (Yaneer Bar-Yamm, "Dynamics of Complexity", 1997)

"A fundamental reason for the difficulties with modern engineering projects is their inherent complexity. The systems that these projects are working with or building have many interdependent parts, so that changes in one part often have effects on other parts of the system. These indirect effects are frequently unanticipated, as are collective behaviors that arise from the mutual interactions of multiple components. Both indirect and collective effects readily cause intolerable failures of the system. Moreover, when the task of the system is intrinsically complex, anticipating the many possible demands that can be placed upon the system, and designing a system that can respond in all of the necessary ways, is not feasible. This problem appears in the form of inadequate specifications, but the fundamental issue is whether it is even possible to generate adequate specifications for a complex system." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"Complex problems are the problems that persist - the problems that bounce back and continue to haunt us. People often go through a series of stages in dealing with such problems - from believing they are beyond hope, to galvanizing collective efforts of many people and dollars to address the problem, to despair, retreat, and rationalization." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"Emergence refers to the relationship between the details of a system and the larger view. Emergence does not emphasize the primary importance of the details or of the larger view; it is concerned with the relationship between the two. Specifically, emergence seeks to discover: Which details are important for the larger view, and which are not? How do collective properties arise from the properties of parts? How does behavior at a larger scale of the system arise from the detailed structure, behavior and relationships on a finer scale?" (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"Engineers use abstraction to simplify the description or specification of the system, extracting the properties of the system they find most relevant and ignoring other details. While this is a useful tool, it assumes that the details that will be provided to one part of the system (module) can be designed independently of details in other parts."  (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"Modularity, an approach that separates a large system into simpler parts that are individually designed and operated, incorrectly assumes that complex system behavior can essentially be reduced to the sum of its parts. A planned decomposition of a system into modules works well for systems that are not too complex. […] However, as systems become more complex, this approach forces engineers to devote increasing attention to designing the interfaces between parts, eventually causing the process to break down."  (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"The basic idea of systems engineering is that it is possible to take a large and highly complex system that one wants to build, separate it into key parts, give the parts to different groups of people to work on, and coordinate their development so that they can be put together at the end of the process. This mechanism is designed to be applied recursively, so that we separate the large system into parts, then the parts into smaller parts, until each part is small enough for one person to execute. Then we put all of the parts together until the entire system works." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"The collapse of a particular project may appear to have a specific cause, but an overly high intrinsic complexity of these systems is a problem common to many of them. A chain always breaks first in one particular link, but if the weight it is required to hold is too high, failure of the chain is guaranteed." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"The complexity of each individual or organization must match the complexity of the task each is to perform. When we think about a highly complex problem, we are generally thinking about tasks that are more complex than a single individual can understand. Otherwise, complexity is not the main issue in solving it. If a problem is more complex than a single individual, the only way to solve it is to have a group of people - organized appropriately - solve it together. When an organization is highly complex it can only function by making sure that each individual does not have to face the complexity of the task of the organization as a whole. Otherwise failure will occur most of the time." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"The complexity of engineering projects has been increasing, but this is not to say that this complexity is new. Engineers and managers are generally aware of the complexity of these projects and have developed systematic techniques that are often useful in addressing it. Notions like modularity, abstraction, hierarchy and layering allow engineers to usefully analyze the complex systems they are working with. At a certain level of interdependence, though, these standard approaches become ineffective." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"The most basic issue for organizational success is correctly matching a system’s complexity to its environment. When we want to accomplish a task, the complexity of the system performing that task must match the complexity of the task. In order to perform the matching correctly, one must recognize that each person has a limited level of complexity. Therefore, tasks become difficult because the complexity of a person is not large enough to handle the complexity of the task. The trick then is to distribute the complexity of the task among many individuals." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"There is a dual nature to engineering. Engineers are responsible for careful quantitative evaluation of how to achieve objectives, what to do to achieve them, and even (a task that most people find almost impossible) how long it will take to do the task. The other side of engineering is an independent creative 'cowboy'-type attitude characteristic of people breaking out of the mold, coming up with novel ideas, implementing them, and changing the world through new technology. This is the culture of high-tech innovation." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"There is no doubt that science has made great progress by taking things apart, but it has become increasingly clear that many important questions can only be addressed by thinking more carefully about relationships between and amongst the parts. Indeed, one of the main difficulties in answering questions or solving problems - any kind of problem - is that we think the problem is in the parts, when it is really in the relationships between them." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"What do people do today when they don’t understand 'the system'? They try to assign responsibility to someone to fix the problem, to oversee 'the system', to coordinate and control what is happening. It is time we recognized that 'the system' is how we work together. When we don’t work together effectively putting someone in charge by its very nature often makes things worse, rather than better, because no one person can understand 'the system' well enough to be responsible. We need to learn how to improve the way we work together, to improve 'the system' without putting someone in charge, in order to make things work." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"What is the solution to coordinating people to perform complex tasks? Analyzing the flows of information and the way tasks are distributed through the system can help. ultimately, however, the best solution is to create an environment where evolution can take place. Organizations that learn by evolutionary change create an environment of ongoing innovation. Evolution by competition and cooperation and the creation of composites of patterns of behavior is the way to synthesize effective systems to meet the complex challenges of today’s world." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"When parts are acting independently, the fine scale behavior is more complex. When they are working together, the fine scale complexity is much smaller, but the behavior is on a larger scale. This means that complexity is always a trade-off, more complex at a large scale means simpler at a fine scale. This trade-off is a basic conceptual tool that we need in order to understand complex systems." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004) 

No comments:

Related Posts Plugin for WordPress, Blogger...

About Me

My photo
IT Professional with more than 24 years experience in IT in the area of full life-cycle of Web/Desktop/Database Applications Development, Software Engineering, Consultancy, Data Management, Data Quality, Data Migrations, Reporting, ERP implementations & support, Team/Project/IT Management, etc.