BUS603: Managing People

Matrix structures move closer to organic systems in an attempt to respond to environmental uncertainty, complexity, and instability. The matrix structure actually originated at a time in the 1960s when U.S. aerospace firms contracted with the government. Aerospace firms were required to "develop charts showing the structure of the project management team that would be executing the contract and how this team was related to the overall management structure of the organization". As such, employees would be required to have dual reporting relationships - with the government and the aerospace company.

Since that time, this structure has been imitated and used by other industries and companies since it provides flexibility and helps integrate decision-making in functionally organized companies.

Matrix designs use teams to combine vertical with horizontal structures. The traditional functional or vertical structure and chain of command maintains control over employees who work on teams that cut across functional areas, creating horizontal coordination that focuses projects that have deadlines and goals to meet within and often times in addition to those of departments. In effect, matrix structures initiated horizontal team-based structures that provided faster information sharing, coordination, and integration between the formal organization and profit-oriented projects and programs.

This structure has lines of formal authority along two dimensions: employees report to a functional, departmental boss and simultaneously to a product or project team boss. One of the weaknesses of matrix structures is the confusion and conflicts employees experience in reporting to two bosses. To work effectively, employees (including their bosses and project leaders) who work in dual-authority matrix structures require good interpersonal communication, conflict management, and political skills to manage up and down the organization.

Different types of matrix structures, some resembling virtual team designs, are used in more complex environments.

For example, there are cross-functional matrix teams in which team members from other organizational departments report to an "activity leader" who is not their formal supervisor or boss. There are also functional matrix teams where employees from the same department coordinate across another internal matrix team consisting of, for example, HR or other functional area specialists, who come together to develop a limited but focused common short-term goal. There are also global matrix teams consisting of employees from different regions, countries, time zones, and cultures who are assembled to achieve a short-term project goal of a particular customer. Matrix team members have been and are a growing part of horizontal organizations that cut across geographies, time zones, skills, and traditional authority structures to solve customer and even enterprise organizational needs and demands.

As part of the next discussed organizational type of structure, networked teams, organizational members in matrix structures must "learn how to collaborate with colleagues across distance, cultures and other barriers. Matrix team members often suffer from the problem of divided loyalties where they have both team and functional goals that compete for their time and attention, they have multiple bosses and often work on multiple teams at the same time. For some matrix team members this may be the first time they have been given accountability for results that are broader than delivery of their functional goals. Some individuals relish the breath and development that the matrix team offers and others feel exposed and out of control". To succeed in these types of horizontal organizational structures, organizational members "should focus less on the structure and more on behaviors".