Turn Vague Executive Feedback into a Clear Action Plan

Transforms ambiguous comments from senior leaders into a structured, numbered table of concrete interpretations ready for fast email sign-off.

You getSubject Line, opening and alignment Table

Prompt

Prompt
Act as an executive communications specialist. Your job is to convert vague executive comments on a critical deliverable into a crisp email that clarifies expectations without sounding defensive or incompetent.

I will paste the executive feedback and brief context below.

Follow these rules:
1. Translate each vague statement into an explicit interpretation paired with a concrete planned action.
2. Keep the framing confident, assuming positive intent and taking ownership of next steps.
3. Present the core plan in a clean Markdown table with three columns: Original Comment, Our Interpretation, Planned Action.
4. Close with a frictionless confirmation ask requiring only a quick "looks good" or a single revision note.
5. Keep the total email draft under 160 words outside the table.

Output format:
- Subject Line: Direct, includes the project name and the words "interpretation check" or "next steps".
- Opening: Two sentences acknowledging the input and stating the goal of this note.
- Alignment Table: Columns for Original Comment, Our Interpretation, and Planned Action.
- Sign-off Request: One sentence requesting sign-off by a specific time, plus standard sign-off.

End with a brief note flagging any major delivery risks or unstated assumptions.

Example output

Example for: an enterprise product manager clarifying ambiguous executive notes on a Q3 roadmap proposal.

Subject Line: Project Atlas Q3 Roadmap: Interpretation check and next steps

Hi Marcus,

Thanks for reviewing the draft on Tuesday. To keep momentum toward our sprint kickoff next week, I want to confirm we interpreted your core notes accurately.

Original CommentOur InterpretationPlanned Action
"Make this more strategic"We need to connect the feature milestones directly to the enterprise retention goal rather than listing feature specs.Replace slides 4-6 with an ROI waterfall showing how each release protects renewal revenue.
"Feels too heavy for phase one"The initial scope risks extending the launch timeline past Q3.Move custom reporting and audit logging to phase two, shipping only pre-built dashboards by September 15.
"Double check with Sarah's team"Risk of duplicating current infrastructure efforts in cloud operations.Meet with Sarah on Thursday to confirm her team handles the auth pipeline before finalizing slide 9.

If this alignment matches your vision, reply with "Approved" and we will publish the updated pack by Friday at 2 PM. If anything is off, let me know which row to adjust.

Best,
Elena


Assumptions & Risks: Assumes Sarah's team has capacity to absorb the auth pipeline work this quarter. If they cannot, phase one delivery may slip by two weeks.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • The 3-column table links the raw critique directly to an actionable solution, eliminating guesswork.
  • The closing uses a micro-commitment format so executives can approve with a one-word reply.
  • Prohibits defensive phrasing, keeping the project owner in command of the delivery timeline.

Use in ChatGPT, Claude, or Gemini when a VP or director leaves brief, cryptic notes on a deck, proposal, or memo. Paste the executive's raw comments right after the prompt.

Common edits

  • Add a column for estimated hours or cost impact if the scope change affects resource allocation.
  • Adjust the sign-off sentence to ask for a 5-minute sync instead of an email confirmation if the feedback was deeply critical.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Email