1:1 meeting: definition, structure and use in OKR steering

A 1:1 meeting (also written one-on-one or 1-on-1) is a regular, two-person conversation between a manager and one of their direct reports. It is used to track progress, surface blockers, adjust priorities and support professional development. Within an OKR program, it is one of the primary moments for updating and steering at the individual level.

Definition

A 1:1 meeting (also written one-on-one or 1-on-1) is a recurring two-person conversation between a manager and a direct report. It typically covers workload and priorities, surfaces or unblocks open issues, adjusts alignment with team goals, and supports the person's professional development over time.

The format was formalized by Andy Grove at Intel in the 1980s. In High Output Management, he described the 1:1 as a high-leverage management mechanism: a relatively small time investment that pays back in productivity over the following weeks. The practice has since spread broadly in organizations adopting OKRs, where it plays a structuring role in operational follow-up.

Role of the 1:1 in an OKR program

In an organization running OKRs, the 1:1 is one of the main moments where Key Results and Initiatives get discussed at the individual level. It is typically used to:

  • Compare the field read of the direct report with that of the manager.
  • Update the confidence score in a setting that lets nuanced takes surface.
  • Surface dependencies and blockers slowing down an Initiative.
  • Adjust priorities for the week ahead.
  • Raise weak signals on alignment or workload that don't come out in group rituals.

Studies on distributed team management converge on the same point: the regularity of 1:1s is one of the more stable indicators of a team's ability to deliver on its operational commitments. It's not the only factor, but it is among the better-correlated levers with execution quality.

Cadence and duration by context

Context Common cadence Typical duration
Direct manager, permanent report Weekly 30 to 45 minutes
Distributed or remote team Weekly 45 minutes
Skip-level (manager's manager) Monthly or quarterly 30 to 60 minutes
Onboarding (first 3 months) Weekly, sometimes twice weekly 45 to 60 minutes
Cross-functional mentoring Biweekly or monthly 30 to 45 minutes

In organizations mature on the topic, the weekly 1:1 between a manager and their direct reports is treated as a stable cadence: typically rescheduled rather than canceled in case of unavailability. A biweekly cadence is also common, particularly with highly autonomous teams or in steady-state cycles.

Structure of a 1:1: five common questions

There is no canonical format for a 1:1. Observed practices converge on a few recurring questions, which form an adaptable baseline depending on the person's role, function and seniority. A frequently used template covers five questions:

  1. How are you? Opens the conversation. Picks up on overall state, energy, and context elements that may affect the work.
  2. What's your workload like? Helps catch silent overload, as well as underload that can translate into disengagement.
  3. What have you moved on since the last 1:1? Gives the direct report a chance to surface their work and the manager a read on where execution actually stands.
  4. What are your blockers? Identifies what's slowing things down, so the manager can act directly or escalate.
  5. What are your priorities until the next 1:1? Commits the week ahead and lets the alignment with team goals be checked.

These questions typically fit in 20 to 30 minutes. Depending on context, they can be complemented with career topics, two-way feedback, or cross-team threads. In mature practice, the direct report sets the agenda; the manager listens, asks questions, and arbitrates rather than interrogates.

Trade-offs and limits

The 1:1 does not mechanically produce good outcomes. Several limits and trade-offs are documented in management literature and observed in practice:

  • Management overload effect. A manager supervising eight people or more struggles to hold eight quality 1:1s every week. Past a certain threshold, either cadence slips, duration shrinks, or listening quality drops.
  • Risk of overlap with group rituals. If 1:1 topics largely duplicate what gets covered in the weekly check-in, marginal value drops. Making the role of each ritual explicit helps.
  • Confusion with performance review. When the 1:1 sits too close to a performance evaluation mechanism, direct reports tend to soften their feedback, which weakens the signal value of the ritual.
  • Heavy dependence on management quality. The format does not compensate for weak managerial skills. A poorly run 1:1, repeated, can create more friction than no 1:1 at all.
  • Scale effects in large organizations. A weekly cadence is harder to sustain in organizations of several thousand people, where management layers multiply and per-manager meeting load becomes a topic in itself.

Frequently observed anti-patterns

Anti-pattern Observable signal Corrective practice
1:1 repeatedly skipped or rescheduled More than 2 skips per quarter Treat the cadence as a stable commitment, reschedule rather than cancel.
1:1 turned into a downward reporting session The manager asks most of the questions, the direct report responds briefly Let the direct report open and set the agenda.
No shared agenda Systematic improvisation at the start of the meeting Maintain a shared document with the items to cover, updated between sessions.
OKRs never come up The 1:1 only covers operational updates Carve out explicit time for the active OKRs, even briefly.
No notes or follow-up The same topics resurface month after month Capture commitments and revisit them in the next 1:1.
Systematically shortened 1:1s 30 minutes scheduled, 10 minutes actual Adjust the cadence (biweekly) rather than cut the duration.

Observed effects on OKR execution

Published experience and research on distributed team performance converge on a few observable effects of a consistent 1:1 practice, without these constituting mechanical laws:

  • Earlier blocker surfacing. A blocker raised in a weekly 1:1 is typically addressed faster than one waiting for a group review or a one-off check-in.
  • More stable sense of purpose. Recurring conversations help reconnect day-to-day work to the Objective it contributes to.
  • A space for doubts. The two-person format is generally better suited than a group ritual for expressing doubts on a KR's trajectory or the relevance of an Initiative.

These effects accumulate over time and depend heavily on how well the ritual is held.


How Serendly tools the 1:1

This section describes Serendly's specific contribution and can be skipped for a purely conceptual read.

In organizations using Serendly, the 1:1 is embedded in the OKR program rather than running alongside it. Three core capabilities:

  • Key Result updates during the 1:1. Progress reported by the direct report flows directly into the KR view, with no double entry.
  • Initiative follow-up in the same ritual. Associated Initiatives are reviewed at the same moment: progress, blockers, decisions to drop or redirect.
  • Task creation in-session. The manager can assign tasks to themselves or to others to address a blocker, with a tracked owner and deadline.

Serendly also includes an assistant that can, on the direct report's request, pre-fill a 1:1 template from the elements already captured in the platform: task progress, KR updates, prior conversations, surfaced blockers. The direct report then completes or adjusts the template before the meeting. User reports indicate a saving of roughly 20 minutes of weekly preparation per direct report, with no change to the 1:1 duration itself.

Talk to the Serendly team


Impact on the organization

The weekly 1:1 is among the rituals most consistently correlated with a team's ability to deliver on its operational commitments. Its value depends heavily on cadence consistency, management quality, and how it fits with the other OKR rituals in the team.


Key takeways for 1:1 Meeting

  1. Regular two-person conversation between a manager and a direct report, typically weekly.
  2. Used to track progress, surface blockers, adjust priorities and support development.
  3. Five common questions: how are you, workload, what you've moved on, blockers, priorities ahead.
  4. Adaptable format based on role, seniority, cadence and team context.
  5. Limited value when management quality is weak, or when the ritual drifts into a performance evaluation.
  6. In an OKR program, one of the main moments for updating Key Results and Initiatives at the individual level.

Curated related readings

Synonyms for 1:1 Meeting : One-on-one; 1-on-1; 1:1; Manager-report meeting; Individual check-in;

Share this definition