Need someone to lead product or development at your software company? I lead product and engineering teams and I'm looking for my next opportunity. Check out my resume and get in touch.

One on One meetings for managers: Frequency and Duration

Freshness Warning
This blog post is over 1 year 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 Components of A Developer Experience (Sep 19)
Making your API a well-rounded product will help developers decide if your API is right for them and help grow their usage.
Principles of Developer Experience: An Introduction (Sep 15)
You can create a great developer experience for everything you build. Introducing the six principles of developer experience.
The KPI that measures Product-Market Fit (Sep 9)
If you ask this question to a different small group of your users every week, you can measure trends over time to determine if you're moving toward product-market fit.
Don't use NPS to measure user happiness for enterprise software (Sep 7)
Measuring the satisfaction and enjoyment of end users is a key to unlocking product-led growth. Net Promoter Score is the wrong tool for this.
Ask One Question To Help You Reach Product-Market Fit (Sep 3)
Learn what adjacent problems you need to solve to become twice as valuable to your customers.
How to scale your product team from one product manager to an entire organization (Aug 25)
As your product management team scales, you'll have issues around redundancy, communication, and consistency. Here's now you might solve those.
Software engineering manager interview questions (Aug 6)
Here are some questions I like to use to get a sense of who an engineering manager is and how they work.
A framework for onboarding new employees (May 15)
There’s no single good way to onboard an employee that works for every role. Here's a framework for creating a process that you can adapt to each situation.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2020 Adam Kalsey.