Document 06 of 10

Leading People

The human operating system: coaching, empathy, culture, and the hard conversations.

Systems and SOPs are the hardware. A manager's judgment is the operating system that runs on top of them. In a remote environment, where the casual hallway moments that build trust simply do not happen, that judgment carries more weight, not less.

This document is the human half of the Global OS: how to empower without losing control, how to listen, how to bridge cultural distance, and how to have the hard conversations most managers avoid until it is too late.

Type

System

Use

Whenever you manage a person

Pairs with

Doc 09

Next doc

Rhythms & Standards

Section 00

Empower, Do Not Micromanage

Remote managers are tempted to micromanage to prove work is getting done. It backfires. Nothing erodes trust faster than a manager hovering over every task. Empower instead: define the outcome, set a clear deadline, and let the person choose the method.

Micromanaging

  • Dictates the method step by step
  • Sets the outline and picks the tools
  • Reviews every draft mid-flight
  • Signals: I do not trust your judgment

Empowering

  • Defines the outcome and the deadline
  • Lets the person choose the approach
  • Reviews the result against a clear standard
  • Signals: I trust you to get there

The wrong way

I need three blog posts this week. Use the same outline as last week. I need a draft by Wednesday.

The right way

Our goal this week is to increase organic traffic by 5 percent through new content. We need to publish three blog posts. I trust you to manage your time and find the best way to do that. Tell me if you need resources or hit a blocker.

Section 01

The Art of Active Listening

In a remote one-on-one, your primary job is to listen. Do not dominate the conversation. Listen for the quiet signals: burnout, confusion, a drop in engagement. A good one-on-one covers just three questions.

01

01

What is working?

Celebrate wins and name the strengths worth leaning on. People repeat what gets noticed.
02

02

What is stuck?

Surface blockers and solve problems together. This is where you earn your keep as a manager.
03

03

What is next?

Talk about where they are heading, both the next task and their growth. Show them there is a path.

Ask these three, then truly listen to the answers. That is how you build a relationship where the person feels safe telling you the truth, which is the only version of a one-on-one worth having. Copy or download the note template below to run it the same way every week.

One-on-One Meeting Notes

Header

Hire name
Date

What is working

Wins from the past week
Strengths to leverage

What is stuck

Current blockers
Problems to solve
Resources needed

What is next

Goals for next week
Professional development
Personal growth opportunities

Action items

Action 1
Owner ___ Due ___
Action 2
Owner ___ Due ___
Action 3
Owner ___ Due ___
Next meeting

Section 02

Empathy and Vulnerability

Your team members are people with lives outside work. Show that you know it. When someone is dealing with a personal issue or a power outage, be flexible. A simple “I understand, take the time you need and we will catch up later” buys more loyalty than any perk.

You can model this by being human yourself. If you had a hard week, say so. Vulnerability from the manager gives everyone else permission to be honest, which is exactly the culture you want on a remote team.

Empathy is not the same as a lowered standard. Doc 09 covers where the line sits between a genuine one-off and a pattern that hurts the business. Both are true at once: care about the person, hold the standard.

Section 03

Bridging the Directness Gap

American workplaces prize direct communication. Get to the point. State feedback plainly. Ask “what is the blocker?” without a runway of preamble. For a remote team this is a feature: it removes ambiguity and cuts the slow back-and-forth that kills async work. But directness lands differently across cultures, and a manager who ignores that will bruise people without meaning to.

Where this comes from

The clearest map of this is Erin Meyer's book The Culture Map (2014). Meyer plots cultures on a communicating scale, from low-context (say exactly what you mean) to high-context (meaning is read between the lines), and on a separate scale for how directly negative feedback is given. English-speaking cultures sit at the low-context, often direct-feedback end. Many of the cultures you will hire from sit elsewhere. Meyer's point is not that one style is better. It is that teams perform when they understand the differences and agree on a shared norm. We choose directness as that norm, and the manager's job is to bridge people to it.

Why directness is the right norm for a remote team:

  • Clarity over comfort. With no body language to read, saying exactly what you mean is a form of respect.
  • Async efficiency. Across time zones you cannot afford veiled messages. I need a decision by end of day beats I was wondering if you had a moment.
  • Accountability. Direct expectations let you hold people to a clear standard, and clear standards build trust because everyone knows where they stand.

Your job is to be a cultural translator. Explain the style upfront rather than letting people discover it through a jarring first piece of feedback.

Setting the norm

On our team we practice direct communication. It is not about being rude. It is about being clear so you can succeed. I will give you feedback directly, and I expect the same from you. If something is unclear or you disagree, tell me. That is how we improve.
Give feedback a predictable shape so it feels safe: what went well, what could be improved, what happens next. A repeatable structure lets someone from a more indirect culture receive hard feedback without feeling ambushed.

Section 04

Difficult Conversation Scripts

Most managers avoid hard conversations because they do not know what to say, so a small problem grows into a firing. Do not improvise these. Below are five scripts for the situations you will actually face. Adapt the words, but keep the structure: name the issue with specifics, listen, get a concrete commitment, document it.

Script 1, missed deadlines

I noticed you missed the deadline for [task] on [date]. This is the first time this has happened. Let us talk about what is going on. What prevented you from finishing on time? [Listen.] Here is what needs to happen going forward: [specific expectation]. Can you commit to that? [Get the commitment.] Good. I am documenting this in our shared file so we are both clear. Let us check in on [date].

Script 2, poor quality work

I reviewed your [deliverable] and it does not meet our standard. Let me show you what I mean. [Share specific examples.] The standard is in the SOP and the Good Job Library. Before you submit, you check your work against both. Walk me through your process for this task. [Listen.] I see the gap. Here is what changes: [specific guidance]. Let us redo it together right now using the five-step method, so you own the standard.

Script 3, communication issues

You are not responding within our 5-minute standard. In the past [timeframe] I sent [number] messages that took [timeframe] to get a reply. That creates blockers for the team. What is going on? [Listen.] The standard exists for a reason: remote teams run on quick acknowledgement. Here is what I need: acknowledge messages immediately, even just “Got it, will update in 30 minutes.” Can you commit to that? [Get the commitment.] I will track this for a week. If it does not improve, we move to a more formal conversation.

Script 4, outage policy violation

You were offline for [duration] yesterday due to an outage. Under our 30/60 policy you switch to your hotspot immediately and notify me within 30 minutes. You did not. Walk me through what happened. [Listen.] I understand it was difficult, and the hotspot policy exists for exactly this. Let us test your hotspot right now. [Test it together.] This is your first warning. Switch immediately, report at 30 minutes, relocate at 60. A second violation is a formal written warning. Understood?

Script 5, moving to a formal plan

We need a serious conversation about your performance. Over the past [timeframe] we have discussed [issues] more than once. Despite coaching and clear expectations, I am not seeing the improvement we need. We are now moving to a formal Performance Improvement Plan. [Explain the structure.] This is your opportunity to show you can meet our standard. The plan runs [duration] and you need to hit [metrics]. If you cannot, we will end the relationship. I want you to succeed, and this is the last step before that. Let us go through the plan together.
Scripts 4 and 5 sit inside the accountability system in Doc 09. Use them together: the conversation lives here, the documentation lives there.

Section 05

The Performance Improvement Plan

When coaching has not worked and you need a formal, signed record, the Performance Improvement Plan is the tool. It states the concerns, the specific improvements required, the support you will provide, the check-in dates, and the consequence if the bar is not met. It protects the person, by making success concrete, and the business, by making the record clear.

Performance Improvement Plan

Header

Employee
Role
Manager
Date
Review period
Start to end date, typically 30 days

Performance concerns (previously discussed)

Concern 1
Specific issue with dates and examples
Concern 2
Concern 3

Required improvements

Improvement 1
Success criteria: how this will be measured
Improvement 2
Success criteria: how this will be measured
Improvement 3
Success criteria: how this will be measured

Support provided

Support 1
Support 2
Support 3

Check-in schedule

Week 1 check-in
Week 2 check-in
Week 3 check-in
Final review

Consequences

If requirements are not met by the end date
Employment will be terminated

Acknowledgment

Employee signature and date
Manager signature and date
A plan is a real chance to recover, not a countdown to firing. Run it in good faith. If it still does not work, Doc 09 covers the clean, documented exit.