Lee G. Bolman

Reframing Organizations


Скачать книгу

boss, and he lacked the authority to compel compliance. Ridge's slow progress led President Bush to create a cabinet‐level Department of Homeland Security. The goal was to cluster independent security agencies under one central authority.

      As often happens, the new structure created its own problems. Folding the Federal Emergency Management Agency into the mix reduced FEMA's autonomy and shifted its priorities toward security and away from its core mission of disaster relief. The same agency that had responded nimbly to hurricanes and earthquakes in the 1990s was slow and ponderous in the aftermath of Hurricane Katrina and lacked authority and budget to move without a formal okay from the new secretary of Homeland Security (Cooper and Block, 2006).

      Successful organizations employ a variety of methods to coordinate individual and group efforts and to link local initiatives with system‐wide goals. They do this in two primary ways: vertically, through the formal chain of command, and laterally, through meetings, committees, coordinating roles, or network structures. We next look at each of these strategies in detail.

      Authority

      The most basic and ubiquitous way to harmonize the efforts of individuals, units, or divisions is to designate a boss with formal authority. Authorities—executives, managers, and supervisors—are charged with keeping action aligned with strategy and objectives. They do this by making decisions, resolving conflicts, solving problems, evaluating performance and output, and distributing rewards and sanctions. A chain of command is a hierarchy of managerial and supervisory strata, each with legitimate power to shape and direct the behavior of those at lower levels. It works best when authority is both endorsed by subordinates and authorized by superiors (Dornbusch and Scott, 1975). In military organizations such as an aircraft carrier or a commando team, for example, the chain of command is usually clear and universally accepted. In schools and human service organizations, authority relations are often fuzzier or more contested. Another well‐known risk of hierarchy is that it may hamper the upward flow of novel information and “bad news” that subordinates fear their bosses may not welcome (Joseph and Gaba, 2020).

      Rules and Policies

      Rules, policies, standards, and standard operating procedures are developed to ensure that individual behavior is predictable and consistent. Rules and policies govern conditions of work and specify standard ways of completing tasks, handling personnel issues, and relating to customers and others. The goal is to ensure the handling of similar situations in comparable ways and to avoid “particularism” (Perrow, 1986)—responding to specific issues based on personal whims or political pressures. Two citizens' complaints about a tax bill are supposed to be treated similarly, even if one citizen is a prominent politician and the other a shoe clerk. The response to two residents requesting garbage pickup or a street repair should follow the same procedures regardless of economic status or race. Once a situation is defined as fitting a particular rule, the course of action is clear, straightforward and, in an ideal world, almost automatic.

      Standard operating procedures (SOPs) reduce variance in routine tasks that have little margin for error. Commercial airline pilots typically fly with a different crew every month. Cockpit actions are tightly intertwined, the need for coordination is high, and mistakes can kill. SOPs consequently govern much of the work of flying a plane. Pilots are trained extensively in the procedures and seldom violate them. But a significant percentage of aviation accidents occur in the rare case in which someone does. More than one airplane has crashed on takeoff after the crew missed a required checklist item.

      SOPs can fall short, however, in the face of “black swans” (Taleb, 2007)—freak surprises that the SOPs were never designed to handle. In the 9/11 terrorist attacks, pilots followed standard procedures for dealing with hijackers: cooperate with their demands and try to get the plane on the ground quickly. These SOPs were based on a long history of hijackers who wanted to make a statement, not wreak destruction on a suicide mission. Passengers on United Airlines Flight 93, who had learned via cell phones that hijackers were using aircraft as bombs rather than bully pulpits, abandoned this approach. They lost their lives fighting to regain control of the plane, but theirs was the only one of four hijacked jets that failed to devastate a high‐profile building.

      Planning and Control Systems

      Reliance on planning and control systems—forecasting and measuring—has mushroomed since the dawn of the computer era. Retailers, for example, want to know what's selling and what isn't. Networked point‐of‐sale terminals now yield that information instantly. Data flow freely up and down the hierarchy, greatly enhancing management's ability to oversee performance and respond in real time.

      Action planning specifies how to do something—methods and time frames as in “increase this month's sales by using a companywide sales pitch” (Mintzberg, 1979, pp. 153–154). Action planning works best when it is easier to assess methods than outcomes. This is often true of service jobs. McDonald's has clear specifications for how counter employees are to greet customers (e.g., with a smile and a cheerful welcome). United Parcel Service has a detailed policy manual that specifies how a package should be delivered. The objective is customer satisfaction, but it is easier to monitor employees' behavior than customers' reactions. An inevitable risk in action planning is that the link between action and outcome may fail. When that happens, employees may get bad results by doing just what they're supposed to do. Unions sometimes use this as a bargaining chip by instructing employees to “work to rule”—scrupulously observing every detail in every procedure—because it is often an effective way to slow work down to a crawl.

      Behavior in organizations is often remarkably overlooked and untouched by commands, rules, and systems. Lateral techniques—formal and informal meetings, task forces, coordinating roles, matrix structures, and networks—pop up