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

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

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.

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

Think Systems, not Symptoms
Dec 15: Piecemeal process creation frustrates teams and slows work. Stop patching problems and start solving systems. Adopting a systems thinking approach helps you design processes that are efficient, aligned with goals, and truly add value.
Your Policies Aren’t Your Culture
Dec 13: Policies guide behavior, but culture is the lived norms and values of your team. Policies reflect culture -- they don’t define it. Netflix’s parental leave shift didn’t change its culture of freedom and responsibility. It clarified how to live it.
Lighten Your Process Burden
Dec 7: Everyone hates oppressive processes, but somehow we keep managing to create them.
Product Add-Ons Are An Expansion Myth
Dec 1: Add-ons can enhance your product’s appeal but won’t drive significant market growth. To expand your customer base, focus on developing standalone products.
Protecting your Product Soul when the Same Product meets New People.
Nov 23: Expand into new markets while preserving your product’s core value. Discover how to adapt and grow without losing your product’s soul.
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.

Older...

What I'm Reading