How do you give feedback in a 1:1?

Make it a small, regular ingredient rather than a rare event. Handle status fast (or async) to free up room, give one specific, recent, forward-looking observation most weeks, anchor it to a concrete moment, frame it toward the next attempt rather than as a verdict, and then stop talking and listen. Frequency is what keeps it low-stakes, so no single instance lands as a judgment.

Why do my 1:1s never get to real feedback?

Usually because status crowds it out — the whole slot goes to project updates that could have been an async message, leaving no room for the developmental conversation. Move status out of the way first, and deliberately reserve space for one piece of feedback. Otherwise the urgent (updates) always displaces the important (feedback).

How do I give feedback without making the 1:1 feel like an ambush

Give it often and make most of it positive, so feedback becomes routine rather than a signal that something's wrong. When the only feedback you ever give is critical, "can we talk" turns into a threat. Frequent, specific, low-stakes feedback — anchored to recent moments and pointed at the next attempt — keeps the meeting safe.

Should I use the feedback sandwich in a 1:1?

No — it backfires. Burying criticism between compliments teaches people to hear praise as a warning and dilutes both messages. Be specific instead: name the actual behavior you want more or less of. Genuine positive feedback and genuine corrective feedback both work better delivered clearly and separately than blended into a sandwich.

How to give feedback in a 1:1 without wasting time

The 1:1 is supposed to be where feedback lives, and in most cases it's the last place you'll find any. The meeting fills up with status — what's done, what's blocked, what's next — the thirty minutes evaporate, and the actual feedback either never surfaces or gets saved up for a quarterly review where it lands as a stockpiled surprise. The other failure mode is worse: feedback only appears in the 1:1 when something's wrong, so the words "can we talk about something" become a threat, and the person spends every 1:1 braced for impact. Neither is inevitable. A 1:1 can be the most natural, lowest-stakes place to give feedback there is — but only if you structure it so feedback is a routine ingredient rather than a rare, heavy event.

Why the 1:1 is the right place — and how it goes wrong

A 1:1 has everything feedback needs: it's regular, it's private, and it's already about the person rather than just the work. That's a far better container than a once-a-year review, where feedback is stockpiled and stale by the time it arrives. But two habits quietly ruin it:

It becomes a status meeting. If the whole slot goes to project updates — things that could have been an async message — there's no room left for the human, developmental conversation the 1:1 is actually for. Status crowds out feedback every single time unless you protect against it.
Feedback only appears when it's negative. If the only time you raise something is when it's gone wrong, you've trained the person to dread the meeting. Feedback that's rare and always critical reads as an attack, no matter how kindly you word it.

The fix for both is the same: make feedback small, specific, and frequent, so it's woven through the 1:1 rather than saved up for it.

The status-only (or ambush) 1:1 vs the feedback-woven one

Status-only, or the ambush

Thirty minutes of "what's on your plate," then either no feedback at all, or — occasionally — a heavy "we need to talk about X" that's been building for weeks. The person leaves either uncalibrated or rattled, and learns to brace for the next one.

Feedback woven in

Status is handled quickly (or async beforehand), leaving room for one specific, recent, forward-looking observation — good or corrective — most weeks. Feedback becomes normal, small, and low-stakes, so it lands as help rather than a verdict.

The structure that doesn't waste anyone's time

You don't need a script or a framework acronym. You need a few habits that keep feedback flowing without turning the meeting into a performance review.

Get status out of the way first — or async
Handle project updates fast, or move them to a shared doc before the meeting, so the 1:1 isn't consumed by things that didn't need a conversation. This is what frees up room for feedback at all.
Make it a regular small ingredient
Aim to give one specific piece of feedback — often positive — most weeks. Frequency is what lowers the stakes: when feedback is routine, no single instance carries the weight of a verdict, and "can we talk" stops being ominous.
Anchor to a specific, recent moment
"In yesterday's standup, when you cut the scope call short" beats "you sometimes rush decisions." A recent, concrete moment is something the person can picture and act on; a general trait is something they can only defend. The feedback models like SBI are just ways to keep this specific.
Point at the next attempt, not the last one
Frame feedback toward what to do next time, not as a judgment of what happened. "Next time, loop in design before you lock scope" is usable; "you should have looped in design" is just a verdict. The goal is the next rep, not the autopsy.
Then stop talking and listen
Give the observation, then leave real silence for their side — context you didn't have, or a question. Feedback that's a monologue is an instruction; feedback that's a short exchange is a conversation, and only the second kind changes anything.

Skip the sandwich and the vague praise

Two moves feel kind and quietly backfire. The feedback sandwich — burying a criticism between two compliments — teaches people to hear praise as a warning shot and dilutes both messages; it's earned its own bad reputation for good reasons. And vague praise — "great job this week!" — feels nice but carries no information; the person can't repeat what they can't identify. Specific beats kind-but-empty in both directions: name the actual behavior, whether you want more of it or less. When the feedback is genuinely hard, that's its own skill — giving corrective feedback to a report without crushing them — but the 1:1's regular cadence is what keeps most feedback from ever having to be that heavy. Research from McKinsey on manager effectiveness and MIT Sloan Management Review on workplace candor keeps converging on the same point: frequent, specific, in-the-flow feedback develops people; saved-up, formal feedback mostly defends the manager.

What this looks like across a few weeks

Take a manager whose 1:1s with a new engineer had become pure status — tickets, blockers, next sprint — with any real feedback saved for review season. She makes one change: status moves to a shared doc updated before the meeting, which frees the whole slot. Week one, she gives a single specific piece of positive feedback: "In Tuesday's incident call, the way you narrated what you were checking kept everyone calm — keep doing that." Small, concrete, nothing heavy. Week three, a corrective one, anchored and forward-looking: "On the auth ticket, the PR shipped before design saw it and we had to redo the modal — next time, loop them in before you lock the markup." Because it's one small item in a steady stream of mostly specific, positive feedback, it lands as coaching rather than a reprimand; the engineer nods, mentions he didn't realize design owned that surface, and they agree on the fix in a minute. No dread, no ambush, no stockpiling. By the time the formal review comes around, there's nothing in it he hasn't already heard and acted on — which is exactly how a review should feel. The only thing that changed was moving status out of the way and treating feedback as a weekly ingredient instead of a quarterly event.

Where Mirorly fits

You've just spent a few minutes on how to give your team better feedback in your 1:1s — which is worth doing. So here's the fair question back: when did your team last give you a real one? Giving feedback well is a manager skill; receiving honest feedback about your own management is much harder to come by, because the people best positioned to give it report to you, and that power gap keeps them quiet. That's the gap Mirorly closes. It's the 360 you run on yourself first — you answer behavioral questions about how you lead, send the same ones to your team, and read your self-view next to theirs, with an anonymity threshold so they can be honest. The core leadership behaviours template is built for exactly that. The best feedback-givers are usually the ones who've felt what it's like to receive it well.

Common questions

The one-line summary

A 1:1 is the most natural place to give feedback and the place it most often dies — crowded out by status or saved up into a dreaded ambush; the fix is to handle status fast, then make feedback a small, regular, specific, forward-looking ingredient most weeks, so it stays low-stakes and lands as help rather than a verdict — and the manager who gives feedback this well should ask when they last received an honest one themselves.