The Basic Building Blocks of Organizational Structure

This text explains the formation of organizational structures. It includes a case study as an example of one company's path to designing the organizational structure after several acquisitions. It also provides an overview of the linkages between leadership and departments.

Creating an Organizational Structure

Reasons for Changing an Organization's Structure

Creating an organizational structure is not a one-time activity. Executives must revisit an organization's structure over time and make changes to it if certain danger signs arise. For example, a structure might need to be adjusted if decisions with the organization are being made too slowly or if the organization is performing poorly.

In 2014, Walmart Canada confirmed that it laid off 750 employees across Canada to re-work its management structure.  According to the company, after testing a new management structure in select stores, 1,300 associates were promoted to more senior roles and about 200 senior managers were added.

Procter and Gamble, the world's largest consumer products manufacturer, announced in 2014 that it may sell off its iconic Ivory soap brand. A range of reports pegged Ivory's 2013 global revenues at $112 million, and its share of the U.S. bar soap market at 3.4 percent. Even though Ivory maintains a high profile, it has retreated significantly from its highs of past decades, and it may be considered an expendable laggard among the high-performance product mix that P&G's CEO wants to create. P&G is being trimmed to concentrate on the seventy to eighty brands that generate more than $100 million in gross annual revenues. Ivory is just above that cutline, and projections do not call for growth.

Sometimes structures become too complex and need to be simplified. Many observers believe that this description fit Cisco Systems Inc., which designs, manufactures, and sells networking equipment. The company's CEO, John Chambers, has moved Cisco away from a hierarchical emphasis toward a focus on horizontal linkages. As of late 2009, Cisco had four types of such linkages. For any given project, a small team of people reported to one of forty-seven boards. The boards averaged fourteen members each. Forty-three of these boards each reported to one of twelve councils. Each council also averaged fourteen members. The councils reported to an operating committee consisting of Chambers and fifteen other top executives. Four of the forty-seven boards bypassed the councils and reported directly to the operating committee. These arrangements are so complex and time consuming that some top executives spend 30 percent of their work hours serving on more than ten of the boards, councils, and the operating committee.

Because it competes in fast-changing high-tech markets, Cisco needed to be able to make competitive moves quickly. The firm's complex structural arrangements are preventing this. In late 2007, a competitor, Hewlett-Packard (HP), started promoting a warranty service that provides free support and upgrades within the computer network switches market. Because Cisco's response to this initiative had to work its way through multiple committees, the firm did not take action until April 2009. During the delay, Cisco's share of the market dropped as customers embraced HP's warranty. This problem and others created by Cisco's overly complex structure were so severe that one columnist wondered aloud, "Has Cisco's John Chambers lost his mind?" (Blodget, 2009). In the summer of 2011, Chambers reversed course and decided to return Cisco to a more traditional structure, while reducing the firm's workforce by 9 percent. Time will tell whether these structural changes will boost Cisco's stock price, which dipped to $18 in mid-2011, but had rallied to the $24 range by 2014.