Intro to Business › Section G · Organizational structure › Topic G.2
Matrix, team, and other contemporary structures
Traditional structures are clear and stable but can be slow to react. Contemporary structures, especially the matrix and the committee, mix and share authority so that specialists from different departments can work on the same problem.
Why new structures emerged
A functional structure is efficient when work is routine, but many organisations now run projects that need several kinds of expertise at once. Designing a new electric scooter needs engineers, designers, finance staff and marketers working closely for a year or two. In a purely functional firm, each specialist reports up through a separate department, and coordination must travel up one ladder and down another. As products became more complex and markets faster, firms experimented with structures that cut across departments. The best-known are the matrix structure and the committee structure, alongside team-based designs examined in the next topic, Using teams to boost performance.
The matrix structure
A matrix structure, which some texts call the project management approach, combines two forms of departmentalisation at once, usually functional and product or project. It is often layered on top of a line-and-staff organisation. People from different functional areas, such as manufacturing, finance and marketing, are assigned to a project, while still belonging to their home department. Each employee therefore has two direct supervisors: the functional manager, who looks after their professional skills and long-term career, and the project manager, who directs their work on the project. On a chart, functions run down the columns and projects across the rows, which is where the name matrix comes from.
Breaking unity of command
Henri Fayol's principle of unity of command, discussed further in the topic Authority and centralization, says each employee should take orders from only one boss. A matrix deliberately breaks this rule. The dual chain of command is the source of both its power and its problems. It lets the organisation balance two sets of priorities, such as technical excellence from the functional side and deadlines and budgets from the project side. But an employee caught between two managers who want different things may not know whose instructions come first. For this reason, firms that use a matrix must agree clearly in advance how conflicts between the two lines will be settled.
Advantages of the matrix
The matrix has several strengths. Teamwork: pooling specialists from different functions increases creativity and makes complex tasks manageable. Efficient use of resources: project managers draw only the specialist time they need, instead of each project building its own large, underused group. Flexibility: project teams can be formed and disbanded as needs change. Balancing objectives: the customer wants quality and predictable cost, the firm wants profit and new technical capability, and different members can speak for each goal. Motivation: project work can raise ownership and commitment. Development: employees build technical and interpersonal skills by working beyond their own department.
Worked example: sharing designers
A product firm runs three projects needing 30, 25 and 25 hours of design work a week. A designer works 40 hours a week. 1. Without a matrix, each project hires its own designer: 3 designers, \(3 \times 40 = 120\) hours available. 2. Hours needed: \(30 + 25 + 25 = 80\). Utilisation: \(80 \div 120 \approx 67\%\), so a third of paid design time is idle. 3. With a matrix, the design department lends its staff to projects as needed: \(80 \div 40 = 2\) designers cover all the work. 4. Utilisation becomes \(80 \div 80 = 100\%\). Had the total been 90 hours, \(90 \div 40 = 2.25\), so 3 designers would be needed: people come in whole numbers. 5. Trade-off: each designer answers to the design head and to several project managers.
Disadvantages of the matrix
The matrix also carries real costs. Power struggles: functional and project managers may have different goals and styles and compete for the same people. Confusion: reporting relationships and responsibilities can be unclear, especially when priorities clash. Weak cohesion: team members from different functions may struggle to communicate and work as one team. Slower decisions: agreeing across two lines takes time, and performance can be hard to measure when two managers judge the same person. Some large firms have moved away from complex matrices for these reasons, simplifying into product divisions with clearer accountability. A matrix works best when managers on both sides communicate constantly and settle conflicts quickly.
Worked example: a clash of priorities
Priya, a quality engineer, reports to the head of engineering and to the project manager for a new medical device. The project manager wants her to sign off a component this week to meet a trade-show deadline; the engineering head wants two more weeks of testing. 1. Identify the cause: the dual chain of command, with each boss representing a legitimate goal, speed and quality. 2. Priya should not quietly pick a side; she should raise the conflict with both managers together. 3. The managers weigh the risks: for a medical device, patient safety outweighs a trade-show date. 4. Outcome: the device is shown as a prototype, and testing continues.
The committee structure
In a committee structure, a group, not a single person, holds authority and responsibility. Committees usually sit within a larger line-and-staff organisation. Many are purely advisory, but some have the power to make and carry out decisions, such as a board-appointed executive committee that runs a company's day-to-day operations, or a hospital's safety committee that can halt a procedure. Committees bring diverse viewpoints to a problem and widen the range of possible solutions, and they help coordinate work across departments. Their drawbacks are well known: they can be slow, can be dominated by one strong member, and make it hard to hold any one person accountable.
Team-based and flatter designs
Some organisations go further and build the whole structure around teams rather than departments. Cross-functional and self-managed teams take on work that supervisors and departments used to handle, and the hierarchy becomes much flatter. A few firms have experimented with removing traditional managers almost entirely, giving teams or individuals responsibility for coordinating directly with colleagues and customers. Results have been mixed: such designs can speed decisions and raise engagement, but some firms that tried them later restored some management roles. The next topic looks at how teams work, and the topic Trends in organizational structure covers network and virtual designs.
Common mistakes to avoid
First, thinking a matrix employee has a single boss: there are two, a functional manager and a project manager. Second, assuming the matrix keeps the unity of command principle; it deliberately breaks it. Third, describing a matrix as a team with no structure; it is a formal design combining functional and product or project lines. Fourth, listing efficiency of resources as a disadvantage; sharing specialists across projects is one of the matrix's main strengths. Fifth, assuming committees always decide quickly because several minds are involved; they are often slower than an individual and make accountability harder to assign.
Key takeaways
Contemporary structures arose to coordinate expertise across departments in complex, fast-moving work. A matrix structure combines functional and product or project departmentalisation, giving each employee two supervisors and breaking unity of command. Its advantages include teamwork, efficient sharing of specialists, flexibility, balanced objectives, motivation and development; its disadvantages include power struggles, confusion, weak cohesion and slower decisions. In a committee structure a group holds authority; committees widen viewpoints but can be slow, dominated by one member and weak on accountability. Team-based designs flatten the hierarchy further.
Flashcards
Flashcard
Combines functional and product or project departmentalisation
Test your understanding
Question 1 of 5
In a matrix structure, who are an employee's two direct supervisors?
Question 2 of 5
Four projects need 20, 15, 15 and 10 hours of analyst time a week, and each analyst works 40 hours. How many analysts does a matrix need, compared with one per project?
Question 3 of 5
Which management principle does a matrix structure deliberately break?
Question 4 of 5
Which is a disadvantage of the matrix structure?
Question 5 of 5
A company sets up a committee to choose a new software system. What drawback should it expect?
