Encouraging 1:1s from other managers in your organization

Freshness Warning
This blog post is over 3 years old. It's possible that the information you read below isn't current and the links no longer work.

If you’re managing other managers, encourage them to hold their own 1:1s. At a minimum, doing them with their direct reports is non-negotiable. It’s such an important tool for managing and leading that everyone needs to be holding them.

I encourage, but don’t require, them to do skip levels and peer 1:1s, too. They’ll get huge benefits from seeing the bigger picture of the company, and you’ll find that managers are less threatened by you doing skip-levels with their reports if they’re doing skip levels of their own.

Most managers don’t do 1:1s well, and like everything else, it’s a learned skill. Teach them this skill.

Use your 1:1s with them to teach by example, and periodically ask them how their 1:1s are going. Dive deep into the problems they struggle with holding a 1:1.

Create templates for agendas, distribute ideas for how to get feedback, point them at blog posts like mine, and otherwise give them a starting point for learning their own effective 1:1 style.

If you have enough managers, invest in some training time with them. Teach them how to avoid falling into talking about the tactical day to day. Walk through what a 1:1 should look like. Have them practice on each other.

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

Recently Written

The Trap of The Sales-Led Product (Dec 10)
It’s not a winning way to build a product company.
The Hidden Cost of Custom Customer Features (Dec 7)
One-off features will cost you more than you think and make your customers unhappy.
Domain expertise in Product Management (Nov 16)
When you're hiring software product managers, hire for product management skills. Looking for domain experts will reduce the pool of people you can hire and might just be worse for your product.
Strategy Means Saying No (Oct 27)
An oft-overlooked aspect of strategy is to define what you are not doing. There are lots of adjacent problems you can attack. Strategy means defining which ones you will ignore.
Understanding vision, strategy, and execution (Oct 24)
Vision is what you're trying to do. Strategy is broad strokes on how you'll get there. Execution is the tasks you complete to complete the strategy.
How to advance your Product Market Fit KPI (Oct 21)
Finding the gaps in your product that will unlock the next round of growth.
Developer Relations as Developer Success (Oct 19)
Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers spend most of their time on something else.
Developer Experience Principle 6: Easy to Maintain (Oct 17)
Keeping your product Easy to Maintain will improve the lives of your team and your customers. It will help keep your docs up to date. Your SDKs and APIs will be released in sync. Your tooling and overall experience will shine.


What I'm Reading


Adam Kalsey

+1 916 600 2497


Public Key

© 1999-2022 Adam Kalsey.