Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Glossary

Matrix organisation: definition, types, advantages and limits

Domain

Project management and PMO

In brief

The matrix organisation is a structure in which each employee reports both to a functional manager and to a project manager. It exists in three variants (weak, balanced and strong matrix) depending on the authority granted to the project manager, and sits between the functional organisation, built on disciplines, and the project-based organisation, built on dedicated teams.

Page contents

Definition of the matrix organisation

The matrix organisation is a company structure in which two lines of authority intersect. The first is vertical: that of disciplines or functions (engineering, production, finance, legal). The second is horizontal: that of projects, products or programmes. Represented as a table, this structure forms a matrix, hence its name.

In practice, an employee keeps their attachment to a functional department, whose manager looks after their skills, appraisal and career. At the same time they are assigned to one or more projects, whose manager expects them to contribute to a result. They therefore have two managers.

What a matrix structure is for

This structure emerged to resolve a tension. A company wants to keep strong centres of expertise, which grouping by discipline allows. It also wants to run projects that cut across these centres, with a single person responsible for the result. The matrix seeks to achieve both.

It makes it possible to share scarce skills between several projects instead of duplicating them. It gives each project an identified point of contact. Finally, it prevents people from losing their professional anchoring when the project ends.

Weak, balanced or strong matrix

Project management frameworks, notably that of the Project Management Institute, distinguish three variants depending on how power is split between the project manager and functional managers.

Criterion Weak matrix Balanced matrix Strong matrix
Authority of the project manager Limited: coordinates and follows up Shared with the functions High: leads
Time the project manager devotes to the project Part time Often full time Full time
Budget control Functional managers Shared Project manager
Assignment of people Decided by the functions Negotiated Requested by the project, provided by the functions
Common reporting line of the project manager A functional department A functional department A projects department or a PMO

The weak matrix remains close to the functional organisation. The strong matrix approaches the project-based organisation, without going as far as completely detaching teams from their discipline.

Advantages and limits

What the matrix brings. Better use of experts, who work where they are useful. A cross-functional view of projects. Skills maintained in functional centres. The ability to launch and close projects without reorganising the company.

What it costs. Dual authority creates priority conflicts, which the employee is the first to suffer. Decisions escalate too high when they have not been planned for. Coordination consumes meeting time. The most sought-after experts end up spread over too many projects, and all the projects slow down together.

A matrix works when three rules are written down: who sets priorities between projects, who decides on a person’s assignment in the event of disagreement, and who appraises the employee. The first rule falls under project portfolio management. The other two fall to senior management.

Functional organisation and matrix organisation: the comparison

The functional organisation is the classic company structure. People are grouped by speciality (sales, production, IT, finance), and each has only one manager. Coordination goes through the hierarchy. When a project involves several departments, it progresses through successive handovers or under the authority of a department head, with no project manager holding authority of their own.

Its strengths are real: clear authority, in-depth expertise, readable career paths and good cost control. Its weaknesses appear as soon as cross-functional projects multiply. No one is answerable for the overall result, day-to-day priorities come before those of the project, and lead times lengthen at every boundary between departments.

Criterion Functional organisation Matrix organisation Project-based organisation
Reporting line of people One functional manager Two managers The project manager
Person responsible for the project result Diluted across departments The project manager, with variable authority The project manager
Strength Expertise and stability Sharing of skills Speed and focus
Weakness Silos Priority conflicts Duplication of resources

The functional structure suits a stable activity, where projects are rare or fit within a single department. The matrix structure is justified when cross-functional projects are numerous and draw on the same skills. Neither is superior in absolute terms, and the same company can combine several structures across its divisions.

Matrix structure and project mode: not to be confused

“Project mode” refers to a way of working: an objective, a multidisciplinary team, a schedule. The matrix organisation refers to a permanent structure, with its reporting lines and rules of authority. A functional company can occasionally work in project mode without being a matrix. Conversely, showing a matrix on the organisation chart is not enough if project managers have no means of obtaining the resources promised.

Example: moving from a weak matrix to a balanced matrix

An industrial company is preparing the launch of a new product range. The project brings together design engineers, a buyer, a lawyer and a quality manager, each attached to their own department. The project manager, himself a design engineer, devotes only part of his time to it and can only make requests of his colleagues. When the lawyer is called on by her department for a dispute, the review of supplier contracts stops, and no one has the authority to decide.

Management then changes three things. The project manager is appointed full time. Assignments are set each month in a meeting between project managers and functional managers. A director is designated to arbitrate disagreements. The reporting lines have not changed, but the project now has a voice in assignment decisions.

Changing a structure alters balances of power: the subject is handled with the methods of change management, and the governance framework that accompanies it falls under setting up a PMO.

Insights

Further reading

All insights
Building a project communication plan, from audiences to measurement

A project communication plan is the document that sets, for each audience affected by a project, what it is told, by whom, through which channel and on what date, and how to check that the message has been understood. Management Square describes here how to build it in five steps (audiences, messages, channels, schedule, measurement), with what each produces and who is accountable for it.

Read the analysis
Resistance to change: reading the symptoms, treating the causes

Resistance to change refers to the behaviours by which people slow down, work around or refuse a new way of working. Management Square treats it here as a symptom to diagnose: the signs to note, the four possible causes (not knowing, not being able, not wanting, not being required to) and the remedies ranked in order of effort.

Read the analysis
What is the difference between a PMO and a project manager, and which do you need?

The difference between a PMO and a project manager lies in what each is accountable for: the project manager answers for delivering a project, the PMO for the reliability of information and the management framework, across one or several projects. Management Square compares the two roles here (scope, accountability, decisions, deliverables) and describes when an organisation needs one, the other or both.

Read the analysis

FAQ

Frequently asked questions

Another question? Ask us

What is a matrix organisation?

It is a structure that crosses two lines of authority: that of disciplines (or functions) and that of projects, products or geographical areas. An employee therefore has two managers: a line manager, responsible for their expertise and career, and a project manager, responsible for the result to which they contribute.

What is the difference between a weak, balanced and strong matrix?

The difference lies in the authority of the project manager. In a weak matrix, the project manager coordinates without decision-making power, and functional managers keep control of people and budget. In a balanced matrix, authority is shared. In a strong matrix, the project manager leads full time, holds the budget and obtains resources from the functions.

What is the difference between a functional organisation and a matrix organisation?

The functional organisation groups people by speciality, under a single line manager, and handles projects within each department or by successive handovers from one department to another. The matrix organisation adds a cross-functional line of authority, that of the project. It gains in coordination what it loses in simplicity of command.

What are the drawbacks of a matrix organisation?

The main one is dual authority: an employee may receive conflicting priorities from their two managers. Added to this are the cost of coordination, slower decisions when trade-offs have not been planned for, and the overload of experts assigned to too many projects at once. These shortcomings can be controlled through explicit arbitration rules.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.