Failure quotes

From Motley Bytes Wiki
Jump to: navigation, search

Contents

Christopher_Wolfgang_Alexander

Time for Equilibrium

“Misfit provides an incentive to change; good fit provides none. In theory the process is eventually bound to reach the equilibrium of well-fitting forms. However, for the fit to occur in practice, one vital condition must be satisfied. It must have time to happen. The process must be able to achieve equilibrium before the next culture change upsets it again... The direct response is the feedback of the process. If the process is to maintain the good fit ... while the culture drifts, it needs a feedback sensitive enough to take action the moment that one of the potential failures actually occurs.”

Robert_N_Britcher

Limits of Testing

“The limits of software are never more obvious than in its testing. Software systems are beyond discrete and statistical analysis. A single incorrect state - out of two to the trillionth states - can down a rocket: To find such a fault in a software system would require a hundred generations of programmers - but after the first failure is found and fixed, all bets are off; they wouldn't be testing the same system anymore. We can design and build fail-safe systems, but can we know we did?”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 56.

Sources of Failures

“I never ran a test that didn't find at least one failure - not only is the software impure, but so are the requirements specifications. And every time we fix the software, there is a 10 percent chance - according to my anecdotal studies - we'll inject another fault. Those are the hardest to find: the faults that result from trying to get rid of them.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 56.

Failure Probability

“The probability of a failure in a computer system is never zero. There are always failures - if not evident, then latent.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 61.

Errors in Tests and Simulators

“The simulator software had to be tested as thoroughly as the software it was built to test. A fault in the simulator would cause the worst kind of problem, what computer analysts call a Byzantine failure. Byzantine failures are like traitors in a family. There is always a risk this will happen.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 61.

Failures Disappointing

“... discovering a failure is disappointing, and then there is pressure from above not to find them. Everyone wants the software out the door.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 61.

Failure Discovery Rate

“A critical parameter in the development of any system is the discovery rate of software failures, especially during system testing.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 62.

Testing Statistics

“...statistics are not enough. The kind of failures, correlated with their frequency, gives a clearer picture of the health of the system.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 63.

Important Development Things

“The single, most important thing is that the individual programmer needs to be given total responsibility and control of the programming, including its function... eliminate project design and review as an exhaustive and rigorous process. Most of the design and review should occur as the program is written. ... Monitor progress on the project by talking to the individual programmers as [code] is being written. ... You must trust developers on the project to create a good product. ... Sometimes there are failures. ... The important thing is to fail quickly so you have time to find another approach. ... Developers must also feel free to say what they think to their supervisor. ... Managers should be the best programmers; ...There should be no overtime pay. ... Use profit-sharing and bonuses to get awesome products. ... Developers should each get their own office. ... Eliminate the dress code. Avoid meetings at all costs. ... Writing software is a lot like writing a book. Almost anyone can write garbage; very few can write a best-seller.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 155-156.

Software Testing Completion Criteria

“Software is never completely fit. ... Testing should simply continue until all of the performance criteria have been met, including the failure rate.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 157.

Acceptance Testing

“The very existence of an acceptance test ensures that, sooner or later, there will be pressure not to find failures, to reconcile test scenarios and the system they exercise so that the system will 'pass'. Remove this concept and testers would pursue the discovery of failures with a vengeance...”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 157.

Up Front Time and Money

“Put enough time and money into any project, up front, and it will fail.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 187.

Fred Brooks

Throw One Away

“Plan to throw one away; you will, anyhow.”
  • Source: Brooks Jr., F. P. (1995). The Mythical Man-Month - Essays on Software Engineering (Anniversary Edition) | 1975/1995 (Anniv.). Boston. MA: Addison-Wesley. ISBN: 0201835959. Chapter 11, page 116.

History Studies What Does Not Work

“The most potent reason to study design history is to learn what doesn’t work, and why.”
  • Source: Brooks Jr., F. P. (2010). The Design of Design. Upper Saddle River, NJ: Addison-Wesley. ISBN: 978-0-201-36298-5. Chapter 3, page 25.

Alistair_Cockburn

Striking Project Findings

"What I find striking about these projects is that they show:
Almost any methodology can be made to work on some project.
Any methodology can manage to fail on some project.
Heavy processes can be successful.
Light processes are more often successful, and more importantly, the people on those projects credit the success to the lightness of the methodology."

People First-Order Effect

"I finally concluded that there is something there, in front of us all the time, which we are not seeing: people. People’s characteristics are a first-order success driver, not a second-order one. In fact, I have reversed the order, and now consider process factors to be second-order issues."

Keywords: People_quotes Methodology_quotes Process_quotes Success_quotes Failure_quotes Conclude_quotes Front_quotes Time_quotes See_quotes Characteristic_quotes First-order_quotes Second-order_quotes Reverse_quotes Order_quotes Factor_quotes Software_quotes Development_quotes

People Characteristics

"People, as active devices, have success modes and failure modes. The following are the main ones that I have named and used to date:
1. People are communicating beings, doing best face-to-face, in person, with real-time question and answer.
2. People have trouble acting consistently over time.
3. People are highly variable, varying from day to day and place to place.
4. People generally want to be good citizens, are good at looking around, taking initiative, and doing 'whatever is needed' to get the project to work.
There are other characteristics that I won’t expand here:
- People need both think time and communicating opportunities...
- People work well from examples...
- People prefer to fail conservatively than to risk succeeding differently; prefer to invent than to research, can only keep a small amount in their heads, and do make mistakes, and find it hard to change their habits.
- Individual personalities easily dominate a project.
- A person’s personality profile strongly affects their ability to perform specific assignments."

DeMarco and Lister

People Not Modular

"Most of us as managers are prone to one particular failing: a tendency to manage people as though they were modular components."
  • Source: Book:: Entitled: 'Peopleware: Productive Projects and Teams'. Edition: 3rd. Written by: Tom DeMarco; Tim Lister. Date published: 1987; 1999; 2013. Publisher: Addison-Wesley. Country: USA; GBR; CAN; DEU; FRA; ESP; ZAF; AUS; JPN; SGP; MEX. Language: en. ISBN: ISBN-13: 978-0-321-93411-6 (alk paper); 0-321-93411-3 (alk paper). Part: I (Managing the Human Resource).

Project Failures

"We observe that about 15 percent of all projects studied came to naught: They were canceled or aborted or 'postponed' or they delivered products that were never used. For bigger projects, the odds are even worse. Fully 25 percent of projects that lasted 25 work-years or more failed to complete. In the early surveys, we discarded these failed data points and analyzed the others. Since 1979, though, we’ve been contacting whoever is left of the project staff to find out what went wrong. For the overwhelming majority of the bankrupt projects we studied, there was not a single technological issue to explain the failure."
  • Source: Book:: Entitled: Peopleware: Productive Projects and Teams. Edition: 3rd. Written by: Tom DeMarco; Tim Lister. Date published: 1987; 1999; 2013. Publisher: Addison-Wesley. Country: USA; GBR; CAN; DEU; FRA; ESP; ZAF; AUS; JPN; SGP; MEX. Language: en. ISBN: ISBN-13: 978-0-321-93411-6 (alk paper); 0-321-93411-3 (alk paper). Chapter: 1 (Somewhere Today, a Project Is Failing).

Project Politics

"The cause of failure most frequently cited by our survey participants was 'politics.' But now observe that people tend to use this word rather sloppily. Included under 'politics' are such unrelated or loosely related things as communication problems, staffing problems, disenchantment with the boss or with the client, lack of motivation, and high turnover. People often use the word politics to describe any aspect of the work that is people-related, but the English language provides a much more precise term for these effects: They constitute the project’s sociology. The truly political problems are a tiny and pathological subset."
  • Source: Book:: Entitled: Peopleware: Productive Projects and Teams. Edition: 3rd. Written by: Tom DeMarco; Tim Lister. Date published: 1987; 1999; 2013. Publisher: Addison-Wesley. Country: USA; GBR; CAN; DEU; FRA; ESP; ZAF; AUS; JPN; SGP; MEX. Language: en. ISBN: ISBN-13: 978-0-321-93411-6 (alk paper); 0-321-93411-3 (alk paper). Chapter: 1 (Somewhere Today, a Project Is Failing).

Error Quota

"For most thinking workers, making an occasional mistake is a natural and healthy part of their work. But there can be an almost Biblical association between error on the job and sin. This is an attitude we need to take specific pains to change. Speaking to a group of software managers, we introduced a strategy for what we think of as iterative design. The idea is that some designs are intrinsically defect-prone; they ought to be rejected, not repaired. Such dead ends should be expected in the design activity. The lost effort of the dead end is a small price to pay for a clean, fresh start. To our surprise, many managers felt this would pose an impossible political problem for their own bosses: 'How can we throw away a product that our company has paid to produce?' They seemed to believe that they’d be better off salvaging the defective version even though it might cost more in the long run. Fostering an atmosphere that doesn’t allow for error simply makes people defensive. They don’t try things that may turn out badly. You encourage this defensiveness when you try to systematize the process, when you impose rigid methodologies so that staff members are not allowed to make any of the key strategic decisions lest they make them incorrectly. The average level of technology may be modestly improved by any steps you take to inhibit error. The team sociology, however, can suffer grievously. The opposite approach would be to encourage people to make some errors. You do this by asking your folks on occasion what dead-end roads they’ve been down, and by making sure they understand that 'none' is not the best answer. When people blow it, they should be congratulated — that’s part of what they’re being paid for."
  • Source: Book: Entitled: Peopleware: Productive Projects and Teams. Edition: 3rd. Written by: Tom DeMarco; Tim Lister. Date published: 1987; 1999; 2013. Publisher: Addison-Wesley. Country: USA; GBR; CAN; DEU; FRA; ESP; ZAF; AUS; JPN; SGP; MEX. Language: en. ISBN: ISBN-13: 978-0-321-93411-6 (alk paper); 0-321-93411-3 (alk paper). Chapter: 2 (Make a Cheeseburger, Sell a Cheeseburger).

Peter_Drucker

Success Outliving Usefulness

“A success that has outlived its usefulness may, in the end, be more damaging than failure.”
  • Source: Peter F. Drucker, Management: Tasks, Responsibilities, Practices, New York: Harper & Row, 1973. p. 159.

Henry_Ford

Failure

“An absence of fear of the future and of veneration for the past. One who fears the future, who fears failure, limits his activities. Failure is only the opportunity more intelligently to begin again. There is no disgrace in honest failure; there is disgrace in fearing to fail. What is past is useful only as it suggests ways and means for progress.”
  • Source: Henry Ford. A book. Entitled My Life and Work. Written by Henry Ford in collaboration with Samuel Crowther. Published 1922, Garden City, NY: Doubleday. Introduction.
    • Also quoted in Samuel Crowther, "Henry Ford's Problem," The Magazine of Business, vol. 52 (1927), p. 182.

Milton_Friedman

Positive Knowledge

“In both social and natural sciences, the body of positive knowledge grows by the failure of a tentative hypothesis to predict phenomena the hypothesis professes to explain; by the patching up of that hypothesis until someone suggests a new hypothesis that more elegantly or simply embodies the troublesome phenomena, and so on ad infinitum. In both, experiment is sometimes possible, sometimes not (witness meteorology). In both, no experiment is ever completely controlled, and experience often offers evidence that is the equivalent of controlled experiment. In both, there is no way to have a self-contained closed system or to avoid interaction between the observer and the observed. The Gödel theorem in mathematics, the Heisenberg uncertainty principle in physics, the self-fulfilling or self-defeating prophecy in the social sciences all exemplify these limitations.”
  • Source: Milton Friedman, Inflation and Unemployment (1976), 348

Gordon_Glegg

Engineers and Designers Are Human

“Throughout this book we have talked about 'designers' and 'engineers' and sought, by analysing their work, to find general and helpful maxims. But there is a danger in doing this, for we may forget that a 'designer' or 'engineer' is first and foremost a human being. A human being who designs or engineers has, in addition, a wide range of complicated and interacting emotions. It is easy to become emotionally involved in a new invention and so resent criticism of it even when that criticism, if heeded, would turn a failure into a success. Confidence may be blinded by conceit or undermined by an inferiority complex. History has shown that many new inventions were not inventions at all; they were re-inventions. The idea was not new but the determination to press through with it was. Character is the foundation of ability. Develop as large a safety margin as you can against such things as laziness, impatience, prejudice and arrogance and all the other human failings that inhibit constructive achievement in all spheres, especially that of creative engineering design.”
  • Source: Glegg, G. L. (1969). The Design of Design. Cambridge, UK: Cambridge University Press. ISBN: 978-0-511-79996-9. Chapter 6, page 92.

Joseph_Heller

Lousy Earth

“What a lousy earth! He wondered how many people were destitute that same night even in his own prosperous country, how many homes were shanties, how many husbands were drunk and wives socked, and how many children were bullied, abused or abandoned. How many families hungered for food they could not afford to buy? How many hearts were broken? How many suicides would take place that same night, how many people would go insane? How many cockroaches and landlords would triumph? How many winners were losers, successes failures, rich men poor men? How many wise guys were stupid? How many happy endings were unhappy endings? How many honest men were liars, brave men cowards, loyal men traitors, how many sainted men were corrupt, how many people in positions of trust had sold their souls to blackguards for petty cash, how many had never had souls? How many straight-and-narrow paths were crooked paths? How many best families were worst families and how many good people were bad people? When you added them all up and then subtracted, you might be left with only the children, and perhaps with Albert Einstein and an old violinist or sculptor somewhere.”
  • Source: Heller, Joseph. 'Catch-22: 50th Anniversary Edition'. Chapter 39 'The Eternal City', page 483. Simon & Schuster. Kindle Edition.

John_Maynard_Keynes

Slow Progress

“From the earliest times of which we have record — back, say, to two thousand years before Christ [BCE 2000] down to the beginning of the eighteenth century [CE 1700] — there was no very great change in the standard of life of the average man living in the civilised centres of the earth... This slow rate of progress, or lack of progress, was due to two reasons — to the remarkable absence of important technical improvements and to the failure of capital to accumulate.”
  • Source: From the Essay “Economic Possibilities for our Grandchildren” written by John Maynard Keynes in 1930. Included in the book “Essays in Persuasion” edited by John Maynard Keynes and published by W. W. Norton & Company in 1963.

Alexander_Kossiakoff et al.

Skeptical Positive Thinking

"The Power of Skeptical Positive Thinking... is meant to capture an important characteristic of successful systems engineering. The skeptical part is important to temper the traditional optimism of the design specialist regarding the probability of success of a chosen design approach. It is the driving force for the insistence of validation of the approach selected at the earliest possible opportunity. The other dimension of skepticism, which is directly related to the characteristic of positive thinking, refers to the reaction in the face of failure or apparent failure of a selected technique or design approach. Many design specialists who encounter an unexpected failure are plunged into despair. The systems engineer, on the other hand, cannot afford the luxury of hand wringing."
  • Source:Kossiakoff, Alexander; Sweet, William N.; Seymour, Samuel J.; Biemer, Steven M.. 'Systems Engineering Principles and Practice'. 2011. Wiley. Kindle Edition. Section 1.6 page 23.

Michael_Sean_Mahoney

Software Crisis and Software Engineering

“Let me say a bit more about the ‘software crisis’. It emerged in the late 1960s as an increasing number of large projects experienced large cost overruns, missed deadlines and failures to meet specifications. Some had to be canceled altogether. One response was calls for a discipline of ‘software engineering’”
  • Source: Michael S. Mahoney in a paper entitled The Histories of Computing(s). Published 2005 in Interdisciplinary Science Reviews, volume 30, number 2, pages 119–135. DOI: 10.1179/030801805X25927.

Richard_Pascale

Efficiency and Variation

“Corporations, in the name of efficiency, suppress variation by 'getting all the ducks in line'. To optimize productivity, they evolve highly refined and internally consistent operating systems. Payoff results - as long as the music lasts. But in the face of nontraditional competitors or major environmental discontinuities, all that streamlining and reengineering limits diversity, suppresses self-organization by those closest to the disruptive change, and curtails a bottom-up emergent response to cope more effectively... Nothing fails like success. Over-adaptive organizations become inflexible. Disruptive change leaves them as helpless as a beached whale.”
  • Source: Richard T. Pascale, Jerry Sternin, Monique Sternin (2010). “The Power of Positive Deviance: How Unlikely Innovators Solve the World's Toughest Problems”, p.190, Boston, MA: Harvard Business Press

Alan_Perlis

Failure and Success

“Dealing with failure is easy: Work hard to improve. Success is also easy to handle: You've solved the wrong problem. Work hard to improve.”

Robert_M_Pirsig

An Experiment is Never a Failure

“An experiment is never a failure solely because it fails to achieve predicted results. An experiment is a failure only when it also fails adequately to test the hypothesis in question, when the data it produces don’t prove anything one way or another.”
  • Source: Zen and the Art of Motorcycle Maintenance: An Inquiry Into Values (1974), 102.

Karl_Popper

Soothsayer Trick

“It is a typical soothsayer's trick to predict things so vaguely that the predictions can hardly fail: that they become irrefutable.”

Rittel_and_Webber

Wicked Problems

“The search for scientific bases for confronting problems of social policy is bound to fail, because of the nature of these problems. They are 'wicked' problems, whereas science has developed to deal with 'tame' problems.”

Bertrand_Russell

Coherence

“It is said that the mark of falsehood is failure to cohere in the body of our beliefs, and that it is the essence of a truth to form part of the completely rounded system which is The Truth.”
  • Source: Bertrand Russell, (1912), In the book entitled “The Problems of Philosophy” by Bertrand Russell. Second edition published in 1998 (originally published in 1912) by Oxford University Press, Oxford, England. Chapter 12. ISBN 978-0-19-285423-0. Online at <https://www.gutenberg.org/ebooks/5827> retrieved 2022.

Theodore_Roosevelt

Hard to Fail

“It is hard to fail, but it is worse never to have tried to succeed.”
  • Source: Theodore Roosevelt, governor of New York, speech before the Hamilton Club, Chicago, Illinois, April 10, 1899.—The Strenuous Life (vol. 13 of The Works of Theodore Roosevelt, national ed.), chapter 1, p. 320 (1926).

Alfred_Tarski

Adequate Truth Definition

“Therefore we can say — considering the failure of previous attempts — that at present we can construct no correct and materially adequate definition of truth for the language under consideration.”

Patrick_Vlaskovits

Faster Horse

“However, even if Ford didn’t verbalize his thoughts on customers’ ostensible inability to communicate their unmet needs for innovative products — history indicates that Henry Ford most certainly did think along those lines... Henry Ford froze the design of the Model T... Ford had no compelling reason to innovate in any other sphere other than cost and price reduction... But everything changed with the onset of the innovations introduced by General Motors in the 1920s, which took the direct opposite of Henry Ford’s tack of “Any color … so long as it is black” and is best summed up by Alfred Sloan’s consumer-research driven “A Car for Every Purse and Purpose”... In 1921, the Ford Motor Company sold about 2/3 of all the cars built in the U.S. By 1926, this share had fallen to approximately 1/3. And in 1927, when Ford belatedly responded (at tremendous financial cost and internal strife) to changes in the market’s tastes and competitive innovation by shutting down production temporarily to re-tool his factories and bring the Model A to the market, that percentage fell to about 15%... Yes, some customers in certain types of businesses are quite capable of verbalizing precisely what sort of innovative product one could build and sell them. And of course, customers in other types of businesses are wholly incapable of verbalizing, with any sort of fidelity whatsoever, what they need and why they need it. An innovator should have understanding of one’s customers and their problems via empirical, observational, anecdotal methods or even intuition. They should also feel free to ignore customers’ inputs. Because by now it should be clear that Ford’s adherence to his vision of the mass-market car and how to materialize that vision was instrumental in both his early success in growing Ford Motor Company as well as his later failure to respond in a timely and effective manner to rapid innovation in the marketplace.”'

Gerald_Weinberg

Knowledge Came Slowly

“In ages past, the knowledge came very slowly, and one man in his life was not likely to see much change other than that wrought by nature. The controlled incorporation of arsenic into copper to make bronze took several thousand years to develop; the substitution of tin for the more dangerous arsenic took another thousand or two. In our modern age, laboratories turn out an alloy a day, or more, with properties made to order. The alloying of metals led to the rise and fall of civilizations, but the changes were too slow to be appreciated. A truer blade meant victory over the invaders, but changes were local and slow enough to be absorbed by a million tiny adjustments without destroying the species. With an alloy a day, we can no longer be sure. Science and engineering have been the catalysts for the unprecedented speed and magnitude of change. The physicist shows us how to harness the power of the nucleus; the chemist shows us how to increase the quantity of our food; the geneticist shows us how to improve the quality of our children. But science and engineering have been unable to keep pace with the second-order effects produced by their first-order victories. The excess heat from the nuclear generator alters the spawning pattern of fish, and, before adjustments can be made, other species have produced irreversible changes in the ecology of the river and its borders. The pesticide eliminates one insect only to the advantage of others that may be worse, or the herbicide clears the rain forest for farming, but the resulting soil changes make the land less productive than it was before. And of what we are doing to our progeny, we still have only ghastly hints. Some have said the general systems movement was born out of the failures of science, but it would be more accurate to say the general systems approach is needed because science has been such a success. Science and technology have colonized the planet, and nothing in our lives is untouched. In this changing, they have revealed a complexity with which they are not prepared to deal. The general systems movement has taken up the task of helping scientists unravel complexity, technologists to master it, and others to learn to live with it.”
  • Source: Weinberg, Gerald (2011-04-07). An Introduction to General Systems Thinking (Kindle Locations 264-267). Weinberg & Weinberg. Kindle Edition.

T_H_White

Learning Cure for Sadness

“‘The best thing for being sad,’ replied Merlyn, beginning to puff and blow, ‘is to learn something. That is the only thing that never fails. You may grow old and trembling in your anatomies, you may lie awake at night listening to the disorder of your veins, you may miss your only love, you may see the world about you devastated by evil lunatics, or know your honour trampled in the sewers of baser minds. There is only one thing for it then — to learn. Learn why the world wags and what wags it. That is the only thing which the mind can never exhaust, never alienate, never be tortured by, never fear or distrust, and never dream of regretting. Learning is the thing for you. Look at what a lot of things there are to learn — pure science, the only purity there is. You can learn astronomy in a lifetime, natural history in three, literature in six. And then, after you have exhausted a milliard lifetimes in biology and medicine and theocriticism and geography and history and economics — why, you can start to make a cartwheel out of the appropriate wood, or spend fifty years learning to begin to learn to beat your adversary at fencing. After that you can start again on mathematics, until it is time to learn to plough.’”
  • Source: White, T. H. (2011). The Once and Future King | 1939. New York, NY: Penguin. ISBN 9781101657546.

Shoshana_Zuboff

Technology Leadership

“The questions that we face today are finally about leadership. Will there be leaders who are able to recognize the historical moment and the choices it presents? Will they find ways to create the organizational conditions in which new visions, new concepts, and a new language of workplace relations can emerge? Will they be able to create organizational innovations that can exploit the unique capacities of the new technology and thus mobilize their organization's productive potential to meet the heightened rigors of global competition? Will there be leaders who understand the crucial role that human beings from each organizational stratum can play in adding value to the production of goods and services? If not, we will be stranded in a new world with old solutions. We will suffer through the unintended consequences of change, because we have failed to understand this technology and how it differs from what came before.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 12. ISBN:0465032125.