Playbooks

Manager check-ins and one-on-ones: A complete guide

Most managers hold the meetings. Few hold conversations. The difference is what you know about the person before you walk in.

16 min read

Most managers who hold weekly check-ins and quarterly one-on-ones run into the same problem sooner or later: the conversations stay generic. The weekly check-in drifts toward a status update, and the quarterly one-on-one drifts toward a vague discussion about growth that neither of you quite knows how to make concrete. You cover the ground and move on, and not much changes.

The problem usually isn't the meeting format. It's what the manager brings into it – or doesn't. When you don't have a clear, current picture of what someone can do, what they've said they want to develop, and where the gap is between the two, the conversation has nowhere specific to go. You ask how things are going, they tell you, you make a note to follow up, and next week looks much the same.

This playbook covers both practices, the weekly check-in and the quarterly one-on-one, and what to bring into each. They're distinct in purpose but connected in effect. When both are running well, grounded in real skills data, they become the way people actually grow, and they make you the kind of manager people don't leave.

A check-in is not a one-on-one

A check-in is business-like. It's a quick weekly meeting where the manager or team leader checks in with team members about progress made on a given task or project – a kind of a status report on how things are going. Fifteen to thirty minutes is usually enough to align on progress, surface blockers and stay coordinated. In short: Check-ins are less about the worker and more about the work.

A quarterly one-on-one, however, is focused on the direct report. It's a longer, more deliberate conversation – at least an hour – that gives them space to reflect on their growth, share what's energising them and what isn't, and work with you on where they want to go. It's the employee's meeting, so your job is to listen and to help them think clearly about their development.

Having said that, the rules aren't written in stone. If you have the time or if it is relevant, an employee's personal and professional growth can also be addressed in check-ins. As experienced managers would know, the final call is obviously yours.

Check-ins and one-on-ones are both forms of continuous performance management, which organisations are adopting as they move away from annual appraisals that look at the past rather than the future. Both matter, and neither replaces the other.

The weekly check-in: How to run it well

The structure of a good check-in is simple. What separates a productive check-in from a routine one is the quality of attention the manager brings, which means knowing enough about each person's work and capability to ask the right questions rather than the obvious ones.

The rhythm takes a little more thought: how often you meet, and for how long, depends on how experienced your direct reports are. A less experienced employee, or someone going through a change, might need longer or more frequent check-ins, while it may be enough to check in with a more skilled employee once every two weeks.

Whatever the rhythm, the preparation is the same. Before the meeting, spend two minutes reviewing where this person is. What are they working on? What's their role on the team right now? What did they flag last week? If you're using MuchSkills, the My Circle manager hub gives you a live view of each direct report's skills, certifications, current development goals and availability, so you go in informed.

During the meeting, a suggested agenda:

Open with something human. Experienced managers usually open with something not directly related to work, such as asking how the person is doing. An icebreaker takes less than two minutes, helps people relax and, over time, helps build strong relationships.

Share any updates. Anything relevant at company, team, or project level that affects them. Don't make them find out through the grapevine.

Ask for their update. What progress have they made? What's blocking them? Are there challenges – resource constraints, dependencies on other teams, anything creating friction? Ask how you can help, and mean it.

Follow up on last week. If they raised a challenge and you said you'd look into it, this is where you report back. Consistency here is what builds trust over time.

Acknowledge what's going well. Recognition doesn't need to be elaborate. A specific observation – "the way you handled the client escalation on Tuesday was exactly right" – carries more weight than generic praise.

Give feedback if it's warranted. Keep it specific and forward-looking. Not "you need to improve your communication" but "when you send project updates, adding a one-line summary at the top would help stakeholders who don't have time to read the full detail."

Agree on the focus for next week. What are they prioritising? Is it clear? Does it align with what the team needs?

Check the temperature on the team. How are things going with colleagues? This surfaces dynamics and tensions early – before they become problems you're managing reactively.

If a check-in has to be cut short, keep the feedback. In Gallup's study of 44,025 US employees (Harter, 2026), about seven in ten of those who had received meaningful feedback in the past week were engaged, against one in four of those who hadn't. The weekly check-in is where that feedback happens.

After the meeting follow up with yourself first. Managers who want to promote a culture of accountability lead from the front: make a note of what you promised to follow up on, and during the week, act on those promises or have a valid reason why you haven't been able to. Then note the tasks or steps you assigned your direct report, and follow up on them at the next check-in. Managers who do both consistently build the kind of trust that makes direct reports bring real problems to check-ins rather than managed versions of them.

What managers shouldn't do in check-ins

A few things that undermine a check-in before it starts:

Don't come to the meeting unprepared. This defeats the purpose of holding the check-in. The employee will realise you are holding the meeting just for the sake of holding it – perhaps because it's part of organisational processes – and is likely to lose interest or enthusiasm for it.

Don't let check-ins be the first thing that goes. When the week gets busy, recurring meetings get cancelled. Check-ins are usually first. But consistency is precisely what makes them useful – a check-in that happens every week, even briefly, builds the continuity and trust that an occasional longer meeting never quite replaces. It's ok to cancel if you absolutely must. But don't make a habit of it and always reschedule.

Don't fail to ask questions. Asking questions indicates to the employee that you are aware of their role in the larger team. It helps keep them motivated and on their toes. A manager who only delivers information in check-ins is broadcasting.

Don't let the meeting get interrupted. This is their time. A check-in held in a corridor or with one eye on your phone is worse than no check-in at all.

Don't make it a performance review in miniature. The check-in is not the place to surface significant concerns about someone's work for the first time. Those conversations need a different setting and a different level of preparation.

The quarterly one-on-one: How to run it well

If the weekly check-in is about the work, the quarterly one-on-one is about the person. It's longer, less structured, and – when done well – the most important conversation a manager has with a direct report all year.

The quality of this conversation depends almost entirely on the preparation that goes into it. A quarterly one-on-one where neither party has done any thinking beforehand will stay surface-level. A quarterly one-on-one where the employee has reflected on their growth, updated their skills profile, and come with a clear sense of where they want to go – that's a conversation with somewhere to go.

One week before

Send your direct report a short email. Ask them to do two things before the meeting:

First, update their MuchSkills profile – specifically their skills levels, any new certifications, and their development goals. This matters because the profile gives both of you a shared, concrete starting point. Instead of asking "how do you feel your skills are developing?", you can look together at where they've rated themselves, what they've flagged as development priorities, and what the gap looks like between where they are and where they want to be.

Second, give them a self-reflection questionnaire. Its main purpose is to encourage self-reflection, so it isn't necessary for them to send the answers back to you. Give them at least a week, because it is important that they have the time to work on it when they feel up to it.

Here's a template for the email:

Email template
SubjectPreparing for our one-on-one

Hi [name],

I'm looking forward to our one-on-one on [date]. To make the most of our time, it would help if you could do two things before we meet:

1. Update your MuchSkills profile – add any new skills, adjust levels where they've changed, and make sure your development goals reflect what you're working toward.

2. Take some time to reflect on the questions below. You don't need to share your answers with me – this is for your own thinking. But if there's anything you'd like to discuss, bring it along.

Let me know when your profile is updated. If you'd like to share your reflections ahead of time, please send them at least five days before we meet.

Looking forward to the conversation.

Self-reflection prompts to include:

  • What have been your biggest achievements since we last spoke?
  • What has been most energising in your work recently – and what has been draining?
  • Which skills do you feel you've developed, and which do you feel are underused?
  • What does growth look like for you in the next six to twelve months?
  • What is holding you back?
  • Is there anything you need from me or the organisation to develop in the direction you want?
  • How are you finding the team dynamics at the moment?
  • How do you let the team support you?

For a fuller set, use the MuchSkills employee reflection template (a Word file).

During the quarterly one-on-one

Ben Horowitz, co-founder of Andreessen Horowitz, put it well: "The key to a good one-on-one meeting is the understanding that it is the employee's meeting rather than the manager's meeting."

Remember, this meeting is all about the employee and how that person can develop professionally. Listen actively, ask open questions, and direct any digressions back to the main subject: the employee.

A suggested agenda:

  • Reflections on the period: Invite them to share what's gone well, what's been hard, and what they've learned.
  • Growth so far: How do they feel their skills and capabilities have developed? Look at their MuchSkills profile together to make the conversation concrete, rather than to audit them.
  • Current focus and energy: What aspects of their work are they finding most engaging right now? Where do they feel their skills are being well used – and where do they feel underused? A manager's attention to strengths is linked to engagement: in Gallup's strengths research (2016), 67% of employees who strongly agreed that their manager focuses on their strengths or positive characteristics were engaged, against 2% of those who strongly disagreed.
  • Challenges and concerns: What's creating friction? Are there skills they need to develop to do their current role better? Barriers to growth they can't resolve themselves?
  • Team dynamics: How are things going with colleagues? Are there relationships or dynamics the manager should be aware of?
  • The next period: What does growth look like for them in the coming months? Work together to set one to three concrete development goals – specific enough to be actionable, connected to both what the employee wants and what the organisation needs.
  • Close the meeting positively: Before wrapping up, reaffirm something specific about the value they bring to the organisation. Of course, don't say anything you don't mean. Your interactions must be honest and respectful.

What managers shouldn't do in quarterly one-on-ones

Don't cancel. As Daniel Nilsson, co-founder of MuchSkills, puts it: "Never cancel a one-on-one. Move it, but never cancel it." A quarterly one-on-one cancelled without rescheduling loses months of development momentum and signals that growth conversations are dispensable. The employee has done the pre-work, reflected and come prepared, and cancelling sends a message no manager intends.

Don't do most of the talking. Ask good questions, listen carefully and keep your own observations about their performance brief.

Don't make it a performance review. The quarterly one-on-one is a development conversation. If there are significant performance concerns to address, those need a separate conversation with appropriate preparation and framing.

Don't skip the follow-up. The commitments made in the room are only as good as what happens after it.

After the quarterly one-on-one

You'll have learned things in a quarterly one-on-one that change how you manage the person, so make sure that knowledge turns into action.

Send a follow-up email within a day or two. Summarise the development goals you agreed on, any commitments you made, and any next steps. Keep it brief and specific.

Email template

Hi [name],

Thank you for the conversation – I really value this time together. Below is a summary of what we agreed:

– You'll [specific development action], aiming to move from [current skill level] to [target] by [timeframe]. – I'll [manager commitment – feedback, access, introduction, etc.]. – We'll revisit progress at our next quarterly one-on-one on [date].

If I've missed anything, let me know. I'm looking forward to supporting you on this.

Activate the plan. If you agreed to connect them with a senior colleague, make the introduction. If you committed to giving them more scope on a project, follow through. The follow-up email is the easy part – the credibility comes from what happens next.

How skills data changes both conversations

There's a reason check-ins drift toward status updates and quarterly one-on-ones toward vague development chat: managers are going in without a clear picture of the person.

When you know what someone can do from a live, current skills profile they've maintained themselves, rather than from a year-old CV or a performance review from six months ago, the conversation changes. You can ask specific questions. You can notice gaps between where they are and where they want to go. You can see whether the work you're assigning them is developing the skills they care about, or just consuming them. If you want to understand the scale of the skills visibility problem most organisations are working with, the MuchSkills skills statistics playbook pulls together the research in one place.

My Circle in MuchSkills gives managers a real-time view of every direct report's skills, certifications, development goals and availability. Before a check-in, it takes two minutes to see where someone is. Before a quarterly one-on-one, it gives you a shared, concrete starting point for the development conversation – instead of starting from scratch every time.

The Goal Setting feature lets employees set development goals, get AI guidance on the route to each goal, find peers working on the same skills, and track progress over time. When those goals are visible to their manager, the quarterly one-on-one has an agenda built in. And because MuchSkills tracks motivation alongside skill level – through the Skill Will methodology – managers can see what someone can do and also what they actually want to do more of.

MarcusThomas, a creative and technology agency using MuchSkills, saw this directly. As Gonzalo M., VP of Technology Enablement, puts it: "Every employee now knows what's expected, how to grow, and where to go next, and our managers are having better 1:1s than ever."

That is what skills data adds: conversations worth having.

Make your next one-on-one count

If your check-ins are feeling like catch-ups and your quarterly one-on-ones are producing vague commitments that don't go anywhere, the fix usually lies in the foundation underneath the meetings.

When managers can see what their people can actually do, what they want to develop, and where the gaps are, every conversation gets more specific. And specific conversations are the ones that lead to real growth.

Book a demo to see how MuchSkills gives managers the skills visibility they need to have better conversations – and to build teams that keep developing while they deliver.

Frequently asked questions

Not answered here? A real person replies, usually the same working day.

Every question, in the FAQ
How often should managers hold one-on-one meetings with employees?

Weekly employee check-ins are the standard for most teams – short, work-focused, fifteen to thirty minutes. Every quarter, one of those meetings should be extended into a deeper, development-focused employee one-on-one of at least an hour. For less experienced employees or those in a period of change, more frequent check-ins may be appropriate. The key is consistency – irregular meetings undermine the trust and continuity that make these conversations useful.

What is the difference between a check-in and a one-on-one?

A check-in is work-focused: progress, blockers, priorities, and team coordination. A 1:1 (or one-on-one) is person-focused: growth, development, motivation, and career trajectory. Both are scheduled between a manager and a direct report, and both form part of continuous performance management – but they serve different purposes and shouldn't be conflated. Running a quarterly one-on-one as if it were a check-in is one of the most common reasons development conversations stay shallow.

How do you make check-ins more effective?

Preparation is the single biggest lever. Managers who review what their direct reports are working on – and what's changed in their skills and goals – before each check-in ask better questions and surface problems earlier. Consistency matters too: a check-in that happens every week, even briefly, builds more trust and continuity than an occasional longer meeting. And following through on commitments made in the meeting is what turns a good check-in into a foundation for accountability.

What should you discuss in a quarterly one-on-one?

The quarterly one-on-one should cover four areas: reflection on the period since the last meeting (achievements, challenges, what was learned), the employee's current energy and engagement (what's working, what isn't, whether their skills feel well-used), development goals for the next period (specific, agreed, and owned by the employee), and anything the manager can do differently to support their growth. The best quarterly one-on-ones are driven by the employee's preparation – which is why sending a self-reflection questionnaire a week before the meeting makes a material difference to the quality of the conversation.

Put the playbook to work

MuchSkills gives you the live skills data these playbooks assume: who can do what, where the gaps are, and who wants to grow.

All playbooks

Checking Daniel’s calendar...

Ask us anything

A real person replies, usually the same working day.

Live webinar

Register for our next webinar