By leaders.fyi Team • April 10, 2026 • 8 min read

The One-on-One Meeting Framework That Actually Works

One-on-ones (1:1s) are one of the highest-leverage tools in engineering management—yet they’re also one of the most commonly wasted. The typical failure mode is familiar: a recurring calendar invite, a vague “so… how’s it going?” and a rushed status update that could’ve been a Slack message.

A great 1:1 is not a meeting. It’s a system: a repeatable framework that creates trust, surfaces risks early, accelerates growth, and improves execution.

Below is a practical one-on-one meeting framework designed for tech managers and leaders who want consistent results.

---

What 1:1s Are For (And What They’re Not)

Before you change your agenda, align on purpose.

1:1s are for:

Trust and psychological safety (so people tell you the truth)

Clarity on priorities, tradeoffs, and decisions

Coaching and growth (skills, behaviors, career goals)

Early detection of delivery risk, burnout, conflict, and misalignment

Feedback in both directions

1:1s are not for:

Project status (that’s what standups, dashboards, and async updates are for)

Performance surprises (feedback should be continuous)

Manager monologues (you’re not there to “download information”)

A simple rule: If the meeting ends and you learned nothing new, the system is broken.

---

The Framework: 10/10/30 + Notes + Follow-Up

This approach works because it balances relationship, execution, and development—without turning the 1:1 into a therapy session or a status meeting.

The structure (for a 50-minute 1:1)

10 minutes: Human + temperature check

10 minutes: Alignment + obstacles

30 minutes: Growth + deeper topics

Then add two system components:

Shared notes (so context isn’t lost)

Follow-up loop (so commitments don’t evaporate)

If you only have 30 minutes, compress to 5/5/20.

---

Part 1 (10 min): Human + Temperature Check

This is where you build the safety required for real conversations. Don’t skip it—even with senior engineers.

Use these prompts (rotate, don’t rapid-fire)

“What’s been energizing you lately?”

“What’s been draining you?”

“On a scale of 1–10, how are you feeling about work this week?” (Then ask: “What makes it that number?”)

“What should I know that I might not be seeing?”

What you’re listening for

Stress signals (fatigue, cynicism, avoidance)

Unspoken conflict (hesitation, vague answers, tension)

Motivation shifts (boredom, loss of challenge, lack of recognition)

Real-world scenario:
An engineer says, “I’m fine—just busy.” You respond, “Busy can mean a lot of things. What’s taking most of your energy right now?” This gently turns a non-answer into something actionable.

---

Part 2 (10 min): Alignment + Obstacles (Not Status)

The goal here is to ensure your report is working on the right things and has what they need to succeed.

Ask for clarity, not updates

Instead of: “How’s Project X going?”

Try:

“What’s the most important thing for you to accomplish before our next 1:1?”

“Where are you stuck?”

“What decision do you need from me?”

“What’s one risk you’re worried about that others may be missing?”

“If we keep going as-is, what’s likely to slip?”

A quick alignment tool: the 3P Check

Use this when priorities feel fuzzy.

Purpose: Why are we doing this?

Priority: What matters most this week?

Plan: What’s the next concrete step?

If any of those are unclear, delivery slows down and frustration rises.

---

Part 3 (30 min): Growth + Deeper Topics

This is the part most managers neglect, even though it’s the biggest long-term multiplier.

Pick one “development theme” per quarter

Examples:

Improving design docs and technical communication

Becoming a stronger project lead

Influencing cross-functional stakeholders

Leveling up in system design

Mentoring junior engineers

Then use 1:1s to make progress in small steps.

Use the GROW coaching model (simple, effective)

G (Goal): “What outcome do you want?”

R (Reality): “What’s happening now?”

O (Options): “What could you try?”

W (Will): “What will you do before next time?”

Example:
An engineer wants to “have more impact.”

Goal: Lead a cross-team initiative this half.

Reality: They avoid stakeholder conversations.

Options: Co-lead a meeting, draft a proposal, shadow you.

Will: They will run next week’s alignment meeting with your support.

Add a lightweight feedback loop (SBI)

Use SBI (Situation–Behavior–Impact) for specific, non-personal feedback.

Situation: “In yesterday’s incident review…”

Behavior: “…you interrupted Alex twice while they explained the timeline.”

Impact: “…the team stopped contributing, and we missed key details.”

Then ask:

“What was going on for you in that moment?”

“What would you do differently next time?”

Also ask for feedback for you:

“What’s one thing I should do more of as your manager?”

“What’s one thing I should stop or change?”

---

The Operating System: Shared Notes That Drive Action

A framework fails if it relies on memory.

Use a shared doc (or shared 1:1 note in your tool of choice) with a consistent template.

Copy/paste 1:1 template

1) Wins since last time

2) Current focus (next 1–2 weeks)

3) Blockers / risks / decisions needed

4) Growth & career

Theme this quarter:

Progress:

Support needed:

5) Feedback (both directions)

6) Action items (owner + due date)

7) Parking lot (topics to revisit)

Rules that make notes effective

The report owns the agenda (they add items first)

You add items too, but avoid dominating

Every action item has an owner and date

End by reading back commitments: “What are we each doing next?”

---

The Follow-Up Loop: How to Make 1:1s Matter

Most 1:1s feel unproductive because they create insight—but not movement.

Close the meeting with two questions

“What are your top 1–2 priorities before next time?”

“What do you need from me, and by when?”

Then do one small thing within 24 hours

Examples:

Send an intro to unblock a dependency

Clarify a priority in writing

Share a resource or example doc

Publicly recognize a win

This builds credibility fast. People learn: “If I raise an issue in a 1:1, it gets handled.”

---

Common 1:1 Failure Modes (And Fixes)

1) The 1:1 becomes a status meeting

Fix: Require async status updates. In the 1:1, ask only about risks, decisions, and tradeoffs.

2) The engineer brings nothing

Fix: Use shared notes and tell them: “I’d like you to add at least 2 topics before we meet.” Offer a starter list of prompts.

3) You talk too much

Fix: Aim for an 80/20 listening ratio. Ask one question, then wait. Silence is a tool.

4) You avoid hard topics

Fix: Put the hard topic first and timebox it: “I want to spend 10 minutes on a difficult piece of feedback.”

5) The 1:1 gets canceled often

Fix: Treat it like a reliability practice. Canceling repeatedly signals “you’re not important.” Move it only for emergencies.

---

How to Adapt This Framework by Seniority

For junior engineers

Spend more time on coaching, unblocking, and confidence-building

Make expectations explicit: “What ‘good’ looks like”

Add structure: checklists, templates, concrete next steps

For senior engineers / tech leads

Focus on influence, prioritization, and leverage

Discuss org constraints and decision-making

Ask: “What’s the highest-leverage thing you could do this month?”

For staff/principal engineers

Explore strategy, cross-team dynamics, and systems health

Ask: “What should we stop doing?” and “Where is the org accumulating risk?”

Use 1:1s to surface weak signals early

---

A Simple Weekly Cadence That Keeps 1:1s Fresh

If you meet weekly, rotate emphasis:

Week 1: Growth + career deep dive

Week 2: Delivery risks + cross-team alignment

Week 3: Feedback (SBI) + relationship check

Week 4: Retrospective: “What should we do differently next month?”

This prevents the “same meeting every week” trap.

---

Your Next 1:1: A 5-Minute Setup That Changes Everything

Before your next one-on-one, do these three things:

Create a shared note using the template above.

Message your report: “Please add 2–3 topics you want to cover before we meet.”

Pick one coaching question from GROW and one feedback prompt from SBI.

One-on-ones work when they’re intentional. Use a repeatable framework, track decisions and commitments, and treat the meeting as your primary mechanism for trust and growth.

Done well, 1:1s don’t just make your team feel supported—they make your team faster, clearer, and more resilient.