Leadership Success Pattern #6

A few years ago, I worked with leaders in a global matrix who had built the structure for good reasons. They needed stronger integration across markets and functions. They needed better use of specialist capabilities. They needed decisions to reflect more than one dimension of the business.

On paper, the logic was sound.

In practice, meetings multiplied, stakeholder lists kept growing, decision speed slowed, and too many issues were resolved through personal networks rather than the intended way of working. The matrix was blamed, as it often is.

But the matrix was not the main problem. Poor processes were.

This is one of the recurring misunderstandings I see in organisations. When matrix performance disappoints, the discussion quickly turns to collaboration, communication, and coordination. These things matter, of course. As The Contextual Leader puts it: “Operating in global matrix organizations and the related stakeholder management is in itself a critical leadership competence. Leaders need to lead and collaborate differently to get the value from the matrix interdependence.”

That is true. But it is not the full explanation.

A matrix is not chosen because collaboration is fashionable. It is chosen because the organisation faces interdependence it cannot handle well through a simple hierarchy: global-local trade-offs, cross-functional value creation, shared resources, or higher external complexity. The matrix is therefore a relevant structural response to a contextual requirement.

What many leaders then get wrong is where to put the centre of gravity.

They look at the matrix structure and try to govern from the org chart. They discuss mandates, forums, stakeholders, and escalation paths as if the structure itself should tell them how work must flow. It cannot. The real design object is not the matrix. It is the set of core processes and projects creating value.

Leading in a matrix is therefore not mainly about leading the structure or making people communicate more. It is about leading the processes that run through it. That changes the practical logic of leadership.

When leaders start with the processes, they can define where decisions belong, where handovers occur, who genuinely has a stake at each stage, what data must be shared, and which meetings are actually needed. They can separate necessary involvement from habits of overinvolvement. They can stop self-appointed stakeholders from entering everything simply because the criteria for involvement are now clearer.

This is also how meeting overload is reduced. In weak matrices, meetings become substitutes for process clarity. In stronger matrices, process milestones and process gates determine which decisions belong in which forums. Coordination becomes purposeful rather than unfocused involvement.

The same applies to formalisation. Many leaders still treat formalisation as bureaucracy. That is a costly mistake. In a matrix, fit-for-purpose formalisation prevents confusion, duplication, and slow decision-making. The issue is not whether to formalise, but what to formalise and at what level.

Core processes should be documented as lean as possible to become operating guideline that everyone can actually use. Detailed procedures, quality controls, and technical instructions can sit underneath where specialists need them. If leaders allow experts to overload the main process description with excessive detail, the process will not come alive in the business.

The matrix also does not become effective through empowerment alone. Empowerment without clear processes often fragments effort and turns voice into noise. The result is a familiar set of unhealthy beliefs: you need to know the right people, involve everyone, or bypass the process to get things done. In a matrix setting, that is poison.

What makes the difference is the combination of people and processes. The process creates the shared frame. The culture makes people use it. This is where discipline matters. Not discipline as rigid compliance, but as a shared commitment to use common processes, shared data, agreed handovers, and defined decision points as “the way we work around here.”

As the Contextual Leader states: “The leaders must get used to deciding together rather than relying on the organisational chart to stipulate who has the mandate to decide over the other.” That is exactly the point. But deciding together only creates value when the process tells us what we are deciding, when, with whom, and on what basis.

If leaders want the matrix to perform, they should stop treating it primarily as a governance chart. Put the core value-creating processes at the centre. Map the value contribution, the handovers, the decision points, the shared data picture, and the minimum necessary exchange spaces around them. Document the processes as lean as possible. Then lead it actively so people do not work around it, but through it. That is how a matrix becomes a powerful organisational capability.