Destava

What to Do When Colleagues Undermine You

When a colleague talks over you, dismisses your input, or claims ownership of your work, ignoring it rarely stops the behavior. You need specific conversational boundaries, disciplined documentation, and a clear standard for when to move on.

How to respond in the moment

Passive responses teach difficult peers that your contributions can be overridden without friction. You don't need an angry confrontation—you need calm, audible boundaries delivered the second the behavior occurs.

If someone cuts you off in a meeting, don't stop speaking immediately. Finish your sentence or use a neutral redirect: "I have one more point on these projections, then I will hand the floor to you."

When a coworker restates your idea as their own, validate the agreement while attaching your name back to the initiative: "I am glad you agree with the recommendation I shared in yesterday's memo. Here is how we should execute it."

For dismissive remarks, ask for specifics: "What data leads you to believe that approach will fail?" Forcing them to explain their objection usually exposes the lack of substance behind it.

Document patterns, not feelings

As explored in a Slate advice column, feeling undermined is rarely about one explosive event. It accumulates as small slights that leave you questioning your standing. Because subtle undermining is easy to deny, documentation must focus on operational facts.

After decisions are made verbally, send a short email: "To confirm our discussion from this morning, I will own the client presentation draft, and Sarah will handle the dataset by Thursday." Keep a personal, off-company log noting dates, who was present, what was agreed upon, and what was disrupted. Stick entirely to verifiable facts. Also save an ongoing folder of written praise, client notes, and completed milestones as ready evidence of your actual output.

Frame the issue for your manager

Complaints about personality conflicts are often dismissed as interpersonal friction. To get results, connect the colleague's behavior directly to team efficiency, deadlines, and project risk.

Instead of saying, "Alex does not respect me," say: "When Alex alters project scopes without including me, it creates duplicate work and delays our release schedule." Then propose a structural fix: "To prevent cross-communication, I suggest we formalize sign-offs so no deliverables move forward without the project lead's explicit review."

If you want to pressure-test your phrasing before meeting with leadership, you can talk through the conversation with Destava's AI career manager to keep your tone objective.

When to plan your exit

If you have addressed the behavior directly, established clear written records, and presented the impact to leadership with no change, the issue is structural. A company culture that tolerates quiet undermining rarely reforms from the bottom up. Protect your energy by shifting focus to the open market. Maintain your daily boundaries at the office and build your pipeline of new roles.

Keep reading