How to ask for feedback before a 1:1 (the 24-hour pre-ask)

You have a 1:1 with someone on your team tomorrow afternoon. At some point in the meeting, you'd like to ask them how you're doing as their manager — what's working, what isn't, where you could be better. You already know how the conversation usually goes. You ask the question in the last five minutes. They pause, say "no, honestly, things are good," and you both move on. You walk out unsure whether you actually got an answer or whether they just didn't want to spend the last five minutes of a meeting telling their boss something uncomfortable.

The fix isn't asking the question better in the moment. The fix is asking it twenty-four hours earlier, in writing, before the meeting starts.

Why end-of-1:1 is the worst time to ask

The end of a 1:1 is the moment with the least useful conditions for honest feedback. Three things are working against you simultaneously, and you can't fix them inside the meeting.

They've used all their meeting energy on their own agenda. A direct report walking into a 1:1 with their manager has things they want to bring up — a project blocker, a career conversation they've been postponing, a question about scope. That's the meeting from their perspective. By the time they've gotten through their own list, plus your check-ins, the last five minutes are mental fumes. Asking "any feedback for me?" at that point is asking them to do work, alone, with no preparation, while they're already trying to wrap up.

The social cost of an honest answer just went up. Saying "yes, actually, I've been frustrated with how you handled X" in the last five minutes of a 1:1 means leaving the meeting on a tense note. There's no time to discuss, no time to repair, no time for you to respond well. The honest answer creates a logistical problem the polite answer doesn't. So they give the polite answer. That isn't cowardice — it's a reasonable read of the situation.

You've already revealed where you stand on the topics that came up. By the end of the 1:1 they've heard your tone on the projects you discussed. If you sounded defensive about the timeline question they raised in minute fifteen, that's now in the air when you ask for general feedback in minute fifty-five. They know how you'd react to more of the same. The earlier you ask in the meeting, the cleaner the slate — but even minute one is too late if you wanted considered feedback rather than reactive feedback.

The standard advice is to "get better at asking" or "create psychological safety." Both can be true and neither addresses the structural problem: a 1:1 isn't the right container for asking someone to evaluate you. It's the right container for receiving the evaluation, after they've had time to formulate it.

The 24-hour pre-ask

What changes if you ask the night before, in writing, instead of in the room?

They have time to think. Upward feedback that's worth hearing isn't a reflex. It's a considered answer to a specific question, drawing on weeks of observation. Asking in the room demands an instant reply. Asking twenty-four hours before lets them sleep on it.

You're signaling that you actually want the answer. A boss who asks "any feedback?" in the closing minute is performing a ritual. A boss who sends a message the day before, saying "I want to make some real time for upward feedback in tomorrow's 1:1 — here's the specific thing I want to know," is doing something different. The medium signals the seriousness, and that signal predisposes them toward a real answer.

The format is asynchronous, which lowers the cost of being honest. When the answer doesn't have to be delivered face-to-face under time pressure, the threshold for honesty drops. They can write something, read it back, soften the parts that are gratuitous, sharpen the parts that are real. They can also choose to wait until the room — but the choice is theirs, not yours.

It limits scope. Asking in advance forces you to name what you want feedback on. "Any feedback?" is unanswerable. "I want feedback on how I ran last week's strategy meeting" is answerable. Naming the topic ahead means you'll get an answer about that topic, not a deflection.

The Center for Creative Leadership has documented this in their development research — the half-life of useful behavioral feedback is days, not months. Pre-1:1 timing puts the question inside that window, with prep time, instead of asking for it cold in the moment.

The three-sentence template

Here's what to send the day before. Three sentences, no more.

"For tomorrow's 1:1, I'd like to spend ten minutes on something specific: how I handled [a specific situation or behavior] over the last few weeks. You don't need to come with a polished answer — even a rough impression is useful. I'm asking because I want to actually get better at this, not because I'm fishing for reassurance."

Three things this template does that "any feedback for me tomorrow?" doesn't:

It names the topic. Not "feedback in general" but "how I handled the timeline conversation with the partnerships team." Specific enough that they can think about a concrete moment, not generic enough that the answer requires summarizing your entire managerial existence.

It lowers the polish bar explicitly. "Even a rough impression is useful" gives them permission to say something half-formed. Without that line, people self-edit out anything that isn't fully thought through — which is most of the honest stuff.

It names the motivation. "I want to actually get better at this, not fishing for reassurance" is the one line that tells them you can absorb a real answer. Without it, the safe assumption is that you want validation, and you'll get validation.

You can vary the topic from week to week. Some 1:1s, ask about a specific meeting. Some, ask about a decision. Some, ask about a behavioral pattern they might have noticed ("am I getting more or less available than I used to be?"). The variety means each pre-ask is anchored to something fresh and observable — and you build a library of small specific observations rather than one annual lump of vague impressions.

What to do in the room

The pre-ask isn't the whole conversation. It's the prompt. The conversation happens in the meeting, and that's where most managers undo the work the pre-ask started.

Don't ask again. Once the pre-ask is out, don't open the in-meeting conversation with "so, any thoughts on that?" That's asking twice and signals you didn't really expect them to have thought about it. Instead: "Let's go straight to what you came up with." That assumes they did the work and gives them the floor.

Listen long. When they start speaking, the only thing you say is what makes them keep going. Not yet what you think. Not yet your explanation. Real upward feedback usually comes in two waves — the first wave is the softened-for-safety version, the second wave is the actual one. The second wave only comes if the first wave wasn't interrupted. Edmondson's work on psychological safety is repeatedly mis-applied to mean "manager talks about safety more"; the operational version is closer to "manager talks less in the moments that matter."

Ask one deepening question, not three. When they finish, the temptation is to clarify five things at once. Resist it. Ask one — the question whose answer you most want to hear — and let them go again. The compound effect of one deep follow-up beats three shallow ones every time.

End with what you'll do, not what you've heard. Closing the conversation with "thanks, that's useful, I'll think about it" is dignified, and also where most upward feedback dies. Closing with "OK — one thing I'll try differently next sprint is X. Want to check in on it in two weeks?" creates a thread that didn't exist before. The thread is the difference between feedback as ritual and feedback as development.

Three common mistakes

Sending five questions instead of one. The temptation to make the pre-ask "comprehensive" is strong. Resist it. Five questions ahead of a 1:1 reads as a survey, not a question. People answer surveys the way they answer surveys — quickly, generically, with hedging. One question, one topic, one moment: get a real answer to one thing, not a stack of vague answers to five.

Sending the pre-ask in a public channel. A direct message is fine. A 1:1 doc you share is fine. A pre-ask in a Slack channel where their peers can see it makes them write for an audience. The whole point of asking in advance is to lower the social cost of an honest answer. A public channel raises it again. (More on the channel choice in How to ask peers for feedback.)

Asking and then not actually leaving room in the meeting. A pre-ask followed by a 1:1 that's still packed with your own agenda is worse than no pre-ask at all — you signalled you wanted the conversation, then didn't make space for it. If you sent a pre-ask, you owe them at least fifteen minutes of unhurried discussion. Move other agenda items if needed. Skipping them once is far less expensive than skipping the feedback conversation.

When the pre-ask is the wrong move

The pre-ask works well when there's existing trust. It doesn't fix the absence of trust, and trying to use it as a shortcut can backfire.

A direct report who's been on your team less than a month. They don't have observations yet. Asking a pre-ask within the first few weeks reads as a test or an evaluation of them — they'll feel pressure to produce something insightful when they barely know how you operate. Wait until at least the second month before pre-asking.

A relationship that's currently tense over something else. If you're in the middle of a disagreement about scope, comp, or role, a pre-ask about your management style is going to land as a deflection from the actual conflict. Resolve the standing issue first, then start the pre-ask rhythm later.

A direct report who's said honest things and seen them go badly. This is the most expensive one to recover from. If they've given you real feedback in the past and you reacted defensively, or it leaked into the next performance conversation, or the relationship visibly cooled afterward — the pre-ask won't undo that. The repair has to come from you naming the prior pattern and changing it. Asking again before that repair is a way of pretending the pattern didn't happen.

When the pre-ask becomes a structured round

Pre-asks work for individual moments and individual people. They don't scale to "how am I doing across my team." For that, the right instrument is a structured round — same questions to everyone, your own answers in parallel, side-by-side comparison of what each person sees.

That's where Mirorly fits. Our pre-1:1 prep template gives you a calibrated set of questions to send to your direct reports a few days before their 1:1s, with anonymous aggregation so you see the pattern across the team rather than guessing at it one conversation at a time. Run it quarterly. Take the gaps it surfaces into your individual 1:1s as the topic of the next pre-ask. The two instruments compose — pre-ask for depth on one moment with one person, round for breadth across the team.

You can also start without any structure. Send the three-sentence template tonight, before tomorrow's 1:1. See what comes back. The instrument matters less than the timing.

The summary

Asking for upward feedback at the end of a 1:1 is asking under the worst possible conditions. Asking twenty-four hours earlier, in writing, on a specific topic, with explicit permission to be rough, transforms the answer you get. The trick isn't the words. It's the timing.