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

Skip-level 1:1s are your hidden superpower

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.

In addition to 1:1 meetings with your direct reports, you should be hosting periodic 1:1s with people that are further down in the reporting chain and with your peers in other groups.

The skip level 1:1 is a very underutilized tool. A skip-level is a 1:1 conversation with people who report to your direct reports, and perhaps to the people who report to the people who report to your reports.

If you want to really know what’s going on in your organization, you have to talk to the people who are doing the work. You can do this by scheduling a weekly 1:1 with someone under you. It doesn’t need to be the same person each week, and it also doesn’t need to be just one level removed. In fact, it’s useful to constantly rotate between different people for the skip level. As you rise in the reporting structure, you should even schedule 1:1s with people all the way down the ladder to get a sense of what is happening "on the ground." If I were the CEO of a 10,000 person company, I’d be talking to the most junior folks in the company at least a couple times a month.

Don’t just think of skip levels with people under you. Schedule peer 1:1s with folks in other parts of the organization that you work with. If you’re an engineering manager, talk to other engineering managers. Talk to marketing. Talk to product support.

A peer 1:1 will be different in tone than a skip-level, but the desired output is the same. Use these to catch up on what’s going on in your peer’s world. What’s going well, what issues are they seeing? Who is being particularly helpful or difficult? You’re using these to understand the big picture surrounding your work and to make sure that other teams have you in their big picture.

Peer 1:1s can be far more infrequent. For the most part, I find that catching up every 3-5 weeks is plenty, and it’s not terribly harmful if you have to skip them here and there.

Expanding your definition about who to hold 1:1s with will help you have a much better view of what’s happening in your company.

This is one of a series of posts about holding 1:1s. View the rest of the series.

Recently Written

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.
Roadmap Outcomes, not Features
Sep 4: Drive success by roadmapping the outcomes you'll create instead of the features you'll deliver.
Different roadmaps for different folks
Sep 2: The key to effective roadmapping? Different views for different needs.
Micromanaging and competence
Jul 2: Providing feedback or instruction can be seen as micromanagement unless you provide context.
My productivity operating system
Jun 24: A framework for super-charging productivity on the things that matter.
Great product managers own the outcomes
May 14: Being a product manager means never having to say, "that's not my job."

Older...

What I'm Reading