Running a weekly one to one worth the half hour

The weekly one to one is the lightest management tool you have, and the easiest to waste. If your calendar is full of half hours that end with “anything else?” and nothing changes, the problem is not the meeting. It is the structure.

This guide covers what to prepare, what to ask, how to handle time zones, and how to follow through. The aim is a half hour that produces decisions instead of small talk. It is for founders and operators of remote teams, where the weekly one to one is often the only reliable human contact in the week.

Why the weekly one to one fails on remote teams

In an office, context leaks. You see someone staring at a screen, hear a sigh, notice they skipped lunch.

Remote work removes all of that. The weekly one to one becomes the only place where a problem can surface before it becomes a resignation letter or a missed deadline.

It usually goes wrong for three reasons.

• It becomes a status update. Status belongs in a written update. If you spend twenty minutes reading back what you already knew, you have wasted the meeting.
• It has no owner. The manager shows up unprepared and asks the report to drive. The report does not know what the manager needs to hear.
• Nothing happens after. Decisions are made, then forgotten. By the next week, the same blocker is back.

A weekly one to one worth the half hour fixes all three. It has a fixed shape, a shared document, and a follow-up that takes five minutes.

What a good weekly one to one actually covers

A good weekly one to one covers three things, in this order: the person, the work, and the week ahead. That order matters.

If you start with tasks, you never get to the person. If you start with the person, the tasks take care of themselves faster because you know what is really going on.

The person

Ten minutes. How are they? Not the polite version.

Ask what drained them this week and what gave them energy. On remote teams, this is where you catch burnout, isolation, and quiet frustration.

You are not solving anything here. You are listening and taking notes.

The work

Ten minutes. What is blocked, what is at risk, and what needs a decision from you.

Not a list of completed tasks. A list of things that will not happen unless you act.

Ask: “What is the one thing slowing you down right now?” Then shut up and let them answer.

The week ahead

Ten minutes. What are the two or three outcomes that matter next week?

What does support look like? What will you do by when? Write it down in the shared doc before the call ends.

That is the whole meeting. Thirty minutes, three blocks, one document.

How to prepare for a weekly one to one in five minutes

Preparation is where the half hour is usually lost. You do not need an hour to prepare. You need five minutes and a running document.

Keep one shared doc per person. It has three sections: open items, wins, and questions.

Both of you add to it during the week. Before the call, you read it. That is your prep.

• Open items: anything decided but not done, with an owner and a date.
• Wins: anything that went well, however small. This is not fluff. It tells you what to protect.
• Questions: anything either of you wants to raise but has not.

If you are running several one to ones, batch your prep. Fifteen minutes on a Monday morning covers four people. The alternative, showing up cold and asking “so, how’s it going?”, is how the meeting becomes a chore.

If you are building a remote team from scratch, this habit is worth setting up before the first hire starts. Our page on embedding remote professionals sets out what you prepare before day one.

A repeatable agenda for the weekly one to one

Here are the same three blocks as an agenda, minute by minute. The person block is the first two items, the work block is the third, and the week ahead is the last two.

1. Two minutes: check-in. One sentence each on how the week went. No problem-solving.
2. Eight minutes: their agenda. They raise what they need. You listen and ask questions.
3. Ten minutes: your agenda. Blockers, decisions, feedback. Be specific and short.
4. Six minutes: the week ahead. Two or three outcomes, owners, dates.
5. Four minutes: commitments. Read back what each of you will do. Confirm the next meeting.

The times are a guide, not a rule. But if you regularly blow past thirty minutes, something is wrong. Either the meeting is carrying work that belongs elsewhere, or you are avoiding a hard conversation.

When to break the agenda

Break it when something real comes up. If someone says “I’m thinking about leaving” or “I can’t keep doing this,” drop the agenda.

The half hour is not sacred. The relationship is. Reschedule the rest and deal with what is in front of you.

Questions that make the weekly one to one useful

Good questions are specific and slightly uncomfortable. Bad questions invite “fine.” Here are ten that work on remote teams.

• What is the one thing slowing you down this week?
• What did you expect to finish that you did not, and why?
• Where are you waiting on someone else?
• What decision are you avoiding?
• What would make next week easier?
• What is not working that you have not told me about?
• What do you want more of? Less of?
• Who on the team needs help right now?
• What did you learn this week that we should share?
• If you were me, what would you change?

Pick three and rotate them. Do not run through all ten. The point is to open a door, not to complete a survey.

Listening rules

• Do not fill silence. Count to five before you speak.
• Do not solve in the first minute. Ask one more question.
• Do not take notes on everything. Note decisions and blockers only.
• Do not check your other screen. They can tell.

Handling time zones, cameras, and short weeks

Remote teams add friction the office never had. Handle it deliberately.

Time zones

Rotate the meeting time if the team spans more than four hours. One week suits the early time zone, the next suits the late one. If someone is always on a call at 7 in the morning or 9 at night, they will eventually resent it.

If you want a managed team with one accountable lead, our Pods service agrees the hours and the reporting with you before we search.

Cameras

Default to cameras on for one to ones. This is not surveillance. It is the only signal you get about how someone is doing.

If someone asks for cameras off occasionally, say yes. If they ask every week, ask why.

Short weeks and holidays

Do not skip the meeting. Shorten it. Fifteen minutes is better than zero.

Skipping teaches the team that the meeting is optional. An optional meeting is the first thing to go when things get busy, which is exactly when you need it.

Async weeks

If a week is genuinely impossible, replace the call with a written update in the shared doc. Three bullets: what is blocked, what needs a decision, what is next.

Reply in writing within a business day. The cadence holds even when the call does not.

Following through after the weekly one to one

This is the part that separates a useful meeting from a ritual. Five minutes after the call, do three things.

1. Update the shared doc. Add decisions, owners, and dates. Delete anything closed.
2. Send the two or three commitments in writing. One short message. No essay.
3. Do your part before the next call. If you said you would unblock something, unblock it. Nothing kills trust faster than a manager who promises and forgets.

At the start of the next meeting, read the open items aloud. Two minutes. If something has been open for three weeks, ask why.

If it is not important, close it. If it is important and not being done, you have found the real problem.

When the one to one is not working

Sometimes the meeting is fine and the role is wrong. If every week surfaces the same blocker, the issue is not the meeting. It is the brief, the tools, or the fit.

That is worth naming directly. If you are hiring for the seat, our Search service finds the person and you hire them onto your own payroll. Every profile has a live identity interview before you see it, so you know who the person is and where they are.

Building the habit across a remote team

One good one to one is easy. Fifty-two in a row is a system. Three things make it stick.

• Same time, same day. Predictability beats convenience. People prepare when they know when it is.
• Same document. One running doc per person, updated weekly. No new templates.
• Same follow-up. Decisions written down, commitments sent, next meeting confirmed.

If you manage managers, run one to ones with them too, and ask them to show you their team’s docs. You will learn more about the health of the team from those docs than from any dashboard.

A note on scale

As a team grows, the manager’s one to ones can start crowding out the work. Two kinds of structure help: support around each seat, and fewer direct reports.

With Embed, an experienced professional joins your team, recruited, engaged, paid and managed by Hiraya. You get one named account owner, a one-business-day response, and check-ins at day 7, 30, 60 and 90, then a monthly report. That structure gives the weekly one to one something to sit inside, rather than being the only thread holding the relationship together.

With Pods, a team of three or more works under one lead who is accountable to you, rather than as several individual reports.

You can read more on our Insights page.

Common mistakes to avoid in the weekly one to one

• Canceling when busy. Busy weeks are when the meeting earns its keep.
• Letting it run long. A half hour that runs to sixty is a half hour that gets canceled next week.
• Doing all the talking. If you speak more than half the time, you are running a briefing, not a one to one.
• Saving feedback for review time. Feedback belongs in the week it happens, not in a quarterly pile.
• Skipping the person section. It feels soft. It is the part that keeps people.
• No written record. If it is not written down, it did not happen.

None of these are complicated. They are just easy to drift into when the week gets loud.

What to do this week

Pick one person. Open a shared doc. Add three sections: open items, wins, questions.

Send them the link today and tell them the agenda. Run the meeting on the same day next week, for thirty minutes, with the three-block structure above.

Write down the decisions. Send the commitments. Do your part before the next call.

That is the whole method. It does not need software, a framework, or money for training. It needs a half hour, a document, and a manager who shows up prepared.

Hiring for a remote seat and want a qualified shortlist in five business days? Book a call and we will walk through what fits your team.

Frequently asked questions

How long should a weekly one to one be?

Thirty minutes is enough if you use a fixed structure: ten minutes on the person, ten on blockers and decisions, ten on the week ahead. If it regularly runs longer, the meeting is carrying work that belongs in a written update or a separate session.

What should I prepare before a weekly one to one?

Five minutes with a shared document. Read the open items, wins, and questions both of you added during the week.

That is your prep. You do not need a slide deck or a status report.

Should the manager or the team member lead the weekly one to one?

The team member leads the person block, raising what they need. The manager leads the work block, covering blockers and decisions, and both own the follow-up. If the manager does most of the talking, it is not a one to one.

How do you run a weekly one to one across time zones?

Rotate the time so the same person is not always on an early or late call. Keep the same day where possible, and shorten rather than skip during busy weeks. When a live call is genuinely impossible, use a written update in the shared doc.

What if the weekly one to one keeps surfacing the same problem?

That usually means the issue is not the meeting. It is the role brief, the tools, or the fit. Name it directly and fix the underlying cause rather than adding another meeting to manage around it.