Leading Without Authority, Part 1

Building consensus at work is one of the most talked-about leadership skills and one of the most misunderstood. Most people think it can be achieved in a meeting. Get the right people in the room, put the options on the table, facilitate a conversation, and walk out with a decision. It sounds clean and easy, but it rarely works that way.

Research from Harvard Business School shows that up to 70% of cross-functional initiatives fail due to ineffective stakeholder management, because leaders underestimated what meaningful engagement actually requires. That is a staggering number, especially when you consider how much time and money organizations pour into these efforts. The strategy was sound. The work was solid. The initiative still failed.

The problem is not the meeting. The problem is everything that didn’t happen before it.

The decision-point trap

Most leaders arrive at a cross-functional review having done solid work. They have analyzed the options and built a strong recommendation. The stakeholders show up with their own views already formed and their priorities already set. The meeting becomes a negotiation between entrenched positions. The person with the highest title typically carries the day, and the people who felt overruled disengage.

A study of 96 cross-functional teams across 25 leading corporations found that nearly 75% of those teams were dysfunctional and failed on at least three of five criteria. Those criteria  include: meeting a planned budget, staying on schedule, adhering to specifications, meeting customer expectations, and maintaining alignment with the company’s corporate goals. These are leading corporations with capable people. What breaks down is the process that leads to the meeting, not the talent of the people inside it.

Consensus does not happen at the decision point. It is built in all of the conversations along the way.

What project managers have figured out

Project managers work without positional authority by design. They are accountable for outcomes they cannot mandate. A project manager cannot order the finance team to prioritize their initiative or require the engineering lead to reallocate resources. They have to earn alignment, and the best ones have developed a clear set of habits for doing so.

They map stakeholders before they schedule meetings. They ask questions before they propose solutions. They separate the conversations where they are gathering information from the conversations where they are making decisions. They understand that every stakeholder is operating from a different set of goals, pressures, and incentives, and they do the work to understand what those are before asking anyone to commit to anything.

When someone feels that their priorities have been understood, they are far more willing to engage with yours.

Three conditions that have to exist first

Before a consensus conversation can succeed, three conditions need to be in place.

The first is that each stakeholder feels their goals have been heard. Not agreed with, just heard. There is an important difference. You do not have to adopt every priority you encounter. You do have to demonstrate that you understand what matters to the people involved.

The second is that people trust the process is fair. A 2024 Gartner study found that 67% of B2B projects fail primarily due to poor stakeholder alignment — not technical or financial obstacles. Fair process does not mean everyone gets what they want. It means the decision-making criteria are transparent, the voices in the room carry equal weight, and no one walks away feeling like the outcome was decided before they arrived.

The third is that there is a shared understanding of what decision is actually being made. Stakeholders frequently arrive at alignment conversations with different assumptions about what is being decided, who has final authority, and what happens after the meeting ends. Ambiguity at that level creates conflict that looks like disagreement but is actually confusion.

Why technically strong leaders often get stuck here

Technical professionals are trained to optimize for the best solution. Consensus optimizes for the most durable one. Those are not always the same thing, and understanding the difference is crucial.

A strong analyst or engineer can walk into a meeting with the objectively superior option and still lose the room — because the other stakeholders do not share the same definition of superior, because they have constraints that were not accounted for, or because they were never consulted before the recommendation was formed. A technically correct solution that lacks buy-in does not get implemented well. Often, it does not get implemented at all.

Leading without authority means accepting that the quality of your idea is necessary but not sufficient. Building alignment is the key to success.

The bottom line

Consensus is not something you build in a meeting. It is something you build so the meeting can be successful. The leaders who consistently move initiatives forward across divisions are not necessarily the most brilliant people in the room. They are the ones who did the work before they called the meeting.

The rest of this series will cover three required steps: How to understand what your stakeholders actually want, how to communicate across different thinking and communication styles, and how to use decision frameworks that hold up after the meeting ends.

If you are working on building these skills in your organization, I would like to hear from you. Connect with me directly or visit NeuroConversant Leadership to learn more about speaking and coaching engagements.