Matrix organisation

A matrix organisation is a company structure where people belong to more than one part of the organisation at the same time. Typically, a functional group (engineering, design, testing, data, etc.) and a product, programme, or project team. Instead of a single hierarchy, the organisation is arranged as a grid or “matrix,” allowing skills to move to where they’re most needed.

Matrix organisations usually use matrix management to coordinate this dual structure. It’s designed to help companies stay adaptable when dealing with complex products, multiple regions, or rapid scaling. You’ll find matrix structures in large, multi-disciplinary organisations, or where collaboration across teams and specialisms is essential. Some organisations have used and discarded this method due to slower decision-making, role and priority ambiguity, and even power struggles.

Working in a matrix organisation means navigating shared ownership, competing priorities, and sometimes conflicting feedback. But when it works well, it gives people a strong home for their professional development while keeping cross-functional teams empowered to deliver real outcomes. When it doesn't work well... watch out.

A matrix is an organisational structure in which two or more lines of command, responsibility, or communication run through the same individual. Matrix management is almost the opposite; an employee will report to two managers, typically a functional manager and a project manager.

Example

In a previous role, my (functional) manager worked in another area of the business and my (project) manager was responsible for my day-to-day activities. Matrix management was adopted for all testers so that an employee (Emily) reported to a manager in the same project or product area (the tech lead, an experienced developer) and another more experienced person of the same job family within the same office location.

When describing my experience in the below article, I described the more senior tester as my “main” manager, however this person didn't have all of the day-to-day context of my project.