Why Matrixed Organizations Adopt MBSE Faster (Sometimes)
A matrix can give the model a cross-functional home or create the dual-authority conflict that kills it.
There is a counterintuitive pattern worth examining: matrixed organizations sometimes adopt MBSE faster than functionally siloed ones. The intuition runs the other way. Matrixed organizations are complicated, with dual reporting lines and built-in tensions, so one might expect this to impede adoption. But the matrix suits MBSE because it requires cross-functional coordination, and the model is a tool for that coordination. The matrix’s existing cross-cutting structures give the model a home that a siloed organization lacks. That is the “faster” part. The “sometimes” part is equally important. The same matrix can create a dual-authority conflict—between functional managers and program managers, each claiming the model—that kills MBSE adoption. Whether the matrix helps or hurts depends on which feature dominates. This article explores the conditions that determine which way it goes.
This article is the second of seven in Week Ten, focused on organizational structure. Yesterday’s article established that models break at organizational boundaries and that the org chart predicts where they break. Today, we examine the matrix, a specific organizational form with a more complicated relationship to MBSE than its reputation suggests. The matrix creates cross-cutting structures that help the model, but also a dual authority that can destroy it. Understanding this dual nature is necessary for anyone adopting MBSE within one, because the same structure that could carry the initiative could also sink it.
## Why the Matrix Sometimes Helps
The matrix helps MBSE adoption when its cross-functional structures give the model a home, and its program managers want what it provides.
The matrix already does cross-functional coordination. A matrixed organization exists to coordinate across functions—to bring functional disciplines together around programs or products. This coordination is hard, and the matrix has built structures to do it: cross-functional teams, integration roles, and coordination processes. The model is a cross-functional coordination tool that fits within the matrix’s structures. In a siloed organization, the model has no cross-cutting home and must create one against the structure. In a matrix, that home already exists, and the model occupies it.
Program managers want the integrated view. In a matrix, they are responsible for delivering integrated outcomes across functions and need an integrated system view to do so. The model provides exactly that cross-functional view. Program managers become natural sponsors of the model. Their sponsorship, backed by program authority, gives the model a powerful advocate that a siloed organization’s purely functional leadership lacks. It creates demand for a shared representation. The functional-versus-program tension inherent in a matrix creates a need for a shared, authoritative representation of the system that both sides can reference—something that grounds the coordination between functional depth and program integration. The model can be that shared representation. The tension that complicates the matrix also creates a demand that the model can meet, and meeting that demand gives the model a clear purpose and a clear constituency.
When these features dominate—when cross-functional structures host the model, program managers sponsor it, and the matrix’s tension creates demand—the matrix accelerates MBSE adoption. The model fits the organization’s needs and finds ready advocates. This is the
## Why the Matrix Sometimes Hurts
The matrix impedes MBSE adoption when its dual authority makes the model a contested territory between functional and program management.
Dual authority creates a question of who owns the model. In a matrix, people answer to both functional and program managers, and the model does too. It serves the program’s integration needs and depends on the disciplinary content of the functions. The question of who owns the model — who decides its structure, standards, and priorities — has two claimants. Dual authority can turn the model into contested territory. The functional side wants the model to serve disciplinary needs; the program side wants it to serve integration needs. Conflict over which need dominates can stall the model’s development, as the proxy-debate article described for tool decisions.
Functional managers can resist what program managers push. When program managers sponsor MBSE but functional managers do not support it, the matrix’s dual authority gives functional managers power to resist, as tomorrow’s discussion of functional-manager veto will show. Program managers can mandate MBSE, but functional managers control people’s time and incentives. Their quiet non-support can defeat the mandate. The matrix’s balance of power, meant to coordinate the two authorities, can instead deadlock them, leaving the model caught in the middle.
Dual reporting divides the modelers’ attention and loyalty. People doing the modeling, answering to both authorities, may receive conflicting signals about how much to invest in the model and how to build it. The functional manager may signal that disciplinary work matters more; the program manager may signal that the integrated model matters more. Modelers caught between cannot fully serve either, and the model suffers from divided attention and loyalty created by the matrix’s dual reporting. Functional managers resist program managers, and the modelers are caught in the middle—the matrix impedes MBSE adoption because the model becomes a casualty of the matrix’s inherent tensions rather than a beneficiary of its cross-cutting structures. This is the
## What Determines Which Way It Goes
The matrix helps or harms, depending on a few conditions that tip the balance toward its model-friendly or model-hostile features.
The alignment between functional and program management matters. When both sides are aligned on MBSE—both see its value and support it—the matrix’s cross-cutting structures carry the model, and dual authority cooperates. When misaligned—one pushing, one resisting—the dual authority becomes a battleground, and the model is caught in the crossfire. Alignment between the two authorities is the most important condition because it determines whether the matrix’s dual nature cooperates or conflicts.
The clarity of model ownership matters. When the matrix establishes clear ownership—a defined authority over structure and standards, vested in a role, shared governance, or an explicit agreement between the functional and program sides—the dual-authority question is resolved, and the model can develop. When ownership is ambiguous, dual authority contests it, stalling the model. Clarity of ownership determines whether dual authority is resolved or leads to ongoing conflict.
The program managers’ commitment matters. When they are genuinely committed to MBSE and willing to use their authority to support it—to align incentives and insist on functional cooperation—the matrix’s program side carries the initiative. When program managers are only nominally supportive and unwilling to use their authority, functional resistance prevails. The depth of program managers’ commitment determines whether the model’s natural sponsors actually sponsor it.
These conditions—the functional-program alignment, ownership clarity, and program manager commitment—determine whether the matrix’s model-friendly or model-hostile features dominate. A matrix with alignment, clear ownership, and committed program managers adopts MBSE faster. A matrix with misalignment, ambiguous ownership, and uncommitted program managers can turn the structure against the model. The matrix is neither inherently good nor bad for MBSE; its effect depends on these conditions.
## What to Do This Week
If your organization is matrixed, take an hour this week and assess which way your matrix is tipping—whether it is giving your model a cross-functional home or turning it into a dual-authority battleground.
Assess the three conditions. Are the functional and program sides aligned on MBSE, or is one pushing while the other resists? Is the model’s ownership clear, with a defined authority over its structure and standards, or is it ambiguous and contested? Are the program managers genuinely committed to MBSE and willing to exercise their authority in support of it, or are they only nominally supportive? The pattern of answers tells you whether your matrix is in its model-friendly or model-hostile configuration.
If the matrix is tipping the right way—alignment, clear ownership, committed program managers—the structure is an asset. The move is to use it: let cross-functional structures host the model and program managers sponsor it. If tipping the wrong way—misalignment, ambiguous ownership, uncommitted program managers—the structure is a liability. The move is to address conditions by aligning with the functional program, establishing clear model ownership, and deepening program managers’ commitment. The matrix’s effect on your MBSE initiative is not fixed; it depends on conditions you can influence.
Tomorrow’s article continues the organizational-structure arc with the IPT boundary, where models always diverge. The week continues through Conway’s Law, the functional manager’s veto, the center-of-excellence debate, and why HR hears about MBSE last.
The matrix can carry the model or sink it. The difference lies in alignment, clarity of ownership, and program manager commitment. Assess which way yours is tipping.
Next in this series:
#66 · The IPT Boundary Where Models Always Diverge
About this series:
Modeling the Mission is a year-long Substack series on the difficulty of adopting MBSE in real organizations. New article every weekday plus weekend reflections.
If this article was useful, the easiest thing you can do is forward it to the colleague in a matrix who cannot tell whether the structure is helping the model or strangling it.