Management quotes

From Motley Bytes Wiki
Jump to: navigation, search

Contents

F_Terry_Baker

Code Library

“The most important of these is a development support library which encourages the visibility and manageability of the product, as well as reduces clerical effort on the part of the programmers. The library is typically maintained and operated by a programming librarian who serves to control the programming assets and to provide the necessary services for both programmers and management. As a result of its use, the entire project is maintained in a centralized, up-to-date, visible form which makes its status immediately apparent to code-competent software managers and makes it possible for programmers to answer their questions directly without relying on others.”
  • Source: Baker, F. T. (1975). Software Management Through Improved Programming Technology. ACM ’75: Proceedings of the 1975 Annual Conference, 286–287. https://doi.org/10.1145/800181.810346

Program Ownership

“A program or program system is a group product and should be produced in a way which allows and encourages maximum knowledge of it by each person involved. Furthermore, the management responsible for its development should be able to determine its status directly and not depend on the programmer's description of his progress on an 'invisible product'.”
  • Source: Baker, F. T. (1975). Software Management Through Improved Programming Technology. ACM ’75: Proceedings of the 1975 Annual Conference, 286–287. https://doi.org/10.1145/800181.810346

Software Management Support

“While the components of the methodology are relatively easy to learn and apply, they are most successful when the management of the organization understands and encourages the process.”
  • Source: Baker, F. T. (1975). Software Management Through Improved Programming Technology. ACM ’75: Proceedings of the 1975 Annual Conference, 286–287. https://doi.org/10.1145/800181.810346

Alexander d'Agapeyeff

Programmer Platoons

"In my experience programmers are rather difficult to shove around like platoons in the army."

Robert_N_Britcher

Lines of Code

“...programmers abhor the line of code. When managers speak of it, programmers quicken their step. Most of them know that the line of code is as central to the meaning of a program as the period is to the meaning of Tolstoy's Anna Karenina.”
  • Source: Britcher, Robert N. (1999). The Limits of Software: People, Projects, and Perspectives. Reading, MA: Addison Wesley. ISBN 0-201-43323-0. Page 50.

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.

Fred_Brooks

Brooks' Law

“Adding manpower to a late software project makes it later.”
  • 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 2, page 25. Known as Brooks' Law.

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.

Specification Hard

“Even perfect program verification can only establish that a program meets its specification. The hardest part of the software task is arriving at a complete and consistent specification, and much of the essence of building a program is in fact the debugging of the specification.”
  • 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 16, page 195.

Productivity Magnitude

“Study after study shows that the very best designers produce structures that are faster, smaller, simpler, cleaner, and produced with less effort. The differences between the great and the average approach an order of magnitude.”
  • 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 16, page 202.

Great Designers

“A little retrospection shows that although many fine, useful software systems have been designed by committees and built by multipart projects, those software systems that have excited passionate fans are those that are the products of one or a few designing minds, great designers.”
  • 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 16, page 202.

Grow Not Build Software

“Grow, not build software... The building metaphor has outlived its usefulness.”
  • 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 16, page 200.

Child Bearing Task Law

“The bearing of a child takes nine months, no matter how many women are assigned. Many software tasks have this characteristic because of the sequential nature of debugging.”
  • 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 2, page 17.

Warren_Buffett

Money Versus Business

“So as a practical matter we need management with the businesses that we buy and three times out of four thereabouts the manager is the owner and is receiving tens of millions maybe hundreds of millions of dollars so they don't have to work and we have to decide in that time when we meet them whether they love the business or love money... I'm not making a moral judgment about whether it's better to love the business or love money but it's very important for me to know which which of the two is the primary motivator with them... so all all we have to do is avoid anything that on our part that diminishes that love of the business or makes other conditions so intolerable that they overcome that love of the business. We have a number of people working for us that have no financial need to work at all and they probably outwork 95 percent or more of the people in the world and they do it because they just they love smacking the ball.”

Burke and Bailey

Recruiting Soft Skills

“Managers actually spend the vast majority of their recruitment time assessing a candidate’s soft skills.”
  • Source: An academic paper. Entitled Becoming an Adaptive Expert. Written by Quinn Burke; Cinamon Sunrise Bailey. Date published 2020. Published in: Communications of the ACM. Language: en. DOI: 10.1145/3366171.

Keywords: Manager_quotes Management_quotes Recruiting_quotes Skill_quotes

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 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).

People Related Problems

"Whatever you name these people-related problems, they’re more likely to cause you trouble on your next assignment than all the design, implementation, and methodology issues you’ll have to deal with. In fact, that idea is the underlying thesis of this whole book: The major problems of our work are not so much technological as sociological in nature."
  • 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).

Seldom Manage That Way

"Most managers are willing to concede the idea that they’ve got more people worries than technical worries. But they seldom manage that way. They manage as though technology were their principal concern. They spend their time puzzling over the most convoluted and most interesting puzzles that their people will have to solve, almost as though they themselves were going to do the work rather than manage it. They are forever on the lookout for a technical whizbang that promises to automate away part of the work. The most strongly people-oriented aspects of their responsibility are often given the lowest priority."
  • 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).

Cheeseburgers

"Development is inherently different from production. But managers of development and allied efforts often allow their thinking to be shaped by a management philosophy derived entirely from a production environment.
Imagine for the moment that you’re the manager of the local fast food franchise. It makes perfect sense for you to take any or all of the following efficient production measures:
- Squeeze out error. Make the machine (the human machine) run as smoothly as possible.
- Take a hard line about people goofing off on the job.
- Treat workers as interchangeable pieces of the machine.
- Optimize the steady state. (Don’t even think about how the operation got up to speed, or what it would take to close it down.)
- Standardize procedure. Do everything by the book.
- Eliminate experimentation—that’s what the folks at headquarters are paid for.
These would be reasonable approaches if you were in the fast food business (or any production environment), but you’re not. The 'make a cheeseburger, sell a cheeseburger' mentality can be fatal in your development area. It can only serve to damp your people’s spirits and focus their attention away from the real problems at hand. This style of management will be directly at odds with the work.
To manage thinking workers effectively, you need to take measures nearly opposite those listed above."
  • 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).

Kicking Ass

"Management is a complex enough thing to defy simple definition, but that nuance was lost on one senior manager we encountered at a professional society meeting in London. He summed up his entire view of the subject with this statement: 'Management is kicking ass.' This equates to the view that managers provide all the thinking and the people underneath them just carry out their bidding. Again, that might be workable for cheeseburger production, but not for any effort for which people do the work with their heads rather than their hands. Everyone in such an environment has got to have the brain in gear. You may be able to kick people to make them active, but not to make them creative, inventive, and thoughtful. Even if kicking people in the backside did boost their short-term productivity, it might not be useful in the long run. There is nothing more discouraging to any worker than the sense that his own motivation is inadequate and has to be 'supplemented' by that of the boss. The saddest thing about this management approach is that it’s almost always superfluous. You seldom need to take Draconian measures to keep your people working; most of them love their work. You may even have to take steps sometimes to make them work less, and thus get more meaningful work done."
  • 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).

W_Edwards_Deming

Handicapped by the System

"The supposition is prevalent the world over that there would be no problems in production or service if only our production workers would do their jobs in the way that they were taught. Pleasant dreams. The workers are handicapped by the system, and the system belongs to the management."
  • Source: W. Edwards Deming (1982) Out Of The Crisis. The MIT Press. (2e ed. 1986) p. 134.

Statistical Methods

"Statistical methods had taken fire in America around 1942, following a series of ten-day intensive courses for engineers, initiated by Stanford University on a suggestion from this author. The war department also gave courses at factories of suppliers. Brilliant applications attracted much attention, but the flare of statistical methods by themselves, in an atmosphere in which management did not know their responsibilities, burned, sputtered, fizzled and died out."
  • Source: W. Edwards Deming. Quality, Productivity and Competitive Position (1982) p. 101.

People Manager

"A manager of people needs to understand that all people are different. This is not ranking people."
  • Source: W. Edwards Deming. The New Economics for Industry, Government, Education (1993).

Peter_Drucker

Management Decision Power

“In the modern corporation the decisive power, that of the managers, is derived from no one but the managers themselves controlled by nobody and nothing and responsible to no one. It is in the most literal sense unfounded, unjustified, uncontrolled and irresponsible power.”
  • Source: Drucker, P. F. (1942). The Future of Industrial Man. Page 64. DOI: 10.4324/9781315132143.

Systems Management

“Organizationally what is required - and evolving - is systems management.”
  • Source: Peter F. Drucker, Management: Tasks, Responsibilities, Practices, New York: Harper & Row, 1973. p. 761.

Learn to Lead People

"We will have to learn to lead people rather than to contain them."
  • Source: Peter F. Drucker, “Management: Tasks, Responsibilities, Practices”, New York: Harper & Row, 1973. p. 30.

Layoffs

“...what's absolutely unforgivable is the financial benefit top management people get for laying off people. There is no excuse for it. No justification. This is morally and socially unforgivable, and we will pay a heavy price for it.”
  • Source: A cantankerous interview with Peter Drucker, Wired (August 1996).

Subordinate Job

“The subordinate's job is not to reform or reeducate the boss, not to make him conform to what the business schools or the management book say bosses should be like. It is to enable a particular boss to perform as a unique individual.”
  • Source: Peter Drucker, “Managing for the Future: The 1990's and Beyond” (1992). p. 138.

Henry_Ford

Wages

“There is nothing to running a business by custom – to saying: 'I pay the going rate of wages.' The same man would not so easily say: 'I have nothing better or cheaper to sell than any one has.' No manufacturer in his right mind would contend that buying only the cheapest materials is the way to make certain of manufacturing the best article. Then why do we hear so much talk about the 'liquidation of labour' and the benefits that will flow to the country from cutting wages – which means only the cutting of buying power and the curtailing of the home market? What good is industry if it be so unskillfully managed as not to return a living to everyone concerned? No question is more important than that of wages – most of the people of the country live on wages. The scale of their living – the rate of their wages – determines the prosperity of the country.”
  • 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. Chapter VIII.

Tony_Hoare

All Problems Technical

“Basically, all problems are technical. If you know what you want to do and you have the necessary technical background, there is no point in making a great management problem out of it. Obviously, a certain amount of resource control and personnel work has to go on but that’s all. On the other hand, you might have a task which is difficult in that you don’t know what you have to do, and that even if you did you wouldn’t know how to do it. Since this is a very difficult task you can start out with the hypothesis that it will take a great number of people. Following down this slippery slope of reasoning, as soon as you have a very large number of people you have a very large management problem. But it all originated out of the fact that you didn’t know what you were doing, or how to do it.”
  • Source: C.A.R.Hoare in Ercoli, P., Bauer, F. L., Aron, J. D., & Hoare, C. A. R. (1970). Software Engineering Techniques: Report on a Conference Sponsored by the NATO Science Committee, Rome, Italy, 27th to 31 October 1969. (J. N. Buxton & B. Randell, Eds.). Retrieved from http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1969.PDF.

Grace_Hopper

Manage Things Lead People

“You manage things, you lead people. We went overboard on management and forgot about leadership. It might help if we ran the MBAs out of Washington.”
  • Source: Grace Hopper as quoted in "The Wit and Wisdom of Grace Hopper" by Philip Schieber in OCLC Newsletter, No. 167 (March/April 1987).

Kenneth_W_Kolence

Software Development Management

“Software product development requires (but is not itself sufficient) the design of rational and correctly integrated management and technical processes.”

Ascher_Opler

Spot the Lemon Early

“In managing software projects the real problem is ‘spot the lemon and spot the lemon early’.”

Willard_Van_Orman_Quine

Science as a Tool

“As an empiricist I continue to think of the conceptual scheme of science as a tool, ultimately, for predicting future experience in the light of past experience. Physical objects are conceptually imported into the situation as convenient intermediaries - not by definition in terms of experience, but simply as irreducible posits comparable, epistemologically, to the gods of Homer. For my part I do, qua lay physicist, believe in physical objects and not in Homer's gods; and I consider it a scientific error to believe otherwise. But in point of epistemological footing the physical objects and the gods differ only in degree and not in kind. Both sorts of entities enter our conception only as cultural posits. The myth of physical objects is epistemologically superior to most in that it has proved more efficacious than other myths as a device for working a manageable structure into the flux of experience.”
  • Source: From A Logical Point of View (1953), p. 44.

Frederick_Winslow_Taylor

Average versus First Class Productivity

“That there is a difference between the average and the first class man is known to all employers, but that the first class man can do in most cases from two to four times as much is known to few, and is fully realized only by those who have made a thorough and scientific study of the possibilities of men.”
  • Source: F.W. Taylor (1903) "Shop management; a paper read before the American society of mechanical engineers, " in: Transactions of the American Society of Mechanical Engineers 24: 1337-1480. p. 1346.

Principal Object of Management

“The principal object of management should be to secure the maximum prosperity for the employer, coupled with the maximum prosperity for each employee.”
  • Source: F.W. Taylor, 1911. Principles of Scientific Management. New York and London, Harper & brothers. Chapter 1.

Maximum Prosperity

“It would seem to be so self-evident that maximum prosperity for the employer, coupled with maximum prosperity for the employee, ought to be the two leading objects of management, that even to state this fact should be unnecessary. And yet there is no question that, throughout the industrial world, a large part of the organization of employers, as well as employees, is for war rather than for peace, and that perhaps the majority on either side do not believe that it is possible so to arrange their mutual relations that their interests become identical.”
  • Source: F.W. Taylor, 1911. Principles of Scientific Management. New York and London, Harper & brothers. Chapter 1.

Kindly Interest

“...in order to have any hope of obtaining the initiative of his workmen the manager must give some special incentive to his men beyond that which is given to the average of the trade. This incentive can be given in several different ways, as, for example, the hope of rapid promotion or advancement; higher wages, either in the form of generous piece-work prices or of a premium or bonus of some kind for good and rapid work; shorter hours of labor; better surroundings and working conditions than are ordinarily given, etc., and, above all, this special incentive should be accompanied by that personal consideration for, and friendly contact with, his workmen which comes only from a genuine and kindly interest in the welfare of those under him.”
  • Source: F.W. Taylor, 1911. Principles of Scientific Management. New York and London, Harper & brothers. Chapter 1.

Great Men Needed

“In the past the man has been first; in the future the system must be first. This in no sense, however, implies that great men are not needed. On the contrary, the first object of any good system must be that of developing first-class men; and under systematic management the best man rises to the top more certainly and more rapidly than ever before.”
  • Source: F.W. Taylor, 1911. Principles of Scientific Management. New York and London, Harper & brothers. p. 7: Introduction.

Gerald_Weinberg

Desire To Eliminate Programmers

“Over the years, executives have backed their desire to eliminate programmers with staggering funds.”
  • Source: Book Entitled: The Psychology of Computer Programming (Silver anniversary edition). Edition: Silver anniversary. Written By: Gerald Weinberg. Published originally: 1971. Republished: 2011.

Programmers Are Human Beings

“If our experiences are any indication, each of them could be functioning more efficiently, with greater satisfaction, if he and his manager would only learn to look upon the programmer as a human being, rather than as another one of the machines.”
  • Source: Book Entitled: The Psychology of Computer Programming (Silver anniversary edition). Edition: Silver anniversary. Written By: Gerald Weinberg. Published originally: 1971. Republished: 2011.

Small Teams More Efficient

“In any case, the basic rule for size and composition of programming teams would seem to be this — for the best programming at the least cost, give the best possible programmers you can find sufficient time so you need the smallest number of them. When you have to work faster, or with less experienced people, costs and uncertainties will rise. In any case, the worst way to do a programming project is to hire a horde of trainees and put them to work under pressure and without supervision — although this is the most common practice today.”
  • Source: Chapter 5. Weinberg, G. M. (2011). The Psychology of Computer Programming (Silver anniversary edition) | 1971. Weinberg & Weinberg.

True Consensus on Group Goals

“To achieve true consensus on group goals, there is no better method than having the group set the goals itself... To be sure, not every programming team can be permitted to set whatever goals it happens to fancy at any moment. A team is usually constituted to accomplish some task which has probably been set down before the team was even assembled. But programming tasks are not usually specified too precisely until much later than team formation, so that unless the upper management is very overbearing, much meaningful and interesting goal setting can be done by the team members in concert. The greatest danger is the manager who has come up through the programming ranks and wants to define every bit and byte before the team even sees the problem. Nothing is more sure to dampen the team enthusiasm and make them feel that they are 'mere coders... Of course, it is best if each team can have a single clearly defined goal, but the world is seldom so simple... When a team is not fully apprised of the emphasis to be placed on each factor, the members of that team may very well be working at cross purposes.”
  • Source: Chapter 5. Weinberg, G. M. (2011). The Psychology of Computer Programming (Silver anniversary edition) | 1971. Weinberg & Weinberg.

Shoshana_Zuboff

Frederick Taylor

“The man who emerged as the chief symbol of the rational approach to management was Frederick Taylor. Though much has been written on Taylor and the philosophy and methods of scientific management, it is worth highlighting a few central themes for three reasons. First, Taylorism explicitly treats the worker's body in its two dimensions -- as a source of effort and as a source of skill. Second, workers' responses to Taylorism reveal the ambivalence that this dual role of the body can create, as it did among the bleach plant operators or the nineteenth-century glassmakers. Third, the logic that motivated the early purveyors and adapters of scientific management has continued to dominate the course of automation in the twentieth-century workplace. As will be argued later, it is a logic that must undergo a fundamental reevaluation as information technology is widely adapted to productive activity.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 41. ISBN:0465032125.

Share the Fruits

“Taylor believed it was necessary to share the fruits of such productivity increases and saw the differential piece-rate system, a central tenet of scientific management, as a method of uniting workers and managers in a bond of common interest. But incentive wages are devilishly hard to administer, and all too often, managers attracted to differential wage schemes succumbed to shortcuts that promised fast gains. Managers would frequently change piece rates as workers learned to meet the standards. This led to the complaints of overwork with which unions relentlessly dogged proponents of Taylorism. Scientific management frequently meant not only that individual effort was simplified (either because of labor-saving equipment or new organizational methods that fragmented tasks into their simplest components), but also that the pace of effort was intensified, thus raising the level of fatigue and stress.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 45. ISBN:0465032125.

Divergence of Interests

“Taylor had believed that the transcendent logic of science, together with easier work and better, more fairly determined wages, could integrate the worker into the organization and inspire a zest for production. Instead, the forms of work organization that emerged with scientific management tended to amplify the divergence of interests between management and workers.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 45. ISBN:0465032125.

Know-How

“The agenda for scientific management was to increase productivity by streamlining and rationalizing factory operation from cost accounting and supervision to the dullest job on the shop floor. Efficiency was the mania, and to achieve efficiency, it would be necessary to penetrate the labor process and force it to yield up its secrets. In order that effort be rationalized, the worker's skills had to be made explicit. In many cases, workers' perceptions of their own interests prevented them from articulating their know-how, but there was yet another involuntary barrier. These skills did not easily yield themselves to explication; they were embedded in the ways of the body, in the knacks and know-how of the craftworker.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 42. ISBN:0465032125.

Time Study Expert

“The time-study expert became the new focus of workers' antagonisms. Informal production quotas persisted and, in many cases, took on an overtly anti-management spirit. The union contract became the most important means for institutionalizing workers' instincts for self-preservation, as rationalization routed out the ordinary graces with which the workday had been laced. Concern over wages and hours, work rules, and working conditions began to replace the craftworker's culturally embedded practices of effort regulation. Overall, the purification of effort meant a heightened standard of labor discipline, and as such it widened the gulf between those who gave of their bodies in the service of production and those who did not.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 46. ISBN:0465032125.

Information and Automating

“To the extent that technology is used only to intensify the automaticity of work, it can reduce skill levels and dampen the urge toward more participatory and decentralized forms of management... However, this approach cannot exploit the unique power of an informating technology. In contrast, an approach to technology deployment that emphasizes its informating capacity uses technology to do far more than routinize, fragment, or eliminate jobs. It uses the new technology to increase the intellectual content of work at virtually every organizational level, as the ability to decipher explicit information and make decisions informed by that understanding becomes broadly distributed among organizational members.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 243. ISBN:0465032125.

Automation and Labor

“Perhaps the most compelling reality that drives managers to a narrowly conceived emphasis on automation is the web of economic logic in which they must operate. Frequently, new expenditures for technology can be justified only as a capital substitution for labor. It is often assumed that whatever was provided by the human contributor can be transferred to the automatic functioning of the machine system.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 248. ISBN:0465032125.

Automation Fantasy

“Some managers experience a sense of relief at the prospect of being freed from this dependency. Their enthusiasm reveals an underlying but potent fantasy, one in which perfect control through total automaticity allows them to avoid the messiness and potential conflict of real human interaction.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 268. ISBN:0465032125.

Computers Over People

“When managers express a preference for computers over people, the effects find their way into every corner of the worker's mind.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 268. ISBN:0465032125.

Computer Dependency

“As managers use computerization to escape their dependency on workers' unique skills, both managers and workers alike become more dependent upon the computer system.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 269. ISBN:0465032125.

Panopticon Coaching

“To be sure, some managers saw the enhanced certainty of their information about subordinates as an opportunity to accelerate learning and improve performance. They found that the data from the Overview System made it possible to survey a wide range of behavior for evidence of irregularities. To the extent that the sources of such irregularities could be discovered, the data could be used to 'coach' subordinates and to help them realign their behavior within acceptable standards... On the other hand, many of Cedar Bluff's managers were more interested in the possibility of obtaining foolproof data than in the opportunity of using such data for coaching. In the context of a conventional technology, managers had to rely on their subordinates for valid information. The quality of the data they received was likely to be a function of the quality of the reciprocal relationship they had established. In contrast, an informating technology could provide valid information under any conditions.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 324. ISBN:0465032125.

Automated Evaluation

“The system automatically computed efficiency ratings for each worker by comparing the amount of time it took to complete a job had been priced. Such calculations with the amount of time for which it could have been generated only by a computer system, since 'we could never have enough clerks to compute these kinds of ratios.' The ratings were considered management information and were not accessible to the craftworkers. Many foremen cautioned against taking the ratings at face value. The most experienced craftsperson frequently was loaded with the most difficult assignments. That individual might show the worst efficiency rating simply because his or her assignments were the most complex and required more than the assigned time.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 331. ISBN:0465032125.

Technology Management

“Even where control or deskilling has been the intent of managerial choices with respect to new information technology, managers themselves are also captive to a wide range of impulses and pressures. Only rarely is there a grand design concocted by an elite group ruthlessly grinding its way toward the fulfillment of some special and secret plan. Instead, there is a concentration of forces and consequences, which in turn develop their own momentum. Sometimes these lines of force run in predictably straight paths. At other times, they twist and spiral, turn corners, and flow to their opposite. Activities that seem to represent choices are often inert reproductions of accepted practice.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 389. ISBN:0465032125.

Management Circles Around Data

“As the intellective skill base becomes the organization's most precious resource, managerial roles must function to enhance its quality. Members can be thought of as being arrayed in concentric circles around a central core, which is the electronic data base.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 396. ISBN:0465032125.

Information Panopticon Isolation

“In the information panopticon, managers... frequently tried to simplify their managerial tasks by displacing face-to-face engagement with techniques of surveillance and control. As a consequence, they became isolated from the realities of their organizations as they were increasingly insulated by an electronic text that in turn was even more vulnerable to workers' antagonisms.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 400. ISBN:0465032125.

Breed of American Worker

“There is a breed of American worker who cherishes the autonomy and sense of self-control afforded by his or her skills and protected by the union contract. When these workers contemplate the prospect of the socially integrated high-technology workplace, they feel despair. They anticipate a loss of their unique identities, of freedom and autonomy, and of well-defined rights and responsibilities. They fear that without the traditional sources of protection provided by their job descriptions and their contract, they will become prey to every capricious whim of their superiors. They understand that the managers' world requires the body as a political instrument for self-presentation and influence, but they know that these are talents they have not developed and toward which they feel more than a little distaste.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 404. ISBN:0465032125.

Informating Strategy

“There are several lessons to be learned here. First, the requirements of an informating strategy support existing work-improvement efforts, such as the high commitment approach to work force management, with its emphasis on self-managing teams, participation, and decentralization.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 413. ISBN:0465032125.

Life at the Data Interface

“Life at the data interface invites the worker into the abstract precincts of managerial work. It provides access to a broader view of the business as well as a deepened understanding of one's tasks and their role in the wider sphere of organizational functions. When work becomes synonymous with responsiveness to data, it engenders inquiry and dialogue, thus opening the way for workers to envision new possibilities and fresh alternatives to the reigning definitions of process, product, and organization.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 301. ISBN:0465032125.

Fundamental Scientific Management Reevaluation

“The logic that motivated the early purveyors and adapters of scientific management has continued to dominate the course of automation... It is a logic that must undergo a fundamental reevaluation as information technology is widely adapted to productive activity.”
  • Source: Zuboff, S. (1988). In The Age Of The Smart Machine: The Future Of Work And Power. New York, NY: Basic Books, p. 42. ISBN:0465032125.