Matrix Organization

Every growing company eventually gets stuck on one question: what do you cut the company along? A functional organization groups people by the work they do, so all the designers sit together. That makes it easy to keep screens consistent and easy to train someone new, but shipping one feature means collecting schedules from three separate teams. A product-oriented organization cuts along products or goals instead, putting planning, design and engineering inside one team that can take a feature all the way out. It's faster, and about six months in the button team A built and the button team B built no longer look alike.

Companies that tried both kept having the same conversation on a two-year loop. It would start with "let's split by product this time so we can move," turn into "quality is all over the place, let's group by craft again" a year later, and a year after that someone would point out that a single feature now takes a month to ship. With only one axis available, choosing one side meant giving the other one up outright.

The matrix answers that by adding a second axis rather than picking a better single one. Put people on mission teams, keep the craft connection alongside it, and you no longer have to trade speed for consistency. What you take on instead is a new problem: two people now have a claim on the same person's attention.

Two reporting lines run to one person at the same time. One is the mission side, which decides what that person works on this week. The other is the craft side, which decides what standard the work has to meet.

The two lines are not equally heavy.

1. Reporting line — the formal relationship, usually drawn as a solid line. Performance reviews, salary decisions and time-off approvals all travel along it.
2. Dotted-line reporting — a working relationship that exists because of the job but carries no review authority. The dotted-line manager can demand a standard and comment on the output, but does not set the person's rating.
3. A decision-rights document — a single page that names who decides at each point where the two lines overlap. It lists hiring approval, prioritization and the right to reject work on quality grounds, and assigns each one to a side.

Which side holds the solid line changes the character of the whole structure. If the solid line sits on the craft side, standards run strong and the mission lead has to ask for cooperation. If it sits on the mission side, delivery speeds up while the craft lead loses the leverage to protect quality. If both lines are solid, every overlapping decision gets escalated by two people at once, and the layer above them accumulates a weekly queue of arguments it has no context for.

Span of control gets pulled in here too. When one craft lead covers people scattered across several mission teams, headcount hasn't changed but the meeting load has roughly doubled. A design lead responsible for ten designers spread across five mission teams runs ten one-on-ones plus five team meetings, and those fifteen slots come out of the same week.

All of this shows up on the org chart as two kinds of line. Solid lines are drawn unbroken, dotted lines broken, and both are drawn reaching the same person.

The most common trigger is a craft that is too small to staff every mission team properly. Four designers and four product teams means one designer per team, and in that arrangement nobody is reviewing anyone else's screens. Adding a single craft lead and connecting the four by dotted line is the smallest working matrix there is.

Crafts where a wrong standard becomes a company-level problem use the same shape. Security, data and legal are the usual ones. If each mission team handles personal data its own way, the incident happens in one team and the liability lands on the company. So the specialist sits with the mission team while the standard is set in one place.

By company size, this pattern clusters between roughly 40 and 300 people. Below that there are only one or two people per craft and no reason to appoint a lead; above it each craft grows into a full team of its own and the company drifts toward running several product-oriented organizations side by side.

Plenty of structures with different names are this same thing. The squads and chapters of the Spotify model are the clearest example. People sit on small goal-owning teams while members of the same craft meet separately, which is two axes holding one person, whatever the vocabulary.

"Let me check with my dotted line and get back to you."

The mission team can't settle this alone; the craft lead's standard has to be confirmed first.

"I write Theo's review. I'll take input from the mission side and factor it in."

Confirming that the solid line sits on the craft side and the mission lead has an advisory role.

"The matrix is fine, but let's write down who decides when priorities collide."

Accepting the structure while pointing out that it does not run without a decision-rights document.

Pagedeck moved to this shape when the company hit 45 people. Noa sits on the document-editing team and draws its screens every day, and is also connected by a dotted line to the person who oversees design across the product, reviewing work together every other week.

The first month after the move was slower, not faster. Noa kept explaining the same thing twice to two people, and whenever the two disagreed the work stopped where it was. The stalls only dropped off after Grace wrote the decision rights onto a single page. Its first line splits the pair cleanly: the mission side decides what gets built, the craft side decides how it gets built.

The most frequent misreading is that "two managers" means two people holding equal authority. With two lines on the chart that's a reasonable guess. In practice one line is solid and the other dotted, and exactly one side writes the review. Leave that difference unwritten and both managers assume they come first, while the person in the middle ends up following whoever pushes hardest.

The second is treating the structure as a fix for collaboration problems. The more a company suffers from scattered standards and endless meetings, the more a new chart looks like the answer. But this shape does not reduce meetings — it adds them. What shrinks is the spread between standards, not the number of conversations. If the real cause was teams chasing different goals rather than overlapping authority, drawing one more line just relocates the same argument onto the new line.