matrix structure
Also called: matrix organization, dual reporting
A setup in which a person answers to two lines at once, for example a functional manager and a project or partner team. It needs clear decision rights between the two, or the person is left to resolve conflicting requests alone.
In a matrix structure a person answers to two lines at once: usually their functional manager (who hires them, develops them and owns their main work) and a project, product or partner team that directs part of their time. Companies use it to share scarce skills and to connect teams without moving people between them. It can be company-wide or small: one coordinator spending one day a week on another team's work is a matrix too.
The cost is that two sets of priorities land on one person. When the two lines want different things on the same day, someone has to choose, and without agreed rules that someone is the person in the middle, who has the least authority to do it. So a matrix works only with clear decision rights between the two managers, agreed before it starts: who sets the priorities for the shared time, what happens when one side has a spike, who gives feedback and contributes to the review, and where disagreements between the two managers go. They go to the managers, or to the person both report to, never to the person in the middle.
For a small team the questions are practical. Who takes the role should depend on interest and growth, not on who never says no. The arrangement should have a review date, because it is easy to undo. And the capacity it removes from the home team has to be counted before the busy season, not discovered during it.
Example
Mid-July 2027. Roman from tutor operations asks Klasna's Support lead for one coordinator to handle tutor scheduling on Tuesdays. Roman would set the Tuesday tasks; the lead stays the coordinator's manager. First, the cost. Under the team's capacity rule a coordinator has 30 ticket hours a week, so one day in five is 6 hours, or 24 hours in a four-week month:
So the reply to Roman sets the decision rights before the start:
- Who: a coordinator who wants it, as a stretch with an end date, not whoever never says no.
- Roman decides the Tuesday priorities; the lead decides everything else and the coordinator's review, with Roman's written input.
- Busy-queue rule: in August, or any week when first replies on shift pass 45 minutes, the Tuesday goes back to the queue; Roman hears it from the lead, not from the coordinator.
- Disagreements between Roman and the lead go to Iryna. Review after four Tuesdays.
Common mistakes
- Leaving the person in the middle to resolve conflicts. Disagreements between the two lines go to the managers.
- No rule for a spike. Agree in advance which side wins when one side is overloaded.
- Feedback from one line only. The review should include the second manager's written view.
- Not counting the capacity it removes. A day a week is a fifth of a person; check it against the busy season.
- Making it permanent by default. Start with a trial and a review date.
Learn it in the course
- Structuring a small team · Choose between a split by subject, by channel or a shared pool, give each area an owner and a backup, and make hand-offs and two-boss setups work.