blog / stop-1-1-status-meetings

    7 Ways to Stop Turning Your 1:1s Into Status Meetings

    7 practical ways to stop status-update 1:1s — async updates, report-owned agendas, and questions that make engineering one-on-ones useful again.

    Alex Chen
    • 1:1s
    • meetings
    • productivity

    If your weekly 1:1 is a ticket walkthrough, you’re burning the highest-leverage meeting on your calendar. Status is cheap async. Trust, coaching, and early warning signs are not. Here are 7 ways to kill status-mode for good.

    Once status is async, fill the time with better 1:1 questions that build trust and surface real blockers.

    1. Move status to async — on purpose

    Pick a channel: Slack standup, Linear/Jira, or a Friday written update. Tell the team: “If it fits in a ticket comment, it doesn’t belong in our 1:1.” Then stop asking “What did you work on?”

    2. Hand them the agenda

    Shared doc. They add bullets the day before. You add yours second. Open with: “What’s top of mind?” If the doc is empty, wait — don’t fill the silence with status questions.

    3. Use a fixed shape so status can’t expand to fill the hour

    • 5 min — Energy check-in (not ticket list)
    • 20–25 min — Their agenda
    • 5–10 min — Your topics (feedback, context)
    • 5 min — Commitments

    4. Replace status prompts with coaching prompts

    Swap “What’s the status on X?” for “What’s getting in your way?” and “How can I help?” Keep a short question bank and rotate — don’t interrogate.

    5. Park project deep-dives for a different meeting

    When a topic turns into a 20-minute design review, schedule a working session. Protect the 1:1 for the person, not the project.

    6. Say the reset out loud — once

    Script: “I’ve been using our 1:1s for status, which wastes your time. Going forward this is your meeting — career, friction, ideas. Status stays async. Sound good?” Then keep the promise.

    7. Review last week’s commitments every time

    Open the shared doc, check follow-ups, then take new topics. That one habit turns “good chat” into compounding trust — and makes status feel pointless by comparison.

    Try this for three weeks. If the meeting still feels like status, you haven’t killed the status questions yet — delete them from your mental script and use the 25-question bank instead.

    Frequently asked questions

    Why are status updates bad in engineering 1:1s?
    Status belongs in standups, tickets, and async updates. Using 1:1 time for it crowds out coaching, career, and the issues people won’t raise in public.
    What should replace status in a 1:1?
    Your report’s agenda first: blockers, growth, feedback, energy, and decisions that need a private conversation.
    How do I tell my team we’re changing 1:1s?
    Say it once, clearly: status moves async; 1:1s are their time. Share a simple agenda template and stick to it for three weeks.

    Related posts

    More in 1:1s & coaching conversations

    ← All posts