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.