How to Run a 1:1 When You've Never Managed Anyone Before

You got the promotion, or you inherited a team, and now there's a recurring meeting on your calendar you're not sure how to fill. Welcome. Almost nobody feels ready for their first 1:1.

Here's the good news: a 1:1 isn't a performance. It's a habit. Run it simply, keep it consistent, and write down what matters. That's most of the job. The rest you'll figure out as you go.

This guide walks you through the practical setup - the rhythm, the prep, what to cover, and how to remember it all - so your first 1:1s feel less like an interview and more like a conversation.

Start with a rhythm you can actually keep

The first decision isn't what you'll talk about. It's how often you'll meet.

Weekly is the standard on most teams, and it's a good default. Thirty minutes is plenty for one person. Some managers run 45. Some go biweekly. The right cadence is the one you'll still be holding six months from now, not the one that looks best on a calendar.

Protect the slot. If your 1:1s get cancelled the moment things get busy, you've just told your team what they're worth. A 20-minute 1:1 that actually happens beats a 60-minute one that keeps moving.

One tip that saves first-timers a lot of grief: set a standing time and don't use it for anything else. No project reviews, no quick syncs. It belongs to the person, not the work.

What a 1:1 is actually for

New managers almost always confuse the 1:1 with a status update. It isn't.

A status update is about the work. A 1:1 is about the person doing the work. How they're doing, what's frustrating them, where they want to grow, what they need from you. The work will come up, and it should - but if the whole conversation is task-tracking, you could have sent an email.

Think of it this way: the 1:1 is the one meeting where the agenda belongs to your report as much as it belongs to you.

How to prepare without over-preparing

You don't need a script. You need a few minutes and a place to write.

Before each 1:1, pull up your notes from the last one. Read them. What did you promise? What did they raise? What's still open? That five-minute gap is where good 1:1s are actually made.

Then jot down two or three things you want to touch on. Not fifteen. Two or three. If you walk in holding a list of twenty items, you've built a status meeting without noticing.

What to cover in each conversation

A simple structure keeps you from freezing on the spot:

Check in first. Ask how they're doing, and mean it. Give them room to say "not great" without rushing past it.

Then hand over the floor. Ask what's on their mind this week. Let them set the opening agenda. You'll learn more from what they bring up than from anything you would have asked.

Cover what's in flight. Blockers, decisions, anything they need from you. Keep it tight.

End on growth and next steps. What are they getting better at? What do they want to take on? And what did the two of you agree to do before you next meet?

That last question matters more than it sounds. Follow-through is the whole game.

How to remember what people said

This is where most first-time managers quietly struggle. You have five direct reports, five sets of concerns, five sets of promises - and a memory that starts blending them together by Thursday.

The answer is boring and effective: write it down. Not in your head, and not in a note you never reopen. Somewhere tied to the person.

Notes you take in a 1:1 should be private. Your report needs to trust that a candid moment in your meeting doesn't turn into a talking point at the next leadership sync. Privacy isn't a feature you bolt on later; it's what makes the honesty possible in the first place.

So keep a running note per person. What they said, what you agreed to, what to follow up on next time.

Stop the slide into a status update

Halfway through a busy quarter, watch for the drift. Suddenly your 1:1 is a project standup with a nicer name.

Here's a cheap fix: open with the person, not the project. If you lead with tasks, you'll stay on tasks. If you lead with how they're really doing, the meeting finds its own center.

Another one: if an issue is really about the work and belongs in a project thread, say so out loud and move it there. That keeps the 1:1 from becoming the catch-all bin for everything.

You're allowed to be new at this

Your reports don't need a finished manager. They need someone who shows up, listens, remembers, and follows through. That's genuinely it.

When you get something wrong - and you will - name it in the next 1:1. Last week you said you'd sort something out and you didn't; say where it stands now. That kind of honesty buys more trust than pretending you've got it all handled.

Where Mora fits

If the notes part is the bit that worries you, that's exactly what Mora was built for.

Mora keeps your notes, goals, and follow-ups together for each report, keeps them private, and drafts a suggested agenda before each conversation so you walk in prepared instead of scrambling. It's made for managers who run their own 1:1s and want to do it well - no seat math, no sales call, no waiting on a company rollout. If you landed here from a search for "mat mora," that's us: a 1:1 meeting tool for managers, and you can try it at meetmora.io.

The short version

Set a rhythm you'll keep. Prepare for five minutes with last time's notes. Let the person talk first. Write down what matters and follow through. Protect the meeting from becoming a status update.

Do those five things and you're already running better 1:1s than plenty of managers with years on you. You'll get sharper with practice. Everyone does.