Читать книгу Reframing Organizations - Lee G. Bolman - Страница 46

Two issues are central to structural design: how to allocate work (differentiation) and how to coordinate diverse efforts after parceling out responsibilities (integration). As we have seen, even in a group as small and intimate as a family or racing crew, it is important to settle issues concerning who does what, when the “what” gets done, and how individual efforts mesh to ensure harmony. Every family, group, and organization will find an arrangement of roles and synchronization that works—or suffer the fallout.

Division of labor—or allocating tasks—is the keystone of structure. Every living system creates specialized roles to get important work done. Consider an ant colony:

Small workers … spend most of their time in the nest feeding the larval broods; intermediate‐sized workers constitute most of the population, going out on raids as well as doing other jobs. The largest workers … have a huge head and large powerful jaws. These individuals are … soldiers; they carry no food but constantly run along the flanks of the raiding and emigration columns. (Topoff, 1972, p. 72)

Like ants, humans long ago discovered the virtues of specialization. A job (or position) channels behavior by prescribing what someone is to do—or not do—to accomplish a task. Prescriptions take the form of job descriptions, procedures, routines, protocols, or rules (Mintzberg, 1979). On one hand, these formal constraints can be burdensome, leading to apathy, absenteeism, and resistance (Argyris, 1957, 1964). On the other, they help to ensure predictability, uniformity, and reliability. If manufacturing standards, aircraft maintenance, hotel housekeeping, or prison sentences were left solely to individual discretion, problems of quality and equity would abound.

Once an organization spells out positions or roles, managers face a second set of key decisions: how to group people into working units. They have several basic options (Mintzberg, 1979):

 Function: Groups based on knowledge or skill, as in the case of a university's academic departments or the classic industrial units of research, engineering, manufacturing, marketing, and finance.

 Time: Units defined by when they do their work, as by shift (day, swing, or graveyard shift).

 Product: Groups organized by what they produce, such as detergent versus bar soap, wide‐body versus narrow‐body aircraft.

 Customer: Groups established around customers or clients, as in hospital wards created around patient type (pediatrics, intensive care, or maternity), computer sales departments organized by customer (corporate, government, education, individual), or schools targeting students in specific age groups.

 Place: Groupings by geography, such as regional or international offices in corporations and government agencies or neighborhood schools in different parts of a city.

 Process: Grouping by a flow of work, as with “the order fulfillment process. This process flows from initiation by a customer order, through the functions, to delivery to the customer” (Galbraith, 2001, p. 34).

Creating roles and units yields the benefits of specialization but creates challenges of coordination and control—how to ensure that diverse efforts mesh. Units tend to focus on their separate priorities and strike out on their own, as New York's police and fire departments did on 9/11. The result is suboptimization—individual units may perform splendidly in terms of their own goals, but the whole may add up to much less than the sum of the parts. This problem plagued Tom Ridge, who was named by President George W. Bush as the director of Homeland Security in the aftermath of the 9/11 terrorist attacks. His job was to resolve coordination failures among the government's many different units that dealt with security. But he was more salesman and preacher than 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.