Engineering thinks marketing overpromises. Marketing thinks engineering moves too slowly. Sales thinks product doesn't listen. Everyone's frustrated, and projects suffer.
I hear some version of this in almost every company I work with. And here's what's interesting: the people involved are usually smart, well-intentioned professionals who genuinely want the project to succeed. So what's going wrong?
Cross-functional friction often looks like departmental conflict. But it's frequently style clash in disguise.
Why Departments Develop Style Personalities
Different functions attract different styles. This isn't a rule, but it's a pattern I've seen hold up remarkably well across industries:
Engineering/Finance/Legal: Often Reasoning-heavy. Analytical, risk-aware, detail-oriented. They need to understand before they act.
Marketing/Design/Strategy: Often Creating-heavy. Big-picture, innovative, possibility-focused. They need to explore before they commit.
HR/Customer Success/Sales: Often Relating-heavy. People-focused, relationship-oriented. They need to know how decisions affect humans.
Operations/Project Management: Often Doing-heavy. Execution-focused, results-driven. They need to see progress.
When departments clash, they're often experiencing style clashes amplified by organizational silos. The silo gives each group permission to see the other as "the problem" rather than a different style that brings something valuable.
The Cross-Functional Friction I See Most
Reasoning vs. Creating: Engineering says marketing's ideas are impractical. Marketing says engineering always says no. I worked with a regional e-commerce company in Bangkok where this dynamic had gotten so bad that the two departments communicated almost entirely through the COO. Every request became a negotiation. Every timeline became a fight.
Reasoning vs. Doing: Legal wants more review time. Operations needs approvals faster. Both are right — and both are driving each other crazy.
Creating vs. Doing: Product keeps changing requirements. Development can never finish. Sound familiar? This is probably the most expensive style clash in tech companies.
Relating vs. Doing: Customer success wants to discuss client feelings and relationship health. Sales wants to close the deal and move on.
How to Bridge the Gaps
1. Name the style dynamics at the start
When kicking off cross-functional work, name the styles in the room. "Engineering, you'll want to analyze thoroughly. Marketing, you'll want to explore possibilities. Let's design a process that serves both." Just saying this out loud changes the dynamic. People stop seeing the other side as obstructive and start seeing them as operating from a different — and valid — starting point.
2. Sequence contributions so every style adds value
Different styles add value at different phases. The mistake most teams make is expecting everyone to contribute the same way at the same time:
- Early ideation: Creating leads, others contribute
- Analysis and risk assessment: Reasoning leads, others contribute
- Stakeholder alignment: Relating leads, others contribute
- Execution: Doing leads, others contribute
When you sequence it this way, each style gets a phase where they're in their element. Nobody feels sidelined. Nobody feels steamrolled.
3. Create translation roles
Assign people who can bridge styles. Someone who understands both engineering's need for precision and marketing's need for speed can mediate between the two. These "translators" are worth their weight in gold on cross-functional projects. In my experience, they're often people with balanced style profiles — they naturally see both sides.
4. Design shared workflows
Build workflows that accommodate all styles:
- Exploration phases with time limits (so Creating gets space, Doing gets closure)
- Analysis phases with decision points (so Reasoning gets thoroughness, Doing gets movement)
- Check-ins for relationship maintenance (so Relating stays connected, everyone stays aligned)
- Execution phases with change control (so Doing can finish, Creating respects commitments)
When Style Clash Hardens Into Culture
Here's where it gets dangerous. Repeated cross-functional friction creates cultural narratives:
- "They never understand us"
- "They're impossible to work with"
- "It's always a fight with that team"
These narratives persist even when individuals change. I've seen new hires absorb these stories within their first week — before they've even had a direct experience with the other department. Breaking these narratives requires naming style differences explicitly rather than blaming departments. It's harder than it sounds, because by the time cultural narratives form, people have invested identity in them.
The Kickoff Conversation That Changes Everything
When starting cross-functional work, try this:
- Share the styles represented at the table — make it visible
- Acknowledge what each style brings and what each needs
- Agree on how phases will be structured — who leads when
- Establish how disagreements will be resolved before they happen
- Build in check-ins to address emerging friction early
I ran this exact conversation with that e-commerce company in Bangkok. Within two meetings, the engineering and marketing leads were talking directly again — no COO intermediary needed. Not because anyone changed their style, but because they understood why the other side worked the way they did.
Where Teams Go Once They Get This Right
Cross-functional collaboration that accounts for style differences moves faster and produces better results. Teams stop fighting about "how we work" and focus on "what we're building." That shift alone can save weeks on any major project.
The style lens depersonalizes conflict and makes it solvable. Different departments aren't enemies — they're complementary styles that need intentional coordination. And in my experience, the organizations that figure this out don't just collaborate better. They innovate faster, because they've unlocked the full value of having diverse perspectives at the table.
