One on One meetings for managers: Frequency and Duration

Freshness Warning
This blog post is over 4 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

The Trap of The Sales-Led Product (Dec 10)
It’s not a winning way to build a product company.
The Hidden Cost of Custom Customer Features (Dec 7)
One-off features will cost you more than you think and make your customers unhappy.
Domain expertise in Product Management (Nov 16)
When you're hiring software product managers, hire for product management skills. Looking for domain experts will reduce the pool of people you can hire and might just be worse for your product.
Strategy Means Saying No (Oct 27)
An oft-overlooked aspect of strategy is to define what you are not doing. There are lots of adjacent problems you can attack. Strategy means defining which ones you will ignore.
Understanding vision, strategy, and execution (Oct 24)
Vision is what you're trying to do. Strategy is broad strokes on how you'll get there. Execution is the tasks you complete to complete the strategy.
How to advance your Product Market Fit KPI (Oct 21)
Finding the gaps in your product that will unlock the next round of growth.
Developer Relations as Developer Success (Oct 19)
Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers spend most of their time on something else.
Developer Experience Principle 6: Easy to Maintain (Oct 17)
Keeping your product Easy to Maintain will improve the lives of your team and your customers. It will help keep your docs up to date. Your SDKs and APIs will be released in sync. Your tooling and overall experience will shine.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2023 Adam Kalsey.