When internal alignment breaks down (and what to do about it)

A leadership team agrees it needs to be more disciplined on discounting.



The logic is sound. Margins are under pressure, too many concessions are being given away early, and the company wants a stronger commercial posture. Nobody in the room seriously disagrees. The trouble starts afterwards. Sales thinks discounting is still available with better justification. Finance thinks the default answer should now be no.

Customer Success assumes renewals will continue to sit under a different set of rules. The CRO believes strategic accounts still need flexibility. The decision has been made in principle, but not in a form the business can use.

Decisions Don’t Fail — They Drift

That problem is more common than most teams admit. Leadership groups spend a lot of time worrying about whether an important decision will turn out to be right. That concern makes sense. In a growing SaaS business, a wrong call can be expensive. You can underprice, overhire, back the wrong product priority, or tie too much of the business to the wrong type of customer. But in practice, many executive decisions do not fail because the strategic direction was obviously poor. They fail because the decision was never made clearly enough for the organisation to use.

Direction Isn’t the Same as a Decision

That distinction matters. A decision can be directionally sound and still create avoidable damage if the business cannot tell what has actually been decided, where the boundary sits, or what behaviour now follows from it. In those cases, the problem is not faulty intent. It is poor definition.

A recognisable example is a leadership team deciding to become more selective about discounting. The reasoning is often sensible. Margins are under pressure. Too many concessions are being given away too early. The company wants a more disciplined commercial posture. Everyone in the room broadly agrees. The problem starts after the meeting. Sales hears that discounting is still possible, but needs stronger justification. Finance hears that the default answer should now be no. Customer Success assumes renewals will still be treated differently from new business. The CRO thinks strategic accounts can still be handled flexibly. Nobody has made a bad-faith interpretation. The decision is simply too loose to operate from.

This is common because senior teams often mistake directional agreement for decision quality. The room arrives at a conclusion, the conversation moves on, and everyone assumes the organisation now has a settled position. What it often has instead is a statement of intent. That is not the same thing. A statement of intent describes where leadership wants to head. A usable decision defines what people should do.

Most Decisions Stop at Principle, Not Operation

Most people get this wrong by treating decision quality as a matter of judgement alone. They ask whether the team chose the best option, weighed the evidence properly, or showed enough courage. Those things matter, but they are only part of the picture. A good decision also needs to survive contact with the rest of the business. It needs to travel across functions without being rebuilt from memory. It needs to shape behaviour consistently after the room has moved on.

That is where many decisions break down. They are made at the level of principle, but not at the level of operation. Leaders agree they will move upmarket, but do not define what that means for qualification, onboarding, product scope, and service expectations. They agree they will protect roadmap focus, but do not define when a customer request is important enough to justify exception handling. They agree to invest in retention, but do not define whether that means more headcount, a tighter renewal process, or a different stance on product commitments. The idea is there. The operating meaning is not.

A better way to think about decision quality is to ask whether the decision changes the operating environment in a usable way. After the decision, do the relevant teams understand what the company is doing, who owns it, what trade-off has been accepted, and what now sits outside scope. Could a sensible manager two layers down interpret the call correctly without needing another round of executive translation. If not, the decision is still incomplete.

When Decisions Don’t Translate, Functions Rewrite Them

This is especially important in B2B SaaS because most material decisions touch several systems at once. A pricing decision is not just a pricing decision. It affects sales behaviour, customer expectation, forecasting, renewal posture, approval routes, and margin quality. A segment decision is not just a go-to-market move. It affects roadmap discipline, support burden, implementation complexity, and the profile of customers the business becomes designed to serve. When those decisions are loosely defined, the organisation starts filling in the blanks function by function.

That is why ambiguity is so costly. People do not stop and wait for clarification. They interpret. They create local versions of the decision that make sense from where they sit. Sales stretches the category of strategic account. Finance narrows the approval boundary. Product assumes the business is more disciplined than it really is. Customer-facing teams make promises based on the most optimistic reading available. None of this looks dramatic in isolation. Taken together, it creates a version of the decision that leadership never explicitly made.

Without Boundaries, Decisions Turn Into Ongoing Negotiation

This is also why good decisions need boundaries, not just direction. A useful executive decision does not only say what the business is doing. It says where the line is. It makes clear what is included, what is excluded, and under what conditions the choice would be revisited. Without that boundary, teams keep renegotiating the edges. The organisation ends up with a rolling series of exceptions instead of a settled operating position.

Take a company deciding to give higher-touch support to strategic customers. That may be entirely sensible. But unless strategic is defined, and unless the additional support model is made explicit, the decision will produce confusion rather than leverage. Does strategic mean ARR, expansion potential, reference value, technical complexity, or some mix of the four. Does higher-touch mean executive sponsorship, faster response, implementation support, product access, or all of the above. Is the model a temporary intervention or a standing service tier? Without those answers, the business has not really made a decision. It has created permission for further debate.

A Decision Isn’t Done Until the Business Can Use It

This is where written decision-making becomes genuinely useful. Not because good operators enjoy paperwork, but because writing exposes vagueness fast. It forces the team to state the action, the owner, the rationale, the trade-off, and the boundary in terms another person can work from. It also makes it easier to see whether the issue has actually been decided or merely discussed with confidence.

A good decision usually has a few observable qualities. It is specific enough that two different leaders would explain it in roughly the same way a week later. It is bounded enough that the business can tell when a case falls outside the original call. It is owned clearly enough that the next move is not left to collective interpretation. And it is honest enough about trade-offs that the organisation is not pretending to have preserved every upside at once. That is less glamorous than strategic rhetoric, but far more useful.

None of this guarantees the decision will prove correct. Markets change. Buyers behave differently than expected. Execution may fall short. New information may emerge. That is part of leadership. But an unclear decision creates a different type of failure, and one that is more avoidable. The company cannot properly evaluate whether the call was good because it never implemented a consistent version of it in the first place.

The practical takeaway is that when a decision keeps generating follow-up explanation, exception handling, or functional reinterpretation, the issue is usually not that people are resistant. More often, the decision was not finished. Before moving on, make sure the business can answer a simple set of questions in the same way: what are we doing, why this way, who owns it, what trade-off have we accepted, and where is the line. When those answers are clear, execution gets much easier.

Need help with a decision? Get in touch now.