Marketing launches a campaign on Monday promising a feature that's still in code review. The developer building it finds out through a Slack thread where someone's asking if the new integration is ready yet. Nobody coordinated anything, and now the choice is between shipping fast and broken, or letting marketing publish something that doesn't exist yet.
This happens on almost every team where marketing and development work together, and it's more common when the team is remote, because there's no hallway to walk down and sort it out. The only coordination that's real is the kind that gets written down.
Why Friction Is Normal, Not a Failure
Marketing and development optimize for different things, and that's fine. Marketing needs to move fast because it's competing for attention in a news cycle that lasts days. Development needs certainty before promising a date, because a broken release costs the product dearly. Neither one is doing anything wrong, they're responding to different incentives that almost nobody bothers to make explicit.
When this goes unnamed, the friction gets experienced as a people problem: marketing is the team that promises things for nothing, and development is the team that always says it can't be done. Neither is true, it's a process problem.
What Works When Collaboration Is Real
Give Marketing a Range, Not a Fake Date
A senior developer doesn't say it'll be ready Friday when what they actually mean is I think Friday, if nothing weird comes up. Communicating the real range, and the risk behind that date, lets marketing plan a campaign with a buffer instead of building everything around a promise nobody can guarantee.
Get Into the Discovery Conversation, Not Just the Delivery One
Most of marketing's impossible requests are born because no one technical was in the room when the plan came together. A senior developer who joins, even for 20 minutes, the planning of a campaign avoids having to say no at the last minute to something announced without checking first.
Say No With an Alternative, Not With Silence
We won't have that ready for launch creates less friction than not answering the message at all. And we won't have that, but we can have this simpler version builds even more trust. Silence is what actually breaks the relationship between teams, not the limit itself.
A Shared Channel With Real Status, Not a Chain of DMs
The relationship between senior devs and marketing isn't going to be harmonious all the time, and it would help to stop pretending it is. What makes a launch work isn't that both teams get along perfectly, it's that when friction shows up, they resolve it fast and with data, not by hierarchy or by who pushes harder.
