Feedback Without Fear: Scripts That Pull Specifics From Your Manager

Asking for feedback feels like handing someone a live grenade labeled “be honest.” They smile, nod, and hand it back with “you’re great.”

New hires on their first dashboard project do this all the time. Halfway through, they toss out “any feedback?” and get a pat on the head. Six weeks later, the review arrives with surprises they could’ve fixed months ago.

Feedback at work is a structured ask for calibration on your output. It’s you saying, show me the gap between what I did and what hits the mark here.

Your manager isn’t grading your soul. They’re checking if your work aligns with team priorities, reduces their risk, and scales without constant oversight. They want to know: does this person ship reliably? Do they need babysitting? Can they handle the next thing alone? Vague questions leave them guessing what you want, so they default to safe, forgettable lines that check the box.

A good feedback exchange sounds like this: you name a recent deliverable. They pinpoint one thing to repeat (the repeatable win) and one to tweak (the quiet miss). You leave with two actionable phrases: “Double down on the data summaries” or “Cut the intro next time; decision-makers skim.” Total time: three minutes. Both sides clearer.

The bad version? You say “how am I doing?” They pause, search for positives: “Keep up the good work. Team loves your energy.” You nod, relieved. Nothing changes. Your blind spots stay blind. Their mental model of you stays fuzzy until it matters.

The scripts that force specifics

This isn’t therapy hour. It’s a quick diagnostic. Timebox it to five minutes in your next 1:1. Pick one output from the last two weeks: a doc, a slide deck, a PR, an email thread. Share the link ahead if async works better.

The core rule: never ask open-ended. Name the thing. Ask for repeat/change. Here’s the kit.

First, the one-liner opener that works every time:

“On the [specific deliverable], what should I repeat next time? What one tweak would make it stronger?”

That’s your base script. Plug in the artifact. Examples:

“On the Q2 metrics deck, what should I repeat next time? What one tweak would make it stronger?”

“In yesterday’s stakeholder email, what should I repeat? One change to land better?”

Managers love this. It scopes their effort to 60 seconds. No essay required. You’ll get lines like “Repeat the executive summary table; skip the methodology unless asked.”

Your manager is juggling thirteen Slack threads and a meeting they’re late for, so this sharp ask cuts through the noise.

If they go vague (“it was good”), nudge once:

“Thanks. Specifically, one thing to keep doing and one to adjust?”

Still vague? You’ve got your baseline: no strong signals. Move on.

For bigger asks, like after a project wrap:

Send this in chat or shared doc pre-1:1. Your manager fills the blanks. Looks proactive. Takes them two minutes.

I’ve used variants of this at Stylitics, like when I pushed a dashboard prototype ten minutes before standup and asked about the viz choices. Got “Repeat the cohort breakdowns; less pie charts, they confuse execs.” Saved me three revisions.

Yes, scripting your feedback request feels a bit silly at first, like rehearsing small talk. Corporate rituals often do. Run it four times, and it feels normal. Your manager starts volunteering unprompted.

One quirk: managers hoard negatives until reviews. They forget you want them early. This pulls them out.

That grenade? It only explodes if you leave it vague. Specifics defuse it every time.

---

(Word count: 732)