When discussion looks like progress, but isn’t
A week later, the issue comes back. Sales has interpreted the conversation as support to negotiate inside a range. Product thinks it agreed only to assess feasibility. Finance believes it made clear that any concession needed executive sign-off. Customer Success has told the account team to hold position until the internal view is clearer. The customer, meanwhile, is still waiting. What looked like progress was mostly conversation. The team had explored the issue, but it had not landed the call.
The gap between conversation and decision
This distinction matters more than most teams realise. Decision and alignment are related, but they are not the same thing. A decision is a call on what the business will do. Alignment is shared understanding around that call, including why it has been made, what trade-offs were accepted, and what each function now owns. Teams get stuck when they treat alignment as a substitute for decision-making, or when they force a decision before the underlying alignment exists.
In early and mid-stage B2B SaaS businesses, this happens all the time because the work is genuinely cross-functional. Important calls rarely sit neatly within one leader’s remit. A pricing move affects sales, finance, and retention. A roadmap commitment affects product, support, revenue, and delivery. A hiring decision may change cost structure, execution capacity, and customer outcomes. The more connected the issue, the more likely it is that people try to solve two different problems in the same conversation. One group is trying to decide. Another is trying to surface concerns and reduce risk. Another is trying to protect optionality because it does not yet trust the frame.
Where teams actually get stuck
That is usually where the delay starts. Teams often describe the problem as slow decision-making, but what they are really experiencing is an unspoken disagreement about whether the room is there to align or to decide. This creates a familiar pattern. Leaders keep adding information because they think the decision is undercooked. Others keep reopening the discussion because they think their concerns were acknowledged but not resolved. The founder or CEO assumes the team is broadly with them because nobody has openly objected. People leave with a version of consent, but not with a consistent operating interpretation.
Most teams get this wrong in one of two ways. The first is to overvalue harmony. They keep talking until the tension feels lower, then assume the issue is done. It usually is not. Polite agreement can hide materially different views about risk, ownership, timing, and scope. The second is to overvalue speed in the wrong way. Someone senior makes the call to break the deadlock, but the surrounding logic is not explicit, so the organisation still cannot execute cleanly. The decision exists in theory, but alignment has not been built around it.
What alignment really means
A better way to think about it is this. Alignment is not everybody liking the decision. It is everybody understanding the decision well enough to act consistently. That means a team may be aligned around a decision some individuals would not have chosen themselves. The job is not to remove all disagreement. The job is to make the business legible to itself.
That only happens when a few things are explicit. First, the decision itself needs to be stated clearly. That sounds obvious, but many teams never get past discussing options. They spend the meeting in analysis, concern-sharing, and context, then finish with a vague sentence like, “Let’s proceed carefully,” or, “We are broadly comfortable with this direction.” Those are not decisions. They are atmospherics. A useful decision names the action, the boundary, and the owner. It answers what the business is doing now, not what people broadly feel.
Second, the team has to separate decision from input. Not every person involved is a decision-maker, and not every valid concern has to delay the call. Good operators create space for challenge without allowing every concern to become a veto. That matters in SaaS environments where specialist functions often hold real expertise and real risk. Product should be able to surface delivery implications. Finance should be able to challenge precedent and exposure. Customer teams should be able to explain commercial and relational impact. But unless the decision rights are clear, useful input becomes another source of drag.
Third, the trade-offs have to be named rather than softened. Teams drift when they pretend there is a version of the decision without downside. There usually is not. Keeping a strategic logo may require an uncomfortable exception. Standardising commercial policy may mean accepting churn. Accelerating a feature for a renewal may create downstream roadmap debt. When those trade-offs remain implied, each function quietly keeps optimising for its own preferred outcome, and the issue reappears in execution.
What happens without that structure
A simple example is a Series B SaaS company deciding whether to support a large expansion opportunity with a custom workflow the product team does not want to build. The leadership conversation often gets framed badly. Sales positions it as revenue. Product frames it as product integrity. Finance frames it as margin discipline. Customer Success frames it as relationship risk. Those are all real, but none of them are the decision. The actual decision might be whether the company is willing to make a time-bound exception for a defined revenue outcome, on the condition that the CEO signs off and the account team does not repeat the promise elsewhere. Once framed like that, the team can decide. It can also align around the logic, the boundary, and the communication.
Without that discipline, teams stay stuck in a fog of partially compatible concerns. They keep trying to improve the conversation instead of improving the decision architecture. More meetings follow. More people are pulled in. The team believes it is being thoughtful. In practice, it is creating organisational ambiguity that will cost more than the original risk.
The fix is not a clever workshop or a better set of meeting notes. It is a cleaner operating frame. Before or during the discussion, someone has to make the structure explicit. Are we trying to align on the shape of the problem, or are we here to make the call? Who owns the decision? What input matters? What trade-offs are real? What exactly will be true when we leave the room? Those questions are not process theatre. They are how you stop smart teams talking past the point of usefulness.
A practical example
In practice, the most effective teams build a short written frame around material decisions. It does not need to be elaborate. It does need to force clarity. What decision is required? Why now? What are the options? What are the consequences? What is being recommended? What is the next move once the decision is made? The value of that document is not presentation quality. It is that it stops the team from confusing a discussion with an operating decision.
The practical takeaway is simple. When a leadership issue keeps returning, do not assume the business has a decision problem in the abstract. Ask whether the team has confused alignment with decision, or skipped alignment and tried to force execution anyway. Most stuck situations are one of those two errors. Once you know which one you are dealing with, the work becomes much easier.
Need help with a decision?
Get in touch now.
