Ask for Feedback Script How-to
“You’re doing fine” feels kind and teaches you nothing. You don’t need a manifesto on candor. You need a short ask that makes it easy for someone to coach you on real work.
Time box: about 10-15 minutes to prep and ask (the conversation may be shorter). The insight: ask for a replay, not a rating. “What’s one thing I should do differently next time on X?” beats “Any feedback?” Specificity is a gift to the giver.
For deeper scripts and timing, see how to ask for feedback at work. Stage homes: Individual Contributor hub and New Hire hub.
When to use (and when not to)
Use after:
– A deliverable, presentation, or customer touchpoint while memory is warm
– A mid-cycle milestone when you can still change habits
– A calm window before review season so you’re not ambushing anyone
Do not use:
– Right after a public miss before you’ve cooled down (you’ll argue)
– Every day (you’ll exhaust people)
– Only when fishing for praise
– To lobby for a performance rating
– To put a peer in an HR-sensitive bind (harassment, discrimination, policy breaches; those go through the proper channels)
This play does not replace formal reviews or employee-relations processes.
Who is involved
- You
- Manager and/or a peer who saw the work
- Occasionally a cross-functional partner who felt the handoff
Ask people with evidence, not a random senior who wasn’t in the room.
Prep checklist (5 minutes)
- Pick one artifact or moment (deck, doc, meeting you ran, ticket thread, customer email).
- Pick one skill or section (clarity of ask, pacing, risk call, handoff quality).
- Write one primary question aimed at a replay: what to do differently next time.
- Note whether they can still change the work (pre-send) or you’re learning for next time.
- Cap the ask: “one thing” or “top two,” not a full review.
Vague vs. specific (fictional):
– Vague: “Any feedback on how I’m doing?”
– Specific: “On yesterday’s roadmap update, what’s one thing I should change next time in how I framed the tradeoff?”
Steps inside the time box
- Prep the artifact + question (above).
- Choose channel: live in 1:1, quick huddle, or async written.
- Ask using a script below. Stop talking after the question.
- Follow up if the answer is vague (“What would that look like next time in one concrete behavior?”).
- Log date, ask, input, and your experiment.
- Close the loop within a week or two: “I tried X based on your note.”
Cadence that usually works: a few specific asks per month, not a daily drip. Fold recurring coaching into your 1:1 operating rhythm.
Scripts
Manager, live (1:1)
I want a replay, not a rating. On [artifact/moment], what’s one thing I should do differently next time on [skill]? A single example is enough.
Peer, live
You saw [meeting/doc]. What’s one thing I should tighten next time: [option A] or [option B], or something else I’m missing?
Async written (Slack/email/doc)
Context: I [shipped / am sending] [artifact] to [audience].
Focus: [clarity / structure / tone / risk call].
Ask: What’s one thing you’d change for next time (or before I send by [time])?
A single bullet is plenty. Thanks.
Follow-ups that turn mush into action
- “What would ‘better’ look like in the first two minutes next time?”
- “Is that a content issue or a delivery issue?”
- “If I only change one habit this month, which one?”
If they say “you’re doing great,” try: “That’s helpful. For my growth edge, what’s the first thing you’d coach if you had to pick one?”
Output: feedback log
| Date | Who | Artifact / ask | Input | My experiment | Closed loop? |
|---|---|---|---|---|---|
| Tue | Maya | Roadmap tradeoff slide | Lead with decision, then options | Reorder next deck | Yes; showed next draft |
You’re collecting experiments, not a shrine of compliments. If you won’t use it, don’t ask for it.
Watch-outs
- Defensiveness. Listen, write, thank. Argue later with yourself, not them.
- Collecting feedback you ignore. That trains people to stop helping.
- Bypassing HR for ER issues. Peer feedback is for craft and collaboration, not investigations.
- Using this to lobby ratings. Separate coaching asks from comp conversations; when you’re ready for the latter, use the Promotion / raise case outline play.
- Assuming honesty is guaranteed. Power dynamics exist. Specific asks raise your odds; they don’t erase incentives.
Close the loop
Quick follow-up: I tried [change] on [new artifact] based on your note about [theme]. If you notice whether it’s landing, I’d welcome one line.
People give better feedback when they see it used. For broader skill building, see giving and receiving feedback and career conversations with your manager.
You’re done when you asked one specific replay question, logged the answer, and named one experiment you’ll try next.