Ad ops is where other people’s bad decisions become emergencies
BY ANONYMOUS PUBLISHER + LIZ MOOREHEAD, BEELER.TECH
The following editorial is a free Below the Fold feature preview from The Stack subscription.
I have worked in ad ops long enough to know how this usually goes.
Somebody sells something.
Somebody promises something.
Somebody somewhere says yes too fast, or says yes too vaguely, or says yes because no one wanted to be the person who made the room uncomfortable.
Then it lands on the desk of ad ops, and it becomes our problem
Actually, let me correct that. It was always going to become our problem.
We just weren’t invited to the part of the conversation where that could have been prevented.
That’s the part I wish more people inside publishing would understand. Ad ops is still treated in too many organizations like the place where work goes after the important thinking is done. The strategy happened already. The deal is closed. The client is excited. Leadership is happy. Sales is moving on to the next thing. And now here come the details. Here come the questions. Here come the constraints. Here comes the part where reality shows up and asks whether any of this can actually work.
That is usually the moment when everyone remembers we exist.
We are not offended because the work is hard. The work is hard. Fine. We all know that. We chose this. We are good at this. Some of us even like this particular flavor of chaos more than is probably healthy.
What wears people down is something else.
It is being treated like support when you are functioning like infrastructure.
It is being treated like execution when your job is risk, feasibility, delivery, communication, systems thinking, troubleshooting, forecasting, triage, and, increasingly, emotional regulation for everyone else in the building.
It is knowing that if you had been in the room thirty minutes earlier, or a week earlier, or six months earlier, half the mess would not exist.
It is being asked to perform miracles in an organization that still does not really understand what you do.
Ad ops is still treated in too many organizations like the place where work goes after the important thinking is done. The strategy happened already. The deal is closed. The client is excited. Leadership is happy. Sales is moving on to the next thing. And now here come the details. Here come the questions. Here come the constraints. Here comes the part where reality shows up and asks whether any of this can actually work.
A lot of people think ad ops traffics campaigns and fixes tags and pushes things live
Sure. We do those things.
We also catch the promises that do not line up with inventory. We catch the targeting that does not line up with audience behavior. We catch the measurement plans that do not line up with the actual product. We catch the timelines that assume no one else is working on anything. We catch the brand safety requirements that carve away the very content a buyer came to us for in the first place.
We catch the disconnect between “we want scale” and “we do not want to be near 90% of your site.”
We find the contradiction between “we want engagement” and “please bury us somewhere sanitized where no one is paying attention.”
And when we do these things, a funny thing happens.
We’re treated like we’re the problem.
That part is exhausting.
There’s a reason ad ops people have a reputation for being blunt. There’s a reason we ask annoying questions. There’s is a reason we can sound skeptical in rooms that would prefer a little more optimism and a lot less math. It’s because we are usually the last line between a bad assumption and a very public failure. We are the people who have to look at the thing after everyone else has had their turn with it and say, okay, but can this actually run?
Can it deliver? Can it perform? Can it be measured? Can it be reported on? Can it renew?
Can we execute this without setting our own team on fire?
You may call that negativity, but this is literally our job.
And if I am being honest, part of the problem is that ad ops has become the part of the organization everyone relies on while pretending it is not really central.
People will tell you, directly or indirectly, that ad ops is a support function
Then they will hand you a pile of impossible conditions and assume you will somehow make it work anyway. They do not respect the machine, but they absolutely expect it to turn on every time.
One of the best ways I’ve heard it described is this; ad ops gets treated like the crawl space of the business. Most people barely think about it unless something goes wrong. They keep running new wires through it, keep shoving more into it, keep assuming it can hold whatever the rest of the house needs it to hold. Then something shorts out, something leaks, something starts sagging, and suddenly everyone wants to know why it’s such a mess down there.
That is funny because it is true. It is also a little bleak, because it is true.
Inside a lot of publishing companies, ad ops is where other people’s shortcuts go to become someone else’s emergency:
- Sales says yes because sales is under pressure to say yes.
- Leadership wants growth because leadership is under pressure to show growth.
- Agencies slap on requirements because they are under pressure to avoid anything going wrong.
- Buyers inherit templates and blocklists and assumptions they did not create, then keep using them because that is what the process says and no one has time to stop and think.
And ad ops gets whatever comes out the other side.
We get the vague ask. We get the Friday night request. We get the thing that needs to launch Monday and somehow still needs legal, creative, tracking, QA, trafficking, forecasting, screenshots, reporting logic, and a plan for what happens when the client realizes their wishlist and the actual site are not the same thing.
We get told the deal will fall apart if we do not answer in an hour. We get told there is no time. We get told the client needs this now. We get told to be agile. We get told to move fast. We get told to stop overcomplicating things.
Then the campaign underdelivers, or does not serve, or the reporting does not tell the story someone wanted it to tell, or the restrictions were impossible from the start, and suddenly everyone wants a deep operational diagnosis from the same team they cut out of the original conversation.
You can see why morale gets weird.
Ad ops gets treated like the crawl space of the business. Most people barely think about it unless something goes wrong. They keep running new wires through it, keep shoving more into it, keep assuming it can hold whatever the rest of the house needs it to hold. Then something shorts out, something leaks, something starts sagging, and suddenly everyone wants to know why it’s such a mess down there.
This is why so many ad ops people feel isolated
A lot of us are sitting in organizations where we are the translator, the brake pedal, the cleanup crew, the historian, the workaround inventor, and the person who still has to smile on the call and explain things for the seventh time.
Some of us are entire departments of one. Some of us built the documentation. Some of us built the internal site. Some of us wrote the guides. Some of us trained sales. Some of us answered the same question again anyway, from someone who has worked here for years and still does not know where the pre-roll inventory is. Some of us learned the hard way that if we do not speak up in the meeting, people will make decisions that create twice the work and half the outcome.
So yes, a lot of us are tired.
But tired is not the whole story.
There is also pride here.
Because for all the ways this job gets flattened by other people, the truth is ad ops people understand more of the business than we usually get credit for. We see where product decisions hit revenue. We see where sales incentives collide with delivery reality. We see where marketing asks overlap with audience behavior. We see where analytics, engineering, account management, and monetization all start stepping on each other’s shoes. We see the whole chain because the whole chain eventually runs through us.
That is why it is so maddening to be treated like we are too tactical to be strategic:
- You don’t get to understand the whole machine and still be “just support.”
- You don’t get to be responsible for whether the promise survives contact with reality and still be treated like a back-office function.
- You don’t get to be the person everyone comes to when they need the truth, then get shut out because the truth is inconvenient.
And let’s talk about one of the most ridiculous examples of this for a second; the way ad ops teams inside publishers get forced to mediate contradictions that no one wants to own.
The whole brand safety thing is a perfect example
There are buyers who want your audience, your scale, your engagement, your context, your trust, your users, your results. They want the value of being on a publisher site. They just do not want to be near the actual content that creates that value. They do not want the news. They do not want the hard story. They do not want the thing users are actually there to read. They hand over giant keyword blocklists, whittle down the available inventory, and then still expect reach, performance, viewability, and beautiful outcomes.
At a certain point, somebody has to acknowledge that the ask and the outcome are fighting each other.
You cannot keep stripping away the environment and still demand the outcome the environment produces.
And the ad ops team gets stuck in the middle of that fiction.
We are the ones saying:
- If you block most of the site, you are going to get less.
- If you want a million impressions, you cannot also refuse the pages where the audience actually is.
- If your agency told you this would all work together, they were wrong.
- The news is not inherently unsafe.
- Your own brand may not even know these restrictions are being imposed in its name.
Again, people hear friction; what they should hear is expertise
There’s a broader organizational problem underneath all of this, and I do think people should say it plainly. Too many publishing companies still confuse ad ops being downstream with ad ops being secondary.
Those are not the same thing.
Being downstream means we inherit the consequences. It does not mean our knowledge matters less. In fact, if a team repeatedly inherits the consequences of decisions made elsewhere, that team probably understands the business in a way leadership should pay a lot more attention to.
- If you want fewer internal surprises, bring ad ops in earlier.
- If you want smarter packaging, bring ad ops in earlier.
- If you want fewer impossible proposals, bring ad ops in earlier.
- If you want sales training that actually sticks, build it with ad ops.
- If you want better client conversations, stop treating feasibility as an awkward afterthought.
- If you want retention, morale, and less institutional burnout, stop building cultures where the same people are expected to absorb preventable chaos over and over again with a good attitude.
And if you are in leadership, I really need you to hear this next part
When your ad ops team sounds frustrated, actually listen to what we’re saying. We’re not baselessly frustrated.
In fact, our frustration is not always resistance to change.
Very often, it comes from experience; from having seen the same bad pattern repeat enough times to recognize it early. Ad ops teams know what happens when feasibility gets treated like a detail, when timelines are driven by pressure instead of reality, and when nobody wants to challenge an easy yes.
What sounds blunt or skeptical in the moment is often the judgment of people who already know where the plan starts to break.
So here is my ask, and it is not complicated
If you work in sales, stop treating ad ops like the department of last resort. Bring them in before the yes, not after it. Learn enough about what they do to understand where the line is between ambitious and impossible. And when they flag something, stop hearing it as disloyalty to revenue. They are trying to protect revenue from fantasy.
If you work in leadership, stop measuring the value of ad ops only by whether disasters were averted quietly. Look at the business knowledge sitting in that team. Look at the relationships they have to manage. Look at the operational truth they are forced to hold for everyone else. Then give them actual authority that matches the responsibility they already carry.
If you work in product, marketing, analytics, engineering, account management, or any other adjacent function, stop waiting until something is broken to loop ad ops in. They are not just there to clean up the end of the process. They can help shape it.
If you are an agency or outside partner, stop making ad ops the recipient of assumptions somebody else should have challenged. Stop hiding behind “the client wants it” when no one has actually interrogated the ask. Have the harder conversation sooner. If a publisher team is telling you the plan does not add up, believe them enough to stay in the room.
And if you are in ad ops reading this and feeling that little knot in your chest because this sounds too familiar, you are not crazy. You are not overreacting. You are not uniquely bad at politics. You are not the only one sitting there wondering why you keep getting handed a mess that could have been prevented by one honest conversation upstream.
A lot of us have been standing in that exact spot, and many of us are still standing there.
The good news, if there is any, is that once people start saying this part out loud, it gets a lot harder to pretend the problem is just personality or communication style or one difficult team.
Sometimes the issue is simpler than that: the people closest to the work have been right the whole time.