🖌️Michael E Porter - Collected Quotes

"The essence of formulating strategy is relating a company to its environment." (Michael E Porter, "Competitive Strategy", 1980)

"Risk is a function of how poorly a strategy will perform if the 'wrong' scenario occurs." (Michael EPorter, "Competitive Advantage: Creating and Sustaining Superior Performance", 1985)

"But the essence of strategy is in the activities – choosing to perform activities differently or to perform different activities than rivals. Otherwise, a strategy is nothing more than a marketing slogan that will not withstand competition." (Michael E Porter, "What is Strategy?", Harvard Business Review, 1996)

"Commonly, the threats to strategy are seen to emanate from outside a company because of changes in technology or the behavior of competitors. Although external changes can be the problem, the greater threat to strategy often comes from within. A sound strategy is undermined by a misguided view of competition, by organizational failures, and, especially, by the desire to grow." (Michael E Porter, "What is Strategy?", Harvard Business Review, 1996)

"Managers must clearly distinguish operational effectiveness from strategy. Both are essential, but the two agendas are different. The operational agenda involves continual improvement everywhere there are no trade-offs. Failure to do this creates vulnerability even for companies with a good strategy. The operational agenda is the proper place for constant change, flexibility, and relentless efforts to achieve best practice. In contrast, the strategic agenda is the right place for defining a unique position, making clear trade-offs, and tightening fit. It involves the continual search for ways to reinforce and extend the company’s position. The strategic agenda demands discipline and continuity; its enemies are distraction and compromise." (Michael E Porter, "What is Strategy?", Harvard Business Review, 1996)

"Strategy is creating fit among a company’s activities. The success of a strategy depends on doing many things well - not just a few - and integrating among them. If there is no fit among activities, there is no distinctive strategy and little sustainability. Management reverts to the simpler task of overseeing independent functions, and operational effectiveness determines an organization’s relative performance."  (Michael E Porter, "What is Strategy?", Harvard Business Review, 1996)

"Strategy renders choices about what not to do as important as choices about what to do. Indeed, setting limits is another function of leadership. Deciding which target group of customers, varieties, and needs the company should serve is fundamental to developing a strategy. But so is deciding not to serve other customers or needs and not to offer certain features or services. Thus strategy requires constant discipline and clear communication. Indeed, one of the most important functions of an explicit, communicated strategy is to guide employees in making choices that arise because of trade-offs in their individual activities and in day-to-day decisions." (Michael E Porter, "What is Strategy?", Harvard Business Review, 1996)

"There's a fundamental distinction between strategy and operational effectiveness. Strategy is about making choices, trade-offs; it's about deliberately choosing to be different. Operational effectiveness is about things that you really shouldn't have to make choices on; it's about what's good for everybody and about what every business should be doing."  (Michael E Porter, "What is Strategy?", Harvard Business Review, 1996)

🖌️Taiichi Ohno - Collected Quotes

"Autonomation [automation with a human touch] changes the meaning of management as well. An operator is not needed while the machine is working normally. Only when the machine stops because of an abnormal situation does it get human attention. As a result, one worker can attend several machines, making it possible to reduce the number of operators and increase production efficiency. [...] Implementing autonomation is up to the managers and supervisors of each production area. The key is to give human intelligence to the machine and, at the same time, to adapt the simple movement of the human operator to the autonomous machines." (Taiichi Ohno, "Toyota Production System: Beyond Large-Scale Production", 1978)

"Autonomation [..] performs a dual role. It eliminates overproduction, an important waste in manufacturing, and prevents the production of defective products. To accomplish this, standard work procedures, corresponding to each player's ability, must be adhered to at all times." (Taiichi Ohno, "Toyota Production System: Beyond Large-Scale Production", 1978)

"'Efficiency', in modern industry and business in general, means cost reduction." (Taiichi Ohno, "Toyota Production System: Beyond Large-Scale Production", 1978)

"Establishing (1) a production flow and (2) a way to maintain a constant supply of raw materials from outside for parts to be machined was the way the Toyota, or Japanese, production system should be operated." (Taiichi Ohno, "Toyota Production System: Beyond Large-Scale Production", 1978)

"I feel the most important point in common between sports and work is the continuing need for practice and training. It is easy to understand theory with the mind; the problem is to remember it with the body. The goal is to know and do instinctively. Having the spirit to endure the training is the first step on the road to winning." (Taiichi Ohno, "Toyota Production System: Beyond Large-Scale Production", 1978)

"In a production plant operation, data are highly regarded - but I consider facts to be even more important. When a problem arises, if our search for the cause is not thorough, the actions taken can be out of focus. This is why we repeatedly ask why. This is the scientific basis of the Toyota system." (Taiichi Ohno, "Toyota Production System: Beyond Large-Scale Production", 1978)

"Just-in-time means that, in a flow process, the right parts needed in assembly reach the assembly line at the time they are needed and only in the amount needed. A company establishing this flow throughout can approach zero inventory." (Taiichi Ohno, "Toyota Production System: Beyond Large-Scale Production", 1978)

"Needs and opportunities are always there. We just have to drive ourselves to find the practical ones." (Taiichi Ohno, "Toyota Production System: Beyond Large-Scale Production", 1978)

"The first rule of kanban is that the later process goes to the earlier process to pick up products. This rule was derived from need and from looking at things upside-down, or from the opposite standpoint." (Taiichi Ohno, "Toyota Production System: Beyond Large-Scale Production", 1978)

"We have eliminated waste by examining available resources, rearranging machines, improving machining processes, installing autonomous systems, improving tools, analyzing transportation methods, and optimizing the amount of materials at hand for machining. High production efficiency has also been maintained by preventing the recurrence of defective products, operational mistakes, and accidents, and by incorporating workers' ideas. All of this is possible because of the inconspicuous standard work sheet." (Taiichi Ohno, "Toyota Production System: Beyond Large-Scale Production", 1978)

"When the problem is clearly understood, improvement is possible." (Taiichi Ohno, "Toyota Production System: Beyond Large-Scale Production", 1978)

"When thinking about the absolute elimination of waste, keep the following two points in mind: (1) Improving efficiency makes sense only when it is tied to cost reduction. To achieve this, we have to start producing only the things we need using minimum manpower. (2) Look at the efficiency of each operator and of each line. Then look at the operators as a group, and then at the efficiency of the entire plant (all the lines). Efficiency must be improved at each step and, at the same time, for the plant as a whole." (Taiichi Ohno, "Toyota Production System: Beyond Large-Scale Production", 1978)

"Costs do not exist to be calculated. Costs exist to be reduced." (Taiichi Ohno) 

"Let the flow manage the processes, and not let management manage the flow." (Taiichi Ohno) 

"Knowledge is something you buy with the money. Wisdom is something you acquire by doing it." (Taiichi Ohno) 

"Machines do not break down; people cause them to break." (Taiichi Ohno) 

"People who can’t understand numbers are useless. […] However, people who only look at the numbers are the worst of all." (Taiichi Ohno) 

"The production line that never stops is either excellent or terrible." (Taiichi Ohno) 

"To understand means to be able to do." (Taiichi Ohno) 

🖌️Joseph M Juran - Collected Quotes

"It is most important that top management be quality-minded. In the absence of sincere manifestation of interest at the top, little will happen below." (Joseph M Juran, "Management of Inspection and Quality Control", 1945)

"Quality planning consists of developing the products and processes required to meet customer's needs." (Joseph M Juran, "Juran on planning for quality", 1988)

"Data are of high quality if they are fit for their intended use in operations, decision-making, and planning." (Joseph M Juran, 1964)

"Without a standard there is no logical basis for making a decision or taking action." (Joseph M Juran, "Managerial Breakthrough: The Classic Book on Improving Management Performance", 1995)

"'Benchmarking' is a recent label for the concept of setting goals based on knowing what has been achieved by others. A common goal is the requirement that the reliability of a new product be at least equal to that of the product it replaces and at least equal to that of the most reliable competing product. Implicit in the use of benchmarking is the concept that the resulting goals are attainable because they have already been attained by others." (Joseph M Juran, "The quality planning process", 1999)

"Customer satisfaction comes from those features which induce customers to buy the product. Dissatisfaction has its origin in deficiencies and is why customers complain."  (Joseph M Juran, "How to think about quality", 1999)

"Many quality failures arise because a customer uses the product in a manner different from that intended by the supplier." (Joseph M Juran, "The quality planning process", 1999)

"Quality goals that affect product salability should be based primarily on meeting or exceeding market quality. Because the market and the competition undoubtedly will be changing while the quality planning project is under way, goals should be set so as to meet or beat the competition estimated to be prevailing when the project is completed." (Joseph M Juran, "The quality planning process", 1999)

"'Quality' means freedom from deficiencies - freedom from errors that require doing work over again (rework) or that result in field failures, customer dissatisfaction, customer claims, and so on." (Joseph M Juran, "How to think about quality", 1999)

"‘Quality’ means those features of products which meet customer needs and thereby provide customer satisfaction." (Joseph M Juran, "How to think about quality", 1999)

"Quality planning generates a large amount of information that is both useful and necessary, but without a systematic way to approach the organization and analysis of this information, the planning team may be overwhelmed by the volume and miss the message it contains." (Joseph M Juran, "The quality planning process", 1999)

"The anatomy of 'quality assurance' is very similar to that of quality control. Each evaluates actual quality. Each compares actual quality with the quality goal. Each stimulates corrective action as needed. What differs is the prime purpose to be served. Under quality control, the prime purpose is to serve those who are directly responsible for conducting operations - to help them regulate current operations. Under quality assurance, the prime purpose is to serve those who are not directly responsible for conducting operations but who have a need to know - to be informed as to the state of affairs and, hopefully, to be assured that all is well." (Joseph M Juran, "How to think about quality", 1999)

"To attain quality, it is well to begin by establishing the 'vision' for the organization, along with policies and goals. Conversion of goals into results (making quality happen) is then done through managerial processes - sequences of activities that produce the intended results." (Joseph M Juran, "How to think about quality", 1999)

"When designing a product, there are actually two related but distinct aspects of what is being developed: the technology elements of what the product’s features will actually do or how it will function and the human elements of the benefits customers will receive from using the product. The two must be considered together." (Joseph M Juran, "The quality planning process", 1999)

"Goal setting has traditionally been based on past performance. This practice has tended to perpetuate the sins of the past." (Joseph M Juran)

"Improvement means the organized creation of beneficial change; the attainment of unprecedented levels of performance. A synonym is 'breakthrough.'"  (Joseph M Juran)

"Quality improvement should be directed at all areas that influence company performance - business processes as well as factory processes. Quality improvement should not be left solely to voluntary initiatives; it should be built into the system." (Joseph M Juran) 

"To achieve improvement at a revolutionary pace requires that improvement be made mandatory - that it become a part of a regular job, written into the job description."  (Joseph M Juran)

🖌️Russell L Ackoff - Collected Quotes

"Scientific models have all these connotations. They are representations of states, objects, and events. They are idealized in the sense that they are less complicated than reality and hence easier to use for research purposes. These models are easier to manipulate and 'carry' than the real thing. The simplicity of models, compared with reality, lies in the fact that only the relevant properties of reality are represented." (Russell L Ackoff, "Scientific method: optimizing applied research decisions", 1962)

"In most management problems there are too many possibilities to expect experience, judgement, or intuition to provide good guesses, even with perfect information." (Russell L Ackoff, Management Science, 1967)

"Managers need all the information they want. Most MIS designers 'determine' what information is needed by asking managers what information they would like to have. This is based on the assumption that managers know what information they need and want." (Russell L Ackoff, "Management Misinformation Systems", 1967)

"Most MIS [Management Information Systems] designers 'determine' what information is needed by asking managers what information they would like to have. This is based on the (often erroneous) assumption that managers know that information they need and want it." (Russell L Ackoff, Management Science, 1967)

"The less we understand a phenomenon, the more variables we require to explain it." (Russell L Ackoff, "Management Science", 1967)

"The systems approach to problems focuses on systems taken as a whole, not on their parts taken separately. Such an approach is concerned with total - system performance even when a change in only one or a few of its parts is contemplated because there are some properties of systems that can only be treated adequately from a holistic point of view. These properties derive from the relationship between parts of systems: how the parts interact and fit together." (Russell L Ackoff, "Towards a System of Systems Concepts", 1971) 

"Managers are not confronted with problems that are independent of each other, but with dynamic situations that consist of complex systems of changing problems that interact with each other. I call such situations messes. Problems are extracted from messes by analysis. Managers do not solve problems, they manage messes." (Russell L Ackoff, "The future of operational research is past", 1979)

"Data is raw. It simply exists and has no significance beyond its existence (in and of itself). It can exist in any form, usable or not. It does not have meaning of itself. In computer parlance, a spreadsheet generally starts out by holding data." (Russell L Ackoff, "Towards a Systems Theory of Organization, 1985)

"Information is data that has been given meaning by way of relational connection. This "meaning" can be useful, but does not have to be. In computer parlance, a relational database makes information from the data stored within it." (Russell L Ackoff, "Towards a Systems Theory of Organization", 1985)

"Knowledge is the appropriate collection of information, such that it's intent is to be useful. Knowledge is a deterministic process. When someone 'memorizes' information (as less-aspiring test-bound students often do), then they have amassed knowledge. This knowledge has useful meaning to them, but it does not provide for, in and of itself, an integration such as would infer further knowledge." (Russell L Ackoff, "Towards a Systems Theory of Organization", 1985)

"Information is data that has been given meaning by way of relational connection. This 'meaning' can be useful, but does not have to be. In computer parlance, a relational database makes information from the data stored within it." (Russell L Ackoff, "Towards a Systems Theory of Organization", 1985)

"Managers are incurably susceptible to panacea peddlers. They are rooted in the belief that there are simple, if not simple-minded, solutions to even the most complex of problems. And they do not learn from bad experiences. Managers fail to diagnose the failures of the fads they adopt; they do not understand them. […] Those at the top feel obliged to pretend to omniscience, and therefore refuse to learn anything new even if the cost of doing so is success." (Russell L Ackoff, "A Lifetime Of Systems Thinking", Systems Thinker, 1999)

"Managers cannot learn from doing things right, only from doing them wrong." (Russell L Ackoff, "A Little Book of F-laws: 13 common sins of management", 2006)

"The less sure managers are of their opinions, the more vigorously they defend them. Managers do not waste their time defending beliefs they hold strongly – they just assert them. Nor do they bother to refute what they strongly believe is false." (Russell L Ackoff, "A Little Book of F-laws: 13 common sins of management", 2006)

"The lower the rank of managers, the more they know about fewer things. The higher the rank of managers, the less they know about many things." (Russell L Ackoff, "A Little Book of F-laws: 13 common sins of management", 2006)

🖌️Harold Koontz - Collected Quotes

"[...] authority - the right by which superiors are able to require conformity of subordinates to decisions - is the basis for responsibility and the force that binds organization together. The process of organizing encompasses grouping of activities for purposes of management and specification of authority relationships between superiors and subordinates and horizontally between managers. Consequently, authority and responsibility relationships come into being in all associative undertakings where the superior-subordinate link exists. It is these relationships that create the basic character of the managerial job." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"Although organization charts are useful, necessary, and often revealing tools, they are subject to many important limitations. In the first place, a chart shows only formal authority relationships and omits the many significant informal and informational relationships that exist in a living organization. Moreover, it does not picture how much authority exists at any point in the organization." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"[...] authority for given tasks is limited to that for which an individual may properly he. held responsible." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"Authority delegations from a superior to a subordinate may be made in large or small degree. The tendency to delegate much authority through the echelons of an organization structure is referred tojas decentralization of authority. On the other hand, authority is said to be centralized wherever a manager tends not to delegate authority to his subordinates." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"Authority is, of course, completely centralized when a manager delegates none, and it is possible to think of the reverse situation - an infinite delegation of authority in which no manager retains any authority other than the implicit power to recover delegated authority. But this kind of delegation is obviously impracticable, since, at some point in the organization structure, delegations must stop." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"Essential to organization planning, then, is the search for an ideal form of organization to reflect the basic goals of the enterprise. This entails not only charting the main lines of organization and reflecting the organizational philosophy of the enterprise leaders (e.g., shall authority be as centralized as possible, or should the company try to break its operations down into semiautonomous product or territorial divisions?), but also a sketching out of authority relationships throughout the structure." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"If charts do not reflect actual organization and if the organization is intended to be as charted, it is the job of effective management to see that actual organization conforms with that desired. Organization charts cannot supplant good organizing, nor can a chart take the place of spelling out authority relationships clearly and completely, of outlining duties of managers and their subordinates, and of defining responsibilities." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"One of the tools for making organization principles work is the organization chart. Any organization which exists can be charted, for a chart is nothing more than an indication of how departments are tied together along their principal lines of authority." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"Responsibility cannot be delegated. While a manager may delegate to a subordinate authority to accomplish a service and the subordinate in turn delegate a portion of the authority received, none of these superiors delegates any of his responsibility. Responsibility, being an obligation to perform, is owed to one's superior, and no subordinate reduces his responsibility by assigning the duty to another. Authority may be delegated, but responsibility is created by the subordinate's acceptance of his assignment." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"Since a chart maps lines of authority, sometimes the mere charting of an organization will show inconsistencies and complexities and lead to their correction. A chart also acts as a guide for managers and new personnel in an organization, revealing how they tie into the entire structure. Charts are, therefore, not only evidences of organization planning but also road maps for decision making, and training devices for those who would learn how a company is organized." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"The essence of managership is the achievement of coordination among people. Coordination is a complex concept, including principles by which harmonious enterprise activity can be accomplished and the many techniques for achieving the greatest synchronized effort." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"The principle of direct contact! states that coordination must be achieved through interpersonal, horizontal relationships of people in an enterprise. People exchange ideas, ideals, prejudices, and purposes through direct personal communication much more efficiently than by any other method, and, with the understanding gained in this way, they find ways to achieve both common and personal goals." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"The primary purpose of delegation of authority is to make organization possible and to make it effective in accomplishing enterprise objectives and efficient in attaining them with the least cost of time and materials. Thus delegation - the vesting of a subordinate with a portion of his superior's authority - has as its principal purpose the creation of managerial jobs." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"Viewed internally with respect to the enterprise, responsibility may be defined as the obligation of a subordinate, to whom a superior has assigned a duty, to perform the service required. The essence of responsibility is, then, obligation. It has no meaning except as it is applied to a person." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"While good charting will attempt, as far as possible, to make levels on the chart conform to levels of importance in the business enterprise, it cannot always do so. This problem can be handled by clearly spelling out authority relationships." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"Another approach to management theory, undertaken by a growing and scholarly group, might be referred to as the decision theory school. This group concentrates on rational approach to decision-the selection from among possible alternatives of a course of action or of an idea. The approach of this school may be to deal with the decision itself, or to the persons or organizational group making the decision, or to an analysis of the decision process. Some limit themselves fairly much to the economic rationale of the decision, while others regard anything which happens in an enterprise the subject of their analysis, and still others expand decision theory to cover the psychological and sociological aspect and environment of decisions and decision-makers." (Harold Koontz, "The Management Theory Jungle," 1961)

"Every organization structure, even a poor one, can be charted, for a chart merely indicates how departments are tied together along the principal lines of authority. It is therefore somewhat surprising to find top managers occasionally taking pride in the fact that they do not have an organization chart or, if they do have one, feeling that the chart should be kept a secret." (Harold Koontz, "Principles of management", 1968)

"Management is defined here as the accomplishment of desired objectives by establishing an environment favorable to performance by people operating in organized groups." (Harold Koontz, "Principles of Management", 1968)

"Organization charts are subject to important limitations. A chart shows only formal authority relationships and omits the many significant informal and informational relationships." (Harold Koontz & Heinz Weihrich, "Essentials Of Management", 2006)

🖌️Kenichi Ohmae - Collected Quotes

"Analysis is the critical starting point of strategic thinking. Faced with problems, trends, events, or situations that appear to constitute a harmonious whole or come packaged as a whole by common sense of the day, the strategic thinker dissects them into their constituent parts. Then, having discovered the significance of these constituents, he reassembles them in a way calculated to maximize his advantage." (Kenichi Ohmae, "The Mind Of The Strategist", 1982) 

"In business as on the battlefield, the object of strategy is to bring about the conditions most favorable to one's own side, judging precisely the right moment to attack or withdraw and always assessing the limits of compromise correctly. Besides the habit of analysis, what marks the mind of the strategist is an intellectual elasticity or flexibility that enables him to come up with realistic responses to changing situations, not simply to discriminate with great precision among different shades of gray." (Kenichi Ohmae, "The Mind Of The Strategist", 1982)

"In strategic thinking, one first seeks a clear understanding of the particular character of each element of a situation and then makes the fullest possible use of human brainpower to restructure the elements in the most advantageous way. Phenomena and events in the real word do not always fit a linear model. Hence the most reliable means of dissecting a situation into its constituent parts and reassembling then in the desired pattern is not a step-by-step methodology such as systems analysis. Rather, it is that ultimate nonlinear thinking tool, the human brain. True strategic thinking thus contrasts sharply with the conventional mechanical systems approach based on linear thinking. But it also contrasts with the approach that stakes everything on intuition, reaching conclusions without any real breakdown or analysis." (Kenichi Ohmae, "The Mind Of The Strategist", 1982) 

"No matter how difficult or unprecedented the problem, a breakthrough to the best possible solution can come only from a combination of rational analysis, based on the real nature of things, and imaginative reintegration of all the different items into a new pattern, using nonlinear brainpower. This is always the most effective approach to devising strategies for dealing successfully with challenges and opportunities, in the market arena as on the battlefield." (Kenichi Ohmae, "The Mind Of The Strategist", 1982)

"Without competitors there would be no need for strategy." (Kenichi Ohmae, "The Mind of the Strategist", 1982)

🖌️John C Maxwell - Collected Quotes

"All great leaders have understood that their number one responsibility is cultivating their own discipline and personal growth. Those who cannot lead themselves cannot lead others." (John C Maxwell, "Developing the Leader Within You", 1993)

"The higher you want to climb, the more you need leadership. The greater the impact you want to make, the greater your influence needs to be. Whatever you will accomplish is restricted by your ability to lead others." (John C. Maxwell, "Leadership 101: What Every Leader Needs to Know", 2002)

"The true measure of leadership is influence - nothing more, nothing less." (John C Maxwell, Leadership 101: What Every Leader Needs to Know, 2002)

"Leadership is seeing the possibilities in a situation while others are seeing the limitations." (John C Maxwell, "The 21 Irrefutable Laws of Leadership", 2007)

"Personal and organizational effectiveness is proportionate to the strength of leadership." (John C Maxwell, "The 21 Irrefutable Laws of Leadership", 2007)

"The more intentional you are about your leadership growth, the greater your potential for becoming the leader you're capable of being. Never stop learning." (John C. Maxwell, "The Leadership Handbook", 2015)

🖌️Kaoru Ishikawa - Collected Quotes

"The fact must be expressed as data, but there is a problem in that the correct data is difficult to catch. So that I always say 'When you see the data, doubt it!' 'When you see the measurement instrument, doubt it!' [...]For example, if the methods such as sampling, measurement, testing and chemical analysis methods were incorrect, data. […] to measure true characteristics and in an unavoidable case, using statistical sensory test and express them as data." (Kaoru Ishikawa, Annual Quality Congress Transactions, 1981)

"As with many other things, there is a surprising amount of prejudice against quality control, but the proof of the pudding is still in the eating." (Kaoru Ishikawa, "Introduction to Quality Control", 1989)

"Quality control is applicable to any kind of enterprise. In fact, it must be applied in every enterprise." (Kaoru Ishikawa, "Introduction to Quality Control", 1989)

"90 percent of all problems can be solved by using the techniques of data stratification, histograms, and control charts. Among the causes of nonconformance, only one-fifth or less are attributable to the workers." (Kaoru Ishikawa, The Quality Management Journal Vol. 1, 1993)

"A standard which is not revised after six months of its establishment, indicates that it is not in use." (Kaoru Ishikawa)

"As long as your products or services are in the market, you should control their quality forever." (Kaoru Ishikawa)

"Basis of control is correct data and correct information. Eliminate false data." (Kaoru Ishikawa)

"Control charts do not exist for checking people. Rather, they are to be used for helping people to work successfully with ease." (Kaoru Ishikawa)

"Control determines predictability and reliability." (Kaoru Ishikawa)

"[Defining] organization is to clarify responsibilities and authority. Organization doesn’t simply involve setting up sections and groups. While authority should be delegated, responsibilities cannot be delegated." (Kaoru Ishikawa)

"Design a product by putting yourself in the shoes of its user." (Kaoru Ishikawa)

"Design without consideration of manufacturing method is not a design." (Kaoru Ishikawa)

"Eliminate causes rather than phenomena, and moreover, eliminate root causes to prevent recurrence." (Kaoru Ishikawa)

"Identify and work on topics which can help improving vertical communication and breaking sectionalism and barriers among different departments at an early stage." (Kaoru Ishikawa)

"Identify important problems, and make a focused attack on them together with others." (Kaoru Ishikawa)

"If an incident repeats for the same cause, then control is not being implemented." (Kaoru Ishikawa)

"If you do not conduct sufficient analysis and if you do not have firm technical knowledge, you cannot carry out improvement or standardization, nor can you perform good control or prepare control charts useful for effective control." (Kaoru Ishikawa)

"Importance of quality control increases with advancement in society and modernization in manufacturing." (Kaoru Ishikawa)

"In management, the first concern of the company is the happiness of people who are connected with it. If the people do not feel happy and cannot be made happy, that company does not deserve to exist." (Kaoru Ishikawa)

"It’s natural that progress of improvement activity in a large organization is not  uniform. If you hear the report saying that all the groups are progressing at the same pace, suspect there is something wrong about the report." (Kaoru Ishikawa)

"Make sure to improve quality, and after that, move on to reduce cost. This will finally lead you to reduce the delivery time." (Kaoru Ishikawa)

"Management based on the theory that man by nature is evil is costly in the first place, and besides, it makes everyone unhappy [...]" (Kaoru Ishikawa)

"Management without goals or objectives is impossible." (Kaoru Ishikawa)

"No matter how good quality information you may have, it is meaningless, if it is not communicated in time. Devise a system for communicating information to relevant departments/sections, as quickly as possible." (Kaoru Ishikawa)

"Quality assurance essentially involves, 1) presenting a document (such as specification), demonstrating the producer’s commitment to production of a product complying with such document, and 2) then delivering the product which complies with the document. It does not mean, 1) producing a product first, 2) testing the product and find its actual characteristics, and then offering a document which describes the testing results/characteristics." (Kaoru Ishikawa)

"Quality control is part of work for every employee and every department/section. It will be successful if all employees and all departments/sections cooperate." (Kaoru Ishikawa)

"Quality control starts and ends with training." (Kaoru Ishikawa)

"Standardization can progress and management can be conducted only when management policy is defined." (Kaoru Ishikawa)

"Standardization enables delegation of authority, allowing the top management and executives to have time to think about future plans and policy, which is their most important duty." (Kaoru Ishikawa)

"Standardize technology so that you may accumulate technology organically in your company." (Kaoru Ishikawa)

"Standardization is not only for quality control. It involves establishing standards for managing the business well as well as for all employees to enjoy their work with comfort." (Kaoru Ishikawa)

"Standardization without needs or clear objectives tends to become ritual." (Kaoru Ishikawa)

"The fact that standards are not revised demonstrates that your technology has stopped progressing." (Kaoru Ishikawa)

"The ideas of control and improvements are often confused with one another. This is because quality control and quality improvement are inseparable." (Kaoru Ishikawa)

"The key is to standardize every technically definable area, and leave what cannot be standardized to the skills." (Kaoru Ishikawa)

"There are two types of badness: one is badness of a system itself, while the other is badness of not following established rules and system precisely. It is important to correct the badness of not complying with rules first." (Kaoru Ishikawa)

"Think how you can accumulate skills of individuals in your company, and build the structure which will allow you to hand them over to the next generation when you are promoted to higher position." (Kaoru Ishikawa)

"Think of at least four factors which influence your problem. See if a shift in one of these causes can give you a different effect to explore." (Kaoru Ishikawa)

"Top management is responsible for demonstrating methods for evaluating quality as well as standards." (Kaoru Ishikawa)

"Understand the reality of the problem first, rather than wondering what its cause may be. The first step of problem solving is to understand the existing conditions." (Kaoru Ishikawa)

"Unless you have good understanding of problems and objectives, you cannot solve them." (Kaoru Ishikawa)

"When problems and objectives become clear, your problems are half solved." (Kaoru Ishikawa)

"When you think you have no problems, you will stop progressing, or rather, you will slip backward." (Kaoru Ishikawa)

"When you try to control, a natural course of event would be improvement, and when you try to carry out improvement, a natural course of event would be good understanding of importance of control." (Kaoru Ishikawa)

"You cannot standardize or control effectively without intrinsic technology." (Kaoru Ishikawa)

"You collect data for using them and for acting on them. Stop taking data which do not lead to actions." (Kaoru Ishikawa)

🖌️Peter M Senge - Collected Quotes

"Few, if any, forces in human affairs are as powerful as shared vision." (Peter M Senge, "The Fifth Discipline: The Art and Practice of the Learning Organization", 1990)

"In great teams, conflict becomes productive. The free flow of conflicting ideas is critical for creative thinking, for discovering new solutions no one individual would have come to on his own." (Peter M Senge, "The Fifth Discipline: The Art and Practice of the Learning Organization", 1990)

"Many leaders have personal visions that never get translated into shared visions that galvanize an organization. What has been lacking is a discipline for translating individual vision into shared vision." (Peter M Senge, "The Fifth Discipline: The Art and Practice of the Learning Organization", 1990)

"Personal mastery is the discipline of continually clarifying and deepening our personal vision, of focusing our energies, of developing patience, and of seeing reality objectively." (Peter M Senge, "The Fifth Discipline: The Art and Practice of the Learning Organization", 1990)

"Real learning gets to the heart of what it means to be human. Through learning we re-create ourselves. Through learning we become able to do something we never were able to do. Through learning we reperceive the world and our relationship to it. Through learning we extend our capacity to create, to be part of the generative process of life." (Peter M Senge, "The Fifth Discipline: The Art and Practice of the Learning Organization", 1990)

"Systems thinking is a discipline for seeing the 'structures' that underlie complex situations, and for discerning high from low leverage change. That is, by seeing wholes we learn how to foster health. To do so, systems thinking offers a language that begins by restructuring how we think." (Peter M Senge, "The Fifth Discipline: The Art and Practice of the Learning Organization", 1990)

"Systems thinking is a discipline for seeing wholes. It is a framework for seeing interrelationships rather than things, for seeing patterns of change rather than static 'snapshots'." (Peter M Senge, "The Fifth Discipline: The Art and Practice of the Learning Organization", 1990)

"Systems thinking is a framework for seeing interrelationships rather than things, for seeing patterns rather than static snapshots. It is a set of general principles spanning fields as diverse as physical and social sciences, engineering and management." (Peter M Senge, "The Fifth Discipline: The Art and Practice of the Learning Organization", 1990)

"The discipline of dialogue also involves learning how to recognize the patterns of interaction in teams that undermine learning. The patterns of defensiveness are often deeply engrained in how a team operates. If unrecognized, they undermine learning. If recognized and surfaced creatively, they can actually accelerate learning. Team learning is vital because teams, not individuals, are the fundamental learning unit in modern organizations. This where "the rubber meets the road"; unless teams can learn, the organization cannot learn." (Peter M Senge, "The Fifth Discipline: The Art and Practice of the Learning Organization", 1990)

"The organizations that will truly excel in the future will be the organizations that discover how to tap people's commitment and capacity to learn at all levels in an organization." (Peter M Senge, "The Fifth Discipline: The Art and Practice of the Learning Organization", 1990)

"The real leverage in most management situations lies in understanding dynamic complexity, not detail complexity. […] Unfortunately, most 'systems analyses' focus on detail complexity not dynamic complexity. Simulations with thousands of variables and complex arrays of details can actually distract us from seeing patterns and major interrelationships. In fact, sadly, for most people 'systems thinking' means 'fighting complexity with complexity', devising increasingly 'complex' (we should really say 'detailed') solutions to increasingly 'complex' problems. In fact, this is the antithesis of real systems thinking." (Peter M Senge, "The Fifth Discipline: The Art and Practice of the Learning Organization", 1990)

"We often spend so much time coping with problems along our path that we forget why we are on that path in the first place. The result is that we only have a dim, or even inaccurate, view of what's really important to us." (Peter M Senge, "The Fifth Discipline: The Art and Practice of the Learning Organization", 1990)

👷🏻Harold Kerzner - Collected Quotes

"The acceptance of project management has not been easy, however. Many executives are not willing to accept change and are inflexible when it comes to adapting to a different environment." (Harold Kerzner, "Project Management", 1979)

"There are always 'class or prestige' gaps between various levels of management. There are also functional gaps between working units of the organization. If we superimpose the management gaps on top of the functional gaps, we find that companies are made up of small operational islands that refuse to communicate with one another for fear that giving up information may strengthen their opponents. The project manager’s responsibility is to get these islands to communicate cross-functionally toward common goals and objectives." (Harold Kerzner, "Project Management: A systems approach to planning, scheduling, and controlling", 1979)

"There is no such thing as a good or bad organizational structure; there are only appropriate or inappropriate ones." (Harold Kerzner, "Project Management: A systems approach to planning, scheduling, and controlling", 1979)

"Project management is the planning, organizing, directing, and controlling of company resources for a relatively short-term objective that has been established to complete specific goals and objectives. Furthermore, project management utilises the systems approach to management by having functional personnel (the vertical hierarchy) assigned to a specific project (the horizontal hierarchy)." (Harold Kerzner, "Project Management for Executives", 1982)

"The acceptance of project management has not been easy, however. Many executives are not willing to accept change and are inflexible when it comes to adapting to a different environment." (Harold Kerzner, "Project Management for Executives", 1982)

"Project failures are not always the result of poor methodology; the problem may be poor implementation. Unrealistic objectives or poorly defined executive expectations are two common causes of poor implementation. Good methodologies do not guarantee success, but they do imply that the project will be managed correctly." (Harold Kerzner, "Strategic Planning for Project Management using a Project Management Maturity Model", 2001)

"Success or failure of a project depends upon the ability of key personnel to have sufficient data for decision-making. Project management is often considered to be both an art and a science. It is an art because of the strong need for interpersonal skills, and the project planning and control forms attempt to convert part of the 'art' into a science." (Harold Kerzner, "Strategic Planning for Project Management using a Project Management Maturity Model", 2001)

"Today, excellent companies realize that project failures have more to do with behavioral shortcomings - poor employee morale, negative human relations, low productivity, and lack of commitment." (Harold Kerzner, "In search of excellence in project management", 1998)

"Today, most project management practitioners focus on planning failure. If this aspect of the project can be compressed, or even eliminated, then the magnitude of the actual failure, should it occur, would be diminished. A good project management methodology helps to reduce planning failure. Today, we believe that planning failure, when it occurs, is due in large part to the project manager’s inability to perform effective risk management." (Harold Kerzner, "Strategic Planning for Project Management using a Project Management Maturity Model", 2001)

"When unmeetable expectations are formed, failure is virtually assured, since we have defined failure as unmet expectations. This is called a planning failure and is the difference between what was planned to be accomplished and what was, in fact, achievable. The second component of failure is poor performance or actual failure. This is the difference between what was achievable and what was actually accomplished." (Harold Kerzner, "Strategic Planning for Project Management using a Project Management Maturity Model", 2001)

"Project management is the art of creating the illusion that any outcome is the result of a series of predetermined, deliberate acts when, in fact, it was dumb luck." (Harold Kerzner, "Project Management: A Systems Approach to Planning, Scheduling, and Controlling", 2009)

👷🏻Kevin Forsberg - Collected Quotes

"A model is a representation of the real thing used to depict a process, investigate an opportunity or a risk, or evaluate an attribute. Properly constructed models are valuable tools because they focus attention on critical issues while stripping away less important details that tend to obscure what is needed to understand and to manage. Because they idealize a complex situation, a variety of different models can be constructed to represent the same situation. A useful model will be simple, but it must retain the essence of the situation to be managed [...]" (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"Being temporary, projects often bring together people unknown to each other. The newly formed group usually includes specialists motivated by the work itself and by their individual contributions. Teams of highly skilled technicians can make costly errors - even fatal ones - simply because the members fail to understand or internalize a systematic approach for applying best practices to project management. A major factor critical to project success is the availability of an effective and intuitive management process - one the group will quickly buy into and build their team upon." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"Developers often focus on what is possible technically regardless of the constraints of cost, a limiting schedule, or what the customer requires." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"Failure usually results from a lack of a common approach to accomplish the work as a team. Inadequate leadership fails to create the environment in which teams can flourish. Furthermore, potential team members are seldom trained in how to share their efforts to accomplish team goals. The team may also assume they know more about teamwork than they actually do. So we need to be able to differentiate between superficial teamwork and the real thing." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"In project management there are two levels of opportunities and risks. Because a project is the pursuit of an opportunity, the first category, the macro opportunity, is the project opportunity itself. The approach to achieving the project opportunity and the mitigation of associated project-level risks are structured into the strategy and tactics of the project cycle, the selected decision gates, the teaming arrangements, key personnel selected, and so on. The second level encompasses the tactical opportunities and risks within the project that become apparent at lower levels of decomposition and as project cycle phases are planned and executed. This can include emerging, unproven technology; incremental and evolutionary methods that promise high returns; and the temptation to circumvent proven practices in order to deliver better, faster, and cheaper." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"Opportunities and risks are endemic to the project environment. However well planned a project may be, there will always be residual project risk." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"Project failures can frequently be traced to unrealistic technical, cost, or schedule targets. Such targets may be entirely arbitrary or based on bad assumptions - setting team members up for failure. Furthermore, the goals that motivate one team member may not motivate another member. All tasks don’t have to be inherently motivating - that’s not sensible. But there have to be motivating factors, if by nothing more than participating in goal determination. This also helps ensure adequate opportunity and risk identification, analysis, and management." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"The appropriate models help avoid costly errors that can lead to failure. One of the major sources of project failure is f lawed requirements and scope management. Models of the project environment, therefore, need to address the development and management of project requirements. Continuing to work on the project solution with an insufficient understanding of stakeholder requirements and a deficient requirements development process often leads to expensive time delays and redesigns. This doesn’t have to be the case. A strong requirements development and management process model can provide that ounce of prevention." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"When we pursue opportunity, we normally incur risk. The opportunity to experience the thrill of an exciting sport like hang gliding or scuba diving brings with it the attendant risks. Many people instinctively make the trade that the thrill is worth the risks. Others decline." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"When we fail to grasp the systemic source of problems, we are left to treat symptoms rather than eliminate underlying causes. Without systemic thinking, the best we can ever do is adapt or react. Systems thinking, powered by visual models, stimulates creative - rather than adaptive - behavior. [...] To benefit from systems thinking, the project team needs to extend that viewpoint upward to the bigger picture of the project’s overall environment."(Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

👷🏻Phil Simon - Collected Quotes

"Adding more resources can have mixed results. If the right people are involved at the right time to perform tasks within their abilities, the benefits will outweigh the costs. However, adding more people will not always fix an issue and make up for lost time. There is no guarantee that these steps will put a project back on target." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"As a general rule, implementations do not just spontaneously combust. Failures tend to stem from the aggregation of many issues. Although some issues may have been known since the early stages of the project (for example, the sales cycle or system design), implementation teams discover the majority of problems during the middle of the implementation, typically during some form of testing." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"Implementation issues are not confined to the data and system realms. On the contrary, many of the problems encountered during a typical implementation stem from people, the roles they are required to play, political issues, and comfort zones." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"Implementing new systems is not like baking a cake. Organizations cannot follow a recipe with the following ingredients: three consultants, six weeks of testing, two training classes, and a healthy dose of project management. Nor do projects bake for six months until complete, after which time everyone enjoys a delicious piece of cake. For all sorts of reasons, a well-conceived and well-run project may fail, whereas a horribly managed project may come in under budget, ahead of schedule, and do everything that the vendor promised at the onset." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"Implementing new systems provides organizations with unique opportunities not only to improve their technologies, but to redefine and improve key business processes. Ultimately, for organizations to consider these new systems successes, the post-legacy environment must ensure that business processes, client end users, and systems work together." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"Organizations cannot expect new systems to concurrently deliver the benefits of integration and decentralization. By definition, more of one means less of another. Decide in advance the acceptable trade-offs, and live by those decisions." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"Organizations considering customizations should look carefully at their available options, ideally with the help of experienced business and technical consultants. It is imperative that they carefully consider the short- and long-term implications of these customizations, lest they be stuck with an unsustainable status quo and paint themselves into a corner." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"Organizations face challenges of all kinds after activating their new systems. To be sure, these challenges are typically not as significant as those associated with going live. Still, executives and end users should never assume that system activation means that everyone is home free. Systems are hardly self-sufficient, and issues always appear." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"Organizations often fail to understand that business processes do not exist in a vacuum; they must be viewed against the backdrop of the technology used to enable those processes. Systems and business processes are related in a symbiotic - but not causal - manner." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"Pre-implementation, post-implementation, and ongoing data audits are invaluable tools for organizations. Used judiciously by knowledgeable and impartial resources, audits can detect, avoid, and minimize issues that can derail an implementation or cause a live system to fail. Rather than view them as superfluous expenses, organizations would be wise to conduct them at key points throughout the system’s life cycle." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"Some end users are so accustomed to seeing data in a certain way that they insist that new reports present the data in a manner identical to legacy reports. This is a problem: no two systems represent data in the same manner." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"The best managed project may fail, whereas a horribly managed project may come in under budget, ahead of schedule, and do everything that the vendor promised at the onset. In reality, however, organizations are unlikely to find themselves in one of these extreme scenarios. On a fundamental level, successfully activating and utilizing a new system is about minimizing risk from day one until the end of the project and beyond. The organization that can do this stands the best chance of averting failure." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"Understanding the causes of system failures may help organizations avoid them, although there are no guarantees." (Phil Simon, "Why New Systems Fail: An Insider’s Guide to Successful IT Projects", 2010)

"Data science is an iterative process. It starts with a hypothesis (or several hypotheses) about the system we’re studying, and then we analyze the information. The results allow us to reject our initial hypotheses and refine our understanding of the data. When working with thousands of fields and millions of rows, it’s important to develop intuitive ways to reject bad hypotheses quickly." (Phil Simon, "The Visual Organization: Data Visualization, Big Data, and the Quest for Better Decisions", 2014)

"It’s a mistake to think of data and data visualizations as static terms. They are the very antitheses of stasis." (Phil Simon, "The Visual Organization: Data Visualization, Big Data, and the Quest for Better Decisions", 2014)

"Just because data is visualized doesn’t necessarily mean that it is accurate, complete, or indicative of the right course of action. Exhibiting a healthy skepticism is almost always a good thing." (Phil Simon, "The Visual Organization: Data Visualization, Big Data, and the Quest for Better Decisions", 2014)

"Metadata serves as a strong and increasingly important complement to both structured and unstructured data. Even if you can easily visualize and interpret primary source data, it behooves you to also collect, analyze, and visualize its metadata. Incorporating metadata may very well enhance your understanding of the source data." (Phil Simon, "The Visual Organization: Data Visualization, Big Data, and the Quest for Better Decisions", 2014)

"The term linked data describes the practice of exposing, sharing, and connecting pieces of data, information, and knowledge on the semantic Web. Both humans and machines benefit when previously unconnected data is connected." (Phil Simon, "The Visual Organization: Data Visualization, Big Data, and the Quest for Better Decisions", 2014)

"There are myriad questions that we can ask from data today. As such, it’s impossible to write enough reports or design a functioning dashboard that takes into account every conceivable contingency and answers every possible question." (Phil Simon, "The Visual Organization: Data Visualization, Big Data, and the Quest for Better Decisions", 2014)

"To be sure, data doesn’t always need to be visualized, and many data visualizations just plain suck. Look around you. It’s not hard to find truly awful representations of information. Some work in concept but fail because they are too busy; they confuse people more than they convey information [...]. Visualization for the sake of visualization is unlikely to produce desired results - and this goes double in an era of Big Data. Bad is still bad, even and especially at a larger scale." (Phil Simon, "The Visual Organization: Data Visualization, Big Data, and the Quest for Better Decisions", 2014)

"Visual Organizations benefit from routinely visualizing many different types and sources of data. Doing so allows them to garner a better understanding of what’s happening and why. Equipped with this knowledge, employees are able to ask better questions and make better business decisions." (Phil Simon, "The Visual Organization: Data Visualization, Big Data, and the Quest for Better Decisions", 2014)

"We acquire more information through our visual system than we do through all our other senses combined. We understand things better and quicker when we see them." (Phil Simon, "The Visual Organization: Data Visualization, Big Data, and the Quest for Better Decisions", 2014)

"We are all becoming more comfortable with data. Data visualization is no longer just something we have to do at work. Increasingly, we want to do it as consumers and as citizens. Put simply, visualizing helps us understand what’s going on in our lives - and how to solve problems." (Phil Simon, "The Visual Organization: Data Visualization, Big Data, and the Quest for Better Decisions", 2014)

"While critical, the arrival of Big Data is far from the only data-related trend to take root over the past decade. The arrival of Big Data is one of the key factors explaining the rise of the Visual Organization." (Phil Simon, "The Visual Organization: Data Visualization, Big Data, and the Quest for Better Decisions", 2014)

👷🏻James P Lewis - Collected Quotes

"A lot of people want to be managers, but many of them don’t want to manage." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"A methodology should be as simple as possible to get the job done. If you make the requirements a burden, rather than a help, then people will resist following them. You want to achieve a consistent, workable approach to managing projects, not hang a noose around the manager’s neck." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"A problem is defined as a gap between where you are and where you want to be that is confronted with obstacles that make closing the gap difficult. It is actually the obstacles that make the gap a problem." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"A project methodology must unambiguously specify what a manager must do to document, execute, and control a project. It must also specify what approvals are needed for various actions, such as procurement, changes to plan, budget variances, risks, and so on. It should tell who is responsible for various aspects of the project, and should spell out the limits of each stakeholder’s authority, responsibility, and accountability." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"[…] all activities are probabilistic, not deterministic! There is a probability that a task can be completed in a certain time, given a fixed level of effort. If you want to guarantee that the task is finished in a fixed time period, then you must vary effort, reduce scope, or sacrifice quality. You can’t have it all. Therefore, an exact estimate is an oxymoron." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"As a rule, it is best to separate discovery from development." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Choosing a proper project strategy can mean the difference between success and failure." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Control cannot be achieved through micromanaging." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Control is exercised by comparing progress against planned performance, and taking steps to correct for any deviations from the proper course." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Ensuring that you have a shared understanding of the mission, vision, and problem is the most important action you can take as a project manager." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Getting project management to work in an organization requires a change in culture." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"If you have no plan, you cannot have control, by definition, because it is your plan that tells where you are supposed to be in the first place. Further, if you don’t know where you are, you can’t have control. This comes from your information system. Most organizations have difficulties with both of these." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"If you treat people as though they are responsible, they tend to behave that way." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"In any system of humans or machines, the element in the system that has the greatest variability in its behavior will control the system." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"In general, two or three small projects are all one person should manage." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Management is proactive, not reactive" (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"No project can succeed when the team members have no commitment to the plan, so the first rule of project planning is that the people who must do the work should help plan that part of the project. You will not only gain their commitment to the plan, but also most likely cover all of the important issues that you may individually have forgotten."(James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Note that a project always begins as a concept, and a concept is usually a bit fuzzy. Our job as a team is to clarify the concept, to turn it into a shared understanding that the entire team will accept. It is failure to do this that causes many project failures." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Projects often fail at the beginning, not the end." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Projects seldom fail because of tools. They fail because of people!" (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"So the first stage in a project is to make sure you have correctly defined the problem being solved, that you have developed a vision for what the end result will be, and that you have stated your mission." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The big fallacy in our assumptions is that the world will stand still while we execute our project plan." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The difference between risks and threats is that a risk is something that can simply happen - an accident, act of nature, or missed deadline - whereas a threat is something that may be done by another entity." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The difference between strategy and tactics is that tactics get you down to the 'nitty-gritty' details of exactly how you are going to do the work." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The entire reason for managing a project is to make sure you get the results desired by the organization. This is commonly called being in control, and it is what is expected of a project manager." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The only time you ever get 80 percent availability from people is when they are tied to their work station, and the only people for whom this is true are factory workers. You may get close to 80 percent availability from them, but for knowledge workers - who aren’t tied to their work stations - you never get such a high level. It is more likely to be around 50 or 60 percent." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The only truly successful project is the one that delivers what it is supposed to, gets results, and meets stakeholder expectations." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The primary objective for a manager is to meet the needs of the organization while helping the followers meet their own needs in the process. To do this, you must help individuals find meaning in their work." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The self-fulfilling prophecy is one of the most important principles from psychology, at least for leaders. The principle is that you tend to get what you expect from others. Thus, if you expect poor performance from a person, you will tend to get it, and conversely." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The way a problem is defined determines how we attempt to solve it. […] If the definition is wrong, you will develop the right solution to the wrong problem." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The word culture designates the sum total of the values, attitudes, traditions, and behaviors that exist in an organization." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The word means a belief, or model of reality. A paradigm is what we believe to be true about any given situation, thing, or event. It is usually a deeply held conviction about how things actually are." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"You can’t delegate responsibility without giving a person authority commensurate with it." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

✒️John L Casti - Collected Quotes

"[…] a complex system is incomprehensible unless we can simplify it by using alternative levels of description." (John L Casti, "On System Complexity: Identification, Measurement, and Management" [in "Complexity, Language, and Life: Mathematical Approaches"] 1986)

"Coping with complexity involves the creation of faithful models of not only the system to be managed. but also of the management system itself." (John L Casti, "On System Complexity: Identification, Measurement, and Management" [in "Complexity, Language, and Life: Mathematical Approaches"] 1986)

"[…] complexity emerges from simplicity when alternative descriptions of a system are not reducible to each other. For a given observer, the more such inequivalent descriptions he or she generates, the more complex the system appears. Conversely, a complex system can be simplified in one of two ways: reduce the number of potential descriptions (by restricting the observer's means of interaction with the system) and/or use a coarser notion of system equivalence, thus reducing the number of equivalence classes." (John L Casti, "On System Complexity: Identification, Measurement, and Management" [in "Complexity, Language, and Life: Mathematical Approaches"] 1986)

"Simple systems generally involve a small number of components. with self-interaction dominating the mutual interaction of the variables. […] Besides involving only a few variables. simple systems generally have very few feedback/feedforward loops. Such loops enable the system to restructure. or at least modify. the interaction pattern of its variables. thereby opening-up the possibility of a wider range of potential behavior patterns." (John L Casti, "On System Complexity: Identification, Measurement, and Management" [in "Complexity, Language, and Life: Mathematical Approaches"] 1986)

"[…] a model is a mathematical representation of the modeler's reality, a way of capturing some aspects of a particular reality within the framework of a mathematical apparatus that provides us with a means for exploring the properties of the reality mirrored in the model." (John L Casti, "Reality Rules: Picturing the world in mathematics", 1992)

"Basically, the point of making models is to be able to bring a measure of order to our experiences and observations, as well as to make specific predictions about certain aspects of the world we experience." (John L Casti, "Reality Rules: Picturing the world in mathematics", 1992)

"Reliable information processing requires the existence of a good code or language, i.e., a set of rules that generate information at a given hierarchical level, and then compress it for use at a higher cognitive level. To accomplish this, a language should strike an optimum balance between variety (stochasticity) and the ability to detect and correct errors (memory)."(John L Casti, "Reality Rules: Picturing the world in mathematics", 1992)

"Skewness is a measure of symmetry. For example, it's zero for the bell-shaped normal curve, which is perfectly symmetric about its mean. Kurtosis is a measure of the peakedness, or fat-tailedness, of a distribution. Thus, it measures the likelihood of extreme values." (John L Casti, "Reality Rules: Picturing the world in mathematics", 1992)

"[…] the complexity of a given system is always determined relative to another system with which the given system interacts. Only in extremely special cases, where one of these reciprocal interactions is so much weaker than the other that it can be ignored, can we justify the traditional attitude regarding complexity as an intrinsic property of the system itself." (John L Casti, "Reality Rules: Picturing the world in mathematics", 1992)

"The core of a decision problem is always to find a single method that can be applied to each question, and that will always give the correct answer for each individual problem." (John L Casti, "Mathematical Mountaintops: The Five Most Famous Problems of All Time", 2001)

"[…] according to the bell-shaped curve the likelihood of a very-large-deviation event (a major outlier) located in the striped region appears to be very unlikely, essentially zero. The same event, though, is several thousand times more likely if it comes from a set of events obeying a fat-tailed distribution instead of the bell-shaped one." (John L Casti, "X-Events: The Collapse of Everything", 2012)

"[…] both rarity and impact have to go into any meaningful characterization of how black any particular [black] swan happens to be." (John L Casti, "X-Events: The Collapse of Everything", 2012)

"Due to the problem of predicting outlier events, they are not usually factored into the design of systems." (John L Casti, "X-Events: The Collapse of Everything", 2012)

"Forecasting models […] ordinarily are based only on past data, which is generally a tiny sample of the total range of possible outcomes. The problem is that those 'experts' who develop the models often come to believe they have mapped the entire space of possible system behaviors, which could not be further from the truth. Worse yet, when outliers do crop up, they are often discounted as 'once in a century' events and are all but ignored in planning for the future. […] the world is much more unpredictable than we’d like to believe."(John L Casti, "X-Events: The Collapse of Everything", 2012)

"If you want a system - economic, social, political, or otherwise - to operate at a high level of efficiency, then you have to optimize its operation in such a way that its resilience is dramatically reduced to unknown - and possibly unknowable - shocks and/or changes in its operating environment. In other words, there is an inescapable price to be paid in efficiency in order to gain the benefits of adaptability and survivability in a highly uncertain environment. There is no escape clause!" (John L Casti, "X-Events: The Collapse of Everything", 2012)

"Sustainability is a delicate balancing act calling upon us to remain on the narrow path between organization and chaos, simplicity and complexity." (John L Casti, "X-Events: The Collapse of Everything", 2012)

"The first path of increasing complexity via innovation often faces limits as to how much complexity can be added or reduced in a given system. This is because if you change the complexity level in one place, a compensating change in the opposite direction generally occurs somewhere else." (John L Casti, "X-Events: The Collapse of Everything", 2012)

"[…] the law of requisite complexity […] states that in order to fully regulate/control a system, the complexity of the controller has to be at least as great as the complexity of the system that’s being controlled. To put it in even simpler terms, only complexity can destroy complexity." (John L Casti, "X-Events: The Collapse of Everything", 2012)

"What is and isn’t complex depends to a large degree not only on a target system, but also on the system(s) the target interacts with, together with the overall context in which the interacting systems are embedded." (John L Casti, "X-Events: The Collapse of Everything", 2012)

✒️Jay W Forrester - Collected Quotes

"[System dynamics] is an approach that should help in important top-management problems [...] The solutions to small problems yield small rewards. Very often the most important problems are but little more difficult to handle than the unimportant. Many [people] predetermine mediocre results by setting initial goals too low. The attitude must be one of enterprise design. The expectation should be for major improvement [...] The attitude that the goal is to explain behavior; which is fairly common in academic circles, is not sufficient. The goal should be to find management policies and organizational structures that lead to greater success." (Jay W Forrester, "Industrial Dynamics", 1961)

"In complex systems cause and effect are often not closely related in either time or space. The structure of a complex system is not a simple feedback loop where one system state dominates the behavior. The complex system has a multiplicity of interacting feedback loops. Its internal rates of flow are controlled by nonlinear relationships. The complex system is of high order, meaning that there are many system states (or levels). It usually contains positive-feedback loops describing growth processes as well as negative, goal-seeking loops. In the complex system the cause of a difficulty may lie far back in time from the symptoms, or in a completely different and remote part of the system. In fact, causes are usually found, not in prior events, but in the structure and policies of the system." (Jay W Forrester, "Urban dynamics", 1969)

"Like all systems, the complex system is an interlocking structure of feedback loops [...] This loop structure surrounds all decisions public or private, conscious or unconscious. The processes of man and nature, of psychology and physics, of medicine and engineering all fall within this structure [...]" (Jay W Forrester, "Urban Dynamics", 1969)

"The structure of a complex system is not a simple feedback loop where one system state dominates the behavior. The complex system has a multiplicity of interacting feedback loops. Its internal rates of flow are controlled by non-linear relationships. The complex system is of high order, meaning that there are many system states (or levels). It usually contains positive-feedback loops describing growth processes as well as negative, goal-seeking loops." (Jay F Forrester, "Urban Dynamics", 1969)

"To model the dynamic behavior of a system, four hierarchies of structure should be recognized: closed boundary around the system; feedback loops as the basic structural elements within the boundary; level variables representing accumulations within the feedback loops; rate variables representing activity within the feedback loops." (Jay W Forrester, "Urban Dynamics", 1969)

"First, social systems are inherently insensitive to most policy changes that people choose in an effort to alter the behavior of systems. In fact, social systems draw attention to the very points at which an attempt to intervene will fail. Human intuition develops from exposure to simple systems. In simple systems, the cause of a trouble is close in both time and space to symptoms of the trouble. If one touches a hot stove, the burn occurs here and now; the cause is obvious. However, in complex dynamic systems, causes are often far removed in both time and space from the symptoms. True causes may lie far back in time and arise from an entirely different part of the system from when and where the symptoms occur. However, the complex system can mislead in devious ways by presenting an apparent cause that meets the expectations derived from simple systems." (Jay W Forrester, "Counterintuitive Behavior of Social Systems", 1995)

"Second, social systems seem to have a few sensitive influence points through which behavior can be changed. These high-influence points are not where most people expect. Furthermore, when a high-influence policy is identified, the chances are great that a person guided by intuition and judgment will alter the system in the wrong direction." (Jay W Forrester, "Counterintuitive Behavior of Social Systems", 1995)

"System dynamics models are not derived statistically from time-series data. Instead, they are statements about system structure and the policies that guide decisions. Models contain the assumptions being made about a system. A model is only as good as the expertise which lies behind its formulation. A good computer model is distinguished from a poor one by the degree to which it captures the essence of a system that it represents. Many other kinds of mathematical models are limited because they will not accept the multiple-feedback-loop and nonlinear nature of real systems." (Jay W Forrester, "Counterintuitive Behavior of Social Systems", 1995)

"Third, social systems exhibit a conflict between short-term and long-term consequences of a policy change. A policy that produces improvement in the short run is usually one that degrades a system in the long run. Likewise, policies that produce long-run improvement may initially depress behavior of a system. This is especially treacherous. The short run is more visible and more compelling. Short-run pressures speak loudly for immediate attention. However, sequences of actions all aimed at short-run improvement can eventually burden a system with long-run depressants so severe that even heroic short-run measures no longer suffice. Many problems being faced today are the cumulative result of short-run measures taken in prior decades." (Jay W Forrester, "Counterintuitive Behavior of Social Systems", 1995)

"No plea about inadequacy of our understanding of the decision-making processes can excuse us from estimating decision making criteria. To omit a decision point is to deny its presence - a mistake of far greater magnitude than any errors in our best estimate of the process." (Jay W Forrester, "Perspectives on the modelling process", 2000)