Executive Decision Brief Prompt

Public field comparison

Executive Decision Brief Prompt

Executive Decision Brief Prompt

Condense a complex business decision into options, tradeoffs, risks, metrics, and a recommended action.

Turn a consequential business decision into an evidence-grounded executive brief with comparable options, explicit trade-offs, risk controls, measurable outcomes, and a recommendation.

—

Use this prompt to prepare a decision-ready brief that helps an accountable executive choose among business options without hiding assumptions, uncertainty, dissent, or implementation risk.

Executive Decision Brief
Operating Review
Decision Planning
Risk Review
Implementation Planning

Board or executive investment decisions
Go, no-go, defer, or pilot decisions
Vendor renewal, replacement, or insourcing decisions
Operating-model and resource-allocation decisions
High-stakes initiatives requiring risk and approval gates

Goal or task
Current context
Constraints
Files, data, or examples
Definition of done

Decision question
Decision owner and approval authority
Decision deadline
Business context
Options under consideration
Evidence pack
Constraints and non-negotiables
Decision criteria and priorities
Affected stakeholders
Risk, authority, and escalation limits
Definition of done

Replace every bracketed placeholder before running. Give the model enough context to inspect assumptions, ask only blocking questions, and produce a concrete deliverable. For code prompts, include relevant files, errors, logs, and test commands.

In ChatGPT, replace every bracketed variable with the actual decision details. Provide the relevant evidence pack, such as financial models, KPI definitions, operating reports, customer research, contracts, policies, option estimates, prior decisions, stakeholder notes, and source dates. Redact sensitive data where appropriate, then run the prompt. Answer any blocking questions ChatGPT raises and have the accountable decision owner plus relevant finance, legal, compliance, security, HR, procurement, or operational reviewers validate the resulting brief before action.

Use this when you need a production-ready strategy result in Business, not a generic brainstorm. The expected output should include findings, implementation steps, risks, and verification checks.

A COO must decide whether to renew an underperforming vendor, replace it, or bring the function in-house. The user supplies service-level results, incident history, contract terms, switching costs, internal capacity, stakeholder concerns, and approval limits. ChatGPT produces an evidence ledger, normalized option comparison, scenario economics, recommendation, risk controls, approval-gated implementation outline, and verification record without implying that procurement or implementation has occurred.

Expert

Expert

ChatGPT

ChatGPT

strategy

strategy

chatgpt
strategy
decision memo
Business

chatgpt
business strategy
executive-decision-brief
decision analysis
risk-management
implementation planning

Executive Decision Brief Prompt | AMO.ng

Executive Decision Brief Prompt | AMO.ng

Condense a complex business decision into options, tradeoffs, risks, metrics, and a recommended action.

Create an evidence-grounded executive brief with comparable options, trade-offs, risks, metrics, approval gates, and a defensible recommendation.

Prompt-body line comparison

Removed Added Unchanged context

−Act as a senior Business specialist using ChatGPT. Your task is: [Goal or task].
+Prepare an executive decision brief for the following decision.
 
−Context:
−- Current situation: [Current context]
−- Constraints: [Constraints]
−- Available materials: [Files, data, examples, URLs, logs, notes]
−- Success criteria: [Definition of done]
+Decision inputs
+- Decision question: [Decision question]
+- Decision owner and approval authority: [Decision owner and approval authority]
+- Decision deadline: [Decision deadline]
+- Business context: [Business context]
+- Options already under consideration: [Options under consideration]
+- Evidence pack: [Evidence pack]
+- Constraints and non-negotiables: [Constraints and non-negotiables]
+- Decision criteria and priorities: [Decision criteria and priorities]
+- Affected stakeholders: [Affected stakeholders]
+- Risk, authority, and escalation limits: [Risk, authority, and escalation limits]
+- Definition of a decision-ready brief: [Definition of done]
 
−Workflow:
−1. Restate the objective in operational terms and identify any missing information that would block a reliable answer.
−2. Make reasonable assumptions only when they are low risk, and label them clearly.
−3. Produce the main deliverable for "Executive Decision Brief Prompt" with enough detail that a skilled operator can execute it immediately.
−4. Include edge cases, failure modes, dependencies, and tradeoffs that a junior prompt would usually miss.
−5. Add a verification checklist with concrete tests, review questions, metrics, or acceptance criteria.
−6. End with the smallest safe next action.
+Input requirements
+Treat the decision question, accountable owner, deadline, known constraints, and at least one credible source describing the current situation as minimum inputs. Financial baselines, operating metrics, forecasts, customer evidence, contracts, policies, prior decisions, stakeholder positions, and option estimates are useful supporting inputs.
 
−Output format:
−- Executive summary
−- Detailed plan or implementation
−- Risks and mitigations
−- Verification checklist
−- Next action
+If the decision question, authority, material constraints, or baseline evidence is missing or contradictory, ask only the questions that block responsible comparison or recommendation. If answers are unavailable, continue only where bounded analysis is safe. Preserve each unresolved item as an unknown, conflict, or assumption; do not manufacture figures, stakeholder agreement, approvals, or evidence.
 
−Do not give generic advice. Optimize for a production-quality strategy outcome.
+Evidence and tool rules
+1. Use ChatGPT to organize supplied material, test reasoning, compare options, calculate only from provided figures, and draft the brief. State any calculation method and show enough working for review.
+2. Do not imply access to internal systems, live dashboards, private links, meetings, or external sources unless their contents are actually available in the conversation. A URL alone is not evidence if its relevant content cannot be inspected.
+3. Classify material claims as one of: supplied fact, direct observation from supplied material, calculation, stakeholder assertion, assumption, hypothesis, forecast, unknown, or conflict. Cite the file, excerpt, table, date, or source label supplied by the user whenever available.
+4. Separate historical results from forecasts and correlation from demonstrated causation. Flag stale data, mismatched periods, inconsistent definitions, selection bias, omitted costs, optimistic adoption assumptions, and unsupported precision.
+5. Never describe an option as approved, funded, validated, compliant, tested, launched, communicated, or completed unless the supplied evidence proves that state. Keep proposed, pending approval, blocked, unverified, and executed states distinct.
+
+Decision analysis workflow
+1. Frame the decision: Rewrite the question as a specific choice to be made by the named owner by the deadline. Define what is in scope, what is excluded, why a decision is needed now, and the consequences of delay or no decision.
+2. Establish the baseline: Summarize the current operating and financial position using the most decision-relevant metrics. Record metric definitions, periods, sources, and known data-quality limitations. Distinguish verified baseline values from estimates.
+3. Confirm decision rights: Identify the recommender, approver, consulted parties, implementers, and parties who must be informed. Flag conflicting mandates or any action exceeding the stated authority limits.
+4. Define evaluation criteria: Convert the supplied priorities into clear criteria such as strategic fit, customer impact, expected value, cash requirement, time to value, operational feasibility, reversibility, compliance exposure, security or privacy impact, workforce impact, and execution risk. Assign weights only when supplied or transparently proposed; do not present invented weights as executive preferences.
+5. Build a complete option set: Analyze the supplied options and add a status quo, defer, pilot, staged commitment, or reversible alternative when materially relevant. Do not add artificial options merely to create symmetry. Define scope, prerequisites, dependencies, timing, resource demand, and opportunity cost for each credible option.
+6. Normalize the comparison: Use consistent time horizons, units, cost boundaries, discounting assumptions, and metric definitions. Reconcile one-time and recurring costs, benefits, downside exposure, implementation capacity, and displaced work. Identify values that cannot be compared reliably.
+7. Test economics and outcomes: Where evidence permits, show formulas and inputs for relevant measures such as incremental revenue, avoided cost, total cost of ownership, contribution margin, payback period, break-even point, or expected value. Use ranges or scenarios rather than false precision. Never invent a return estimate when required inputs are absent.
+8. Stress-test the options: Evaluate base, upside, and downside cases; key sensitivities; adoption or demand shortfalls; schedule slippage; cost overruns; dependency failure; vendor or concentration risk; regulatory, legal, privacy, security, reputational, and workforce effects where applicable. Identify assumptions capable of reversing the ranking.
+9. Account for stakeholder effects: State who benefits, who bears cost or disruption, likely objections, distributional effects, change-management needs, and unresolved dissent. Do not infer stakeholder consent from silence.
+10. Form the recommendation: Recommend one option only when the evidence supports a defensible preference. Explain why it wins against the criteria, what trade-offs are accepted, confidence level, and what new evidence would change the recommendation. If evidence is insufficient, issue a conditional recommendation or a clearly bounded no-recommendation finding.
+11. Design execution gates: Translate the recommendation into decision gates, accountable owners, dependencies, resources, approval points, leading and lagging indicators, review cadence, stop-loss thresholds, and rollback or exit conditions. Treat all owners and dates not explicitly confirmed as proposed.
+12. Verify decision readiness: Reconcile important claims to sources, arithmetic to inputs, option scores to rationale, recommendation to criteria, risks to controls, and implementation gates to named authority. Report every failed or unperformed check rather than claiming verification.
+
+Authority and safety boundaries
+- Produce analysis and a recommendation, not an approval. Do not authorize spending, sign contracts, change policy, contact stakeholders, publish communications, move data, alter systems, or initiate implementation.
+- Require explicit human authorization for commitments involving funds, personnel, customers, regulated activity, contracts, production operations, security, privacy, legal positions, or external communications.
+- Minimize exposure of personal, confidential, privileged, security-sensitive, or commercially restricted information. Recommend redaction or aggregation when detailed data is unnecessary. Do not reproduce secrets or credentials.
+- Flag where qualified finance, legal, compliance, security, privacy, HR, procurement, or operational review is required. Do not represent the brief as a substitute for those approvals.
+- Stop at analysis and escalate when evidence suggests unlawful conduct, material safety danger, unauthorized access, sanctions exposure, serious privacy or security risk, an unbounded financial commitment, or a decision outside the named owner's authority.
+- For difficult-to-reverse actions, prefer staged commitment, pilot controls, backups, rollback planning, and explicit kill criteria where practical.
+
+Required output
+
+A. Decision header
+- Decision statement
+- Accountable decision owner and required approvers
+- Decision deadline and urgency
+- Scope and exclusions
+- Current state of the decision: exploratory, under review, recommended, pending approval, or another evidence-supported state
+
+B. Executive position
+- Recommended option or no-recommendation finding
+- Three to five reasons tied to evidence and criteria
+- Material trade-offs being accepted
+- Confidence level with rationale
+- Immediate decision requested from the owner
+
+C. Baseline and decision trigger
+Provide the relevant operating, customer, market, workforce, and financial baseline; why action is being considered now; cost of delay; and status quo trajectory. Include source, period, metric definition, and limitation for each pivotal baseline claim.
+
+D. Evidence ledger
+Create a table with columns: ID; material claim; classification; source or calculation; source date or period; reliability or limitation; confidence; and implication. Include contradictory evidence rather than silently resolving it.
+
+E. Decision criteria
+Create a table with columns: criterion; definition; weight or priority; measurement method; threshold; source of priority; and uncertainty. Clearly mark proposed weights.
+
+F. Options and trade-off matrix
+Create a table with one row per credible option and columns: option; scope; strategic fit; expected benefits; full costs; time to value; feasibility; key dependencies; reversibility; principal risks; stakeholder effects; evidence gaps; and criterion-based result. Include status quo or defer when materially relevant. Follow the table with concise explanations for any scoring or ranking.
+
+G. Economics and scenario analysis
+Show applicable formulas, inputs, units, time horizon, and results. Compare base, upside, and downside cases. Identify the variables with the greatest effect on the outcome and any break-even threshold. If economics cannot be calculated, list the missing inputs and avoid numeric conclusions.
+
+H. Recommendation rationale
+Explain why the preferred option is superior to each viable alternative, which disadvantages remain, why they are tolerable, what assumptions the recommendation depends on, and the evidence or event that would reverse it. State meaningful dissent or unresolved objections.
+
+I. Risk and control register
+Create a table with columns: risk; cause; affected objective; likelihood; impact; exposure; early warning indicator; preventive control; contingency or recovery action; proposed owner; escalation threshold; and residual risk. Distinguish existing controls from proposed controls.
+
+J. Approval-gated implementation outline
+Create a table with columns: phase or gate; intended outcome; proposed owner; prerequisites; resources; approval required; target timing; acceptance evidence; stop condition; and rollback or exit path. Do not imply that any phase has begun unless execution evidence was supplied.
+
+K. Measurement and review plan
+Define the baseline, target, metric owner, data source, measurement frequency, leading indicators, lagging outcomes, guardrail metrics, review dates, and trigger for continue, adjust, pause, scale, or stop decisions. Note whether each target is supplied or proposed.
+
+L. Verification and acceptance record
+Create a table with columns: check; expected condition; actual observation from supplied material; evidence reference; result as passed, failed, unperformed, or blocked; and required resolution. At minimum check:
+- the decision owner and approval path are explicit;
+- options use consistent scope, units, and time horizons;
+- pivotal claims trace to evidence;
+- calculations reconcile to source inputs;
+- assumptions and forecasts are labeled;
+- status quo and delay consequences were considered;
+- recommendation follows the stated criteria;
+- material downside and affected stakeholders are represented;
+- authority, specialist-review, privacy, and compliance limits are addressed;
+- implementation gates have acceptance evidence and stop or exit conditions;
+- no completion or approval claim exceeds available evidence.
+
+M. Open issues and handoff
+List blocking questions, non-blocking unknowns, evidence conflicts, required specialist reviews, decisions reserved for humans, and the smallest safe next action. End with a concise decision-owner checklist separating: decide now, obtain evidence, seek approval, and defer.