Remote Manager One on One Question Template for Distributed Team Check Ins

Running effective one-on-one meetings with a distributed team requires more than copying your in-office habits into a video call. The asynchronous nature of remote work, the lack of hallway conversations, and the time zone differences all demand a more intentional approach to check-ins.

This guide provides a practical question template you can adapt for your distributed team, along with implementation strategies that actually work for developers and technical power users.

Why Standard One-on-One Questions Fail Remotely

In an office, you can casually ask “How’s it going?” and get a real answer because there’s context—you see your teammate’s expression, notice they’re frustrated with their code, or overhear a conversation about a difficult bug. Remote work removes these cues.

Most managers default to generic questions like “How are you?” or “Any blockers?” which yield generic answers: “Good” or “No blocks.” These check-ins provide zero value and quickly become a waste of time that team members dread.

Effective remote one-on-ones need to surface context that would normally happen organically in an office. Your question template should prompt for specific, actionable information while respecting the asynchronous nature of distributed work.

The BASE Framework for Distributed One-on-Ones

This template uses the BASE framework: Blockers, Accomplishments, Support needs, Energy and wellbeing. Each category serves a distinct purpose:

Blockers: Identify obstacles preventing progress
Accomplishments: Acknowledge progress (not just task completion)
Support needs: Surface where help would accelerate work
Energy and wellbeing: Check for burnout signals and motivation levels

Weekly Check-In Question Template

Here’s a markdown-formatted template you can paste directly into your team wiki or async tool:

## Weekly One-on-One Check-In

**Week of:** [DATE]

### 1. Blockers
What, if anything, is blocking your progress this week?
- Technical blocker (dependency, bug, infrastructure):
- Process blocker (approval, review, decision needed):
- People blocker (waiting on someone, unclear ownership):

### 2. Accomplishments
What did you complete that you're proud of?
-
-

### 3. Support Needs
What would help you move faster or more effectively?
-
-

### 4. Energy & Wellbeing
How would you rate your energy level (1-10)?
What's draining you? What's energizing you?

### 5. Anything else
Topics you want to discuss in our sync?

Follow-Up Questions by Category

Generic questions get generic answers. After your team member submits their check-in, dig deeper with specific follow-ups:

For Blockers:

“What’s the specific error message you’re seeing?”
“Who needs to make the decision you’re waiting on?”
“Is this a new blocker or something that’s been persistent?”

For Accomplishments:

“What was the trickiest part of that implementation?”
“How did you approach solving [specific challenge]?”
“What did you learn from that debugging session?”

For Support Needs:

“Would pairing on this help, or would you prefer to figure it out solo first?”
“Do you need me to talk to [person/team] on your behalf?”
“Would a written decision doc help unblock [process]?”

For Energy and Wellbeing:

“What does a typical day look like for you right now?”
“Are you getting enough uninterrupted focus time?”
“Is there anything about how we work that’s making your job harder?”

Async-First One-on-One Format

For distributed teams across time zones, synchronous one-on-ones aren’t always feasible. Here’s an async-first workflow that still builds connection:

Step 1: Pre-Meeting Async Exchange (24-48 hours before)

Send the template above to your direct report. Ask them to fill it out by [specific day]. The key instruction: be specific. “I fixed a bug” tells you nothing. “I fixed the memory leak in the image processing worker that was causing our containers to restart every 4 hours” tells you exactly what they accomplished.

Step 2: Manager Review and Notes

Before your sync (whether 15 minutes or 30), review their responses and prepare:

One thing to celebrate from their accomplishments
One question to dig deeper on their blockers
One offer of support based on their stated needs

Step 3: Short Synchronous Touchpoint

For distributed teams, use the sync time for:

Real-time clarification on blockers
Relationship building (ask one personal question)
Career development discussion
Anything that requires back-and-forth

Keep the sync focused. If you spend the whole meeting discussing blockers, you’re using synchronous time for something that should have been handled async.

Code Snippet: Automated Reminders

If your team uses Slack or similar tools, automate the weekly check-in reminders with a simple script:

// Slack workflow builder or Slack app reminder
const checkInPrompt = {
  channel: "#1-on-1-checkins",
  text: "Weekly check-in time! Please share your update using the template in the wiki.",
  blocks: [
    {
      type: "section",
      text: {
        type: "mrkdwn",
        text: "📋 *Weekly One-on-One Check-In*\nPlease fill out your BASE check-in before Thursday EOD."
      }
    },
    {
      type: "actions",
      elements: [
        {
          type: "button",
          text: { type: "plain_text", text: "Fill Out Check-In" },
          url: "https://your-wiki-url/one-on-one-template",
          style: "primary"
        }
      ]
    }
  ]
};

Adapting the Template for Different Team Sizes

Small Teams (2-5 people)

With small teams, you can afford deeper one-on-ones. Consider:

30-minute syncs weekly
More personal questions about career goals
Discussing team dynamics and collaboration

Medium Teams (6-15 people)

At this scale, consistency matters more than depth:

15-minute syncs bi-weekly
Focus on blockers and support needs
Use async check-ins between syncs

Large Teams (15+ people)

For larger teams:

Rotate between 1:1s and small group check-ins (you can’t meet 1:1 with everyone weekly)
Consider skip-level meetings for senior ICs
Document patterns in blockers and address them in team meetings

Common Mistakes to Avoid

Scheduling only when there’s a problem. One-on-ones should happen consistently regardless of whether there’s a crisis. The relationship you build during good times makes it easier to navigate hard times.

Making it a status report. If your one-on-one is just you asking “What did you do this week?” and them listing tasks, stop. That’s what project management tools are for. Use one-on-ones for human connection and career development.

Ignoring the async prep. If you ask team members to fill out a template but never read it or respond to it asynchronously, they’ll stop putting effort into it. Acknowledge their async responses before the sync.

Using the same template forever. Your team’s needs change. What you needed to ask when they were onboarding differs from what matters during a tight deadline or after a difficult project. Adjust your questions to the context.

Building the Habit

Consistency beats intensity. Better to have 15-minute weekly one-on-ones that actually happen than 60-minute monthly ones that get cancelled. Put them on the calendar, protect the time, and treat them as non-negotiable as any external meeting.

The question template is a starting point, not a rigid script. The best managers adapt their approach based on what they learn about each team member. Some people need more structure, others need more space. Some weeks call for deep blocker discussion, others call for pure relationship building.

Start with the BASE framework, gather feedback from your team on what’s helpful, and iterate. The goal isn’t perfect—it’s consistent attention to your team members as humans, not just as productivity units.

Built by theluckystrike — More at zovo.one