Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

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

Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.
Build the whole product (Oct 6)
Your code is only part of the product
Input metrics lead to outcomes (Sep 1)
An easy to understand example of using input metrics to track progress toward an outcome.
Lagging Outcomes (Aug 22)
Long-term things often end up off a team's goals because they can't see how to define measurable outcomes for them. Here's how to solve that.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2024 Adam Kalsey.