What Not to Discuss in a One-on-One Meeting: 10 Topics to Avoid or Handle Differently

One-on-one meetings are designed for conversations that deserve individual attention. They give managers and employees room to discuss challenges, feedback, workload, development, working relationships, goals, and support.

That does not mean every workplace topic belongs there.

Some subjects are better handled in a project meeting or team channel. Others involve information a manager should not share at all. And certain serious issues may first come up during a one-on-one, but require a formal process beyond the meeting.

Knowing the difference matters.

The goal is not to make one-on-ones so cautious that managers avoid difficult conversations. In fact, some of the most valuable one-on-ones involve uncomfortable subjects. The goal is to protect the meeting from conversations that are irrelevant, inappropriate, unnecessarily confidential, or better handled somewhere else.

Here are 10 topics managers should avoid or handle differently in one-on-one meetings. 

Does "What Not to Discuss" Mean Difficult Topics Should Be Avoided?

No.

A difficult conversation is not automatically inappropriate.

Managers should still be able to discuss:

• Constructive performance feedback.
• Missed expectations.
• Workload concerns.
• Career dissatisfaction.
• Motivation.
• Compensation questions.
• Employee mistakes.
• Workplace conflict.
• Development needs.
• Feedback about the manager.
• Problems affecting the employee's ability to work effectively.

Many of these are exactly the kinds of subjects one-on-ones are designed to support.

The better question is not:

"Is this topic uncomfortable?"

It is:

"Is a one-on-one the right place, with the right people and the right process, to discuss it?"

A topic may be unsuitable for a one-on-one because it belongs in another meeting, involves information the employee does not need to know, crosses a personal boundary, or requires a formal organizational response.

Quick Guide: What Belongs in a One-on-One?

1. Routine Project Status Updates

What It Looks Like

The manager spends most of the one-on-one asking:

• What did you finish?
• Where are we with the project?
• What's due next?
• Did the client respond?
• When will that task be completed?

By the time the updates are finished, little time remains for anything else.

Why It Doesn't Belong or Needs Different Handling

A small amount of project context is perfectly reasonable. The problem begins when the meeting becomes a private status-reporting session.

Routine updates can often be handled more efficiently through:

• Project-management tools.
• Team meetings.
• Written updates.
• Stand-ups.
• Shared dashboards.

Using the entire one-on-one for status reporting leaves less room for subjects that benefit from private conversation, such as workload, development, feedback, frustration, or manager support.

What to Do Instead

Use project information as a starting point rather than the destination.

Instead of asking:

“What's the status of the project?”

go deeper:

• "What's making this project harder than expected?"
• "Where are you blocked?"
• "Which priority is creating the most pressure?"
• "Is there anything I could do to help you move faster?"
• "What have you learned from the project so far?"

The employee's one-on-one should help the manager understand the experience behind the work, not simply collect information that is available elsewhere.

Important Exception

If a project problem is affecting the employee personally through workload, unclear expectations, difficult collaboration, or a lack of support, it absolutely belongs in the one-on-one. 

The distinction is between reporting progress and discussing what that work means for the employee.

Lighthouse's 10 Myths and Disadvantages of One-to-One Meetings reinforces the importance of protecting 1:1 time from routine status reporting. It argues that managers should vary their conversations rather than discussing the same topics in every meeting, making room for goals, feedback, development, ideas, team relationships, and employee concerns. Regular meetings, thoughtful follow-up, and action items also help ensure important issues surface early and lead to meaningful progress.

2. Detailed Technical or Project Troubleshooting

What It Looks Like

An employee mentions a blocker.

The manager opens a document.

A spreadsheet appears.

Someone starts sharing their screen.

Thirty minutes later, the meeting turned into a detailed working session.

Why It Doesn't Belong or Needs Different Handling

Technical troubleshooting may be necessary, but a one-on-one is often not the best setting for it.

A complicated problem may require:

• Another specialist.
• Additional team members.
• Data.
• Technical documentation.
• Extended analysis.
• A longer working session.

Trying to solve everything during the one-on-one can consume the entire meeting and push aside conversations that are not easy to have elsewhere.

What to Do Instead

Use the one-on-one to understand the blocker and determine what support is needed.

For example:

"It sounds like this needs a deeper technical session. Let's schedule time with the right people rather than using the rest of our one-on-one to troubleshoot it."

The one-on-one can answer:

“What is getting in your way, and what support do you need?”

A separate working session can answer:

"How exactly do we solve the technical problem?"

Important Exception

Simple blockers that can be resolved in a few minutes do not need another meeting.

Use judgment. The goal is not to create unnecessary meetings; it is to prevent a complicated operational problem from taking over the employee's entire one-on-one.

3. Team-Wide Announcements and General Updates

What It Looks Like

Managers use individual one-on-ones to explain the same information repeatedly:

• A new team process.
• A company announcement.
• An upcoming deadline.
• A departmental change.
• A policy update.
• A new project that everybody is joining.

Why It Doesn't Belong or Needs Different Handling

If everyone needs the same information, delivering it individually is inefficient and can create inconsistent messaging.

One employee may receive more context than another. Details may change slightly from conversation to conversation.

The manager also uses valuable individual time to communicate information that could have been shared once.

What to Do Instead

Deliver common information through an appropriate shared channel:

• Team meeting.
• Email.
• Group chat.
• Shared document.
• Company communication platform.

Then use the one-on-one to discuss how the information affects that particular employee.

For example:

"You've seen the announcement about the reorganization. How do you think it will affect your responsibilities?"

That turns a general announcement into a personalized conversation.

Important Exception

Employees may have individual questions or concerns about a team-wide change.

Those absolutely belong in a one-on-one.

The announcement itself may be shared collectively; the employee's reaction to it may require individual discussion.

4. Gossip and Speculation About Coworkers

What It Looks Like

A conversation moves from a legitimate work issue into speculation:

• "I wonder why they promoted her."
• "I heard he's trying to leave."
• "She seems to have problems at home."
• "Management doesn't really trust that team."
• "Everyone knows those two don't get along."

The conversation may feel informal, but the damage can be significant.

Why It Doesn't Belong

Managers have influence over team culture.

When managers participate in gossip, employees may wonder what the manager says about them when they are not present.

Gossip can also:

• Damage trust.
• Create unnecessary conflict.
• Spread inaccurate information.
• Encourage cliques.
• Make the workplace feel less psychologically safe.

A one-on-one being private does not make gossip appropriate.

What to Do Instead

Keep discussions about colleagues focused on workplace behavior and its impact.

For example, this is appropriate:

"I'm having difficulty getting information from Chris before the handoff deadline."

That gives the manager something concrete to address.

This is not useful:

"Chris doesn't seem to care about the team."

Focus on:

observable behavior → impact → next step

rather than assumptions about someone's personality, motivation, or private life.

Important Exception

Employees should be able to raise genuine concerns about coworkers.

The answer is not to shut down those conversations. Managers should help employees separate legitimate workplace concerns from rumors, speculation, and personal criticism.

5. Confidential Information About Other Employees

What It Looks Like

A manager shares details such as:

• Another employee's performance concerns.
• Salary information.
• Medical information.
• Personal circumstances.
• Disciplinary issues.
• Private conversations.
• Reasons behind someone's absence.

The manager may believe the information provides useful context.

Often, it provides more information than the employee needs.

Why It Doesn't Belong

Managers frequently have access to information because of their role.

That access is not permission to share it.

Unnecessary disclosure can damage trust across the entire team. Employees may reasonably wonder whether their own private conversations are being discussed elsewhere.

What to Do Instead

Share only the context the employee needs to understand their own work.

For example, instead of saying:

"Jordan is having performance issues, so I'm transferring some of their responsibilities to you."

say:

"We're redistributing some responsibilities. I'd like to discuss what that means for your workload and priorities."

The employee receives the information they need without unnecessary details about someone else.

Important Exception

There are situations in which managers must communicate changes to other employees.

The key is to share what the employee needs to know, not everything the manager knows.

6. Invasive or Irrelevant Personal Questions

What It Looks Like

Healthy manager-employee relationships often include personal conversation.

A manager may ask about someone's weekend, family, hobbies, or vacation.

That becomes problematic when curiosity turns into pressure.

Employees should not feel required to disclose private information about areas such as:

• Relationships.
• Family plans.
• Health.
• Finances.
• Religion.
• Political beliefs.
• Other sensitive personal matters unrelated to their work.

Why It Doesn't Belong

There is a difference between being interested in an employee as a person and expecting access to their personal life.

Some employees enjoy sharing personal details. Others prefer clear boundaries.

Both approaches can be completely reasonable.

Repeatedly pushing for information can make a supportive conversation feel intrusive.

What to Do Instead

Allow employees to decide how much they want to share.

If something appears to be affecting work, managers can focus on support without demanding unnecessary details.

For example:

"You don't need to give me personal details, but if anything is affecting your workload that I should take into account, let me know how I can help."

This keeps the conversation relevant while respecting privacy.

Important Exception

Employees may voluntarily choose to discuss personal matters because those circumstances affect their work.

Managers can listen with empathy while keeping the focus on appropriate workplace support.

7. The Manager's Personal Complaints and Grievances

What It Looks Like

The manager starts using the employee's one-on-one as an opportunity to vent.

They complain about:

• Senior leadership.
• Other managers.
• Difficult employees.
• Organizational politics.
• Decisions they disagree with.
• Their own workload.
• Internal conflicts.

Occasional honesty is one thing. Turning the employee into the manager's emotional support system is another.

Why It Doesn't Belong

A power difference exists between managers and employees.

When managers vent, employees may feel pressure to:

• Agree.
• Take sides.
• Provide reassurance.
• Keep secrets.
• Manage the manager's emotions.

It can also make employees reluctant to raise their own concerns because the manager already appears overwhelmed.

What to Do Instead

Managers can be transparent without oversharing.

It is reasonable to say:

"This has been a demanding week, so I may need to be more deliberate about priorities."

It is less appropriate to spend the meeting complaining about specific colleagues or leaders.

Managers should use peers, their own manager, coaching, or other appropriate support systems for conversations that primarily concern their own frustrations.

Important Exception

A manager's experience can occasionally provide useful context or show healthy vulnerability.

The question is whether sharing the information helps the employee or mainly helps the manager feel better.

8. Unapproved Promises About Raises, Promotions, or Future Opportunities

What It Looks Like

An employee asks about career progression.

The manager wants to be encouraging and says:

"You'll definitely be promoted this year."

or:

"I'm sure we can get you a substantial raise."

The manager may genuinely believe it will happen.

But the final decision may depend on budgets, leadership approval, performance cycles, headcount, or other factors outside the manager's control.

Why It Needs Different Handling

Compensation and career progression are entirely legitimate topics for one-on-one discussions.

The mistake is not discussing them.

The mistake is presenting an uncertain possibility as a guaranteed outcome.

Unsupported promises can create:

• False expectations.
• Frustration.
• Loss of trust.
• Confusion about decision-making.

What to Do Instead

Clearly separate:

• What has been approved.
• What the manager can recommend.
• What the manager can influence.
• What remains uncertain.

For example:

"I believe you've built a strong case for promotion, and I'm prepared to support it. I can't guarantee the final decision because it goes through a wider review process."

Then discuss what the employee can control.

Questions might include:

• What expectations need to be met?
• What evidence would strengthen the case?
• What development would be useful?
• When should the conversation be revisited?

Important Exception

Managers should not avoid compensation discussions simply because they cannot control every outcome.

Employees deserve honest information about the process and what the manager knows.

9. Formal Disciplinary or Termination Actions Treated Like Ordinary Agenda Items

What It Looks Like

A normal one-on-one is underway.

Halfway through, the manager casually introduces a formal warning, disciplinary action, or termination decision as if it were simply another item on the agenda.

Why It Needs Different Handling

Regular one-on-ones are appropriate places to discuss performance expectations and give timely feedback.

Formal employment actions are different.

Depending on the organization and situation, they may require:

• Specific documentation.
• HR involvement.
• Defined procedures.
• Additional participants.
• Clear communication.
• Organizational policy to be followed.

Managers should not improvise serious formal actions simply because a one-on-one is already scheduled.

What to Do Instead

Address everyday performance concerns early in regular conversations.

Do not save ordinary feedback until a formal process is required.

When a situation does become formal, follow the organization's established procedure.

If a separate meeting is required, hold one.

Important Exception

Performance itself is not a forbidden one-on-one topic.

Managers should discuss:

• Missed expectations.
• Quality concerns.
• Behavioral issues.
• Required improvements.
• Support.
• Progress.

The distinction is between ongoing management and coaching and formal employment action.

10. Serious HR, Safety, Harassment, or Misconduct Issues Handled Only as a Normal One-on-One

What It Looks Like

An employee uses a one-on-one to disclose something serious.

For example, they may describe:

• Harassment.
• Discrimination.
• Threatening behavior.
• A safety concern.
• Serious misconduct.
• Retaliation.
• Another significant workplace issue.

The manager listens but treats it as a normal employee concern that can remain inside the one-on-one.

Why It Needs Different Handling

The employee may have chosen the one-on-one because it was the first place where they felt comfortable raising the issue.

Managers should not discourage that.

But the conversation may need to move beyond the normal one-on-one process.

Serious concerns can carry responsibilities under:

• Company policy.
• HR procedures.
• Safety processes.
• Security procedures.
• Other organizational requirements.

What to Do Instead

When an employee raises a serious concern:

• Listen carefully.
• Avoid dismissing or minimizing it.
• Clarify the important facts without turning the conversation into an unauthorized investigation.
• Avoid promising absolute secrecy if the issue may require escalation.
• Explain what you will do next when possible.
• Follow the appropriate organizational process promptly.

A useful response might be:

"I'm glad you raised this. I want to make sure it's handled properly. I may need to involve the appropriate people, and I'll explain what I can about the next steps."

Important Exception

Do not tell employees that serious issues “don't belong” in one-on-ones.

They may arise there naturally.

The important distinction is:

The issue can be raised in a one-on-one, but the one-on-one may not be where the response ends.

What Should You Discuss in a One-on-One Instead?

Once low-value and inappropriate topics are removed, one-on-ones have more room for conversations that genuinely benefit from individual attention.

Good topics include:

Current Challenges

Discuss what is making work difficult.

Ask:

• "What's getting in your way?"
• "What has been harder than expected?"
• "Where do you feel stuck?"

Workload

Explore whether priorities and capacity are realistic.

Ask:

• "What is taking most of your energy?"
• "Are there priorities we need to reconsider?"
• "What could we simplify?"

Manager Support

Permit employees to talk about what they need from you.

Ask:

• "Where could I be more useful?"
• "Is there anything you need more or less from me?"
• "What could I do differently?"

Feedback

Feedback should move both ways.

Managers can discuss employee performance while inviting feedback on communication, decision-making, and management style.

Career Development

Talk about:

• Skills.
• Career interests.
• Stretch assignments.
• New responsibilities.
• Learning opportunities.
• Long-term goals.

Motivation and Engagement

Ask what is:

• Energizing.
• Frustrating.
• Becoming repetitive.
• Creating interest.
• Affecting motivation.

Team Relationships

Employees should be able to discuss collaboration problems without turning the conversation into gossip.

Focus on specific behaviors, impact, and possible solutions.

Recognition

Do not use one-on-ones only for problems.

Recognize good work and explain what made it valuable.

Employee Ideas

One-on-ones can also surface ideas that employees may hesitate to raise in a larger meeting.

For a broader look at how the purpose and agenda change across weekly, remote, performance, development, and other formats, see our guide to different types of one-on-one meetings.

Don't Confuse "Uncomfortable" With "Inappropriate”

One of the worst ways to use advice about "what not to discuss" is to turn it into an excuse for avoiding difficult conversations.

Good managers still need to talk about uncomfortable subjects.

Performance Problems

If expectations are not being met, discuss them.

Do not wait for a formal review simply because the conversation feels awkward.

Employee Mistakes

Mistakes can become useful coaching opportunities.

Focus on:

• What happened?
• Why did it happen?
• What was learned?
• What should change?

Workload Concerns

Employees should be able to say:

"This isn't sustainable."

Managers need that information early.

Career Dissatisfaction

If an employee feels stuck, a one-on-one is exactly where the conversation may belong.

Compensation

Employees should be able to ask questions about pay, promotion criteria, and career progression.

Managers should simply avoid making promises they cannot guarantee.

Conflict

If a conflict with another employee is affecting the person's ability to work effectively, discuss it.

Keep the conversation focused on specific behavior rather than character judgments.

Feedback About the Manager

Employees should be able to say:

"I needed more context before that decision."

or:

"I'd prefer feedback earlier."

A manager who avoids those conversations misses one of the most useful parts of a one-on-one.

A good rule is simple:

One-on-ones should not avoid discomfort. They should avoid conversations that are irrelevant, inappropriate, unnecessarily confidential, or better handled through another process.

How to Decide Whether a Topic Belongs in a One-on-One

When you are unsure, ask five questions.

1. Is This Primarily About This Employee?

Does the topic involve their:

• Work.
• Development.
• Performance.
• Experience.
• Support.
• Goals.
• Working relationships.

If yes, a one-on-one may be the right place.

2. Could Another Channel Handle It Better?

Would the subject be more efficiently addressed through:

• A team meeting?
• A project-management tool?
• A working session?
• A written update?

If yes, preserve the one-on-one for a higher-value conversation.

3. Am I Sharing Information About Someone Else?

Ask:

"Does this employee actually need to know this?"

If not, do not share it.

4. Am I Crossing a Personal Boundary?

Consider whether the information is necessary to support the employee's work.

If not, allow them to decide whether they want to share it.

5. Does This Require a Formal Process?

Some subjects cannot be handled solely through a manager's ordinary conversation.

If an issue involves serious misconduct, formal discipline, safety, HR procedures, or another defined organizational process, follow that process.

An easy framework is:

Individual + useful + appropriate → discuss in the one-on-one.

Operational + shared → move to another work channel.

Confidential or invasive → don't share or pressure.

Serious or formal → follow the appropriate process.

One-on-one meetings should create room for conversations that employees and managers cannot easily have elsewhere.

That makes protecting the time important.

Routine status reporting, detailed technical troubleshooting, and team-wide announcements often belong in more efficient channels. Gossip, unnecessary confidential information, intrusive questions, and manager venting do not belong in the conversation at all. Meanwhile, formal disciplinary actions and serious workplace concerns may require processes that go beyond a normal one-on-one.

But managers should not misunderstand these boundaries.

Performance feedback, workload concerns, compensation questions, conflicts, career dissatisfaction, mistakes, and employee feedback can all be addressed in a productive one-on-one.

The deciding factor is not whether the conversation is difficult. It is whether the one-on-one is the right place, involving the right people, with the right level of privacy and the right process.

Protect those boundaries, and the meeting has more room for what it should do best: help managers understand employees, surface problems early, support development, strengthen communication, and make it easier to have the conversations that actually matter.