رمزگشای بازخورد مدیر: بازخورد مبهم عملکرد را به یک برنامه اقدام مشخص تبدیل کنید
چرا این پرامپت اهمیت دارد
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.
ما از آن برای چه استفاده میکنیم
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.
پرامپت
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.
نتیجه
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 |
بازخورد مبهم عملکرد نوع خاصی از ناامیدکننده است: بهوضوح آنقدر مهم بوده که مدیر آن را مطرح کرده، اما به شکلی بیان شده که هیچ دستورالعملی برای اینکه واقعاً چه چیزی باید متفاوت انجام شود، ارائه نمیدهد. «استراتژیکتر باش.» «حضور اجرایی بیشتری نشان بده.» «تصویر بزرگتر را ببین.» هر یک از اینها میتواند سه یا چهار معنای واقعاً متفاوت داشته باشد، و حدس اشتباه یک کل چرخه بررسی را هدر میدهد.
چرا این پرامپت چند تفسیر تولید میکند نه یکی
دستور تولید ۲ تا ۳ تفسیر مشخص برای هر عبارت مبهم، بهجای یک حدس بهترین، انتخاب طراحی اصلی است. بازخورد مبهم اغلب عمداً غیرمشخص است — گاهی چون خود مدیر کاملاً بیان نکرده منظورش چیست، گاهی چون نماینده چیزی است که راحت نیست مستقیماً بگوید. فروکاستن این ابهام به یک تفسیر با اطمینان کاذب بدتر از پذیرفتن آن است.
تبدیل ویژگیها به اقدامات قابلمشاهده
الزام اینکه هر تفسیر به یک اقدام مشخص و قابلمشاهده تبدیل شود — نه یک ویژگی درونی مانند «با اعتمادبهنفستر باش» — به این دلیل وجود دارد که ویژگیها قابلاقدام نیستند و نمیتوان تغییرشان را تأیید کرد. «حضور اجرایی بیشتری نشان بده» وقتی به «توصیهات را پیش از ارائه دادههای پشتیبان بیان کن، بهجای اینکه به سمت آن بسازی» ترجمه شود، چیزی است که یک همکار واقعاً میتواند متفاوتبودنش را در یک جلسه ببیند.
سؤال روشنکننده مهمتر از برنامه است
خواستن از مدل برای پیشنهاد یک سؤال روشنکننده غیرتدافعی احتمالاً باارزشترین خروجی کل پرامپت است. اکثر مردم یا بیصدا درباره بازخورد مبهم حدس میزنند یا از پرسیدن درباره آن اجتناب میکنند چون سؤالات روشنکننده میتوانند مانند مقاومت بهنظر برسند. یک سؤال خوبطراحیشده — با کنجکاوی واقعی بهجای تدافعیبودن — اغلب باعث میشود مدیر در سی ثانیه چیزی را بگوید که استنباط درستش سه چرخه بررسی دیگر طول میکشید.
چرا پرامپت از دادن همیشگی پاسخی مطمئن خودداری میکند
محدودیت پرچمگذاری بازخوردی که واقعاً برای تفسیر بیشازحد مبهم است، بهجای اختراع یک خوانش قابلقبول اما بدون پشتوانه، اهمیت دارد چون اطمینان کاذب اینجا فعالانه مضر است — یک حدس اشتباه که برای ۹۰ روز به آن عمل شود بدتر از نداشتن هیچ برنامهای است.