Defining the Executive Decision or Approval Needed

Welcome back. In the baseline lesson, you recorded how you currently present under realistic conditions and scored what the audience could observe: structure, influence, delivery, and your internal confidence. This lesson makes one crucial shift: from giving an update to defining the response your presentation is meant to produce.

For senior leaders, a presentation is rarely valuable simply because it contains accurate information. Its value is in helping the right people make, authorize, or initiate a consequential next move. By the end of this lesson, you will have a concise, decision-ready request for the same topic you used in your baseline recording.

---

Define the finish line before building the presentation

A technical leader can easily spend most of a presentation explaining the system, incident history, architecture options, delivery plan, or cost model. All of that may be relevant, but none of it tells executives what they are supposed to do.

Your first planning question is therefore not, “What should I tell them?” It is:

When this meeting ends, what must be different because we met?

The answer should name a decision, approval, or action.

Type of outcome	What it means	Software-engineering example
Decision	Leaders choose among meaningful paths.	Choose a staged platform migration rather than a full replacement or deferral.
Approval	Leaders authorize funding, capacity, priority, or a bounded plan.	Approve up to USD 500,000 for a 12-week reliability pilot.
Action	A named person takes a concrete next step.	Ask the CTO to sponsor a cross-functional security review by the end of the month.
Alignment	Leaders explicitly confirm a direction so execution can proceed.	Confirm that reliability work takes priority over two lower-value roadmap items this quarter.

“Alignment” is only useful when it is made behavioral. “I want alignment on the strategy” is vague. “I am asking the product and technology leadership team to confirm that the checkout resilience program is the top engineering investment for Q3” is observable and actionable.

A single presentation can have several consequences, but it should normally have one primary ask. If you ask for budget, headcount, priority, sponsorship, an architecture decision, and a delivery commitment all at once, the group has to unpack a bundle of decisions before it can respond. That creates delay.

Choose the next gating commitment: the one decision without which the initiative cannot sensibly proceed.

For example, if the organization has not yet validated the scale of a reliability problem, the appropriate ask may be approval for a short diagnostic effort, not approval for a multi-year platform rebuild. A well-scoped request shows judgment: you are asking executives to decide only what the evidence can support at this point.

---

Separate the recommendation from the request

These two statements belong together, but they do different jobs.

• A recommendation states your judgment: what you think the organization should do.
• A request states the response you need from the decision-maker.

Consider this example:

Recommendation: I recommend a phased resilience program for our checkout services, beginning with the two failure points responsible for most peak-period incidents.

Request: Today, I am asking the Technology Investment Committee to approve up to USD 500,000 and two dedicated engineering teams for a 12-week first phase.

The recommendation communicates ownership. You are not handing executives raw facts and asking them to do the analysis. The request makes the meeting’s purpose unmistakable.

Then add the consequence:

Why now: Approval this month allows the work to complete before the peak-season change freeze; deferring it leaves the current incident exposure in place through that period.

This gives you a compact executive logic:

1. What I recommend
2. What I need you to decide or authorize
3. Why this decision matters now

The supporting evidence will come later in the presentation. For now, you are defining the destination that evidence must support.

The image’s “one sentence, one number, one date” guidance is a useful discipline rather than an absolute rule. A number might be a funding cap, team capacity, expected impact, or pilot duration. A date might be the decision deadline or the execution milestone that delay would threaten. Do not invent precision, but do remove avoidable ambiguity.

---

Make the request easy to answer

A decision-ready request has five properties.

Property	What good looks like	Weak version
Decision owner	The person or forum with authority is explicit.	“Leadership should approve this.”
Decision verb	Uses a clear verb such as approve, select, authorize, confirm, or sponsor.	“We need support.”
Specific scope	States what is included and, where useful, what is not.	“Invest in modernization.”
Bounded commitment	Includes a budget cap, duration, capacity level, or defined phase.	“Give us the resources we need.”
Timing and consequence	Identifies when a decision is needed and the real cost of delay.	“It would be great to decide soon.”

A useful template is:

By [date], I am asking [decision-maker] to [approve / select / authorize / confirm] [specific commitment and scope] so that [business result or risk consequence].

Here are three examples at different levels of scope:

• Reliability: “By 15 May, I am asking the Technology Investment Committee to authorize a 12-week checkout-resilience pilot, capped at USD 500,000, so we can reduce peak-season incident exposure before the Q3 change freeze.”

• Security: “Today, I am asking the CIO to appoint an executive sponsor for the identity-access remediation program and confirm quarterly progress reviews, so unresolved audit findings have visible ownership.”

• Capacity and roadmap: “By next Tuesday, I am asking the product and engineering leadership team to approve moving two teams from lower-priority feature work to the customer-onboarding performance program for Q3, so the enterprise launch date remains viable.”

Notice that these are not yet full presentations. They are the contract for the presentation. Once the ask is clear, you can decide which facts, options, risks, and visuals deserve time. Anything that does not help the audience make this particular decision is a candidate for an appendix, a follow-up document, or removal.

---

Turn your baseline topic into a decision statement

Use the topic from your two-minute baseline recording. Spend about 12 minutes completing this planning canvas in writing. Keep the language plain initially; polish comes after the decision itself is clear.

1. Identify the next real commitment

Write one sentence beginning:

At the end of this meeting, I need __________ to __________.

Name the actual authority, not an abstract group if a specific accountable leader exists. For example, write “the CTO” or “the Product and Technology Investment Committee,” rather than “senior leadership.”

2. Bound the scope

Add the details that make “yes” meaningful:

• the option, initiative, or action being approved;
• the funding, people, time period, or priority involved;
• the boundary of the commitment.

For instance, “approve a 90-day discovery phase” is materially different from “approve the full migration.” Executives need to know which one is in front of them.

3. State the consequence of both action and delay

Complete these two phrases:

A positive decision enables __________.

If the decision is delayed until __________, the likely consequence is __________.

Keep this honest and concrete. A reason to act now might be a product-launch dependency, an expiring vendor commitment, a forecasted operational-risk window, a hiring cycle, or an opportunity cost. Artificial urgency weakens credibility; a specific cost of delay strengthens it.

4. Draft the three-line executive close

Write the following in your own context:

Recommendation: I recommend __________.

Decision request: I am asking __________ to __________ by __________.

Reason now: This enables / avoids __________.

Read it aloud. A strong version should be understandable to a non-technical executive without further translation.

---

Deliver the request, then listen for ambiguity

Spend five minutes on a short standing rehearsal. Use no slides and no more than a small cue card containing your three lines.

Deliver this in 45 seconds:

1. One sentence of context: the business problem or opportunity.
2. Your recommendation.
3. Your explicit decision request.
4. Your reason to act now.

Do one recording. On playback, listen for three common ways an ask becomes unclear:

• The request appears too late. The listener receives background but does not know why it matters.
• The request is hidden in soft language. Phrases such as “we were hoping to,” “it would be good to,” or “we would welcome thoughts” can be useful in collaborative settings, but they should not replace a decision request.
• The request contains several decisions. If you cannot say precisely what “yes” means, reduce the request to the next necessary commitment.

Revise your wording once. The goal is not to sound forceful for its own sake. It is to make it easy for an executive to understand the decision, judge it, and respond responsibly.

A clear opening and closing can use nearly the same request:

Opening: “Today I am seeking approval for a 12-week resilience pilot capped at USD 500,000.”

Close: “To proceed before the Q3 change freeze, I am asking for approval of that 12-week pilot today. If approved, I will return in July with measured results and the decision required for the next phase.”

Repetition here is not redundancy. It gives a busy audience a stable reference point while the middle of the presentation supplies the reasoning.

---

You now have the first building block of an influential executive presentation: a defined finish line. Your presentation should lead to one appropriately scoped decision, approval, or action; make the authority, commitment, timing, and consequence explicit; and distinguish your recommendation from the request itself.

Keep your three-line executive close. In the next lesson, you will map this same topic to the priorities of directors, VPs, and C-suite leaders, so that your request is framed in terms that matter to the people who must decide.