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.

One on One Meetings - a collection of posts about 1:1s

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.

I’ve been blogging a lot recently about holding 1:1 meetings with your reports. Here’s the entire collection of these works.

One on One meetings for managers
A one on one meeting is one of the top ways you can build your managerial leverage
One on One meetings: Frequency and Duration
How long should your 1:1s be? How often should you run them?
Do you need a 1:1 if you’re regularly communicating with your team?
You’re simply not having deep meaningful conversation about the process of work in hallway conversations or in your chat apps.
What should you talk about in a 1:1?
Who sets the agenda? What should you discuss, and what should you avoid discussing?
What agenda items should a manager bring to a 1:1?
At least 80% of a 1:1 agenda should be driven by your report, but if you also to use this time to work on things with them, then you’ll have better meetings.
Handling “I don’t have anything to talk about” in your 1:1s
When someone says they have nothing to discuss, they’re almost always thinking too narrowly.
Are 1:1s confidential?
Is the discussion that occurs in a 1:1 confidential, even if no agreed in the meeting to keep it so?
Skip-level 1:1s are your hidden superpower
Holding 1:1s with peers and with people far below you on the reporting chain will open your eyes up to what’s really going on in your business.
Encouraging 1:1s from other managers in your organization
If you’re managing other managers, encourage them to hold their own 1:1s. It’s such an important tool for managing and leading that everyone needs to be holding them.

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.