- Shopping Bag ( 0 items )
- Spend $25, Get FREE SHIPPING
List Price
$22.95
Textbook Details
Used & New From our Trusted Marketplace Sellers
To try again, please visit the B&N Marketplace.
Although much has been written about how to make better decisions, a decision by itself changes nothing. The big problem facing managers and their organizations today is one of implementation--how to get things done in a timely and effective way. Stanford Business School Professor Jeffrey Pfeffer argues that problems of implementation are really issues of how to influence behavior, change the course of events, overcome resistance, and get people to do things they would not otherwise do. In a word, power. Managing with Power provides an in-depth look at the role of power and influence in organizations. Power is often disparaged, yet Pfeffer shows convincingly that its effective use is an essential component of strong leadership. With vivid examples from Lyndon Johnson and Henry Kissinger to John Sculley and Henry Ford, he makes a compelling case for the necessity of power in mobilizing the political support and resources to get things done in any organization. And he provides a fascinating look at the personal attributes--such as flexibility, stamina, and a high tolerance for conflict--and the structural factors--such as control of resources, access to information, and formal authority--that can help managers advance organizational goals and achieve individual success. Pfeffer begins his comprehensive evaluation of power by helping managers recognize situations that involve the use of power, and shows how to identify the principal actors and their likely points of view. He then looks at the different sources of power, and explains why some organizations and people use power more effectively than others. Next, he explores the specific strategies and tactics through which power and influence are used--how they help managers achieve tangible results. And finally, he considers issues of power dynamics: how power is lost, the role of power in the process of organizational change, and the positive and negative consequences of power for organizations. Politics and infl
| Acknowledgments | ||
| Pt. I | Power in Organizations | |
| 1 | Decisions and Implementation | 3 |
| 2 | When Is Power Used? | 33 |
| 3 | Diagnosing Power and Dependence | 49 |
| Pt. II | Sources of Power | 69 |
| 4 | Where Does Power Come From? | 71 |
| 5 | Resources, Allies, and the New Golden Rule | 83 |
| 6 | Location in the Communication Network | 111 |
| 7 | Formal Authority, Reputation, and Performance | 127 |
| 8 | The Importance of Being in the Right Unit | 147 |
| 9 | Individual Attributes as Sources of Power | 165 |
| Pt. III | Strategies and Tactics for Employing Power Effectively | 187 |
| 10 | Framing: How We Look at Things Affects How They Look | 189 |
| 11 | Interpersonal Influence | 207 |
| 12 | Timing Is (Almost) Everything | 227 |
| 13 | The Politics of Information and Analysis | 247 |
| 14 | Changing the Structure to Consolidate Power | 267 |
| 15 | Symbolic Action: Language, Ceremonies, and Settings | 279 |
| Pt. IV | Power Dynamics: How Power Is Lost and How Organizations Change | 299 |
| 16 | Even the Mighty Fall: How Power Is Lost | 301 |
| 17 | Managing Political Dynamics Productively | 317 |
| 18 | Managing with Power | 337 |
| Notes | 347 | |
| Bibliography | 367 | |
| Index | 379 |
Technical or engineering complexities do not account for the delays, nor do they explain why the Bay Bridge was repaired while nothing else was. San Francisco's and California's response to the earthquake presents a situation that is repeated often in both public and private sector organizations-a paralysis that reflects an inability to mobilize sufficient political support and resources to take action. Confronted with a problem, in this case-or opportunities, insome other instances-organizations are often unable to get things accomplished in a timely manner. This inaction can have severe consequences. The continuing closure of the Oakland section of the freeway costs some $23 million per year in extra transportation costs and fuel, while the continuing indecision about the repair of the freeways and off-ramps in San Francisco has cost much more in terms of lost business in the city.
It is, perhaps, not surprising that there is delay and indecision when the issue is as inherently ambiguous as the location and repair of roadways. Even in cases of life and death, however, there are failures to effectively mobilize political support and get things done that have serious consequences. Consider the chronology of the discovery of transfusion-transmitted AIDS, and the subsequent delays in getting anything done about it:
In March 1981, an "Rh baby" received a transfusion of blood provided by a 47-year-old donor at the Irwin Memorial Blood Bank in San Francisco.
In July 1981, epidemiological evidence led many members of the medical community to conclude that the so-called Gay Cancer was a contagious disease, spread by both sexual contact and through blood.
In September 1981, the child who received the transfusion in March was sick, suffering from immune dysfunctions; the donor, also sick, went to his doctor at about the same time and noted that he was a regular blood donor.
In December 1981, Don Francis, an epidemiologist at the Center for Disease Control (CDC) wanted to put blood banks on the alert. He argued that if the disease spread like hepatitis, it would be spread by blood transfusions.
In January 1982, the CDC learned that hemophiliacs were dying from a disease with symptoms similar to those spreading through the gay community, and that transfusions seemed to be the mechanism of transmission.
In November 1982, Dr. Selma Dritz, assistant director of the Bureau of Communicable Disease Control at the San Francisco Department of Public Health, was concerned about protecting the integrity of the blood supply; she had documented, at least to her satisfaction, the first case of AIDS transmitted by blood transfusion.
The reaction by the blood-bank industry was denial. "The first public announcement that AIDS might be in the blood supply brought an angry reaction from blood bankers in the East .... Dr. Joseph Bove, who . . . served as an officer of the American Association of Blood Banks, went on network television to say flatly that there still was no evidence that transfusions spread AIDS. Privately, some blood bankers thought the CDC was overstating the possibility . . . to get publicity and, therefore, more funding.
On January 4, 1983 (more than a year after it was first suspected that AIDS could be spread by blood transfusions), at a meeting of an ad hoc advisory committee for the U.S. Public Health Service, Don Francis of the CDC was angry. "How many people have to die?" shouted Francis, his fist hitting the table again. "How many deaths do you need? Give us the threshold of death that you need in order to believe that this is happening, and we'll meet at that time and we can start doing something."
In March 1983, the hepatitis antibody screening sought by the CDC was rejected because of opposition from the blood banks, although donor screening was introduced to try to eliminate high-risk donors.
In May 1983, Stanford University Hospital became the only major medical center in the United States to decide to begin testing blood for evidence of AIDS infection. "The rest of the blood industry was stunned .... Some said it was a gimmick to draw AIDS-hysteric patients to Stanford from San Francisco hospitals."
In January 1984, the blood industry was continuing to stonewall. The cost of AIDS screening would be high; moreover, the industry was afraid of what it would do to both the supply of donors and the demand for blood from nonprofit blood banks. "In early January, Assistant Secretary for Health Ed Brandt set up a conference call of blood bankers and CDC officials to discuss the AIDS problem. The upshot of all the talk was no new FDA policy; instead the blood bankers agreed to form a task force to study the issue." 5 The careful...
To try again, please visit the B&N Marketplace.



