Need someone to lead product management at your software company? I build high-craft software and the teams that build it. I'm looking for my next opportunity. Check out my resume and get in touch.

This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Management & Leadership

One on One meetings for managers: Frequency and Duration

Freshness Warning
This blog post is over 5 years old. It's possible that the information you read below isn't current and the links no longer work.

How long should your 1:1s be? How often should you run them?

My default is one hour once a week for people that report to me. The length is important since it often takes people a long time to come around to bringing up difficult topics. People don’t like to discuss hard things and need some time to warm up before they get going.

Some managers like to do half-hour 1:1s, but I find that’s not enough time to dive into meatier topics, and you’re often just getting to the hard parts of the conversations at 25 minutes in.

If you don’t take up the whole hour, that’s fine. Let your report end early. But if they’re consistently running out of things to say 10-15 minutes in, then you probably need to do some things to help the employee have a more effective 1:1. More on how to do that in a future blog post.

I start with once a week because this is sometimes the only time my team is talking to me, especially if you have a distributed team. While I encourage them to bring up things that can’t wait if they come up between 1:1s, sometimes they just don’t feel comfortable doing that. Having a weekly checkpoint makes sure that things don’t go too long before getting handled.

If someone’s a lot more senior in their role and self-sufficient, it might make sense to push these back to every other week. A CEO probably doesn’t need to talk to the VP of Sales that’s been with them 15 years every single week. Same with the tech lead on your team that’s been a tech lead with this same team for many years. But it’s important to realize that a senior person is only senior for that specific role. If you take a 20-year employee and put them in a new role, they’re no longer senior and probably need to talk a whole lot more.

This is one of a series of posts about holding 1:1s. View the rest of the series.

Recently Written

Building the Next Big Thing: A Framework for Your Second Product
Nov 19: You need a first product sooner than you think. Here's a framework for helping you identify a winner.
A Framework for Scaling product teams
Oct 9: The people, processes, and systems that make up a product organization change radically as you go through the stages of a company. This framework will guide that scaling.
My Networked Webcam Setup
Sep 25: A writeup of my network-powered conference call camera setup.
Roadmap Outcomes, not Features
Sep 4: Drive success by roadmapping the outcomes you'll create instead of the features you'll deliver.
Different roadmaps for different folks
Sep 2: The key to effective roadmapping? Different views for different needs.
Micromanaging and competence
Jul 2: Providing feedback or instruction can be seen as micromanagement unless you provide context.
My productivity operating system
Jun 24: A framework for super-charging productivity on the things that matter.
Great product managers own the outcomes
May 14: Being a product manager means never having to say, "that's not my job."

Older...

What I'm Reading