Your 1-on-1s show The Broadcaster patterns — here's where to start

Why ask this

Managers often assume they already know what kind of help someone needs, when the honest answer might be something small like protecting their calendar or something bigger like advocating for them in a room they're not in. Asking directly instead of guessing means the support you offer actually matches what they need instead of what you assume they need. It also signals that helping them succeed is something you're actively thinking about, not just a line you say once a quarter.

Why ask this

Managers who jump straight to solving a problem often step on someone who just wanted to think out loud, and managers who hold back advice sometimes leave a report stuck when they actually wanted help. Asking which one they want up front removes the guesswork and stops you giving the wrong kind of support at the wrong moment. It's a small question that prevents a surprising amount of frustration on both sides.

Why ask this

Most people won't volunteer this kind of feedback unprompted, even when it's costing them real time or energy, because it can feel risky to criticize the person who reviews them. Asking directly, and naming that you might not realise it, removes some of that risk and makes clear you actually want the answer. Whatever comes up is also usually fixable once you know about it, which is the whole point of asking.

Why ask this

Limiting it to one thing makes the question feel manageable instead of an invitation to list every complaint, which makes people more likely to actually answer honestly. It also forces them to prioritise, so whatever they say first is usually the thing that matters most to them. Softer versions of this question are easy to deflect with a vague answer, but this phrasing is direct enough that a non-answer stands out.

Why ask this

It's easy for a 1-on-1 to quietly turn into a status update that only serves the manager, and this question checks for that directly instead of assuming the format is working. A flat yes is worth pushing on with a follow-up, since most people won't volunteer that a recurring meeting has stopped being useful to them. Asking this every few months also gives you permission to actually change the format if the answer is lukewarm.

Why ask this

This is a more targeted version of a general support question, since asking for one area forces a real answer instead of a polite 'I'm fine.' It also puts the responsibility on you to act on what comes back, which is part of what makes the question worth asking in the first place. Coming back to this a few months later is a good way to check whether the support you added actually helped.

Why ask this

Asking someone to imagine being in your seat gets past the usual politeness of a direct 'what should I be doing differently' and gets you their actual priorities instead. The top-3 format keeps the answer focused instead of turning into a wish list, and it often reveals what they think is actually broken versus what's just mildly annoying. It's also a good gut check on whether your own priorities match theirs.

Why ask this

People hold back feedback for their manager more than almost anyone else, since it's the relationship with the most at stake if it lands badly. Naming that you know feedback might be sitting there unsaid makes it easier for them to actually say it instead of waiting for a safer moment that may never come. Whatever they raise is worth taking seriously, since it likely took some nerve to bring up.

Why ask this

People are often harder on their own work than anyone else, and if something's been bothering them without ever coming up, it's usually because they assumed it wasn't worth mentioning or didn't want to look like they were making excuses. Asking directly gives them permission to raise it before it turns into a bigger issue at review time. It's also a chance to catch a real quality problem before a customer or another team does.

Why ask this

This surfaces a mismatch in perception before it becomes a surprise, since most people carry some assumption about how their manager sees them that's rarely checked directly. A big gap in either direction is worth a real conversation, whether that means correcting an inflated self-view or reassuring someone who's underrating their own work. It's a faster way to get at calibration than waiting for a formal review to reveal the gap.

Why ask this

People hold back honest opinions about how work actually gets done day to day, especially anything that reflects on you or the team. Framing it as advice for someone else, rather than a direct complaint, makes it much easier to say the parts they'd normally soften. It also surfaces process gaps and workarounds that never come up in a normal status update.

Why ask this

Team conflict rarely gets raised proactively, since most people would rather work around a difficult dynamic than name it directly to their manager. Tying the question to productivity, rather than just asking about team harmony, gives it a practical framing that makes it feel less like gossip and more like a legitimate work topic. Catching this early is a lot easier than untangling it once it's affected a delivery date.

Why ask this

Organisational change is exactly the kind of thing people speculate about privately instead of raising directly, since it can feel like there's no safe way to ask without sounding like they're resisting it. Giving them a direct opening to name a concern means you find out what's actually worrying people before it turns into rumour or disengagement. It also gives you a chance to correct a misunderstanding while it's still small.

Why ask this

Peer feedback tends to be the hardest kind to give, since there's no formal structure forcing it the way a review cycle does with manager feedback. A low score here is worth digging into, since it usually points at either a trust issue on the team or just a lack of practice having those conversations. Tracking this over time also shows whether team-building or process changes are actually making peer feedback easier to give.

Why ask this

Recognition almost always looks fine from the manager's seat and thin from everyone else's, since the manager sees every decision behind a result and the team mostly sees the outcome. A quick scale answer catches that gap before someone quietly decides their work doesn't matter here. Watching the score over several sessions also tells you whether a change you made actually landed.

Why ask this

Decisions made in a hallway conversation or an impromptu desk chat rarely get written down, which puts remote team members at a real disadvantage even when nobody intends it. Asking this directly surfaces a structural gap rather than a personal complaint, since the fix is usually about how decisions get documented rather than about any one person. If the answer is yes, it's worth treating as a process problem rather than something to just apologise for.