“… the organization chart will initially reflect the first system design, which is almost surely not the right one [… ] as one learns, he changes the design [… ]. Management structures also need to be changed as the system changes…”

—  Fred Brooks

The Mythical Man-Month: Essays on Software Engineering (1975, 1995)

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "… the organization chart will initially reflect the first system design, which is almost surely not the right one [… ] …" by Fred Brooks?
Fred Brooks photo
Fred Brooks20
American computer scientist 1931

Related quotes

Rensis Likert photo

“The management system of an organization must have compatible component parts if it is to function effectively. This conclusion has a very important implication; experiments in organizations must involve internally consistent changes. The traditional atomistic research design is not appropriate for experiments involving organizational theory or management systems. Every aspect of a management system is related to every other part and interacts with it.
The results obtained by altering a single variable or procedure while keeping all others the same usually will yield quite different results from those obtained when that variable is changed along with simultaneous and compatible changes in all other aspects of the management system. The true influence of altering one aspect of the system cannot be determined by varying it and it alone… In experiments involving organizational theory and management systems, therefore, a systems approach must be used. The organic integrity of each system must be maintained while experimental variations are being made.”

Rensis Likert (1903–1981) American statistician

Source: The Human Organization, 1967, p. 123

“Changes in the inhabitants of the earth do not reflect a constant process of improvement in the design of organisms, any more than changes in fashion over the years reflect a constant process of improvement in the quality of clothing.”

Steve Stewart-Williams (1971)

Source: Darwin, God and the Meaning of Life: How Evolutionary Theory Undermines Everything You Think You Know (2010), p. 173

“The formal administrative design can never adequately or fully reflect the concrete organization to which it refers, for the obvious reason that no abstract plan or pattern can—or may, if it is to be useful—exhaustively describe an empirical totality. At the same time, that which is not included in the abstract design (as reflected, for example, in a a staff and-line organization chart) is vitally relevant to the maintenance and development of the formal system itself.”

Philip Selznick (1919–2010) American sociologist

Source: "Foundations of the Theory of Organization," 1948, p. 25

“Systems don't need to be changed. The trick is for a trader to develop a system with which he is compatible.”

Ed Seykota (1946) American commodities trader

Source: Schwager, Jack D., Market Wizards, HarperCollins (1989), page 159, ISBN 0-88730-610-1

Ram Dass photo

“As one individual changes, the system changes.”

Ram Dass (1931–2019) American contemporary spiritual teacher and the author of the 1971 book Be Here Now

George Orwell photo

“One's got to change the system, or one changes nothing.”

George Orwell book Keep the Aspidistra Flying

Source: Keep the Aspidistra Flying (1936), Ch. 10

“The software architecture of a system or a family of systems has one of the most significant impacts on the quality of an organization's enterprise architecture. While the design of software systems concentrates on satisfying the functional requirements for a system, the design of the software architecture for systems concentrates on the nonfunctional or quality requirements for systems. These quality requirements are concerns at the enterprise level. The better an organization specifies and characterizes the software architecture for its systems, the better it can characterize and manage its enterprise architecture. By explicitly defining the systems software architectures, an organization will be better able to reflect the priorities and trade-offs that are important to the organization in the software that it builds.”

Scott W. Ambler (1966) Canadian software engineer/consultant/author

James McGovern, Scott W. Ambler and M. E Stevens (2004) A Practical Guide to Enterprise Architecture. p. 35

“There are four distinct bases on which a system-design book might be organized. First are the chronological phases through which the system-design effort passes, such as organization and preliminary design. Second are the logical steps such as analysis of the single thread (operation on a single input) and high traffic (methods of handling multiplex inputs). Third are the parts of the system, such as communications and displays. Fourth are the tools of system design, such as information theory and queueing theory.”

Robert E. Machol (1917–1998) American systems engineer

Source: System Engineering (1957), p. 8

“Experienced object designers explore the design space from many different angles. They refine ideas of how their system should respond while they are in the middle of building and discarding ideas about how their design should work. Getting a design to gel involves making assumptions, seeing how they play out, changing one’s mind or perspective slightly and re-iterating. Design is a difficult, involved task. It inherently is a non-linear process. Yet, we are asked to trace our design results back to system requirements. And, if we uncover some implications during design, we’d like to tune our system requirements to reflect necessary design compromises.”

Rebecca Wirfs-Brock (1953) American software engineer

Abstract
Designing scenarios: Making the case for a use case framework (1993)

“A perennial problem of any organization which is involved in systems work of a changing nature is the need for the organization itself to change as it adapts to new opportunities, new objectives, new equipment, and new people.”

Harold Chestnut (1917–2001) American engineer

Source: Systems Engineering Tools, (1965), Systems Engineering Methods (1967), p. 119

Related topics