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.

Are 1:1s confidential?

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.

You’re having a 1:1 and someone brings something to you that feels like it needs addressing with someone else. Maybe they’re having a problem with a teammate. Maybe they’ve been approached about a new role. What do you do? Is the discussion confidential, even if they didn’t ask you to keep it so?

Mark Rabkin, VP Engineering and Product Facebook said, "If it’s safe enough to be overheard — it’s not the right content for a 1:1." The very idea of a 1:1 is to talk about things that shouldn’t be discussed in groups. Confidentiality is a requirement.

Skip-level 1:1s are almost always complaint sessions, often about their boss or teammates. You have to keep them 100% confidential. This is hard because it often feels like you need to fix things. You’re the manager after all, and what is your job there for if not to fix things? You must resist this urge. If the team doesn’t feel they can tell you things without it getting out, they will hold back, and you’ll miss out on the benefits of the skip levels.

If Carly tells you she’s thinking of applying for a spot somewhere else in the company, you can’t go tell her boss about it or your trust is blown and the skip levels become useless.

You often have to avoid taking direct action after a 1:1, so you don’t inadvertently leak what was talked about. Evan tells you that his boss is taking forever to approve the latest plans, you’ll have to wait a while to talk about it with his boss, or he’ll think Evan tattled on him.

In 1:1s with your own reports, they’re talking to their boss, so they have an absolute expectation of privacy. Unless you specifically talk to them about bringing someone else into the discussion, their thoughts and concerns should stay completely between the two of you. If you find that you’re regularly talking bringing something up with someone else, then you either have a seriously dysfunctional company, or you’re talking about the wrong things in your 1:1s (hint: stop talking about the work you’re doing).

Of course, if something illegal or unethical is going on, address it right away. Take whatever steps you can to sanitize the source, but you can’t allow bad behavior to continue.

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.