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

Management & Leadership

Do you need a 1:1 if you're regularly communicating with your team?

One of the dangers of having a scheduled 1:1 meeting is that your report will hold everything and just talk to you then. They may think that because they have a weekly with you that this is the only time you’re available to them. You need to make it explicit that you’re available all the time. Things that can wait to the 1:1 should (they might solve it on their own if given the time), but they can always talk to you.

I tell my teams that I’m never doing something that’s more important than them. If they need me, grab me casually or schedule something with me. And if it looks like I’m completely booked up, tell me they need me and I’ll clear space. My job is to make the team successful.

The opposite problem can also happen. People can think that because they talk to you regularly, the 1:1 isn’t needed. I hear people say, "my manager is always available and we talk every day, so we only schedule a 1:1 for 15 minutes once a month." That’s completely missing the purpose of the 1:1.

These people are treating the 1:1 as a fail-safe: "at least if we all get busy, I know we’re going to check in every once in a while." That’s a certainly a function of the 1:1, but it’s not the prime function.

The 1:1 is there to work on how the work happens. It’s to dive deeper into why we’re doing things and how we grow. It’s to make us all better at our jobs. You’re simply not having these levels of conversation in hallway conversations or in your chat apps.

Think of the times you’ve gone to lunch or dinner with the boss, just the two of you. The discussions you had were deeper than usual, whether they were about family, office politics, or debating if you should move to microservices. How great are those moments?

Now imagine you could do those every week, with every employee. These are your 1:1s.

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