The cost of compliance over co-ownership

You’re logged into a briefing call, looking at a grid of digital faces. A few seconds ago, the team was talking about weekend plans and trading this week’s tales. As more names start popping up on the participant list, the chatter slowly stops. A wave of polite corporate smiles settles over the screen.

Someone hits the screen share and right on cue, the row of cameras turns off. Everyone is now hiding behind the curtain of a dense PowerPoint deck.

Then comes The Line. The one repeated in a thousand calls, the one that any thinking mind in the room quietly dreads:

“We already have the core idea and the foundation is locked down. We just need you to help it come together by Tuesday.”

The door slams shut. There is zero curiosity in the tone. It is a polite call signaling your mind is not required, and the team’s only job is to color inside the lines.

The slow burn of “Yes”

A team rarely surrenders on day one. At first, they try to engage. They ask clarifying questions, look for strategic openings, and attempt to bring their expertise to the table. But when a briefing closes the door to curiosity, pushback is treated as an obstruction.

The wear-down happens over the next few days, sometimes weeks. The work starts talking in the hallways. The feedback loops degenerate into a war of semantics, with endless threads of emails trying to patch structural holes with surface-level tweaks.

Finally, after weeks of spinning wheels and burning budget, the exhaustion wins. The team taps mute, sighs, and rolls into full compliance mode.

“Yeah, whatever. Let’s just build exactly what they asked for.”

This is the most expensive moment in a project’s lifecycle. At this moment, I am always reminded of the Pontiac Aztek.

The tragedy of the Pontiac Aztek

In the late 1990s, a committee of executives at General Motors had a brilliant concept. They correctly predicted the crossover market, realizing consumers wanted a vehicle that combined the convenience of a smaller car with the rugged utility of an SUV.

The premise was worth billions. But the collaborative loop was entirely dead.

Management locked down a rigid spreadsheet of engineering specifications and closed the door to any iteration. They didn’t want to co-author the vehicle with their team—they wanted their assumptions validated.

Because there was no trust and no open dialogue, the team couldn’t challenge the awkward proportions or stress-test the functionality. The team quietly went into compliance mode, checked every corporate box, and delivered exactly what the committee mandated.

The output was the most universally mocked, brand-damaging failure in automotive history.

A brilliant idea, completely ruined by a creative process that prioritized compliance over co-ownership.

Compliance is a universal trap

I have watched this exact tragedy play out across every domain. A breakthrough technology gets wrapped in a generic user experience because leadership refused to open the door to true design iteration. A major corporate rebrand spends millions only to walk away with a lifeless asset that looks like every other competitor because the team was forced to validate a personal preference. Global campaigns stall because the emotional punch of the message is entirely sanitized by committee revisions, leaving behind a beautifully produced piece of noise that moves no one.

The symphony of trust

True co-ownership isn’t about dividing a project into territories where a team owns the logic and the other owns the magic. Everyone in the room must own the ultimate success of the work together.

The power of collective ownership is unlocked when the distinct expertise and perspectives of a team are allowed to clash, challenge each other, and sharpen the core idea.

When you open the door to true ownership, the energy changes completely. People lean in. Cameras stay on. The team feels empowered because they aren’t just executing someone else’s thoughts.

Creating true co-ownership

When a project hits the screen, the conversation shouldn’t lean on subjective commentary. The only thing that should matter is solving for: why.

Why are we doing this? Why do people care? Why does it work? Why now?

The why opens the room, allowing expertise to speak up and the subjective banter to fade out. It unlocks the ability to make hard, high-stakes decisions together.

A design lead can look a business leader in the eye and say, “If we delay this launch by one week to properly address the user experience, the platform will perform.” Conversely, a go-to-market leader can say, “The market window is closing and we have to move now.” And because the teams trust each other, compromises are calculated and the best work ships out.

The greatest work isn’t built by yes-men hiding behind turned-off cameras, or by stubborn partners commanding from isolation.

Great work is built by people who care about the why. People who open the door to curiosity and collaboration. People who build the trust to respect each other’s roles and create shared ownership over the goal.