Stop Fixing Your Processes. Fix Your Power Structure Instead.

You’ve been there. The cross-functional meeting ends. Everyone nods. The decision is made. And then… nothing happens.

The sales lead pulls your engineer for a “quick client favor.” The R&D manager quietly reassigns your resources to a “more urgent” priority. The procurement rep says they need to “check with their boss” before honoring the plan. You walk away with a signed document and zero actual progress.

A signed document doesn’t change who actually holds the resources. You didn’t have a process failure; you had a silent coup.

In matrix organizations, we are taught to believe that cross-functional teams own the outcomes. But look closely at your own company: the functional departments still own the resources, the priorities, and the performance reviews. Paper rules and actual rules run in parallel, and when push comes to shove, paper rules lose every single time.

When this happens, what do we do? We add more meetings. We build more Jira boards. We mandate another round of process training. We treat a power struggle as a communication bug.

It’s a fatal mistake. If you study frameworks like Integrated Product Development (IPD), you’ll hear the mantra: “first rigidify, then optimize, then solidify.” Most people think “rigidification” means blindly following a new process until you learn it. Like training wheels on a bicycle.

That is completely wrong.

“Rigidification” isn’t a learning sequence. It is a power transfer mechanism. Without enforcing who has the right to decide—and making that authority stick during conflict—all later optimization is just polishing a process that never actually runs.

Let’s look at a scenario. A client requests a major feature change. The cross-functional product team assesses the impact and decides to protect the current release schedule, putting the feature in the next sprint. It’s the right call for the product.

But after the meeting, the Sales Director bypasses the team and tells the engineer to just build it anyway. The engineer complies, because the Sales Director influences their performance review. The team’s decision is silently overwritten.

Who really made the decision? The person who could make the team’s choice stall indefinitely. In an organization, if someone can make a completed decision wait by withholding resources, they retain actual control. The formal team merely owns the blame.

This is why “rigidification” exists. It is the brutal, necessary phase where top leadership forces the old power structure to yield to the new one. It means explicitly defining what decisions the cross-functional team owns, what resources they are guaranteed, and what happens when a functional boss tries to override them.

It means leadership has to restrain themselves.

When the first major conflict hits—and it will—leaders are always tempted to make a “pragmatic” exception. “Just this once, the client is too important, let’s bypass the new system.” But every time a leader bypasses the new rules for a VIP client or a loud department, the organization learns a toxic lesson: the new rules are just a suggestion. The real decisions still happen in the hallways.

If your leaders can bypass the process whenever a VIP client calls, you don’t have a matrix organization. You have a feudal system with extra paperwork.

True rigidification means that when a functional manager disagrees with the cross-functional team, they cannot just silently pull their people. They must bring the conflict to the new decision table. They have to argue their case based on the new rules of engagement. If they lose, they must comply. If they win, the decision is updated officially, not whispered over lunch.

And it’s not just about stripping power from functional managers. It’s about aligning the entire system. If a team member prioritizes the cross-functional project over their department’s side-quest, does their performance review reflect that? If their bonus is still solely controlled by the department head they just defied, the system is rigged against the new rules. The tasks, the resources, and the evaluation metrics must match.

Only when this new power dynamic is enforced—when the organization allows a team to make a decision that a department hates, and actually lets it stick—can you begin to “optimize.”

Because what are you optimizing otherwise? If you try to optimize a process where decisions are still being overruled in the shadows, you’re just adding speed to a broken engine. You won’t know if a delay is caused by a flawed process or a hidden power grab. You need the new rules to actually run, cleanly and visibly, to see where the real friction is.

Process design is critical. You need to know who decides, who participates, and when to escalate. But process design without power transfer is a fantasy.

So before you schedule another process improvement workshop, ask yourself a hard question: When your cross-functional team makes a decision that steps on a powerful department’s toes, does the organization let it happen?

If the answer is no, you don’t have a process problem. Stop fixing your flowcharts. Start fixing your power structure.