The Manager Feedback Decoder: Turn Vague Performance Feedback Into a Concrete Action Plan
Why this prompt matters
Vague feedback given without a translation step tends to either get ignored, because there's nothing concrete to act on, or over-corrected into the wrong behavior from guessing wrong about what the manager meant. Both outcomes waste an entire review cycle — often 6 to 12 months — before the same feedback resurfaces, at which point it starts to look like a pattern instead of a one-off comment.
What we use it for
You just left a performance review or 1:1 with feedback like 'be more strategic' or 'show more executive presence' — phrases that sound important but give you no idea what to actually change before the next review cycle.
Prompt
Role: Act as an executive coach who specializes in translating ambiguous performance feedback into specific, actionable behavior change — someone who has sat in enough calibration meetings to know what vague phrases like "be more strategic" actually tend to mean in practice. Context: - The feedback I received, as close to verbatim as I can recall: [PASTE THE FEEDBACK FROM A REVIEW, 1:1, OR PEER FEEDBACK] - Who gave it: [MANAGER / SKIP-LEVEL / PEER / 360 REVIEW] - My role and level: [E.G. "SENIOR PRODUCT MANAGER, IC5"] - What I think might be behind it, even if I'm not sure: [YOUR GUESS, OR WRITE "NOT SURE"] - Any recent projects or incidents that might be related: [OPTIONAL CONTEXT] Task: 1. For each vague phrase in the feedback, generate 2-3 concrete, observable interpretations of what it likely means in practice. Do not settle on a single meaning — vague feedback is often intentionally non-specific and could point to more than one real issue. 2. For each interpretation, describe what doing it well would look like as a specific, observable action (a meeting behavior, a document, a decision pattern) — not an internal trait. 3. Flag which interpretation seems most likely given the context I provided, and explain your reasoning. 4. Propose one clarifying question I could ask that would help confirm the right interpretation, phrased so it reads as genuine curiosity rather than pushback. 5. Build a 30-60-90 day action plan for the most likely interpretation, including a way to measure whether the behavior actually changed. Constraints: - Do not assume the feedback is fair or accurate — note if a phrase is unfalsifiable or if more evidence should be gathered before acting on it. - Do not translate feedback into personality changes like "be more confident" — every interpretation must resolve into a specific, observable action. - If the feedback is genuinely too vague to interpret with any confidence, say so explicitly rather than inventing a plausible-sounding but unsupported reading. Output Format: 1. A "Possible Interpretations" table: Phrase | Interpretation | Observable Version | Likelihood. 2. A one-paragraph "Most Likely Read" section explaining the reasoning. 3. The clarifying question to ask, with a one-sentence note on why it's phrased that way. 4. A 30-60-90 day plan as a table with milestones and a measurement for each.
Result
Possible Interpretations
| Phrase | Interpretation | Observable Version | Likelihood |
|---|---|---|---|
| "Be more strategic" | Frames decisions around 12-month company priorities, not just the current sprint | Opens roadmap discussions by naming which company OKR a feature ladders up to, before describing the feature itself | High |
| "Be more strategic" | Proactively surfaces second-order risks and dependencies before being asked | Includes a "what could break this" section in project docs without a manager prompting for it | Medium |
| "Be more strategic" | Communicates trade-offs in business-outcome language rather than feature-list language | Replaces "we're building X, Y, Z this quarter" with "we're prioritizing retention over acquisition this quarter, which means X and Y, and deprioritizing Z" | Medium-High |
Most Likely Read
Given that you're a Senior PM (IC5) and the feedback came from your direct manager during a formal review rather than an offhand comment, the first and third interpretations are most likely — at the IC5 level, "strategic" almost always means connecting day-to-day work explicitly to company-level priorities in written and verbal communication, not a vague personality trait. The second interpretation (proactive risk-surfacing) is plausible but usually gets called out more specifically as "risk management" rather than "strategic thinking" when that's the actual gap.
Clarifying Question
"When you say 'more strategic' — is that mainly about how I'm framing decisions in docs and meetings, or is it more about the substance of what I'm prioritizing? I want to make sure I'm working on the right thing before the next check-in." This works because it offers two concrete hypotheses rather than asking an open-ended "what did you mean," which makes it easy for a manager to just pick one in a few seconds.
30-60-90 Day Plan
| Timeframe | Milestone | How to Measure |
|---|---|---|
| 30 days | Rewrite your next 3 project docs to open with the company priority the work ladders up to | Manager or peer can name the linked company priority after reading your doc's first paragraph |
| 60 days | Reframe one roadmap presentation entirely in trade-off language (what you're prioritizing and deprioritizing, and why) | Ask 2 meeting attendees afterward what trade-off they remember — they should be able to state it back accurately |
| 90 days | Check in directly with your manager on whether the framing shift has registered | Explicit manager confirmation, ideally documented in a 1:1 note, ahead of the next formal review |
Vague performance feedback is a special kind of frustrating: it clearly matters enough that a manager brought it up, but it's phrased in a way that gives no instructions for what to actually do differently. "Be more strategic." "Show more executive presence." "Think bigger picture." Each of these could mean three or four genuinely different things, and guessing wrong wastes an entire review cycle.
Why This Prompt Generates Multiple Interpretations Instead of One
The instruction to produce 2-3 concrete interpretations per vague phrase, rather than a single best guess, is the core design choice. Vague feedback is often intentionally non-specific — sometimes because the manager themselves hasn't fully articulated what they mean, sometimes because it's a proxy for something they're not comfortable stating directly. Collapsing that ambiguity into one confident-sounding interpretation is worse than acknowledging it, because it sends someone confidently in a single wrong direction instead of a productively uncertain one.
Turning Traits Into Observable Actions
The requirement that every interpretation resolve into a specific, observable action — not an internal trait like "be more confident" — exists because traits aren't actionable and can't be verified as changed. "Show more executive presence" translated into "state your recommendation before presenting the supporting data, instead of building up to it" is something a colleague can actually notice happening differently in a meeting. That's the difference between feedback you can act on and feedback you can only feel bad about.
The Clarifying Question Matters More Than the Plan
Asking the model to propose one non-defensive clarifying question is arguably the most valuable output of the whole prompt. Most people either silently guess at vague feedback or avoid asking about it because clarifying questions can sound like pushback. A well-framed question — asked with genuine curiosity rather than defensiveness — often gets a manager to say in thirty seconds what would have taken three more review cycles to infer correctly.
Why the Prompt Refuses to Always Give a Confident Answer
The constraint to flag feedback that's genuinely too vague to interpret, rather than inventing a plausible-sounding but unsupported reading, matters because false confidence here is actively harmful — a wrong guess acted on for 90 days is worse than no plan at all. Some feedback genuinely needs a follow-up conversation before any action plan makes sense, and the prompt is built to say so rather than paper over that gap.