Executive Communication Intelligence

The presentation is excellent.

The analysis is deep.

The subject-matter expert has anticipated almost every question.

There are thirty-seven slides, three appendices, fourteen risks, five scenarios and a model that took six weeks to build.

The meeting ends.

Nobody is sure what decision was requested.

This is not a lack-of-information problem.

It is a decision-communication problem.

Senior audiences are often given more detail precisely when they need more judgement.

The presenter mistakes completeness for usefulness.

The board, investment committee, minister, CEO or operating committee is left to convert information into a recommendation while the person who understands the subject best stays safely inside the facts.

The more consequential the decision, the more tempting this becomes.

Detail feels defensible.

Judgement feels exposed.

But leadership communication exists to make judgement visible.

Executive Authority Answer

When the audience must decide, organise the communication around the decision, not the subject. State the decision required, give your recommendation, explain why now, show the two or three facts that matter most, rank the principal risk, state what would change your recommendation, and ask for the decision explicitly. Put supporting detail behind that structure rather than in front of it.

A useful decision sequence is:

Decision → Recommendation → Why now → Proof → Risk → Change condition → Ask

The expert may need one hundred pages to prepare.

The decision-maker may need one page to decide.

Those are not contradictory requirements.

Why detail expands when confidence falls

Presenters rarely overload senior audiences because they do not care.

They overload them because they care intensely.

They want to prove they did the work.

They fear omitting something that later becomes important.

They want every stakeholder to see their issue represented.

They do not want to be accused of bias.

They feel safer describing options than recommending one.

They anticipate challenge and add material in advance.

Each motive is understandable.

Together they can destroy the communication.

Research on information overload has linked excessive information with poorer decision-making, reduced productivity and cognitive pressure. Research specifically on board-level use of big data has also identified cognitive overload and capability challenges at senior decision levels.

The practical lesson is not anti-data.

It is pro-hierarchy.

Decision-makers need to know what matters first.

Mistake 1: Explaining the subject before stating the decision

The presenter begins:

“Let me take you through the background.”

Twenty minutes later, the board discovers it is being asked to approve a $120 million capital programme.

That order is backwards.

The decision should be visible at the start.

“We are asking the board to approve $120 million for Phase 1 of the capacity programme. Management recommends approval because the existing site reaches safe capacity in Q3 next year and the alternative lead times are longer than the remaining window.”

Now every piece of detail that follows has a purpose.

The audience can test it against the decision.

Without that frame, people listen to information and guess why it matters.

Mistake 2: Presenting options evenly when your judgement is not even

“Option A has these advantages. Option B has these advantages. Option C has these advantages.”

The presentation sounds balanced.

The committee asks:

“What do you recommend?”

The presenter replies:

“It depends on your risk appetite.”

That phrase often hides a failure of judgement.

If the presenter has the expertise to analyse the options, the presenter should normally be able to state which option is preferred under the assumptions given.

A stronger answer:

“Management recommends Option B. It costs 8% more than A, but it removes the single-supplier dependency that creates our largest operational risk. We would move to A only if the board’s priority is lowest near-term cash outflow rather than resilience.”

That is still balanced.

It is not neutral.

Decision-makers need informed judgement, not merely a catalogue.

Mistake 3: Treating completeness as a defence against challenge

The presenter includes every risk because somebody might ask about the one that was omitted.

Fourteen risks appear on the slide.

The board now has a new problem: which three matter?

A risk register is not a decision narrative.

Rank the risks.

Say which one could change the recommendation.

Say which one is material but accepted.

Say which one is unlikely but catastrophic.

Say which ones are monitored but not decision-changing.

For example:

“There are eleven identified risks. Three matter to today’s decision. The first is permitting delay because it can destroy the timetable. The second is contractor concentration because it can increase cost. The third is demand risk because it can make the capacity unnecessary. The remaining eight are managed within the normal programme controls and are in the appendix.”

Nothing has been hidden.

The hierarchy has been made visible.

Mistake 4: Using detail to avoid making the recommendation personal

Experts often retreat into passive language.

“The analysis indicates…”

“It could be considered…”

“One possible route would be…”

“There may be merit in…”

Who believes what?

Who is accountable for the recommendation?

A senior audience needs to know whether the person presenting the work stands behind it.

“I recommend we delay the launch by eight weeks.”

That sentence changes the room.

It exposes judgement.

It also allows challenge to become productive.

“Why?”

“What would make you change your mind?”

“What risk are you accepting?”

A recommendation creates a surface the board can test.

A cloud of detail does not.

Mistake 5: Describing uncertainty without saying how it affects the decision

“We have uncertainty around demand, inflation, implementation timing and competitor response.”

True.

Now what?

Uncertainty matters only when it changes the choice, timing, size or conditions of the decision.

A stronger formulation is:

“Our recommendation survives the current demand range. It does not survive a six-month permitting delay. If approval is not obtained by 1 February, we recommend stopping Phase 1 and returning with a smaller option.”

Now uncertainty has a decision threshold.

This is far more useful than a long caveat list.

Decision-makers do not need uncertainty removed.

They need it organised.

Mistake 6: Failing to explain the cost of not deciding

Some decisions feel optional because only the proposed action is described.

The presenter explains the cost of doing something.

The audience never hears the cost of waiting.

That creates an asymmetry.

Approve the project: visible cost, visible risk, visible accountability.

Delay the project: appears free.

It rarely is.

If delay consumes capacity, increases cost, weakens negotiating leverage, extends uncertainty or closes an opportunity window, say so.

“We can defer the decision for one quarter. The consequence is that we lose the current equipment slot and the earliest commissioning date moves by approximately seven months.”

Now the committee is comparing two choices rather than action versus nothing.

Good decision communication makes the status quo visible as a decision.

Mistake 7: Ending with “Any questions?” instead of asking for the decision

The presentation closes.

“Thank you. Any questions?”

The room discusses details for twenty minutes.

The chair looks at the clock.

Somebody says, “Good work.”

The meeting moves on.

No decision.

If approval is required, ask for it.

“We are asking the board to approve Option B and authorise management to enter final contract negotiations within the $120 million cap.”

If guidance is required, ask for it.

“We need the committee to choose whether resilience or near-term cash preservation is the governing priority before we complete the final design.”

If no decision is required, say that too.

“Today is an information session. No approval is requested. We return in November with the investment case.”

The audience should never have to guess what kind of meeting it is in.

The Decision Compression Page

Before presenting upward, reduce the case to seven lines.

Element Required answer
Decision What exactly must be decided?
Recommendation What do you recommend?
Why now Why is a decision needed at this time?
Proof Which two or three facts carry the case?
Risk What is the largest risk you are asking the audience to accept?
Change condition What fact would change your recommendation?
Ask What approval, guidance or action do you need now?

If you cannot fill the page, the deck is not ready.

If you need forty pages to defend the seven lines, keep the forty pages.

Put them behind the seven.

Worked example: technology investment

Weak opening:

“Today we will cover the current infrastructure landscape, the architecture review, vendor assessment, migration pathways, security considerations, cost scenarios and implementation options.”

Decision-centred opening:

“We are asking the executive committee to approve a two-year migration from our current platform to Vendor B. We recommend it because the existing platform reaches support end-of-life in eighteen months and Vendor B is the only shortlisted option that meets both our resilience and data-residency requirements. The decision must be made this quarter to protect the migration window.”

The second opening does not remove technical complexity.

It tells the committee what the complexity is for.

Worked example: board acquisition proposal

Weak:

“The team evaluated 42 potential targets, narrowed the field to seven and conducted detailed work on three.”

Better:

“We recommend acquiring Target C at no more than $480 million. It gives us the distribution capability our current strategy assumes we can build organically, but eighteen months faster. The central risk is customer concentration: one client represents 22% of Target C revenue. If that customer will not sign a three-year renewal before completion, management recommends we do not proceed.”

Decision.

Recommendation.

Why now.

Proof.

Risk.

Change condition.

The diligence still matters.

It now supports a visible judgement.

Worked example: ministerial or public-sector briefing

The same problem appears outside companies.

A policy team can provide fifty pages on implementation and leave the minister unclear about the actual choice.

A decision-centred brief might say:

“Decision required: whether to launch nationally in January or run a six-month regional phase first. Officials recommend the regional phase because the national data-sharing agreement is not yet operational. The cost is a six-month delay in national coverage. The recommendation changes if all three required data-sharing agreements are signed by 15 October.”

The leader can now interrogate the choice rather than discover it.

Detail has three legitimate homes

Not every detail belongs in the same place.

1. Decision layer

The minimum needed to decide.

2. Challenge layer

Evidence needed to answer foreseeable questions.

3. Audit layer

The full analysis, assumptions, calculations and record required for governance, assurance or later review.

Weak communication mixes all three.

Strong communication keeps all three available and makes the layer visible.

That is how you simplify without becoming simplistic.

This is why “make it shorter” is bad advice by itself

A short presentation can still be useless.

Five slides of vague statements are not better than thirty slides of analysis.

The goal is not brevity.

The goal is decision density.

Every minute should help the audience understand the choice, test the recommendation, see the uncertainty or decide.

A twenty-minute presentation that achieves that may be excellent.

A five-minute presentation that hides the trade-off may be dangerous.

The relationship between detail and authority

Executives sometimes believe authority comes from demonstrating how much they know.

At senior levels, authority often appears in what the leader can leave out without losing truth.

Compression is evidence of mastery when the hidden analysis exists and can be produced under challenge.

A leader who says:

“There are fifteen variables in the model. Three change the answer. Let me show you those three.”

signals both depth and judgement.

A leader who walks through all fifteen before stating the answer signals work.

Those are not the same thing.

The same decision in three formats

A decision may appear as a paper, a presentation and a live discussion.

The architecture should remain consistent even though the amount of detail changes.

The paper

The first page should make the decision visible.

Decision required.

Recommendation.

Reason now.

Material trade-off.

Largest risk.

Supporting analysis can follow.

The presentation

Do not spend the first ten minutes retelling the paper.

Use the room for the judgement that benefits from interaction.

Open with the recommendation, show the two or three variables that carry it, then invite challenge where the decision is genuinely sensitive.

The discussion

The presenter must be able to defend the recommendation without returning to the deck for every answer.

That requires knowing the logic, not memorising slides.

If the recommendation falls apart as soon as the order of questions changes, the decision architecture was never clear enough.

What belongs in the appendix

Executives often ask what they are “allowed” to move out of the main narrative.

The better question is what the decision-maker must understand before the decision can be made responsibly.

Material that usually belongs behind the main narrative includes:

  • full methodology;
  • detailed scenario tables;
  • complete risk registers;
  • vendor scoring sheets;
  • sensitivity analysis beyond the decision thresholds;
  • technical architecture diagrams not required to understand consequence;
  • detailed chronology;
  • supporting market data already summarised in the recommendation.

Material that usually belongs in the main narrative includes:

  • the decision;
  • the recommendation;
  • the reason the decision is needed now;
  • the facts that determine the recommendation;
  • the material downside;
  • the uncertainty that could reverse the decision;
  • the cost of waiting;
  • the exact authority requested.

The appendix is not where weak arguments go to hide.

It is where necessary depth sits after the decision logic is visible.

The “show me your work” problem

Senior presenters often overcorrect for a past experience in which a board member said, “I want to see the analysis.”

From then on, every future presentation includes the analysis in the main flow.

But “show me your work” does not mean “make everybody walk through every step before you tell us your answer.”

A strong presenter can say:

“The recommendation rests on three assumptions. They are on this page. The full model and sensitivity analysis are in Appendix B, and I am happy to go there if the board wants to test any of them.”

This signals preparedness without imposing the cost on every listener.

The detail remains available.

The decision remains visible.

Rehearse the challenge, not only the presentation

Decision communication frequently looks clear until the first hard question.

Then the presenter retreats into data.

“Why are you recommending B?”

“Well, if you look at slide 28…”

That is a warning sign.

Prepare the recommendation under challenge.

Ask:

  • Why this option?
  • Why now?
  • What are we giving up?
  • What is the worst credible downside?
  • Which assumption are you least confident in?
  • What would make you reverse the recommendation?
  • What happens if we do nothing?
  • Why should the board trust this analysis?

Answer each in plain language before returning to a slide.

The deck should prove the answer.

It should not be the only place the answer exists.

The decision owner and the subject-matter expert may be different people

Another reason detail replaces judgement is role confusion.

The expert presents because the expert knows the subject.

The executive owns the recommendation because the executive owns the trade-off.

If those are different people, make the split visible.

For example:

“The CTO will take the board through the technical risk. I am recommending Option B because, taking that risk together with cost and timing, it best meets the company’s objective.”

Now the expert is not forced to make a commercial judgement outside their authority, and the executive cannot hide behind the expert’s detail.

This is particularly important in cyber, safety, clinical, engineering and regulatory matters where technical expertise and institutional decision rights are not identical.

When more detail is the right answer

There are moments when the audience genuinely needs depth before deciding.

A novel risk.

A safety-critical system.

A complex transaction.

A decision with irreversible downside.

A governance issue where the record matters as much as the outcome.

The answer is still not to abandon hierarchy.

Instead say:

“This decision cannot responsibly be reduced to one variable. There are four issues the board must understand before voting. I will take them one at a time, and then return to the recommendation.”

The audience now knows why the detail exists and how to organise it.

Complexity becomes navigable rather than merely abundant.

The final decision test

At the end of the meeting, ask whether every person in the room could independently state:

  1. What decision was made?
  2. Why was it made?
  3. What risk was knowingly accepted?
  4. What assumption matters most?
  5. What would trigger reconsideration?
  6. Who now owns execution?

If those answers differ materially across the room, the communication did not close the decision even if the vote passed.

That creates decision debt: future arguments about what was agreed, why it was agreed and whether conditions have changed.

Clear decision communication reduces that debt at the moment it is cheapest to fix.

Questions people ask

Isn’t it risky to simplify a complex decision?

Yes, if simplification removes a material fact or uncertainty. Decision compression does not remove the evidence; it orders it. The full analysis remains available for challenge, audit and governance.

What if there is genuinely no clear recommendation?

Say why. Identify which unresolved variable prevents a recommendation and what evidence or decision is required next. “No recommendation yet” can be a strong position when it is precise.

Should every board paper start with a recommendation?

If the paper is seeking a decision, the requested decision and management recommendation should normally be visible early. Information-only and discussion papers should state that no approval is requested.

How many risks should be in the main presentation?

As many as can materially change the decision. The full risk register can sit behind the main narrative. Rank rather than dump.

What does a decision-maker need from an expert?

Not just expertise. The decision-maker needs the expert’s judgement about what the expertise means for the choice.

The point

Detail is not the enemy.

Unstructured detail is.

The most knowledgeable person in the room should not force the least knowledgeable person to build the recommendation from raw material.

That is backwards.

Do the analytical work.

Then do the communication work.

State the decision.

State your recommendation.

Explain why now.

Show the facts that carry the case.

Rank the risk.

Say what would change your mind.

Ask for the decision.

Everything else should make that judgement easier to test, not harder to find.

Related Executive Authority reading

Sources

For a board, investment committee or senior decision room where expertise must be converted into a clear decision, request confidential counsel.

Written by

Principal, Executive Authority

Kevin Abdulrahman is the Principal of Executive Authority, a private advisory practice retained by chief executives, board chairs, ministers, and sovereign leaders who require counsel at the level their position demands. His work spans executive communication architecture, board-level positioning, crisis counsel, and the leadership presence that shapes how power is perceived and sustained. Over two decades, he has advised principals in high-stakes negotiations, before boards and cameras, and in the moments that determine institutional legacy.

Published by Executive Authority

Published by
Kevin Abdulrahman — Principal
Request Counsel →
← Back to Insights