There's a version of the 1:1 that I've sat in on too many times, on both sides of the table. The meeting starts. Someone asks, "How's everything going?" The other person says, "Good, yeah, pretty busy." There's a brief discussion of whatever's happening that week. The meeting ends ten minutes early. Both people get a little bit of time back and feel vaguely like they could have just sent a message. Nobody complains. The 1:1 stays on the calendar. And nothing actually improves. The instinct is to blame the direct report. They didn't come prepared. They didn't have anything to talk about. But in my experience, that's the wrong diagnosis. A 1:1 that consistently goes nowhere is almost always a structural problem: either nobody has set expectations for what the meeting is *for*, or the format has drifted into something too passive to be useful to either person. You can't fix a vague meeting by waiting for someone to stop being vague. ## The 1:1 Belongs to the Direct Report Most writing about 1:1s frames them as a manager's tool, a way to stay informed, spot problems early, and maintain a pulse on the team. That's all true, and it's all backwards. The most important frame for a 1:1 is the direct report's: this is *your* best recurring opportunity to steer your own career at the company. Let's think about what that means in practice. The 1:1 is where you can surface a problem before it becomes a crisis. It's where you can ask for the type of work you actually want to be doing. It's where you can get a clear-eyed read on how your manager perceives your performance, not through the sanitized language of a performance review, but in real conversation. It's where you find out what's valued and what isn't, before it matters. If you don't understand the 1:1 as your meeting to own, you'll treat it as a status update. Status updates are fine, but they don't need thirty minutes and a standing calendar invite. They need a Slack message. ## The Asymmetry Problem Here's what makes the vague 1:1 so persistent: both people think it's going fine. The manager thinks it's going fine because no one is bringing problems. The direct report thinks it's fine because they don't want to seem high-maintenance or like they're constantly asking for things. So the meeting stays on the calendar, both people show up, and the value quietly drains out of it over several months. I've been guilty of this as a manager. A direct report I had early on would show up every week with a couple of project updates, I'd share some context about what was happening on the broader team, and we'd wrap up. I thought it was a solid 1:1. It wasn't until that person told me, months later, that they'd felt directionless during that period that I realized the meeting had been giving both of us the feeling of connection without any of the substance. I just hadn't been asking the right questions, or really any questions at all. ## Stop Asking "How Am I Doing?" The most common version of seeking feedback in a 1:1 is also the least useful: "How am I doing?" or "How do you think that project went?" These are hard questions to answer well in the moment. They require your manager to rapidly scan everything you've done, filter it through their current mood and priorities, and deliver something that's useful to you. More often than not, you get something like, "You're doing great, just keep it up." Which feels good and tells you nothing. The fix is targeted feedback, and it changed how I think about these conversations. Instead of asking your manager to evaluate everything, you bring a specific scenario and a specific question about it. Something like: "On the last sprint planning, I tried to push back more on scope before we committed. I felt okay about it in the moment, but I'm not sure I made the case clearly to the product team. It came across a bit abrupt. What did you observe, and how would you have handled it?" Now your manager has something concrete to respond to. They know exactly what you're referring to. They can give you a real read on what they saw, and the two of you can have an actual discussion about it rather than a performance assessment that goes nowhere. The more precisely you can frame the question, the more useful the answer. This applies in both directions. Managers can use the same technique when asking for feedback on their own performance with their reports. ## Tools That Help Direct Reports Show Up Prepared One thing I've noticed is that direct reports often don't come prepared not because they're disengaged, but because they haven't built habits for reflection. They know things happened that week, but they haven't processed them into something worth discussing. A few lightweight tools have made a real difference for my teams. ****The 5-15 report**** is a weekly async update that takes fifteen minutes to write and five to read. Three sections: what did you accomplish this week, what are you working on next week, and what's blocking you or needs attention. I ask my direct reports to send this before our 1:1 each week. What it does is force a moment of reflection before the meeting, which means they almost always arrive with something to talk about. It also means I can skip the status update portion of the conversation entirely and go straight to what matters. ****The brag document**** is something I've borrowed and adapted: a running log of wins, impact, and things you're proud of. I ask direct reports to maintain one throughout the year, not for me, but for themselves. It sounds slightly self-congratulatory but it's genuinely useful. People forget what they did three months ago. When review season comes, or when someone needs to make a case for a promotion, the brag document is the raw material. More importantly, it develops a habit of noticing impact as you go rather than trying to reconstruct it at the end of the year. ****Quarterly self-reflections**** are a more structured version of the same instinct. Every quarter I ask my reports to write a short reflection: what did you accomplish, what did you learn, what do you want to focus on next quarter? We discuss it in the 1:1. It creates natural moments to zoom out from the day-to-day and have the kind of career conversation that gets squeezed out when every meeting is about the current sprint. None of these are onerous if you keep them lightweight. The risk is over-engineering the process until the overhead outweighs the value. The 5-15 should take fifteen minutes, not an hour. If it starts taking longer, something has gone wrong with the format. ## What to Do When Someone Comes With Nothing If a direct report regularly shows up to 1:1s with nothing to discuss, the worst thing you can do is fill the silence for them every time. That just trains them to wait for you. Instead, ask something specific: "On the API migration, how do you feel about the approach you took to the authentication piece? Anything you'd do differently?" A specific question is much easier to answer than an open invitation. If the pattern continues, name it directly. Something like: "I've noticed our 1:1s have been a bit light on your side. I want this time to be genuinely useful for you. What would make it more valuable?" That question is worth more than three months of carrying the meeting yourself. The manager has a responsibility to come prepared too. If you show up with nothing and ask "anything on your mind?", you're signalling that the meeting isn't a priority. I try to come to every 1:1 with one or two things I want to share or discuss: something I've heard from leadership that affects their work, a piece of feedback I've been meaning to give, or a question I've been sitting on about something they're working on. The meeting doesn't belong only to the direct report. It belongs to both of you. ## The 1:1 Isn't a Therapy Session This one is worth saying plainly: a 1:1 is not a substitute for emotional support infrastructure, and a manager is not a therapist. That's not a cold take. People need to vent sometimes, and a good manager should be someone you can be honest with about when things are hard. But if every 1:1 is spent processing frustration, that's usually a sign of something that needs to be addressed more directly: a team dynamic problem, an unclear role, a workload issue. Not something that should keep getting absorbed in weekly conversation. There's a meaningful difference between a 1:1 where someone shares that they're finding a particular project frustrating and wants to think through it together, and one where the meeting becomes a recurring emotional outlet without ever getting to resolution. The first is healthy and useful. The second is a slow drain on both people and often a signal that the underlying issue isn't being acknowledged. When I notice a 1:1 drifting toward the latter, I try to name it with care: "It sounds like this has been weighing on you for a while. I want to make sure we're actually addressing it rather than just talking around it. What would make a real difference here?" ## Show Up With Something Real The 1:1 is only as good as what you bring to it. That's true whether you're the manager or the direct report. The meeting isn't going to fix itself because it's on the calendar, and it won't improve by hoping the other person takes the lead. The thing I keep coming back to is that most people want these meetings to be useful. They just haven't been given a clear enough picture of what useful looks like. Show them. Come with a specific question. Build the habits that make reflection easy. And if the meeting has been going nowhere for a while, say so. A ten-second honest conversation about the format will do more than six more months of showing up and hoping it gets better.