I will state my side early: for most mid-sized Indian companies, a full matrix organisation costs more than it returns, and a clean single reporting line with well-defined dotted lines does the job better. That said, the matrix exists for a reason, and there are companies where it is the only structure that works. Let me compare the two fairly.
What the matrix is trying to solve
Every organisation has at least two things it wants to organise by. A software services firm cares about technology practices (data, cloud, testing) and about customer accounts. A consumer goods company cares about products and about regions. A pharmaceutical company cares about functions like research and regulatory affairs and about each drug programme.
A traditional structure picks one axis and lives with the pain on the other. Organise by practice, and the account manager has no say over the people delivering for their customer. Organise by account, and each account builds its own small cloud team, and the company’s cloud expertise is split into pieces that never learn from each other.
The matrix says: do both. A data engineer reports to a practice head for skills, standards and career growth, and to a project or account manager for day-to-day work. Two bosses, two axes, both visible.
What you gain
- Shared expertise. Specialists sit in one pool and move to where they are most needed, instead of idling in one account.
- Better use of scarce skills. One rare security architect can serve five projects.
- Both views stay on the table. Customer needs and technical standards are each represented by someone who has authority.
What it costs
The cost shows up as friction. The person with two bosses gets two sets of priorities, and when they conflict, the employee is the one who has to choose, which is a bad place for a junior to stand. Who writes the appraisal? Usually the home manager, who has seen very little of the daily work, based on a note from the other manager who has seen all of it and has no power over the rating. That is a source of grievance in almost every matrix I have read about in practice.
Decision speed drops. Anything that touches both axes, such as whether to staff a project with a particular person, needs two managers to agree. When they disagree, it goes up to the first common boss, which may be several levels away. You also pay in meetings. A matrix runs on resourcing conversations, forecast calls and escalation forums that a single-line structure simply does not need.
And there is the human cost that exists in a quiet way: unclear ownership. When everyone shares responsibility for an outcome, it is easy for nobody to feel accountable for it.
The alternative: one line, with real dotted lines
A simpler option is to choose one primary axis and give it full authority over the person: hiring, appraisal, pay, promotion. The other axis gets a defined influence, a dotted line, with specific rights written down. The practice head may set technical standards and must be consulted on promotions. The account manager may escalate performance problems and must give a written input to appraisals. The employee knows exactly who decides.
This gives up some of the flexibility of the matrix. In return, there is one boss who owns the person, and the conversations are shorter. For a company of a few hundred or a couple of thousand people, that trade is usually good.
When I would still choose the matrix
Not always, and I would not claim otherwise. A matrix earns its keep when three things are true together. The company is large enough that duplicating specialists across every unit would be wasteful. The work really does require both axes to co-decide, such as a global product company where regional pricing and global product standards both have to be right. And the leadership is willing to invest in the supporting machinery: a clear escalation rule, joint goal-setting, and a decision on who owns the appraisal that is announced before the first dispute, not after it.
If any of those is missing, the matrix tends to become an organisation chart with two sets of lines and no real change in who decides. Employees then work for whoever shouts louder, and that is a bad way to run anything.
A quick test before you adopt one
Take one typical employee and ask four questions. Who sets their goals? Who rates them? Who decides their promotion? Who do they go to when two requests clash? If the answers are four different names, or if the honest answer is “it depends”, you have an unclear matrix. If you can answer each question with one name and a written rule, you have a structure that people can work in, whatever shape the chart takes.
Leave a Reply