Oh My Learning

Running one-on-ones and building trust loops

managers-path/04 senior drafted · 7 min read

The Manager's Path (Camille Fournier), Chapter 4 - Managing People

Prerequisites managers-path/03

Running one-on-ones and building trust loops#

TL;DR#

The 1:1 is the manager's core recurring tool: a protected, regular slot that belongs to the report, not the manager, used to surface problems early, build trust, and understand what actually motivates each person - skipping or degrading it into a status update is the single most common way new managers lose touch with their team.

The idea#

Most of what a manager needs to know - who's about to quit, who's quietly stuck, who's bored and flight-risk, who has a personal situation affecting their work - never shows up in a status report, a stand-up, or a Slack channel, because people don't volunteer that information in group or public settings. The 1:1 exists to create a private, low-stakes, recurring space where that information can surface before it becomes a crisis (a surprise resignation, a missed deadline nobody flagged, a conflict that's been simmering for months).

Fournier's central claim is that the 1:1 belongs to the report, not the manager - its agenda should be driven primarily by what the report wants to talk about, not a checklist of project status the manager wants to extract. A manager who runs 1:1s as project status meetings ("where are we on X, where are we on Y") is wasting the one venue specifically designed for the things that don't fit in a status meeting, and reports quickly learn that the 1:1 isn't a safe place to raise a real concern, so they stop raising them there - and stop raising them anywhere.

How it works#

Protect the cadence and the report's agenda#

1:1s should happen regularly (weekly is the common default) and should almost never be cancelled outright - if a manager needs to reschedule, move it rather than skip it, because a pattern of cancelled 1:1s signals to the report that they're not a priority, exactly when trust is being built. A simple, effective opening: "What do you want to talk about today?" rather than the manager leading with their own list. If the report has nothing prepared, the manager can have a light backup list (career goals, current blockers, recent feedback) but should default to following the report's lead.

Use 1:1s to build a trust loop over time#

Trust compounds through small, repeated demonstrations that the manager listens and follows through - a report mentions a blocker, the manager actually removes it before the next 1:1 and reports back that they did; a report shares a concern about a teammate, the manager handles it discreetly and the report sees the situation improve. Concrete example: an engineer mentions offhand in a 1:1 that they're bored doing repetitive maintenance work. A manager who does nothing with that information erodes trust every week the situation continues unaddressed. A manager who, within a few weeks, finds them a stretch project on the new subsystem and explicitly connects it back to that conversation ("I remembered you said you wanted more challenge, so I got you onto X") builds trust rapidly, because the report now believes the 1:1 actually changes things.

Surface the "iceberg" - go beneath status#

Fournier describes the 1:1 as where you find the part of the iceberg that's underwater: career anxieties, frustration with a teammate, doubts about the project's direction, personal stress bleeding into work. None of this comes up unprompted in week one. A useful technique is asking open, non-leading questions repeatedly over time rather than once: "How are you feeling about the team lately?" asked genuinely and consistently, eventually gets an honest answer, even if the first few times the answer is a guarded "fine."

Take notes and follow through visibly#

Keeping a private running log per report - what they said, what you committed to, what came up last time - lets the manager start each 1:1 with continuity ("Last time you mentioned X, how did that go?") instead of the report having to re-explain context every session. This single habit does more for trust than almost any other 1:1 technique, because it proves the manager was actually listening, not just present.

Pros#

  • Surfaces problems (flight risk, burnout, interpersonal conflict, blockers) early enough to act on them, instead of learning about them at exit-interview time.
  • Builds the trust that makes harder conversations - performance feedback (managers-path/05), difficult team changes (managers-path/06) - land better, because the relationship has a track record before it's tested.
  • Gives the manager a direct read on individual motivation and career goals, which is otherwise invisible in group settings and easy to get wrong by assumption.

Cons#

  • Real time cost that scales linearly with team size - a manager with 8 direct reports doing weekly 30-minute 1:1s spends 4 hours a week just on this, before any other management work.
  • Easy to let 1:1s degrade into status updates under time pressure, silently losing their actual value while still "technically happening."
  • Requires genuine follow-through - a manager who takes notes but never acts on them trains reports to stop bringing up real issues, which is worse than never having tried.

Alternatives#

  • Skip-level 1:1s - a manager's manager holds occasional 1:1s directly with individual contributors two levels down, surfacing information that might not reach the direct manager, or might be filtered on the way up; complements rather than replaces direct 1:1s.
  • Team-wide retros / open forums - surface group-level issues (process friction, cross-team blockers) more efficiently than 1:1s, but cannot surface the individual, personal, or interpersonal issues 1:1s are built for; the two are complementary, not substitutes.
  • Async check-ins (written status updates) - lower time cost and useful for pure status tracking, but they cannot replace the real-time, judgment-reading, trust-building function of a live conversation.

When to use it#

Every direct report, every week (or at minimum bi-weekly for very senior, highly autonomous reports), without exception - this is not a tool to deploy only when there's a problem; its value comes from being a steady, predictable presence before problems arise.

When NOT to use it#

Don't run 1:1s as project status meetings - that function belongs in stand-ups, planning meetings, or written updates, and using the 1:1 for it burns the one venue built for what those meetings can't surface. Also don't treat a report's silence in 1:1s as "nothing to discuss" and start skipping or shortening them - silence, especially early in a relationship, usually means trust hasn't been built yet, not that there's nothing there.

Key takeaways / mental model#

The 1:1 is the report's meeting, not the manager's - protect the cadence, follow the report's agenda, and treat every small follow-through as a trust deposit; the goal is that when something serious comes up, this is already the place it feels safe to say it.

Self-check questions#

  1. A report has said "everything's fine" in your last four 1:1s, but you suspect they're actually unhappy. What would you change about how you're running the 1:1, based on this lesson?
  2. Why does Fournier insist the 1:1 agenda should belong to the report rather than the manager, even though the manager usually has genuine status questions?
  3. Describe the "trust loop" mechanic in your own words - what specific manager behavior builds it, and what breaks it?
  4. Your team is growing from 5 to 10 direct reports. What are your options for preserving 1:1 quality under that time pressure, and what are the trade-offs of each?

References#

  • The Manager's Path (Camille Fournier), Chapter 4: "Managing People".