--- title: "Running a one-on-one that actually helps" source: https://www.taim.io/career-skills/running-a-one-on-one-that-actually-helps published: Sun May 10 2026 13:31:22 GMT+0000 (Coordinated Universal Time) updated: Sun May 10 2026 13:32:09 GMT+0000 (Coordinated Universal Time) description: "Turn your one-on-ones from status read-outs into working sessions using a three-question agenda, clear safety rules, and simple follow-up notes." --- # Running a one-on-one that actually helps Most one-on-ones decay into polite status updates because no one is clear what the slot is for. Treat it as a working session around three questions, and the conversation changes fast. Most one-on-ones decay into polite status updates because no one is clear what the slot is for. Treat it as a working session around three questions, and the conversation changes fast. ## What you’ll walk away with - A three-question agenda you can drop into your calendar today. - A 25-minute first-attempt script for your next one-on-one. - Specific signals that tell you if your 1:1s are working or just wasting time. - Simple follow-up notes that turn talk into trackable progress. ## Why most one-on-ones rot into status meetings On most teams, the one-on-one is the only recurring private slot. That makes it a magnet for everything: status, venting, last-minute approvals, and whatever is top-of-mind for you as the manager. Without a clear purpose, people default to the safest pattern they know: reporting progress. It feels productive, it’s low-risk, and it matches how many managers run team meetings. The problem: status is available from dashboards, stand-ups, and project docs. Using your highest-leverage time for read-outs is expensive. You learn very little you couldn’t have read yourself, and your report gets no meaningful help. Most employees won’t voluntarily steer the meeting away from this. Power dynamics and evaluation concerns make them **opt for safe, not useful**. This is consistent with findings on upward feedback and psychological safety (Edmondson 1999): people under-eport problems and over-report progress when stakes are ambiguous. So the 1:1 quietly rots. It’s on the calendar, but it’s not doing the job it could: removing blockers, accelerating learning, and aligning expectations before they calcify into performance issues. ## The three-question agenda that actually changes behavior You do not need a 20-item template. You need a sharp agenda that forces the right kind of conversation. Use this every week: 1. **What is in your way?** 2. **What are you learning?** 3. **What do you want me to know?** Each question has a job: **What is in your way?** Surfaces blockers, constraints, and slow decisions. Your role is to remove or reduce these, not to lecture on them. **What are you learning?** Shifts the focus from tasks completed to skills built. It exposes where they’re stretching vs. just executing, which is what actually compounds in a career. **What do you want me to know?** Gives them agency. They choose what matters: context from the team, concerns, ambitions, or feedback for you. It also flushes out “I wish you knew…” resentment before it hardens. The key is to protect these three from being drowned by status. You can ask for a quick headline on projects if needed, but once you’ve heard the headline, move to blockers and learning. > A good one-on-one is not a weekly therapy session and not a mini stand-up. It is a small, predictable decision engine: surface the real constraints, decide what to do about them, then write down who is doing what by when. Everything else is optional. The three questions are just a way to force that engine to run every single week. ## Choose your starting level: how strong are your current 1:1s? Before you overhaul anything, place yourself roughly: **Level 0: Calendar decoration.** You often cancel when busy, or skip weeks. When they do happen, you wander through updates and leave with no clear actions. **Level 1: Friendly status.** Meetings happen most weeks. You get project updates, maybe some light venting. You rarely discuss blockers in a way that leads to concrete changes. **Level 2: Issue-focused.** You sometimes dig into obstacles or decisions, but only when they’re already on fire. Feedback tends to be reactive, not preemptive. **Level 3: Working session.** You routinely leave with 1-3 actions for each of you. You catch issues early, adjust scope, and talk about skill growth. Notes from past 1:1s show a trail of decisions. If you’re at Level 0-1, start by **making the slot reliable** and introducing the three questions lightly. If you’re at Level 2-3, refine structure and follow-up so you’re not relying on memory or personality to carry it. ## Your first attempt: a 25-minute three-question one-on-one Run one experiment before you redesign everything. Take your next 1:1 and do this, once. **The day before (2 minutes):** send a short note: “Tomorrow I’d like to try a tighter 1:1 format so it’s more useful for you. Three questions: 1) What’s in your way? 2) What are you learning? 3) What do you want me to know? Bring a few bullets for each; I’ll do the same.” **In the meeting (25 minutes):** 1. **Minute 0-3: Reset purpose.** “I want these 1:1s to be for removing blockers, helping you grow, and making sure I’m not missing anything important. We’ll use the three questions today and see how it feels.” 2. **Minute 3-12: What is in your way?** Ask, then shut up. If they start describing tasks, redirect: “Of that list, what’s actually slowing you down or frustrating you?” Your output should be 1-3 specific obstacles you can act on this week. 3. **Minute 12-18: What are you learning?** If they struggle, narrow it: “In the last 2 weeks, what’s one thing you can do now that you couldn’t six months ago?” Or: “What did you learn from that last incident / launch / project?” Capture where you can give them more practice or support. 4. **Minute 18-23: What do you want me to know?** Ask it directly, then tolerate a pause. Accept whatever they bring: team dynamics, concerns, goals, or feedback. Clarify what, if anything, you will do with that information. 5. **Minute 23-25: Recap and next steps.** Say: “Here’s what I’m taking away…” and list 2-4 concrete commitments (some for you, some for them). Confirm timelines and expectations. Right after the meeting, block 5 minutes to write a short follow-up note (we’ll cover format later). That note is the real artifact of the 1:1; the meeting is just the input. This is your **first attempt**, not your permanent structure. The goal is not perfection. The goal is to generate enough signal to know what to adjust. ## Reading the signals: was that 1:1 effective? Look at behavior, not vibes. After your first attempt, check for a few strong and weak signals. **Strong signals:** - They named at least one concrete blocker, and you agreed on a next step or experiment. - You heard at least one learning or stretch area, not just “I’m learning a lot.” - They brought at least one topic for “what do you want me to know?” without heavy prompting. - You both left clear on 1-3 actions and owners. **Weak signals:** - You spent most of the time reviewing tickets or walking through a doc. - Their answers stayed vague: “It’s fine,” “Nothing really,” “Just the usual.” - You ended with “Cool, thanks” instead of articulated next steps. - You didn’t send a follow-up note, so the conversation evaporated. Over 3-4 weeks, effective 1:1s show up in your calendar and inbox: issues surface earlier, fewer “urgent” pings, and your report starts using the 1:1 to negotiate trade-offs or ask for resources. If nothing about their behavior changes, your 1:1 is not yet doing its job. ## Adjust and retry: tightening your second round Assume the first run was messy. That’s fine. What matters is **what you change**. If blockers didn’t surface, you probably accepted status as an answer. Next time, when you hear pure progress, ask: “What, if anything, is slowing this down or making it harder than it should be?” Stay on that question until you have one thing you could plausibly influence. If they said they were “not really learning much,” that’s data. It might mean work is too easy, or they don’t recognize learning. Link it to specific tasks: “When you handled X, what was new or uncomfortable about it?” Over time you’re training them to recognize and name skill growth. If “what do you want me to know?” yields nothing, lower the bar. Offer examples: “This can be anything from ‘I’m worried about Y project’ to ‘You’re missing context about Z’ to ‘Here’s how you’re showing up to the team.’” Then sit with the silence for a few seconds longer than is comfortable. For your **second attempt**, keep the same three questions but adjust: - Shorten or lengthen the slot based on last time’s pace. 25-45 minutes works for most. - Move any recurring status talk to an async update or a team stand-up. - Improve your follow-up note so you can reference it next week without rereading everything. You’re not looking for a perfect script. You’re building a **repeatable feedback loop**. ## Making it safe enough to surface real issues You can’t force honesty, but you can make it cheaper to tell you the truth than to hide it. Psychological safety, in practice, is about how you respond when people share bad news or uncertainty (Edmondson 1999). If the price of raising a blocker is a lecture, they’ll stop paying it. Concrete moves: - When they share a blocker, first response: “Thanks for flagging that.” Only then move to problem-solving. - If you’re part of the problem, say it plainly: “That delay was on me. Here’s what I’ll change.” - Share your constraints: “Here’s the trade-off I’m making between your project and X. If you disagree, say so.” Another lever is predictability. If you regularly cancel 1:1s or repurpose them for your emergencies, they learn the slot is not for them. You don’t need to be warm or therapeutic. You do need to be consistent, specific, and non-punitive when someone brings you something ugly. Over time, the three questions act as a script that legitimizes tough topics. “What is in your way?” is permission. Your behavior decides whether they’ll use it. ## Follow-up notes that create a real feedback loop Most 1:1s fail in the last five minutes. Good intentions are expressed, then disappear into memory. A short, structured follow-up note is cheap insurance. It also creates a light-weight decision journal you can reference in performance discussions, promotion packets, and your own planning. Right after each 1:1, send something like this (email, doc, or DM is fine): --- **Subject:** 1:1 recap: [Date] **1) What is in your way** - [Blocker] → [Next step] (Owner: [You/Them], by [Date]) **2) What are you learning** - [Skill / insight] → [Next opportunity to apply or stretch] **3) What do you want me to know** - [Key point] → [Any action or just “Noted”] **Agreed actions** - [Name] will [do X] by [Date]. - [Name] will [do Y] by [Date]. --- Aim for 3-7 bullets total. If it feels long, you’re taking notes on the conversation, not on the decisions. Trim until only the commitments and key learnings remain. Next week, open the note for the last 2 minutes: “Here’s what we said we’d do. What happened?” That’s where accountability lives. ## When to skip a one-on-one, and when you never should Skipping occasionally isn’t a crime. It’s the pattern that matters. It’s reasonable to skip when **both** conditions are true: a) there’s a time-bound, external constraint (e.g., you’re traveling across time zones, they’re on leave), and b) you propose an alternative touchpoint (async update, short check-in at another time) **before** canceling. Do **not** skip in these situations: - You’re behind on your own work and need “focus time.” That tells them their development is optional. - There is active conflict, underperformance, or a critical project. That’s when private, structured conversation is most needed. - You want to avoid an awkward topic. That’s how small issues grow teeth. When you must cancel, treat it like rescheduling a customer meeting: propose 2-3 alternative slots and keep the same duration. The signal you send with your calendar is louder than anything you say about “how much I value these conversations.” ## Antipatterns: cancel-when-busy, surprise feedback, agenda hijack A few patterns show up repeatedly. Name them explicitly so you can avoid them. **The cancel-when-busy.** Behavior: whenever work spikes, 1:1s are the first to go. Impact: your report learns their growth time is the lowest priority. They stop preparing or bringing hard topics. Fix: set a personal rule: “I cancel 1:1s only for emergencies I’d also cancel external meetings for.” When you do cancel, reschedule in the same week. **The surprise performance feedback.** Behavior: you avoid giving hard feedback until it’s intolerable, then drop it into a 1:1 as a “by the way.” Impact: they feel blindsided, and the 1:1 becomes something to brace for, not use. Fix: treat performance feedback as **expected content**, not a surprise twist. Give small, specific feedback early, tied to concrete events. Flag it as such: “I want to give you some performance feedback on that incident.” No monologues out of nowhere. **The agenda hijack.** Behavior: you arrive with your own urgent topics and dominate the time; their list never gets touched. Impact: they learn not to bother preparing. The 1:1 becomes another meeting that happens to be 1:1-shaped. Fix: time-box yourself. “I’ve got 10 minutes of topics, then we switch to your list and the three questions.” If something truly urgent eats the whole slot, explicitly move **their** topics to the top of the next 1:1. Effective 1:1s depend less on clever questions than on avoiding these predictable failures. ## FAQ: practical decisions about time, agenda, and feedback #### ⏱️ How long should a 1:1 actually be? For most knowledge work, 30 minutes weekly is enough if you’re disciplined about status. If your report has a broad scope or you’re in a high-change environment (reorg, major product shift), 45 minutes may be justified for a few months. Shorter than 25 minutes tends to force you into status-only mode; longer than 60 minutes usually degenerates into rambling unless there’s a specific deep-dive topic. Err on the side of shorter and more frequent rather than long and rare. You can always add a separate ad-hoc block if a specific issue needs it. #### Should I have an agenda or let them lead? Use a **fixed skeleton** and let them add meat. The three questions are your skeleton: they ensure blockers, learning, and upward information flow happen every time. Ask them to bring topics under those headings, but don’t outsource agenda design completely—power dynamics make many reports default to “nothing” if they think they’re wasting your time. Over time, as they see you consistently make their topics actionable, they’ll start leading more of the agenda naturally. #### What if my report has nothing to say? Assume this is about safety, habit, or clarity, not laziness. First, lower the scope: “In the last week, what’s one thing that felt harder than it should?” or “What’s one thing that went better than expected?” Then wait; don’t rescue the silence with your own monologue. If this is a pattern, share the goal explicitly: “If you come with nothing, I’ll still ask these three questions because my job is to remove obstacles and help you grow. Over time, I expect you to bring 1-2 examples each.” You’re training a new behavior; it often takes 3-5 cycles. #### ⚠️ When is it OK to give performance feedback in a 1:1? Performance feedback **belongs** in 1:1s, but not as a jump-scare. Use the slot for timely, specific, behavior-level feedback tied to actual events, positive or negative. Signal it clearly: “I want to give you feedback on how the incident call went yesterday.” Describe what you observed, the impact, and what “good” would look like next time. Avoid saving everything for formal reviews—that’s where people feel ambushed. And if the topic is extremely serious (e.g., potential termination), plan the conversation more deliberately and consider involving HR, but still avoid springing it on them with zero context. #### How often should I change the structure of my 1:1s? Not often. Stability builds trust. Keep the three-question structure for at least 6-8 weeks before you consider tweaks. You can flex **within** the structure based on current needs: some weeks spend 80% on blockers, other weeks go deep on learning after a big project. If you change the format, explain why: “For the next month, I want to add 10 minutes each time to focus on your promotion case.” Surprises in form create unnecessary friction; save the surprise for the content, not the container. ### Cheatsheet: field guide for effective one-on-ones #### ⚡ The three-question agenda Use this as your default weekly structure: (1) What is in your way? (10-20 minutes) → aim for 1-3 concrete blockers with owners and dates. (2) What are you learning? (5-10 minutes) → capture at least one skill or insight and where it will be applied next. (3) What do you want me to know? (5-10 minutes) → 1-3 points, each tagged as “info only” or “needs action.” Keep total time between 25-45 minutes. #### Pre-meeting prep in under 5 minutes T-24 hours: send a 2-3 sentence reminder with the three questions and ask for 1-3 bullets under each. T-5 minutes: skim last week’s 1:1 note, highlight any actions due today. Jot 2-3 prompts you’ll use if they stall (one for blockers, one for learning, one for “what do you want me to know”). Arrive with your own example under each question so you can model the level of specificity you expect. #### Follow-up note format Right after the 1:1, send a recap with four short sections: (1) What is in your way → bullets of blockers + next step + owner + date. (2) What are you learning → bullets of skills + next opportunity. (3) What do you want me to know → bullets tagged as [Action] or [Noted]. (4) Agreed actions → 2-6 bullets, each in the format: “Name will do X by DATE.” Target 3-7 total bullets; if you have more, consolidate or drop non-actions. #### ⛔ Antipatterns to avoid Watch for three patterns: (1) Cancel-when-busy → more than 1 cancellation per month per report is a warning sign; if you must cancel, reschedule in the same week. (2) Surprise performance feedback → never drop major, first-time criticism in the last 5 minutes; instead, address behaviors within 1-7 days of the event with 10-15 minutes of dedicated time. (3) Agenda hijack → if you talk for >60% of the time three weeks in a row, reset: cap yourself at 10 minutes, then switch to their topics under the three questions. ### FAQ: using this in real one-on-ones #### ⏱️ How long should a 1:1 actually be? For most teams, 30 minutes per week per report is the right starting point. It’s long enough to get past surface updates and into at least one real blocker or learning, but short enough that you and your report will protect it. In high-change or high-scope roles, you can extend to 45 minutes for a quarter and then reassess. If you’re consistently running out of time, look first at how much of the meeting is eaten by status updates before you simply lengthen the slot. #### Should I have an agenda or let them lead? You should own the default structure, or the 1:1 will slide into status-by-habit. The three-question agenda gives you that skeleton without being oppressive. Within that frame, explicitly invite them to add topics, but ask them to map each to one of the three questions so the meeting stays coherent. Over time, as they see their topics being taken seriously and turned into actions, they will naturally bring more and start effectively leading portions of the conversation. #### What if my report has nothing to say? Treat that as a design problem, not a personality flaw. Narrow the time window (“in the last week”) and the domain (“about project X” or “about collaboration with Y”), and ask for one example instead of a list. If they still say “nothing,” share one of your own answers to the question to model the level of specificity you expect. Finally, make the expectation explicit: tell them you expect them to arrive with at least one blocker and one learning each week, and remind them the day before until it becomes habit. #### ⚠️ When is it OK to give performance feedback in a 1:1? It’s usually better than any other forum, as long as it’s timely and clearly labeled. You want small, frequent adjustments, not rare, explosive dumps of frustration. When something happens(good or bad)aim to discuss it in the next 1:1 while the details are fresh, starting with a clear frame like “I want to give you feedback on…”. Avoid using the final two minutes of a 1:1 to unload big, first-time criticism; that leaves no time for clarification or repair. If the feedback is materially career-impacting, plan that conversation deliberately and avoid making it feel like an ambush. #### How often should I change the structure of my 1:1s? Structure works because it’s predictable; if you change it every few weeks, people will stop trusting it. Commit to the three-question format for at least 6-8 cycles before tweaking. Use variation inside the structure(some weeks heavier on blockers, others on learning)based on what’s happening in their work. When you do adjust the format, explain the rationale and what is staying the same so they don’t waste cognitive effort recalibrating to your habits instead of focusing on the content. ### Bring the three questions into your next Tuesday You don’t need a new tool or a leadership offsite to upgrade your one-on-ones. You need a clear purpose, a minimal agenda, and the discipline to run the same play every week. Use the three questions as your spine: **what is in your way, what are you learning, what do you want me to know**. Protect the slot from status, avoid the predictable antipatterns, and write short follow-up notes that capture decisions. Over a quarter, the difference compounds. Issues surface before they explode. Skill growth becomes explicit instead of accidental. And your 1:1s become what they were supposed to be: the place where small, correct decisions about someone’s work and development get made on purpose—not a recurring meeting that everyone secretly hopes will get canceled. ### Next steps: turn this into a real experiment - Pick one report or peer and commit to running the three-question agenda with them for the next 4 weeks, without changing the structure. - For your next 1:1, send the 2-minute pre-note with the three questions and ask for bullets in advance, then run the 25-minute script from this article. - Create a simple 1:1 note template (in a doc or note app) with headings for the three questions plus “Agreed actions,” and use it live or immediately after each meeting. - After 3-4 cycles, review your notes for that person and ask yourself: Are blockers surfacing earlier? Are we talking about learning at all? Are actions actually happening? Adjust based on what you see, not how the meetings feel.