↓Skip to main content

Running remote and hybrid teams, one habit at a time

How to manage remote teams effectively without micromanaging

·6 mins
Managing Remote Teams Remote Management Micromanagement Team Norms Autonomy
Table of Contents

It’s Wednesday afternoon. You haven’t heard from two people on your team since the morning standup, a deadline is on Friday, and you can feel the urge to send a “how’s it going?” message. Then another. Then to check who’s showing as online.

That urge is the start of remote micromanagement, and almost every remote manager feels it. It doesn’t come from distrust so much as from missing information. In an office, you’d glance across the room and see progress. Remote, the silence feels like a problem even when nothing is wrong.

The fix is not to try harder to resist the urge. It’s to build a team system that gives you the information without anyone having to be chased for it.

Swap the habit for a structure

Each micromanaging habit is a manager trying to get a piece of information. Give the information a regular home and the habit loses its reason.

The habit What you actually want to know The structure that replaces it
“How’s it going?” messages Is the work on track? A written status on a fixed rhythm, in one shared place
Watching online status Is the person working? Agreed outcomes for the week, reviewed in the 1:1
Asking to be copied on everything Will I miss something important? A decisions log and a weekly team summary
Reviewing every piece of work Will the quality be right? A written definition of done for each type of work
Surprise calls Are they stuck? A clear, named route for raising blockers early

Notice that none of the right-hand column depends on you being online at the same time as anyone else. That’s what makes it work across time zones as well.

On activity tracking specifically: apart from being a poor proxy for output, it brings legal obligations in many places. The UK Information Commissioner’s Office, for example, publishes guidance on monitoring workers that expects monitoring to be necessary, proportionate and open. Most teams get a better result from the structures above.

Agree how much autonomy each piece of work gets

A lot of micromanaging comes from never saying out loud how much freedom someone has on a task. The manager assumes “check with me first”; the team member assumes “just get on with it”. Both feel let down.

Name the level when you hand work over. Four levels cover most cases:

  1. Do it as specified. The approach is fixed; ask before changing anything. For work with legal, financial or client risk.
  2. Recommend, then act. Propose the approach in writing; go ahead once agreed.
  3. Act, then tell. Make the call and post what you decided and why.
  4. Just act. Fully yours. Mention it in your normal status update if it’s worth knowing.

Most work for an experienced person should sit at 3 or 4. If you find yourself putting everything at 1 or 2, that’s worth noticing: either the person needs more support, or you need to let go.

Raise the level as trust builds. Saying “this one’s a level 4 now” is a small, specific way of showing confidence that lands better than general praise.

Make the team’s work visible to itself

Visibility isn’t just for the manager. When the team can see what everyone else is doing, they coordinate directly instead of routing everything through you, which is the opposite of micromanagement.

Three habits do most of the work:

  • One shared board or tracker for current work, with an owner and a status on every item. The board is the source of truth; nobody asks for status that the board already shows.
  • A short written status from each person on a fixed rhythm. Done, next, blocked. Our guide to async communication for remote work covers how to make these useful rather than performative.
  • A fortnightly show-and-tell where people share finished or in-progress work for ten minutes each. It gives credit in public and spreads knowledge sideways.

Run fewer team meetings, and better ones

Meetings are where remote managers often compensate for anxiety. If you can’t see the work, at least you can see faces. The result is a team with no time to do the work you’re anxious about.

The 37signals guide to internal communication makes the point that an hour-long meeting with five people costs five hours, not one. Treat the team calendar as a budget.

A lean pattern for most remote teams:

  • One weekly team sync with an agenda posted a day ahead. Items that are pure information go in writing instead.
  • Asynchronous standups by default, with a live standup only if the team actually prefers it.
  • Problem-solving calls booked when needed, with only the people who need to be there.
  • Notes posted within 24 hours of any meeting, so absentees aren’t penalised.

Write a team working agreement

Most remote friction comes from mismatched assumptions: about response times, camera use, what “urgent” means, who decides what. A one-page team working agreement removes them, and because the team writes it together, it doesn’t feel like a rule imposed from above.

Draft it in a 45-minute session. Ask each question, collect answers in a shared doc, agree, and revisit every six months or when someone new joins. The template at the end of this page is a starting point.

If your company has a remote work policy, the working agreement sits underneath it: the policy covers contracts, equipment and hours; the agreement covers how this particular team works day to day.

A quick self-check

Once a month, answer these honestly:

  • Did I ask anyone for a status update that was already written down somewhere?
  • Did I review work that the person was already trusted to do alone?
  • Did anyone wait for my approval on something that could have been theirs to decide?
  • Did I message anyone outside their working hours without scheduling it?
  • Did I cancel a 1:1?

Two or more yeses is a sign that the structures need fixing, not that you need more willpower. For the individual side of this, including how to run 1:1s and handle performance, see our operating manual on how to manage remote employees.

Team working agreement (copy this) 

TEAM WORKING AGREEMENT: [Team]   Agreed: [date]   Review: [date + 6 months]

HOW WE SHARE STATUS
- Work lives on [board/tool]. Every item has an owner and a status.
- Written update every [day / Mon-Wed-Fri] in [channel]: done, next, blocked.
- Nobody asks for status the board already shows.

AUTONOMY LEVELS (named when work is handed over)
1 Do as specified   2 Recommend, then act   3 Act, then tell   4 Just act

DECISIONS
- Decisions that affect others go in [decision log] with what/why/who/date.

MEETINGS
- Weekly sync: [day, time UTC], agenda posted 24h ahead, notes within 24h.
- Standups are async unless we agree otherwise.
- Camera: [on for 1:1s and small calls / optional in large meetings].

RESPONSE TIMES (reader's working hours)
- Urgent: [route]. Mentions: 1 working day. Doc comments: 2 working days.

BLOCKERS
- Raise a blocker as soon as you've spent [x hours] stuck, in [channel].

HOURS
- Core overlap: [window UTC]. Outside it, schedule messages.