Der Feedback-Decoder für Führungskräfte: Verwandeln Sie Vages Feedback in einen Konkreten Aktionsplan
Warum dieser Prompt wichtig ist
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.
Wofür wir ihn verwenden
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.
Ergebnis
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 |
Vages Leistungsfeedback ist eine besondere Art von Frustration: Es ist eindeutig wichtig genug, dass eine Führungskraft es angesprochen hat, aber so formuliert, dass es keinerlei Anleitung gibt, was tatsächlich anders gemacht werden soll. „Sei strategischer." „Zeig mehr Führungspräsenz." „Denk größer." Jede dieser Aussagen könnte drei oder vier tatsächlich unterschiedliche Dinge bedeuten, und falsches Raten verschwendet einen ganzen Beurteilungszyklus.
Warum dieser Prompt mehrere Interpretationen statt einer erzeugt
Die Anweisung, 2-3 konkrete Interpretationen pro vager Aussage zu erzeugen, statt einer einzigen besten Vermutung, ist die zentrale Designentscheidung. Vages Feedback ist oft absichtlich unspezifisch — manchmal weil die Führungskraft selbst nicht vollständig artikuliert hat, was sie meint, manchmal weil es ein Ersatz für etwas ist, das sie nicht direkt aussprechen möchte. Diese Mehrdeutigkeit auf eine einzige, selbstsicher klingende Interpretation zu reduzieren, ist schlimmer, als sie anzuerkennen.
Eigenschaften in beobachtbare Handlungen verwandeln
Die Anforderung, dass jede Interpretation sich in eine spezifische, beobachtbare Handlung auflöst — nicht eine innere Eigenschaft wie „sei selbstbewusster" — existiert, weil Eigenschaften nicht umsetzbar sind und ihre Veränderung nicht überprüft werden kann. „Zeig mehr Führungspräsenz" übersetzt in „nenne deine Empfehlung, bevor du die unterstützenden Daten präsentierst, statt dich schrittweise dorthin vorzuarbeiten" ist etwas, das ein Kollege tatsächlich als anders ablaufend in einem Meeting bemerken kann.
Die klärende Frage zählt mehr als der Plan
Das Modell zu bitten, eine nicht-defensive klärende Frage vorzuschlagen, ist wohl das wertvollste Ergebnis des gesamten Prompts. Die meisten Menschen raten entweder still bei vagem Feedback oder vermeiden es, nachzufragen, weil klärende Fragen wie Widerstand klingen können. Eine gut formulierte Frage — gestellt mit echter Neugier statt Abwehrhaltung — bringt eine Führungskraft oft dazu, in dreißig Sekunden zu sagen, was drei weitere Beurteilungszyklen gebraucht hätte, um es korrekt zu erschließen.
Warum der Prompt sich weigert, immer eine sichere Antwort zu geben
Die Einschränkung, Feedback zu kennzeichnen, das wirklich zu vage ist, um es zu interpretieren, statt eine plausibel klingende, aber unbelegte Lesart zu erfinden, ist wichtig, weil falsches Vertrauen hier aktiv schädlich ist — eine falsche Vermutung, nach der 90 Tage gehandelt wird, ist schlimmer als gar kein Plan.