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

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

Your OKR Cascade is Breaking Your Strategy
Aug 1: Most companies cascade OKRs down their org chart thinking it creates alignment. Instead, it fragments strategy and marginalizes supporting teams. Here's what works better than the waterfall approach.
Your Prioritization Problem Is a Strategy Problem
Jul 23: Most teams struggle with prioritization because they're trying to optimize for everything at once. The real problem isn't having too many options—it's not having a clear strategy to choose between them. Without strategy, every decision feels equally important. With strategy, most decisions become obvious.
Behind schedule
Jul 21: Your team is 6 weeks late and still missing features. The solution isn't working harder—it's accepting that your deadlines were fake all along. Ship what you have. Cut ruthlessly. Stop letting "one more day" turn into one more month.
VC’s Future Lies In Building Winners
Jun 21: AI and megafunds are about to kill the traditional venture model, forcing smaller VCs to stop hunting for hidden gems and start rolling up their sleeves to fix broken companies instead.
Should individual people have OKRs?
May 14: A good OKR describes and measures an outcome, but it can be challenging to create an outcome-focused OKR for an individual.
10 OKR traps and how to avoid them
May 8: I’ve helped lots of teams implement OKRs or fix a broken OKR process. Here are the 10 most common problems I see, and what to do instead.
AI is Smart, But Wisdom Requires Judgement
May 3: AI can process data at lightning speed, but wisdom comes from human judgment—picking the best imperfect option when facts alone don’t point the way.
Decoding Product Leadership Titles
Mar 18: Not all product leadership titles mean what they sound like. ‘Head of Product’ can mean anything from a senior PM to a true VP. Here’s how to tell the difference.

Older...

What I'm Reading