Your monthly operating review has the shape of accountability. The leadership team is in the room, the CEO and CFO are there, and each function walks through its numbers and answers for the month that closed. On the calendar it's the most serious hour you spend.

Now think about what that hour produced last time. Marketing presented pipeline contribution, sales presented forecast and coverage, and the two numbers implied different things about the same quarter. Someone noted it. Someone agreed to take it offline. The agenda moved, because there was a next slide and the meeting ended on time.

The month got reported accurately, but the disagreement that surfaced left the room in the same condition it entered: unresolved, unowned, and handed off to a follow-up conversation that may or may not happen.

A review that reports and a review that decides look almost identical on your calendar. They produce very different quarters.

Your review probably wasn't designed as a decision forum. It accumulated into one. A monthly leadership meeting existed, reporting requirements got added to it, and each function was asked to bring its numbers and then more of them as the business grew. The hour meant to hold decisions filled up with presentations instead.

You can see the accumulation in how the meeting is built:

That last one does the damage. The numbers that conflict are the most useful thing on your table, because they mark the exact place where the two teams are working from different assumptions about the same quarter. Reconciling them is the work.

But reconciliation has no owner. You can't settle it alone, neither can the other team, and your CEO is usually hearing the specifics for the first time with no basis to settle it on the spot. So it falls to whoever is willing to press the point in front of the CEO and CFO. Pressing costs something you can only spend a few times a year, and you save it for the quarter that matters.

So everyone behaves reasonably and the disagreement survives anyway. Taking it offline is the only move the meeting leaves you.

The cost shows up in the weeks after the meeting.

An unreconciled disagreement leaves the room as two different understandings of what got decided. You leave believing the priority held. The other team leaves believing it was open for revision. Both of you are working in good faith on two different things.

That gap compounds quietly, and it surfaces where leadership is already looking:

By the time it resurfaces the drift is a full cycle old, and it doesn't look much like the thing that caused it. If you run sales, you're answering for a forecast built on a priority that moved. If you run marketing, you're answering for spend committed against the same moving target. Either way you're accountable for the outcome of a decision the room didn't actually make.

The more expensive cost is what leadership concludes while this repeats.

Your review is where the CEO and CFO form their working judgment about whether sales and marketing can operate together. They're not reading your slides as closely as you think. What they're tracking is whether the same issue keeps coming back.

When it does, they reach for the explanation that's easiest to see from the outside. Two capable executives keep surfacing the same conflict and keep failing to close it, so the conclusion forms quietly and it lands on the two of you. This is friction between two people.

You've probably watched this happen, or had it happen to you. The pipeline number and the forecast number disagree for several cycles running, and each time it gets noted and taken offline. Neither leader got worse at the job in the meantime, and both were working it hard between meetings. What didn't change was the meeting itself, which had no way to settle a disagreement between two functions and nobody responsible for settling it. By the fourth cycle the CEO had stopped hearing a structural problem and started hearing two people who couldn't get along.

That's how a design problem gets read as a people problem. Your CEO isn't being careless here. The review shows the symptom on a reliable schedule and keeps the cause out of view, so the room can see that the disagreement persists without ever seeing why.

Once the read turns personal, what follows tends to be personal too. Coaching conversations, adjusted reporting lines, sometimes a change in one of the two seats, and a long stretch where both leaders are managing perception instead of the problem. Meanwhile the meeting that produced the misread stays exactly as it is.

You don't need to change anything to test this. You just need to pay attention to different things for one cycle.

Watch for four things:

Then ask one question out loud, right when the discrepancy surfaces. Who owns closing this before we meet again? It's a fair question, it doesn't accuse anyone, and the answer tells you a lot. If it turns out the question has no owner, you've found the thing that's been costing you.

When you raise it upward, name it accurately. Your review is built to report, and you're asking it to decide. That distinction changes the conversation with a CEO, because it moves the problem off the two of you and onto something that can be changed.

Some rooms leave with a decision that holds. Others leave with a record. Both feel productive on the way out.

If this was useful, forward it to a colleague who would benefit from rethinking how sales and marketing align to drive sustainable growth.

Until next week,

Jeff

RevEngine™ | Built for Revenue Leaders Driving Alignment and Growth — Together.