Sales closes a job. Production doesn’t find out until the customer calls asking when the crew is coming.
Operations makes a scheduling change. The dispatcher finds out the same time the field does.
Everyone is working hard. Everyone is doing their job. And yet the left hand has no idea what the right hand is doing, and the customer experience keeps suffering for it.
The friction between departments isn’t a communication problem. It’s a team design problem.
Departments That Understand Their Own Goals but Not Each Other’s Are Structurally Set Up to Conflict.
Most businesses are designed by function.
Sales does sales. Operations does operations. Field does field. Each department has its own priorities, its own metrics, and its own definition of a good week.
What they don’t have is a shared picture of how their work connects to each other.
Sales is optimizing for close rate. Operations is optimizing for schedule efficiency. Production is optimizing for job completion speed.
None of those goals are wrong. But when they’re pursued independently, they pull against each other.
Sales closes volume that production can’t absorb. Operations changes schedules that sales promised to customers. Production rushes jobs to hit completion targets that generate callbacks operations has to handle.
The silos aren’t forming because departments don’t want to work together. They’re forming because the team was never designed to work together.
The HVAC Company Where Sales and Production Were Constantly at War
I worked with an HVAC contractor about two years ago. Sixteen million in revenue. His sales lead and his production manager had been with him for years.
Both were strong individually. Both genuinely cared about the business.
And they were in the owner’s office at least twice a week with a version of the same complaint about each other.
The sales lead was frustrated that production kept pushing back on install timelines. It was making him look bad to customers and slowing his close rate.
The production manager was frustrated that sales kept promising timelines without checking capacity. It was creating impossible schedules and technician burnout.
The owner had mediated this conflict so many times he could recite both sides from memory.
When I mapped how the two departments actually interacted, the structural gap was immediately visible.
There was no shared capacity metric both teams tracked. No defined handoff process between close and scheduling. No weekly checkpoint where sales and production reviewed pipeline and capacity together before commitments went out to customers.
Each department was doing its job correctly. They just had no shared operating layer that required them to coordinate before the conflict happened instead of after.
The owner wasn’t dealing with a people problem. He was dealing with the absence of a team design that connected two functions that had to work in sequence to produce a good customer outcome.
What Team Design Actually Requires
The Starting Five is a framework for thinking about team design at the seat level.
It asks: does every seat on the team have the right behavioral wiring for what that seat demands, and does the team as a whole have the right composition to cover what the business needs?
But team design also has to address how the seats connect to each other, not just how each seat performs individually.
That’s where the Results Ownership Map and the shared meeting cadence do their most important work.
The Results Ownership Map for each seat defines not just what that seat owns, but where it hands off to another seat, and what the standard for that handoff looks like.
For the sales lead, it defines: what information has to be confirmed with production before a timeline is promised to a customer.
For the production manager, it defines: what capacity information needs to be visible to sales at all times so they’re not selling into a full schedule.
When both documents exist and both leaders have reviewed them, the conflict isn’t a personal one anymore. It’s a process question. And process questions are solvable.
The weekly leadership meeting creates the shared coordination layer. When sales and production sit in the same weekly meeting reviewing the same scorecards and the same pipeline, the conversation about capacity and timeline happens before commitments go to customers, not after the damage is done.
The team doesn’t need to like each other more. They need a structure that makes coordination automatic.
What Cross-Functional Friction Keeps Costing
The owner stays the integration point between departments.
Every conflict between sales and production, field and office, operations and finance, routes back to the one person everyone knows will make the final call.
The customer experience suffers in the gaps.
Disconnected teams produce disconnected customer journeys. The customer who was sold a timeline that production couldn’t deliver remembers. The customer who received conflicting information from two departments doesn’t come back.
The departments themselves get more entrenched over time.
When sales and production keep conflicting, both sides eventually stop trying to coordinate and start protecting their own metrics. The silos harden. The friction becomes structural and cultural.
A business Built to Sell or Built to Sail™ has departments that coordinate by design, not by personality. The handoffs work. The shared metrics create alignment. And the owner stops being the referee between people who were never designed to work together clearly.
If Your Departments Keep Conflicting, the Design Is the Problem.
If departments understand their own goals but still struggle to work together, the issue usually isn’t effort. It’s that the business was never designed around how those functions actually need to operate together. I do a 30-minute Discovery Call where we look at where communication, handoffs, and collaboration are breaking down, and what structural changes would reduce the friction. No pitch. Just a conversation about where your business is and what’s getting in the way.