Executive Committee Influence: Point of View, Rationale, Ask

Senior-team settings are not the place for cautious updates alone.

That is a hard lesson for many strong functional executives and practice leaders. They are capable. They know their business. They prepare carefully. They show up with the facts. They tell the executive committee what is happening in their area.

And then they wonder why their influence does not grow.

The problem is usually not intelligence, effort, or preparation.

The problem is that updates do not create the same impact as a clear point of view.

At senior levels, leaders are expected to do more than report. They are expected to interpret. They are expected to recommend. They are expected to help the team make better decisions across the whole business.

This is where stakeholder management becomes a real executive capability.

A leader may have a strong function, practice, or business unit. But if they cannot influence peers, resolve friction, and speak with clarity in senior-team settings, their impact stays limited.

I saw this clearly in coaching work with a senior practice leader who was operating with a lot of independence. He was successful in his own area, but needed to increase his influence across the enterprise and with the executive committee.

The work was not about becoming louder.

It was about becoming clearer.

The structure we used was simple:

Point of view.Rationale.Ask.

That structure helped him move from cautious updates to stronger executive contribution. It helped him speak up more clearly, reduce unnecessary caveats, address friction with a senior peer, and eventually apply those lessons in a meaningful acquisition and integration effort.

Why updates are not enough in senior-team settings

Updates have a place.

Senior teams need to know what is happening. They need visibility into performance, risk, customers, people, financials, operations, and strategic priorities. A clean update can be useful.

But an update by itself is often not enough.

A leader who only provides updates may sound prepared, but not influential. They may be seen as responsible, but not necessarily strategic. They may provide information without helping the senior team decide what to do with it.

That distinction matters.

At the executive committee level, people are listening for more than status. They want to know what the issue means, what tradeoff is involved, what risk is growing, what decision is needed, and what the leader recommends.

A cautious update might sound like this:

“We have been working through several issues with the integration team. There are some concerns around client communication, operating process, and how the teams will coordinate over the next few months. We are continuing to meet with the relevant leaders and will bring more information back as it develops.”

There is nothing wrong with that sentence. But it does not create much executive traction.

A stronger contribution sounds different:

“My point of view is that we need one integration lead and one client communication plan within the next two weeks. The rationale is that the acquired team is receiving mixed signals, and that is creating risk with both employees and clients. My ask is that we agree today on the executive sponsor and decision rights for the integration lead.”

That is a different level of contribution.

The leader is not merely describing activity. The leader is helping the executive team focus.

This is why many high-performing functional leaders and practice leaders have to change their communication pattern as they move up. Earlier in their careers, being accurate and thorough may have been enough. At the senior level, the question becomes:

What do you think?

Why do you think it?

What do you need from the room?

That is executive communication.

Without that structure, leaders can disappear into their own updates. They talk, but do not move the conversation. They share information, but do not shape decisions. They attend the executive committee, but do not fully contribute to it.

That is a missed opportunity.

The structure: point of view, rationale, ask

Point of view, rationale, ask is simple enough to use in real time.

That is why I like it.

Many leadership frameworks are too complex to remember in the middle of a difficult conversation. This one gives leaders a practical way to organize their thinking and improve their influence quickly.

The point of view answers the question: What do you believe should happen?

The rationale answers: Why does this matter, and why does your recommendation make sense?

The ask answers: What do you need from the person or group?

Each part matters.

A point of view without rationale can sound like opinion.

Rationale without a point of view can sound like analysis.

A point of view and rationale without an ask can leave the conversation unresolved.

The full structure creates movement.

For example, a practice leader might say:

“My point of view is that we should stop treating this client as three separate practice opportunities and manage it as one enterprise relationship. The rationale is that the client is making one strategic decision, and fragmented outreach weakens our position. My ask is that we agree on one relationship lead and one account plan before the next client meeting.”

That is clear. It gives the senior team something to respond to.

A functional executive might say:

“My point of view is that we should delay the internal launch milestone by two weeks. The rationale is that the current timeline creates execution risk and will likely produce more rework. My ask is that we align today on the revised timing and the message to the field.”

Again, the leader is not simply providing background. They are helping the business make a decision.

This structure is especially helpful for leaders who tend to over-caveat.

Many capable leaders weaken their own influence because they try to make the statement safe before they make it clear. They say things like:

“I could be wrong here.”

“There are a lot of variables.”

“This may not be the right way to think about it.”

“I do not want to overstate the issue.”

Some caution is useful. Nobody wants reckless certainty. But too many caveats can cause senior executives to discount the message before the leader has even made the point.

Point of view, rationale, ask helps the leader sound clear without sounding careless.

It creates a way to speak with conviction and judgment at the same time.

How to speak straight without creating unnecessary friction

Speaking straight is not the same as being blunt.

This distinction matters in senior teams.

A leader who avoids direct communication may preserve short-term harmony, but leave important issues unresolved. A leader who communicates too bluntly may create unnecessary resistance. The goal is to speak directly in a way that helps the business move forward.

That requires clarity and care.

The senior practice leader I coached needed to contribute more actively in executive committee discussions. He had valuable perspective, but was sometimes too cautious about offering it, especially when the topic sat outside his direct domain.

Through feedback, he realized something important: others valued his perspective even when he was not the technical expert on the issue.

That is a common surprise for high-capability leaders.

They assume they should only speak when they are the deepest expert in the room. But executive committees do not only need domain expertise. They need business judgment, pattern recognition, thoughtful challenge, and the ability to connect issues across the enterprise.

Speaking straight starts with owning the perspective.

A leader might say:

“My point of view is not based on owning this function, but on what I am seeing across clients.”

Or:

“I know this sits primarily with operations, but I think there is an enterprise risk we should name.”

Or:

“I may not have all the detail, but I think we are avoiding the tradeoff.”

Those are useful openings because they create context without over-apologizing.

The leader is not pretending to have authority they do not have. They are also not hiding behind caution.

Speaking straight also requires separating the business issue from the person.

For example, instead of saying:

“Your team is not communicating clearly.”

A leader might say:

“The issue I see is that the field is receiving different messages from different functions. That is creating confusion, and I think we need one owner for communication.”

That keeps the focus on the problem.

The structure helps here too.

Point of view: “We need one owner.”

Rationale: “The field is receiving mixed messages.”

Ask: “Can we agree today who owns the communication plan?”

This kind of communication is direct, but not inflammatory.

It improves stakeholder management because it reduces ambiguity. People know what is being said, why it matters, and what is being requested.

What lateral trust has to do with executive presence

Executive presence is often misunderstood.

People sometimes reduce it to polish, confidence, tone, or how someone carries themselves in a meeting. Those things matter, but they are not the whole story.

At senior levels, executive presence is also relational.

Do peers trust you?

Do they believe you are solving for the enterprise?

Do they experience you as fair, clear, and direct?

Do they believe you understand their pressures, not only your own?

That is where lateral trust comes in.

A leader can have strong presence in a formal presentation and still struggle to influence peers. Why? Because peers are not only responding to the message. They are responding to the relationship.

This was part of the practice leader case.

He needed greater impact across the enterprise, not simply better executive committee comments. There was also friction with a senior executive in another part of the business. That friction had to be addressed because low trust limits influence.

The coaching work included relationship investment.

Prepare before important discussions. Share pre-reads when useful. Contribute a clear point of view. Follow up afterward. Address the conflict directly rather than letting it remain in the background.

That combination mattered.

Lateral influence improves when leaders stop treating executive presence as a performance inside the meeting and start treating it as a pattern of trust built before, during, and after the meeting.

Before the meeting, strong leaders invest in understanding stakeholder concerns.

During the meeting, they speak clearly and connect their recommendation to the business.

After the meeting, they follow through.

That is how trust compounds.

This matters even more in cross-functional environments where authority is limited. If you need people to move with you and they do not report to you, trust becomes part of the operating system.

Technical expertise alone will not carry the day.

The leader has to be experienced as credible, clear, and oriented toward the business.

That is executive presence in practice.

Lessons from the practice leader case

The practice leader’s growth offers several useful lessons for functional executives, CHROs, and leaders trying to increase influence in senior-team or cross-functional settings.

The first lesson is that senior teams need contribution, not only reporting.

If you are in the executive committee, your role is not simply to update the room on your area. Your role is to help the team make better decisions. That requires a point of view.

The second lesson is that perspective has value even outside your domain.

Many leaders hold back because they are not the expert on a particular issue. That caution is understandable. But senior teams benefit when leaders bring thoughtful enterprise perspective. You do not need to pretend to own the issue. You do need to contribute to the business conversation.

The third lesson is that fewer caveats create more impact.

Caveats can be useful when they clarify uncertainty. They become a problem when they weaken the message. Leaders who want more influence need to state their recommendation clearly, then explain the nuance.

The fourth lesson is that lateral trust is part of executive impact.

If there is unresolved friction with a senior peer, it will show up in the work. Addressing that friction may be one of the most important leadership moves available.

The fifth lesson is that structure helps leaders speak straight.

Point of view, rationale, ask gives leaders a way to be clear without being combative. It helps them bring a recommendation, explain the business reason, and move to a specific request.

The sixth lesson is that influence grows through repetition.

The practice leader did not become more influential through one conversation. He built new routines. Prepare. Speak up. Follow up. Repair trust where needed. Apply the structure in real situations.

Those repetitions mattered when he later helped lead an acquisition and integration effort.

That kind of work requires more than technical competence. It requires stakeholder management, lateral influence, executive clarity, and the ability to keep people aligned through complexity.

This is why communication structure can change executive impact.

When leaders move from cautious updates to clear perspectives and asks, others experience them differently. They become more useful in the room. More influential across functions. More trusted in enterprise work.

That is the development opportunity.

Ready to increase executive impact?

If you have a leader who is respected but not creating enough impact in senior-team or cross-functional settings, the issue may be communication structure and lateral influence.

A focused conversation can help sharpen the leader’s point of view, rationale, and ask in the real meetings where influence matters most.

Book a Call