One-on-One Template for Operations Managers: Weekly, Monthly & Quarterly Formats

Most operations managers run 1:1s the same way they run team meetings: with a status update agenda, a round-robin of project updates, and a close that feels like a check mark. The format is familiar. The outcomes are thin. Attrition happens quietly. Blockers stay buried. Development conversations never start. The direct report gets hired elsewhere by a manager who asks different questions.

Andy Grove dedicated more pages to one-on-one meetings than to any other management practice in High Output Management. His logic was straightforward: the 1:1 is the highest-leverage tool available to a manager. One hour of a well-run 1:1 can multiply a direct report's output for the entire week. One hour of a poorly-run 1:1 produces nothing except the illusion of management.

Operations managers face a specific challenge that makes 1:1s harder to run well. Unlike sales reps whose pipeline is visible in the CRM, or engineers whose commits are visible in version control, an ops manager's direct reports often work on processes, coordination, and firefighting that do not surface in any single dashboard. The work is real and important. It is also invisible to the manager unless the 1:1 is designed to surface it.

This guide provides three complete 1:1 templates for operations managers — weekly check-in, monthly development, and quarterly growth review — plus a 50-question bank organized by topic, the research on what makes 1:1s effective, and specific guidance for running 1:1s with distributed and remote ops teams.

Why 1:1s are the highest-leverage activity for ops managers

Grove's argument in High Output Management was that a manager's output is not their own work — it is the output of the people and teams they manage and influence. On that framing, the 1:1 is not a meeting. It is the primary mechanism by which a manager transfers information, context, coaching, and motivation to the individual who will do the work.

Grove estimated that a one-hour 1:1 between a manager and a direct report, done well, could improve that direct report's output by 10 to 20 percent for the week. Multiply that across five direct reports and the weekly return on two and a half hours of 1:1 time is significant. Done poorly, 1:1s produce nothing except the feeling of management activity.

Manager Tools, whose podcast and methodology is based on 20 years of research into what makes managers effective, found that managers who hold consistent weekly 1:1s score higher on every measure of team performance: direct report engagement, retention, and upward feedback. The correlation is strong enough that Manager Tools treats the weekly 1:1 as the single most important behavior change for a new or improving manager.

For operations managers specifically, the case is even stronger. Operations work is inherently cross-functional, process-dependent, and blocker-intensive. An ops direct report who cannot surface blockers in a safe, structured conversation will absorb friction until they leave. The 1:1 is the primary venue for surfacing that friction early enough to do something about it.

What makes ops 1:1s different from other functions

Sales 1:1s are anchored on pipeline. Engineering 1:1s are anchored on sprint progress and technical blockers. Marketing 1:1s are anchored on campaign performance and funnel metrics. Operations 1:1s do not have a single anchor because operations work spans all of those domains and none of them cleanly.

This creates three specific challenges for ops 1:1s.

The invisible work problem. An ops manager's direct report may spend the entire week doing critical work — resolving a vendor dispute, rebuilding a broken handoff process, coordinating a cross-functional launch — that does not appear in any system the manager can check. If the 1:1 does not have a structured slot for "what did you actually work on this week," the manager is flying blind.

The firefighting problem. Operations teams absorb disproportionate firefighting. When something breaks — in any function — it usually lands in ops. Direct reports who spend 40 percent of their week on firefighting rarely mention it in 1:1s because it feels like a complaint rather than a reportable fact. A well-designed ops 1:1 template creates a standing question for "what pulled you away from planned work this week" that makes firefighting visible without making it feel like a complaint.

The coordination tax problem. Ops work involves high cross-functional coordination. Direct reports often spend significant time unblocking other teams, attending meetings that do not directly advance their own work, and translating between functions. This coordination tax is rarely tracked and rarely surfaced. Over time it is a leading indicator of burnout and attrition. A 1:1 template that asks "what percentage of your week was unplanned coordination?" surfaces the pattern before it becomes a retention problem.

Template 1: Weekly check-in (30 minutes)

The weekly check-in is a working session, not a status briefing. Both parties fill in their sections of the shared document before the meeting. The direct report's section is filled first. The manager reviews it before the call and prepares follow-up questions. The conversation focuses on blockers, priorities, and coaching — not on status that can be read asynchronously.

The weekly format deliberately keeps the agenda short. Thirty minutes is enough for three priorities, two blockers, and one action list. If the conversation regularly runs over, either the blockers are systemic (and need a separate working session) or the format is being used as a status briefing (and needs to be redesigned).

Template 2: Monthly development conversation (45 minutes)

The monthly development conversation zooms out from the weekly operational cadence. Its purpose is not to check on projects. It is to assess how the direct report is growing, what is energizing them, what is draining them, and whether their work aligns with what they want to be good at. Grove called this the "teaching" function of management. Manager Tools calls it the "development" portion of the 1:1.

This conversation is harder than the weekly check-in because it requires the manager to ask questions they may not know the answers to, to stay in coaching mode rather than advice mode, and to hold space for answers that are uncomfortable. Most ops managers skip this conversation because it feels disconnected from the work. It is not. A direct report who does not feel seen or developed is a direct report who is updating their LinkedIn.

The most important section in the monthly template is the feedback exchange — both directions. Grove was explicit that feedback flows both ways in an effective 1:1. The manager's feedback to the direct report is expected. The direct report's feedback to the manager is rarer and more valuable. Building it into the template as a standing section signals that the manager wants to hear it, not just tolerate it.

Template 3: Quarterly growth review (60 minutes)

The quarterly growth review is the annual performance conversation divided into four smaller, less anxious conversations. Most performance management systems wait until the annual review to discuss career trajectory, compensation, and long-term development. By then, the feedback is stale, the surprises are bad, and the conversation happens under artificial time pressure.

A quarterly format runs four 60-minute sessions per year instead of one 90-minute session. Each conversation covers the same ground but is connected to the current quarter's context. The result is continuous performance visibility rather than a once-a-year event that neither party looks forward to.

Question bank for operations managers (50 questions organized by topic)

The templates above provide structure. The questions below provide depth. Use them to fill specific sections of the templates or to break through a conversation that has stalled. The questions are organized into six topic areas relevant to operations roles.

Priorities and focus

• What is the one thing you need to get done this week that everything else depends on?
• If you could only finish two things this week, which two would have the most impact?
• What is on your list that should probably come off?
• What are you working on right now that feels misaligned with what the team actually needs?
• Where are you spending time that you wish you were not spending time?
• What would you do differently with your calendar this week if you had complete control over it?
• What would "a great week" look like — what would you have shipped or decided?
• What are you deliberately not doing right now, and is that the right call?

Blockers and friction

• What is the biggest thing preventing you from making progress on your top priority?
• What pulled you away from planned work this week that you wish had not?
• Where are you waiting on someone else and it is slowing you down?
• What decision are you stuck on that you would like to think through together?
• What process is creating the most friction for your team right now?
• If you could get rid of one meeting or recurring task, which would it be?
• Where do you feel like you are managing up to get decisions made that should be made at your level?
• What do you need from me this week that I have not given you yet?

Team health and dynamics

• How would you describe the team's energy level this week — high, normal, or drained?
• Is there anyone on the team who seems disengaged or struggling that I should know about?
• Where is the team carrying load they should not be carrying?
• What does the team need from leadership right now that they are not getting?
• Who on the team is doing great work that is not getting enough recognition?
• Where is there friction between team members or across functions that I should be aware of?
• What would make the team more effective in the next 30 days?
• Is there anyone on the team who is at risk of burning out?

Development and growth

• What did you learn last month that surprised you?
• What skill do you most want to develop in the next quarter?
• What kind of work do you want more of — and less of?
• Where do you feel you are operating below your potential?
• What would you like to be responsible for in six months that you are not responsible for now?
• What project or problem would stretch you in a way that would accelerate your growth?
• Is there a role model — inside or outside the company — whose career you want to learn from?
• What do you want to be great at in three years?

Feedback and alignment

• What is one thing I am doing that makes your work harder, even if unintentionally?
• What is one thing I could stop doing that would free you up?
• Do you feel clear on what success looks like in your role right now?
• Are the goals you are working toward still the right goals, given how the quarter is going?
• Is there feedback you have been holding back that I should hear?
• How well do you feel your work connects to the company's priorities right now?
• Is there a decision that was made recently that you disagreed with — and do you feel like you had a chance to weigh in?
• What would make you feel more confident in your own impact here?

Remote and distributed teams

• Are you feeling connected to the team, or does remote feel isolating right now?
• What is falling through the cracks because we are not co-located?
• Is there context you are missing because you are not in the room when decisions get made?
• Are the async communication norms working for you, or do they create friction?
• What would make our remote collaboration more effective?
• Do you have what you need to do your best work from where you are working?
• What is the hardest thing about working on a distributed ops team that does not get talked about?

Running 1:1s for remote and distributed ops teams

Distributed operations teams face a specific challenge that co-located teams do not: ambient context does not transfer automatically. In an office, a manager picks up signals continuously — the tone of a conversation in the kitchen, the body language of a team member during an all-hands, the informal update shared while waiting for a meeting to start. In a distributed team, none of that happens passively. The 1:1 is the primary channel through which that context must be transferred deliberately.

Four adjustments make ops 1:1s more effective for distributed teams.

Shared async doc before the meeting. The weekly template works best when both parties fill their sections before the call — the direct report's section at least four hours before, the manager's section (with follow-up questions) at least one hour before. This preserves context across time zones and allows both parties to arrive at the meeting ready to discuss rather than ready to inform.

Video on as a default. Body language is a significant communication channel. A direct report who types "I'm fine" while visibly stressed is sending a clearer signal on video than in a message. Manager Tools' research found that video-on 1:1s produced significantly higher direct report satisfaction scores than audio-only 1:1s, even when the content was identical. This is not about surveillance. It is about connection.

A standing "team pulse" question. In distributed teams, the manager is further from day-to-day team dynamics. A standing question in the weekly template — "how is the team feeling this week?" — gives the manager a structured window into dynamics they cannot observe directly. The direct report's answer to this question is often more useful than anything else in the meeting.

Higher frequency, shorter meetings. A 20-minute weekly touchpoint is more effective for distributed teams than a 45-minute biweekly one. Frequency preserves context and connection. Length creates fatigue. If your current 1:1 cadence is biweekly or monthly, move to weekly and halve the time. The outcome is better connection and less calendar burden.

The most common 1:1 mistakes ops managers make

After working across many operations teams, the same failures recur. Here are the six most common, with the fix for each.

Using the 1:1 as a status update meeting. If the conversation is 80 percent project updates, both parties leave with information they could have gotten from a report. The fix: add a standing rule that operational status belongs in a pre-meeting doc. The call is for topics that require discussion, coaching, or decision — not for reading metrics aloud.

Letting the manager's agenda crowd out the direct report's. Grove's instruction was clear: the 1:1 is the direct report's meeting. The manager's topics should consume no more than 20 to 30 percent of the time. If you consistently have more to say than your direct report, you are running the meeting in the wrong direction.

Rescheduling 1:1s under pressure. Manager Tools is unambiguous on this point: canceling or rescheduling a 1:1 sends a clear signal to the direct report that they are not a priority. Ops managers are frequently pulled into escalations, fires, and last-minute cross-functional meetings. The 1:1 should be the last meeting that gets moved, not the first.

Skipping the development conversation. Monthly development and quarterly growth conversations get deprioritized when the team is under operational pressure — which in ops means always. Build them into the calendar as recurring, non-optional meetings separate from the weekly check-in. If they live in the same slot as the weekly check-in, they will always lose.

Not taking notes or tracking actions. A 1:1 without a shared document produces conversations that evaporate. Actions are implied but not confirmed. Feedback is given verbally but not recorded. Three weeks later, neither party can remember what was decided. The shared doc solves this. It creates a running record of the relationship, the development conversation, and the action list.

Treating all direct reports identically. Grove distinguished between task-relevant maturity — the experience level of the direct report on the specific task at hand — and overall performance. A high-performing generalist who is new to a specific ops domain needs more direction than an expert in that domain, regardless of their seniority. The 1:1 format and question mix should adapt to where the direct report is on the task-relevant maturity curve, not just to their job title.

Key takeaways

• Andy Grove's High Output Management treats the 1:1 as the manager's single highest-leverage activity. One well-run hour can multiply a direct report's output for the entire week.
• Ops 1:1s require explicit surfacing of invisible work — blockers, firefighting, and coordination tax that do not appear in any dashboard but drive attrition when left underground.
• Three formats cover the full cadence: weekly check-in (30 min) for operational rhythm, monthly development (45 min) for growth, and quarterly review (60 min) for career and goals.
• The direct report owns the agenda. The manager's topics should occupy no more than 20 to 30 percent of the conversation. If the manager is doing most of the talking, the format is inverted.
• For distributed teams, frequency matters more than duration. A 20-minute weekly call beats a 60-minute biweekly call. The shared async doc preserves context across time zones.
• Manager Tools' 20-year research found consistent weekly 1:1s to be one of the strongest predictors of direct report retention, engagement, and performance across all management roles and functions.