3 ways high-performing teams make better decisions

3 Decision-Making Habits That Separate High-Growth Teams From the Rest

If your team meetings feel like a car engine that keeps revving but never shifts into gear, you’re not alone. I’ve sat through enough of them to know the pattern: smart people, good intentions, endless debate, zero closure. The meeting ends, and everyone walks out thinking, “Well, that was productive… I think?” But nothing actually moved.

That’s the silent killer in B2B growth. Not bad strategy. Not lack of talent. It’s a decision-making vacuum that sucks the energy out of your revenue engine.

High-performing teams don’t just make better choices by accident. They build a shared language for navigating uncertainty. They move from vague discussion to concrete action. And they know the difference between a real risk and the discomfort that comes with any move worth making.

Here are the three habits I’ve seen separate the teams that scale from the teams that stall.

1. Stop Asking “What Should We Do?” – Start Making Proposals

I’ve worked with dozens of GTM teams, and almost every one of them hits what I call the swirl. It’s that frustrating loop where everyone in the room is smart, ideas are flying, but by the end, the only agreement is that you need another meeting. The swirl is expensive. It burns time, morale, and momentum.

The fix is deceptively simple: shift the default from open-ended questions to concrete proposals.

One of my clients at a consumer health company was stuck in exactly this pattern. Their transformation team had become a permission-seeking machine. People waited for clarity from above. They waited for consensus from peers. They waited for someone—anyone—to take ownership. The result? Meetings that produced conversation, not decisions.

The turning point came when the team changed the expectation. Instead of showing up with open questions, team members started saying, “I propose we…” That small shift changed everything. Junior members who had been hesitant to speak up started driving the agenda. Conversations got shorter. Decisions actually stuck. The team didn’t need perfect answers. They needed something concrete to react to.

Think about what a proposal does: it forces clarity. It gives others something to push back on, improve, or build upon. And it breaks the paralysis of infinite options.

How to apply this in your team today:

  • Before your next meeting, ask each attendee to bring one specific proposal—not a question.
  • When a conversation starts circling, interrupt the swirl with: “I propose we…”
  • A proposal doesn’t have to be complete. It just has to be concrete enough for someone to say “Yes, but let’s adjust this part.”

That phrase—“I propose we…”—is one of the most productive strings of words any revenue team can adopt. And here’s the best part: anyone on the team can use it, regardless of seniority.

2. Learn to Distinguish a Real Objection from Ordinary Hesitation

Here’s where most teams sabotage themselves. Someone senior says, “I’m not sure about this approach,” and suddenly the entire room freezes. The idea gets shelved. The project stalls. And nobody asks the obvious question: Is this a genuine risk, or just discomfort with making a move?

I’ve seen good ideas die because a VP said “I would have done this differently.” That’s not an objection. That’s a stylistic preference. But teams treat it as a veto.

The truth is, most decisions die from discomfort, not from danger. Teams mistake “I feel uneasy” for “This is a bad idea.” They confuse the ordinary anxiety of uncertainty with a real red flag.

High-performing teams have a filter for this. They ask:

  • “Is there a specific downside we haven’t considered?”
  • “What data would change your mind?”
  • “Is this a dealbreaker, or a preference?”

A real objection has teeth. It points to a clear, measurable risk—a customer churn trigger, a compliance violation, a resource constraint that’s already maxed out. An ordinary hesitation is vague. It sounds like “I’m just not sure,” or “Let’s wait and see.”

Reframe the conversation:

  • When someone hesitates, don’t pause the room. Ask for the specific concern.
  • Create a norm: “I’m feeling some discomfort, but that doesn’t mean we stop. Let’s name the risk and decide if it’s worth taking.”
  • Use a simple threshold: “If we can’t articulate the downside in one sentence, it’s probably not a real objection.”

Teams that get this right move faster, take smarter risks, and stop letting seniority override logic.

3. Make the Final Call—Even When Someone More Senior Disagrees

This is the hardest habit to build, especially in B2B teams where hierarchy still whispers in every room. But high-performing teams have a rule: the person closest to the decision makes the call. Not the person with the highest title.

I’ve seen this play out in real time. A product manager with deep customer data recommends a pricing change. A VP of Sales disagrees based on a gut feeling. The room looks to the VP. The PM defers. And a good move dies because the person with the most authority didn’t have the most context.

That’s not leadership. That’s abdication disguised as respect.

The best teams build a decision-making framework that separates input from authority. Everyone gets a voice. But the person who owns the outcome gets the vote. And once that vote is cast, the debate is over—even if the CEO disagrees.

How to operationalize this:

  • Use a clear decision-making model. The simplest one is DACI: Driver, Approver, Contributors, Informed. The Driver makes the recommendation. The Approver has final say. Contributors provide input. Informed people are kept in the loop, but don’t vote.
  • Set the expectation upfront: “This is Sarah’s call. She’s heard everyone’s input. After she decides, we’re moving forward.”
  • When someone senior disagrees, they can escalate—but only once. If the Driver’s decision is overridden, the override comes with a documented reason and a clear owner for the outcome.

This doesn’t mean ignoring senior input. It means creating a system where decisions don’t get stuck because one person’s title outweighs everyone else’s data. Speed becomes a feature, not a bug.

The Bottom Line: Uncertainty Isn’t the Enemy—Stuckness Is

High-performing teams don’t eliminate uncertainty. That’s impossible in B2B SaaS, where markets shift, buyers behave unpredictably, and every new quarter brings its own chaos. What they do is navigate uncertainty with speed, clarity, and a shared decision-making language.

They stop asking “What should we do?” and start proposing. They stop treating hesitation as a veto. And they give decision-making power to the people closest to the problem.

If your team is still stuck in the swirl, pick one of these three habits and start today. It doesn’t require a new tool or a restructuring. It just requires a shift in how you talk about decisions.

Because in the end, the teams that win aren’t the ones with the most data or the smartest people. They’re the ones that know how to move from discussion to action—fast.


Want to go deeper? I’m breaking down how revenue teams at top SaaS companies build decision-making velocity. Drop me a line or share this with your GTM team. Let’s stop meeting about meetings and start making moves.

Leave a Comment