How to Conduct Effective One-on-Ones That Aren't Status Updates

Most one-on-ones are bad. Not because managers don't care, but because the meeting defaults to "what are you working on?" — and then 30 minutes disappear into a status rundown that could've been a Slack message. Here's how to fix it.

Why Status Update 1:1s Are a Waste

You already have standups, project boards, and async updates to track what's getting done. If your 1:1 is just another venue for task review, you're burning the one meeting where a person can tell you what's actually going on — what's frustrating them, where they want to grow, what they'd change if they could.

When 1:1s become status meetings, real problems go underground. Your team starts seeing the meeting as overhead rather than something valuable. That's when people start canceling or showing up with nothing to say.

A Better Agenda Structure

Keep it simple. A good 1:1 has three blocks:

1. Their items (first half). The direct report drives the first part of the meeting. They bring what's on their mind — blockers, frustrations, ideas, feedback, career questions. If they consistently show up with nothing, that's a signal. Either they don't trust the meeting, or you haven't coached them on how to use it.

2. Your items (a few minutes). Share context they might not have — upcoming org changes, feedback from stakeholders, or things you've noticed about their work. Keep it targeted. This isn't a performance review; it's a heads-up.

3. Growth and development (ongoing thread). Not every meeting needs a deep career conversation, but you should revisit it at least monthly. Where do they want to be in a year? What skills are they trying to build? Are they getting opportunities to practice those skills on current projects?

Questions That Actually Open People Up

Ditch "how's it going?" (the answer is always "fine"). Try these instead:

• "What's the hardest part of your work right now?"
• "If you could change one thing about how our team operates, what would it be?"
• "What's something you've done recently that you're proud of?"
• "Is there anything slowing you down that I could help remove?"
• "Do you feel like you're learning here? What would help you learn faster?"
• "Is there feedback you've been wanting to give me?"

That last one matters. If you never ask for feedback as a manager, you'll never get it — and you'll miss problems until they become resignations.

How Often and How Long

Weekly is ideal. Every two weeks is the minimum. Monthly 1:1s are too infrequent — by the time you meet, small issues have calcified into big ones.

Thirty minutes is the sweet spot. Don't default to an hour. Shorter meetings force focus.

Don't cancel. Rescheduling is fine. Canceling signals that the person isn't a priority. Do it repeatedly and expect your best people to start job searching.

Taking Notes and Following Through

Keep a shared doc for each direct report. Both of you can add agenda items before the meeting. After the meeting, jot down action items and commitments. This prevents the most common 1:1 failure: talking about the same problem every week without doing anything about it.

If you committed to something — removing a blocker, giving a stretch assignment, having a conversation with another team — do it before the next 1:1. Nothing kills trust faster than a manager who agrees to help and forgets.

Handling 1:1s in Remote and Web3 Teams

When you're spread across time zones and might not share a single overlapping work hour, the traditional weekly video call doesn't always work.

Async 1:1s are a valid option. Use a shared document or thread where your report writes updates, concerns, and questions throughout the week. You respond within 24 hours. Hold a live call biweekly for the conversations that need real-time back-and-forth — career growth, sensitive feedback, conflict resolution.

In DAOs and flat-structure Web3 teams, the 1:1 dynamic shifts. You might not have a formal manager-report relationship, but regular check-ins between collaborators still matter. If you're a project lead, set up informal 1:1s with core contributors. These conversations catch misalignment early, especially when everyone's pseudonymous and distributed.

Video-off is fine. Some of the best remote 1:1s happen audio-only. It reduces fatigue and often leads to more honest conversation.

The Simplest Test

After your next 1:1, ask yourself: did I learn something I didn't know before? If the answer is yes, the meeting worked. If the answer is no, you're probably still running a status update.

Good 1:1s are how you retain people, develop talent, and catch problems before they explode. If you're stepping into a management role in Web3, getting this right from day one sets the tone for everything else.