The Messenger Is Not the Decision
This post is part of my Medium blog.
There is a meeting that happens once or twice a year in a lot of technology organizations.
The CTO decides it is time to gather the direct reports and talk about spending. Everyone is summoned. The calendar says the meeting is important, and the room is large enough to make it feel that way. Someone puts a dashboard on the wall. Someone else brings a deck. The organization prepares to have a serious conversation about accountability.
Then the FinOps person walks in.
In Redundant, that person is Rob Coleman. He is the Director of FinOps, which means he has prepared the numbers. Something costs too much. Something is underused. A platform was supposed to replace another platform three years ago and is still running beside it. An AI initiative is spending more than anyone expected because the original budget assumed enthusiasm would behave like a fixed cost.
Rob has the slides. He does not have the authority to decide what the VPs should do about them.
That distinction is easy to lose once the meeting starts.
Rob shows a chart that puts a project well over its expected spend. The VP responsible for the project does not argue with the chart. The VP argues with the implication. If the project is too expensive, what does that say about the priority. If the CTO thinks the budget is wrong, does the CTO also think the project is wrong. If FinOps is showing this number now, is the message that the team should stop.
The question is no longer "is this number accurate."
The question is "what are you trying to make me do with it?"
Rob did not make the budget. He did not choose the project. He did not decide it should be funded, and he did not decide it should be cut. He is there to say the number is out of line.
The room is not interested in his job description. The room is using him.
This is the strange performance of an executive accountability meeting. The CTO wants to tell the direct reports that spending matters. The direct reports want to explain why their spending is different. Nobody wants to argue directly about the strategy, so the argument travels through the FinOps presentation.
Rob shows the red line. Someone defends the roadmap. Someone else says the roadmap was approved. The CTO asks why the team is spending so much. The VP asks whether the CTO still supports the priority. Rob sits at the table while an argument about authority moves through his slides.
He is not the person they are angry with. He is the person they can safely argue through.
That is what happens to the bearer of bad news: the executive says the number is a problem, and the team hears the FinOps person saying the project is a problem. The VP says the project matters, and Rob becomes the symbol of the person who does not understand the strategic priority.
Neither interpretation is correct.
Rob is reporting the condition. The argument belongs to the people who created it.
This is one reason FinOps is such a difficult job. You spend a lot of time telling engineering things engineering does not want to hear, then telling finance things finance does not want to hear, and then sitting in a room while both sides pretend the problem is your attitude.
The data is not always welcome. That does not make it wrong.
In the meeting, Rob is asked questions that are far beyond what he is there to decide. Someone brings up the philosophical importance of a project. Someone asks whether the company really wants to be the kind of organization that cuts investment in the future. Someone turns a cost question into a referendum on innovation, ambition, or whether the executive team has lost its nerve.
Rob has learned how to answer.
"I am not here to make decisions about your budget. I am here to tell you that you are over it."
That is the scope boundary. It is not evasive. It is the only way to keep the conversation attached to reality.
If the VP wants to defend the project, defend the project. Explain what it does, what it is expected to produce, and why the cost is justified. Do not ask the FinOps person to decide whether the organization should want the thing. That is a different meeting, with different people, and ideally a different presentation.
The problem is that organizations like to collapse those questions because the collapse makes accountability easier to avoid. If the project is a strategic priority, the cost conversation becomes an attack on strategy. If the cost conversation is an attack on strategy, the person who raised it is being difficult. If the person is being difficult, the organization can discuss the person instead of the number.
That is how the messenger becomes the problem.
Rob has seen the cycle enough times to recognize it. The room starts with the numbers. Someone moves to the roadmap. Someone else moves to the company's future. Five minutes later, the FinOps director is defending the existence of cost management to a group of people who asked him to come there and explain the cost.
It would be funny if the consequences were not real.
The meeting is not useless. Accountability matters. Senior leaders should know what their organizations spend. Projects should be challenged when they exceed their assumptions. A direct report should be able to explain why a project costs what it costs and what the organization receives in return.
But that conversation requires the room to keep separate questions separate.
What did we spend. Why did we spend it. What did we expect to receive. What did we actually receive. Is the project still worth doing. Who gets to decide.
Those are related questions. They are not one question, and asking the FinOps person to answer all of them is a way to make sure nobody owns the final answer.
Rob's role is narrower and more useful. He makes the number difficult to ignore. The executives can decide what to do with it. They may spend more. They may cut the project. They may decide the original estimate was wrong and change the plan. They may decide that the thing they called strategic is not strategic enough to pay for.
Those are management decisions. FinOps can inform them. It cannot make them.
That is what I wanted to capture in the opening meeting of Redundant. The meeting looks like a cost review, but the real argument is about who gets to define the company's priorities. Rob's deck becomes the surface where that argument appears. He knows what is happening because he has been in these rooms before.
The number is his responsibility. The decision is not.
The organization will still try to make him carry both.
In Redundant, the first book in The Condition Set trilogy, Rob Coleman runs the FinOps review that names the waste nobody wants to hear about. The numbers do not change. The question is who they get used against.