Executive Authority Answer

Communicating effectively with a minister is not about sounding impressive or making a commercial pitch more persuasive. It is about making a proposal institutionally legible. A minister or senior government leader must be able to understand the mandate connection, public value, evidence, constraints, implementation reality, stakeholder implications and precise decision being requested. Executive Authority uses the Mandate Fit Map: mandate → public value → evidence → constraint → implementation → ask. When those elements are clear, the conversation becomes easier to evaluate, escalate and act on without forcing the government counterpart to reconstruct the case on the speaker’s behalf.

The private-sector pitch can fail in government even when the idea is good

A chief executive enters a ministerial meeting with a strong proposition.

The company has capital. The project is credible. The slides are elegant. The CEO knows the commercial logic intimately.

Twenty minutes later, the meeting is polite and inconclusive.

Nobody said no.

Nobody said yes.

The delegation leaves believing the minister needs more persuasion.

That diagnosis is often wrong.

The minister may have understood the business case perfectly and still lacked a clear institutional reason to move the proposal forward.

Government communication is not simply corporate communication delivered in a more formal room. The decision architecture is different. A minister may need to consider statutory authority, public value, political and administrative constraints, budget cycles, regulators, public perception, procurement rules, cabinet or agency coordination, delivery capacity and precedent.

The private-sector speaker sees the opportunity.

The minister must see the governable decision.

This is why senior leaders can be commercially sophisticated and still underperform in government-facing communication. They explain why the project is attractive to the company before making clear why it is legible to the institution.

The practical shift is simple:

Do not ask the minister to translate your proposition into public logic. Do that work before you enter the room.

Institutional legibility is different from persuasion

Persuasion asks, “How do I make this more compelling?”

Institutional legibility asks, “How can the decision-maker understand what this means inside their mandate?”

Those are different jobs.

A persuasive pitch can emphasise scale, innovation, speed and upside. A ministerial conversation must often answer a broader set of questions:

What public problem does this solve?

Which policy objective does it support?

What is being asked of government specifically?

What risks move to the public sector?

What dependencies exist across agencies?

What evidence supports the claim?

What happens if the proposal is delayed?

Who bears implementation responsibility?

What might the public reasonably question?

The OECD’s work on trust in public institutions repeatedly connects trust with evidence, responsiveness, fairness and the quality of public communication. The World Bank’s PPP guidance likewise treats stakeholder engagement as part of project quality and sustainability, not as decorative messaging added after the commercial structure is complete.

That does not mean every ministerial meeting is a public-private partnership discussion. It means serious government decisions are usually evaluated through a wider institutional lens than the commercial sponsor’s own return case.

The Mandate Fit Map

Executive Authority uses six questions to prepare leaders for ministerial and senior-government conversations:

Mandate → Public Value → Evidence → Constraint → Implementation → Ask

The map does not replace policy, legal, procurement, diplomatic or technical advice. It disciplines the leader’s communication so the appropriate experts can be heard inside a coherent decision case.

1. Mandate: why is this relevant to this office?

The first failure is often not poor content. It is poor institutional fit.

A CEO may explain a project in terms of sector growth while the ministry’s current mandate is employment quality, resilience, competition, national capability or regional development. The project may contribute to those objectives, but if the connection is left implicit, the government side must do the translation.

A senior leader should therefore be able to answer:

Which formal or publicly stated objective does this proposal support?

Why does this ministry, authority or office have a legitimate reason to engage?

What part belongs elsewhere?

What should not be asked of this minister?

This prevents the common mistake of treating seniority as universal jurisdiction.

A minister can be interested in an idea and still be the wrong institutional owner.

Good communication makes that boundary visible without embarrassment.

2. Public value: what changes for citizens, users or the national system?

Commercial leaders naturally begin with investment size, technology, jobs, revenue or speed.

Government leaders need to see what those inputs produce in public terms.

Public value may involve service access, resilience, productivity, capability transfer, competition, safety, infrastructure quality, affordability, employment, export potential or another legitimate policy outcome.

The point is not to decorate the commercial case with patriotic language. It is to articulate a testable public consequence.

Weak language says:

“This will be a landmark project that positions the country as a global leader.”

Stronger language says:

“The proposal materially increases domestic processing capacity, reduces a current dependency on imported capacity, and includes a training obligation for the technical roles that currently constrain scale.”

The second version gives the institution something it can interrogate.

3. Evidence: what can the minister safely rely on?

A ministerial meeting is a poor place for unsupported superlatives.

Claims travel.

A number may appear in a briefing note. A commitment may be repeated to another agency. A projection may be tested by technical staff. The more consequential the claim, the more dangerous it becomes to rely on enthusiasm as evidence.

Preparation should distinguish:

Verified fact — already true and supportable.

Projection — modelled and dependent on assumptions.

Commitment — something the organisation is prepared to be accountable for.

Ambition — a desired outcome that should not be presented as a forecast.

This classification protects both credibility and follow-through.

A CEO who says “we will create 5,000 jobs” when the actual commitment is conditional on land, permits, financing and demand creates unnecessary risk. A more mature formulation states the assumptions and identifies what the organisation controls.

4. Constraint: what could stop the idea from working?

Private-sector speakers sometimes hide constraints because they fear weakening the pitch.

In government, unmentioned constraints can make the proposal look less mature.

A minister knows that serious projects face friction. Land, licensing, inter-agency coordination, utilities, financing, public acceptance, procurement, skills, foreign-exchange exposure, environmental obligations, data requirements and implementation capacity may all matter depending on the context.

Naming a constraint is not the same as transferring it to government.

The leader should explain:

What the company can solve itself.

What requires a government decision.

What requires coordination but not special treatment.

What remains uncertain.

What would make the project unviable.

This is where credibility rises. Sophisticated decision-makers do not expect frictionless projects. They expect adults who know where the friction lives.

5. Implementation: who does what after the meeting?

Many ministerial conversations die in the gap between strategic interest and administrative action.

The minister may like the idea. The CEO may leave encouraged. Yet nobody has defined the next institutional step.

Implementation communication should answer:

Which organisation leads?

Who owns the technical workstream?

Which approvals or assessments come next?

What information must the company provide?

What decision point follows that work?

What is a realistic sequence?

The World Bank’s PPP reference materials repeatedly emphasise the importance of institutional frameworks, stakeholder engagement and implementation process. The broader communication lesson is transferable: a proposal becomes more credible when the route from interest to execution is visible.

6. Ask: what decision are you requesting today?

Senior leaders often arrive with a large proposition and a vague ask.

“Support.”

“Partnership.”

“Alignment.”

“Help.”

Those words sound collaborative and create ambiguity.

A good ministerial ask should be proportionate to the stage of the matter.

It may be:

Permission to begin a technical assessment.

Designation of a government counterpart.

A meeting with the responsible authority.

Clarification of a policy position.

Agreement to explore a defined structure.

A decision on a specific issue already within the minister’s authority.

The ask should not force the minister to invent a process or promise an outcome the institution has not examined.

The five-room test before a government meeting

A ministerial message should survive beyond the room in which it is delivered.

Before the meeting, test whether the proposition can survive five possible retellings:

The minister’s office: can an adviser summarise it accurately in three paragraphs?

The technical agency: can specialists identify the assumptions and questions?

The finance function: can someone see the cost, risk and dependency logic?

The public explanation: if the project became public, could its rationale be explained without embarrassment?

The implementation team: is there enough clarity to know what happens next?

If the message collapses in any of those rooms, the original pitch is not yet institutionally complete.

What not to do in a ministerial conversation

Do not use flattery as a substitute for fit

Respect for office and protocol matters. Excessive praise weakens commercial seriousness. The strongest respect is demonstrated by arriving prepared for the institution’s actual responsibilities.

Do not imply political access you do not have

A leader who name-drops other officials, royal courts, presidents, ministers or influential intermediaries may believe they are signalling credibility. They may instead create discomfort or a question about process integrity.

Do not confuse urgency with entitlement

Your deadline is not automatically the government’s deadline. Explain the consequence of delay where real, but do not convert commercial timing pressure into an institutional emergency without evidence.

Do not present a private benefit as though it were public value

Tax incentives, land, exclusivity, regulatory exceptions or public support may be legitimate subjects in some contexts. They require a clear public-interest rationale and appropriate process. Communication should never pretend the two sides of the exchange are identical.

Do not promise outcomes controlled by third parties

A company can commit to its own investment, standards and actions. It should be careful when promising jobs, financing, demand, community acceptance or downstream investment that depends on others.

A worked application: the strategic investment conversation

Imagine a company considering a major investment in a market where government support could accelerate infrastructure and permitting coordination.

The weak presentation begins with company history, global footprint, investment size and a request for “strategic partnership.”

Using the Mandate Fit Map, the conversation becomes more precise.

Mandate: the project aligns with an existing national objective to increase domestic capability in a defined sector.

Public value: the project reduces a known capacity gap, creates a training pipeline and supports a measurable service or industrial outcome.

Evidence: the company separates committed capital from possible later phases and labels demand assumptions clearly.

Constraint: grid connection and a specific approval sequence are the critical dependencies; the company does not ask government to solve issues within its own control.

Implementation: the next step is a technical working session with the responsible agencies and submission of a defined data pack.

Ask: the minister is requested to nominate the appropriate government lead and authorise exploration, not to approve the whole project on the spot.

That conversation is less theatrical and more actionable.

How to answer a difficult government question

A hard ministerial question often tests judgement rather than knowledge.

“What happens if demand is half your forecast?”

“Why should we support you rather than a local competitor?”

“What risk does the government carry?”

“Why do you need an exception?”

“What if the public opposes this?”

The wrong response is to defend immediately.

A stronger response sequence is:

Acknowledge the premise → state the current evidence → identify the relevant trade-off → define the boundary → answer the institutional question.

For example:

“If demand were half the current base case, phase two would not proceed on the same timetable. Phase one remains viable under the downside case we submitted, but the employment and capacity numbers would also be lower. We should therefore separate the committed first phase from the contingent expansion rather than present the headline number as guaranteed.”

That answer may sound less promotional. It is more trustworthy.

The one-page ministerial brief

The best preparation artifact is often not the deck. It is a one-page decision brief that could survive after the delegation leaves.

It should state: the issue; the relevant mandate; the public-value case; the company’s commitment; the evidence; the major constraints; the specific government dependency; the decision requested; and the proposed next step. Append technical detail separately.

If the case requires fifteen pages before the reader understands what decision is being requested, the communication architecture is not finished.

The delegation choreography

Large delegations can weaken ministerial communication because everyone arrives wanting speaking time. Decide roles before the meeting.

The principal opens with mandate and decision. The technical expert handles evidence. The country or policy lead explains institutional context. The finance lead addresses economics if required. One person owns the ask. Nobody introduces a new promise without the delegation lead understanding it.

This choreography prevents the meeting from becoming a collection of disconnected mini-pitches.

Cultural calibration without stereotype

Government communication is highly contextual. Forms of address, sequencing, pace, directness, use of silence, delegation order and protocol can vary materially by country and institution.

Preparation should therefore use specific local knowledge rather than broad cultural clichés. “Middle Eastern leaders prefer relationships” is too crude to guide a serious ministerial meeting. Which ministry? Which country? Which official? Which decision? What protocol? What prior relationship? What language will be used? Who is expected to speak first?

Cultural intelligence begins with specificity.

The no-surprise rule

If the proposal contains a request that could be politically, fiscally or institutionally sensitive, do not hide it on slide twenty-seven. Put the issue early enough that the government side can frame the discussion properly.

Surprise can look like clever negotiation in a commercial setting and like process manipulation in a ministerial one. Serious institutional relationships benefit from issues being surfaced before they become traps.

When the answer is no

A mature government-facing executive can receive a negative answer without damaging the relationship.

Clarify whether the rejection is about policy, timing, evidence, authority, budget, process or the proposal itself. Do not immediately renegotiate every condition. Do not imply the official has misunderstood simply because the company dislikes the outcome.

A clean response is: “Thank you. To make sure we do not misread the decision internally, is the issue that this structure is not supportable under the current policy, or that the proposal needs a different route?”

That question can save months of pursuing the wrong problem.

After the meeting: the 24-hour discipline

Government-facing communication is often weakened by poor follow-up.

Within a day, the company should record:

What was actually said.

What was requested.

What was not agreed.

What evidence was promised.

Who owns each next step.

What must remain confidential.

What interpretation should be corrected internally before it spreads.

This protects against the dangerous sentence, “The minister supported the project,” when the minister may only have agreed that the idea deserves technical review.

Institutional relationships are damaged when internal enthusiasm converts interest into a commitment that was never made.

What a strong outcome looks like

The best outcome is not always approval. It may be a clear rejection that prevents wasted work, a referral to the correct authority, agreement on the evidence required, a defined technical process or a better understanding of the public-interest test.

Evaluate the meeting by whether it improved the decision path, not by whether the delegation left feeling encouraged.

Common questions about communicating with ministers

Should the CEO lead the meeting?

Only when the CEO’s authority is relevant to the decision. Technical leaders, country heads, policy specialists or project sponsors may need to carry different parts of the conversation. Seniority should support clarity, not crowd out expertise.

How much protocol is enough?

Respect the norms of the office, country and institution. Protocol should create confidence and order. It should not become performance that distracts from substance.

Should the presentation be highly visual?

Use visuals where they clarify scale, sequence, geography, economics or implementation. Government leaders do not need decorative slides. They need material that can survive scrutiny by advisers and agencies after the meeting.

Is ministerial communication the same as public affairs?

No. Public affairs may address policy environment, stakeholder strategy and institutional relationships. Executive communication focuses on the principal’s judgement, language, preparation, answers and ability to make the case clearly within those boundaries. The disciplines can work together.

Can strong communication secure government support?

No responsible adviser can guarantee that. Government decisions depend on mandate, law, policy, evidence, competing priorities, public interest and institutional process. Strong communication improves the quality and legibility of the case; it does not replace the decision.

The deeper return

A single government conversation can influence months of work because it can clarify ownership, accelerate the right technical process, prevent a false assumption or reveal that the proposal is poorly aligned before more capital is spent.

That is the economic value of stronger government-facing communication.

Not the elegance of the presentation.

The quality of the next decision.

Conclusion

Senior leaders communicate well with ministers when they make serious decisions easier to evaluate.

Connect the proposal to mandate.

Translate commercial value into public value without pretending they are identical.

Separate evidence from projection.

Name the constraints.

Show the implementation route.

Make a proportionate ask.

Then record the meeting accurately enough that nobody inside your own organisation upgrades interest into approval.

For CEOs, founders and institutional leaders preparing consequential government conversations, Executive Authority provides confidential counsel focused on principal-level preparation, decision architecture, stakeholder interpretation and the language that must remain credible after the meeting ends.

The institutional interpretation audit

Before the delegation leaves for the meeting, assign one person who has not built the proposal to read the briefing as though they work inside government. Their job is not to make the pitch prettier. Their job is to identify where the institution would have to infer too much.

Ask them to mark every sentence that requires one of five hidden translations: commercial benefit into public value; company urgency into government urgency; ambition into evidence; senior interest into actual authority; and enthusiasm into an executable next step.

Every marked sentence is a communication risk because the ministerial side may make a different translation from the one the company assumes.

This audit often reveals that the delegation has prepared the answer to “Why is this good for us?” far better than the answer to “Why should this office act?” The correction is not to remove commercial logic. It is to make both sides of the decision visible.

The public-value balance sheet

For material proposals, create a simple two-column public-value balance sheet before the meeting.

On one side, list the public benefits the proposal may create: capacity, jobs, resilience, skills, access, competition, tax base, technology transfer, infrastructure or another legitimate outcome. On the other side, list the public burdens and dependencies: incentives, infrastructure commitments, regulatory complexity, environmental impact, exclusivity, contingent liabilities, implementation risk or administrative demand.

This prevents the presentation from implying that public value is costless.

A minister or adviser can then see the exchange more honestly. The objective is not to make the burdens disappear. It is to demonstrate that the company understands the whole institutional bargain.

When the minister asks for something unexpected

A senior official may introduce a condition, alternative structure or request the delegation did not anticipate.

The dangerous response is to agree in the room because the CEO wants momentum. Another dangerous response is to reject immediately without understanding the institutional reason for the request.

Use a three-part response.

First, clarify exactly what is being asked. Second, identify which elements the delegation can discuss and which require internal review. Third, set a specific follow-up path.

For example:

“We understand the objective. I do not want to commit the company to the mechanism before our finance and legal teams test the implications. We can return within five working days with either a confirmed structure or a clear explanation of what would need to change.”

That answer protects the relationship and the company from impulsive commitment.

The ministerial meeting should improve the proposal even if nothing is approved

Government stakeholders often see system effects that a company does not see from inside its own commercial model.

A question about affordability may reveal a user problem. A question about local capability may expose a staffing assumption. A concern about public narrative may reveal that the project’s claimed social value is not yet credible. An inter-agency issue may show that the company has misunderstood the implementation path.

Treat those questions as intelligence, not resistance.

One mark of a mature executive is the ability to leave a senior-government meeting with a better proposal rather than merely a stronger desire to defend the original one.

This is also why communication quality has economic value. A clear conversation can surface a fatal constraint before money is committed, reveal a route that was previously invisible or prevent months of lobbying the wrong institution. None of those outcomes depends on theatrical persuasion. They depend on accurate institutional understanding.

The discipline of accurate optimism

A government-facing executive can be ambitious without presenting aspiration as certainty. Describe what the company intends to achieve, what is already committed, what remains conditional and what evidence will determine the next stage. Accurate optimism is more useful than ceremonial confidence because it allows the institution to distinguish enthusiasm from obligation.

Related Executive Authority resources

Public sources

  1. OECD — Survey on Drivers of Trust in Public Institutions: 2024 Results
  2. OECD — Trust and information integrity
  3. World Bank — Stakeholder Communication and Engagement for PPPs
  4. World Bank — PPP Reference Guide

Author and institutional attribution

Kevin Abdulrahman, Principal — Executive Authority

Executive Authority is the institutional publisher. Kevin Abdulrahman appears as the accountable author/principal under the established Insight author component.

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