Values and cross-collaboration fights are opposites

Every company says "we need better cross-team collaboration". Then they add more syncs, more alignment meetings, more docs. And the fights keep happening.

We keep fixing the wrong layer.

Where fights really come from

Think of the last cross-team fight. On the surface it's about the work:

• "This adds friction"
• "This delays the release"
• "This hurts the metric"

Go one layer down. It's rarely about the work. It's about what each team thinks matters more. Speed vs polish. Growth vs trust. This quarter vs next year.

That's not a collaboration problem. It's a values problem.

The flip side

When values are actually shared, something nice happens. Teams don't need one process. Each can work its own way and still line up.

• Engineering scopes its way
• Design explores its way
• Growth runs its own experiments

Nobody clashes, because every rule came from the same shared values. That's why I say values and collaboration fights are opposites. Where one is strong, the other mostly disappears.

A quick test

Watch a conflict:

• Poster values: settled by who's senior or louder
• Shared values: settled by "we agreed trust comes before conversion", and the room reorders itself

If every disagreement needs an escalation, the values aren't shared. They're just written.

For you as a designer

• Before a project, agree the trade-off order. If speed, quality and scope collide, what do we drop first? Get it in writing.
• Argue from the shared value, not your title. "We agreed trust is first, and this breaks it" beats "as a designer I feel...".
• If a fight repeats, fix the value underneath, not the instance.

Meetings sync calendars. Shared values sync decisions.