Matrix organizational structure explained

Org chart

The chart shows the functional lines that own each person: engineering, design and quality. The project office holds the project managers who also direct the same people horizontally, a second line the tree cannot draw.

Levels and designations

Approval chains

How the model works

Two managers share each person, on purpose. The functional manager owns the person's skill, pay, growth and where they sit between projects. The project manager owns what the person delivers on the current job, its scope and timeline. Take a 400-person engineering services firm in Chennai: an engineer belongs to the mechanical engineering function under an engineering manager, and is also assigned to a client project under a project manager. The engineer takes technical direction from the function and task direction from the project. When the project ends, the engineer stays in the function and moves to the next project, so scarce specialists are shared rather than duplicated in every team.

Strengths and weaknesses

The strength is sharing scarce experts across many projects while keeping their skills sharp in a home function. It balances two competing needs, deep expertise and project delivery, and lets the company flex its best people onto the work that matters most right now.

The weakness is the double boss. When the function and the project pull in different directions, the person is caught in the middle, and authority over priorities, leave and appraisal can blur. It needs more meetings and negotiation, decisions can slow, and it works only when the two managers cooperate and one line is agreed as primary for people matters.

• Scarce specialists shared across many projects at once
• A balance of deep skill and project delivery
• Conflict and confusion from two managers with different priorities
• More coordination, meetings and slower decisions

When it fits

The matrix fits companies that run several projects or products at the same time and cannot afford a full set of specialists in each, so they must share people. IT services, consulting, EPC and product firms use it often. It works only when leaders accept the extra coordination and set clear rules: usually the functional manager is the primary reporting manager for pay, leave and reviews, while the project manager directs daily work. It fits badly in simple, stable operations where a single clear boss is faster and less confusing than a grid.

• Several parallel projects or products needing shared experts
• A culture that accepts coordination and negotiation
• A clear rule on which line is primary for people matters
• Not for simple, stable operations that need one clear boss

Set up this structure in ZeniaHR

1. Create departments for the functions, such as Engineering, Design and Quality, and add a projects grouping so both lines exist under Organization masters.
2. Decide which line is primary for people matters, usually the function, and set that manager as each person's single reporting manager in the system.
3. Add designations for functional roles and for project roles like Project Manager, and use grades to hold pay bands across projects.
4. Give every person one reporting manager of record, the functional manager, so leave, attendance and reviews have one clear owner, even though a project manager directs the daily work.
5. Use the org chart to keep the functional reporting line clean, since ZeniaHR approvals follow the reporting manager then HR.
6. Route reimbursement through the project manager and finance where project budgets apply, while keeping leave and attendance on the reporting manager then HR.

Frequently asked questions