Skip to main content
AboutWorkServicesWritingPodcastBlogNewsletterBook a call
Performance ReviewsCareer MistakesProfessional DevelopmentWorkplace PoliticsCareer RecoveryCommunicationCareer Path

The Performance Review That Got Me Fired (And the Career Lesson That Saved Me)

I walked into what I thought was a routine performance review. I walked out unemployed. Here's the complete story of how overconfidence and poor political awareness cost me a job—and the framework I built to never let it happen again.

February 20, 2026· 16 min read
The Performance Review That Got Me Fired (And the Career Lesson That Saved Me)

THE MEETING I DIDN'T SEE COMING

November 8th, 2019. 2:30 PM.

"Syed, can you come to the GM's office?"

I grabbed my notebook. Probably a routine check-in. Maybe discussing next quarter's training budget.

I walked in.

My GM sat at the conference table. The Director of HR sat next to her.

That's when I knew.

HR only attends meetings for one reason: terminations or disciplinary action.

My stomach dropped.

GM: "Syed, we need to talk about your performance. Close the door."

What followed was a 22-minute conversation that ended my employment at that property.

Not for theft. Not for harassment. Not for negligence.

For something far more insidious: political blindness and perceived arrogance.

This wasn't a story I wanted to write. Getting fired is humiliating. Admitting you deserved it is harder.

But this experience taught me more about leadership, workplace dynamics, and self-awareness than any success ever could.

Here's what happened, what I did wrong, what I learned, and the framework I built to ensure I never repeat those mistakes.

WHAT ACTUALLY HAPPENED (THE TIMELINE)

Context

I was a Front Desk Supervisor at a 480-room upscale hotel. I'd been in the role for 9 months. Performance was solid—guest scores were up, my team liked me, operations ran smoothly.

But beneath the surface, I was making catastrophic political mistakes I didn't even recognize.

Mistake #1: I Criticized Leadership in Front of My Team (Month 4)

The Situation

Our GM announced a new policy: All front desk agents must upsell room upgrades to every guest. Agents would get $5 commission per upgrade sold.

I thought this was a terrible idea. It felt pushy, transactional, not aligned with our "hospitality-first" brand.

My Response (In Front of My Team)

During a shift meeting, I said

"Look, I know corporate is pushing this upsell thing. Honestly, I think it's a bad policy—it makes us feel like used car salesmen. But we have to comply. Just do your best, and don't stress about it."

What I Thought I Was Doing

Being honest with my team

Building solidarity ("we're in this together")

Taking pressure off them

What I Was Actually Doing

Undermining leadership's decision

Signaling to my team: "You don't have to take this seriously"

Positioning myself as "good cop" vs. management's "bad cop"

What Happened

One of my agents mentioned my comment to the Rooms Director during a one-on-one.

Rooms Director told my GM: "Syed is openly criticizing the upsell policy in front of his team."

This was Strike #1. (I didn't know it at the time.)

Mistake #2: I Went Over My Manager's Head (Month 6)

The Situation

I proposed a new training program to reduce front desk turnover. I presented it to my direct manager (Front Desk Manager) first.

Her response: "I like it, but now's not the right time. We have too much going on. Let's revisit next quarter."

I thought she was being overly cautious. I believed in the project. So I did something stupid.

My Response

I scheduled a meeting directly with the GM (skipping my manager) and pitched the training program.

GM: "This is great, Syed. Why hasn't [your manager] brought this to me?"

Me: "I showed it to her, but she said it wasn't a priority right now. I thought you should see it anyway."

What I Thought I Was Doing

Taking initiative

Advocating for a good idea

Being proactive

What I Was Actually Doing

Disrespecting chain of command

Making my manager look bad (undermining her)

Signaling: "I don't trust my manager's judgment"

What Happened

GM told my manager about the meeting.

My manager pulled me aside: "If you disagree with my decision, we talk about it privately. You don't go around me to the GM. That's not how this works."

I apologized. But the damage was done.

This was Strike #2. (Still didn't realize how serious this was.)

Mistake #3: I Made a Joke at Leadership's Expense (Month 8)

The Situation

At a hotel-wide staff meeting, the GM announced we were implementing a new "guest recovery budget"—$50/agent/month to resolve complaints without manager approval.

After the meeting, in the break room, a few colleagues were talking

Agent: "Do you think we'll actually be able to use that $50, or will management second-guess us?"

My Response (Meant as a Joke)

"Knowing this place, they'll give us $50 and then audit every penny we spend. We'll need a 12-page justification form."

Everyone laughed.

What I Thought I Was Doing

Making a harmless joke

Building camaraderie with team

What I Was Actually Doing

Undermining a positive initiative

Creating cynicism ("management doesn't trust us")

Signaling negativity about leadership

What Happened

Someone mentioned the joke to a manager. It got back to the GM.

This was Strike #3.

The Breaking Point (Month 9)

At my quarterly performance review, I expected positive feedback.

Instead

GM: "Syed, we need to talk about some concerns. Over the past few months, multiple people have reported that you undermine leadership decisions, go around your manager, and make negative comments about management."

I was stunned. I tried to explain

"The upsell comment—I was just being real with my team."

"Going to you directly—I thought I was showing initiative."

"The break room joke—it was just a joke."

GM: "Individually, these might be small. Together, they show a pattern. You position yourself as separate from leadership—like you're on the team's side against management. That's not a supervisor's role. A supervisor bridges the gap between leadership and staff. You're widening it."

I argued. I defended myself. I said I was being misunderstood.

That was my final mistake: I didn't take ownership.

GM: "I don't think you're a good fit for a leadership role here. We're letting you go, effective today."

WHAT I DID WRONG (THE BRUTAL SELF-ASSESSMENT)

It took me 3 months of unemployment and serious reflection to understand what actually happened.

Here's what I learned

Error #1: I Didn't Understand My Role

What I Thought My Role Was

Advocate for my team

Protect them from "bad" policies

Be the "cool supervisor" they could trust

What My Role Actually Was

Execute leadership's vision (even when I disagreed)

Translate corporate decisions into frontline action

Represent leadership to the team AND represent the team to leadership

The Mistake

I positioned myself as "one of the team" instead of "one of the leaders."

Why This is Fatal

When you're in a leadership role (even supervisor), you're no longer "one of the guys." You're management.

If you undermine management, you undermine yourself.

The Correct Approach

If I disagreed with the upsell policy, I should have

Privately discussed concerns with my manager or GM

Publicly supported the policy with my team

Coached my team on how to execute it well (within brand standards)

Script

"I know upselling can feel uncomfortable, but here's how we can do it in a way that feels genuine: [specific examples]. Let's make this work within our hospitality culture."

Error #2: I Confused "Honesty" with "Transparency"

What I Thought

"I'm just being honest with my team. They appreciate that I'm real with them."

The Reality

There's a difference between transparency and undermining.

Transparency: Explaining the "why" behind decisions, even difficult ones.

Undermining: Communicating that leadership is wrong and you're just complying under protest.

What I Should Have Said

Instead of: "I think this policy is bad, but we have to comply."

Say: "Leadership is prioritizing revenue growth this quarter. This upsell initiative is part of that strategy. Here's how we'll make it work."

The Lesson

Your team doesn't need to know your private disagreements with leadership. They need to know you support the direction, even when it's hard.

Error #3: I Didn't Respect Chain of Command

What I Thought

"If my manager isn't moving fast enough, I should escalate to someone who will."

The Reality

Going over your manager's head is a career-killer—even if you're right.

Why

It signals to leadership: "This person doesn't respect authority and can't work within structure."

It destroys your relationship with your manager (they'll never trust you again).

The Correct Approach

If I disagreed with my manager's decision to delay the training program

Option AAccept her decision. Wait for next quarter.
Option BAsk for a follow-up conversation: "I respect that now isn't the right time. Can you help me understand what would need to change for this to be a priority? I want to make sure I'm aligned with your vision."
Option CIf I genuinely believed it was urgent, escalate with my manager's knowledge: "I feel strongly about this. Would you be open to us presenting it to the GM together?"

What I Did Instead

Went around her. Fatal mistake.

Error #4: I Didn't Realize Jokes Have Consequences

What I Thought

"It's just a joke. Everyone knows I'm kidding."

The Reality

When you're in a leadership role, your words carry weight—even casual ones.

Your "joke" becomes the team's belief.

What Happened

My joke about management auditing the $50 budget planted doubt. Even though it was meant to be funny, it made the team cynical about the initiative before it even started.

The Lesson

When you're a leader, you don't get the luxury of casual cynicism. Your team takes cues from you.

If you're negative—even jokingly—they'll be negative seriously.

Error #5: I Didn't Take Ownership When Confronted

What I Did

When the GM confronted me, I defended every action

"That's not what I meant"

"People are misinterpreting me"

"I was just trying to help"

What I Should Have Done

Taken full ownership immediately

"You're right. I see how those actions undermined leadership. I was trying to build rapport with my team, but I crossed a line. I apologize. Here's what I'll do differently moving forward: [specific behavior changes]. Can you give me a chance to rebuild your trust?"

The Reality

By the time I was confronted, the decision to let me go was already made. But my defensiveness sealed it.

If I had owned it immediately, I might have had a chance to course-correct.

THE AFTERMATH: UNEMPLOYMENT AND REBUILD

Month 1 (Shock and Denial)

I was furious. "They fired me for being honest? For taking initiative? This is ridiculous."

I blamed them.

Month 2 (Realization)

I started talking to mentors. One conversation changed everything.

Mentor: "Syed, you were fired for political incompetence. You didn't understand the game you were playing. Leadership roles aren't just about operations—they're about navigating relationships, hierarchy, and perception. You failed at all three."

That stung. But it was true.

Month 3 (Rebuilding)

I started job hunting. But I realized: If I don't fix the underlying behavior, I'll repeat this mistake at the next property.

I built a framework to prevent this from happening again.

THE FRAMEWORK: POLITICAL AWARENESS FOR LEADERS

I now use this framework at every property I work at. It's kept me employed, promoted, and politically savvy.

PILLAR 1: UNDERSTAND YOUR ROLE

The Role Clarity Test (Answer These Questions)

Who do I represent?

Answer: Leadership. Not the team. Leadership.

Your job is to execute leadership's vision, even when you privately disagree.

What's my responsibility to my team?

Answer: Translate leadership decisions into action. Coach them to succeed within the system.

What's my responsibility to leadership?

Answer: Provide frontline feedback. Advocate for your team's needs. But support final decisions.

The Test

If a team member asks: "Do you agree with this new policy?"

Bad Answer: "Honestly, no. But we have to do it."

Good Answer: "I understand why leadership is prioritizing this. Here's how we'll make it work."

PILLAR 2: RESPECT CHAIN OF COMMAND (ALWAYS)

The Escalation Rules

Rule #1: Always go to your direct manager first. Even if you think they're wrong.

Rule #2: If you disagree with your manager's decision, request a follow-up conversation. Use this script:

"I respect your decision. Can you help me understand your reasoning? I want to make sure I'm aligned with your priorities."

Rule #3: Never, ever go over your manager's head without their knowledge.

Exception: If your manager is doing something illegal, unethical, or unsafe—then escalate. But this is rare.

The Test

Before escalating, ask yourself

"If my manager finds out I went around them, will they trust me less?"

If the answer is yes → Don't do it.

PILLAR 3: MANAGE PERCEPTION (NOT JUST REALITY)

The Perception Rule

It doesn't matter what you meant. It matters how it's perceived.

How to Manage Perception

In Meetings

Support leadership decisions publicly (disagree privately if needed)

Use language that signals alignment: "We're focused on..." "Leadership's priority is..." "Here's how we'll deliver on this..."

In Casual Conversations

Avoid cynicism or sarcasm about leadership (even as jokes)

If someone complains about a policy, redirect: "I hear you. Here's how I'm thinking about it: [reframe positively]."

In Written Communication

Emails/Slack can be forwarded. Write as if leadership will read it. Because they might.

The Test

Before saying something about leadership, ask

"If this got back to my GM, would it hurt my reputation?"

If yes → Don't say it.

PILLAR 4: OWN MISTAKES IMMEDIATELY

The Ownership Script

When confronted about a mistake

Step 1: Acknowledge

"You're right. I see how that was a problem."

Step 2: Apologize

"I apologize. That wasn't the impact I intended, but I understand why it was perceived that way."

Step 3: Explain (Briefly, Not Defensively)

"I was trying to [intention], but I see now that I should have [correct action]."

Step 4: Commit to Change

"Here's what I'll do differently: [specific behavior change]."

Step 5: Ask for Feedback

"I want to rebuild your trust. Can you let me know if you see any other areas where I need to adjust?"

The Test

If your first instinct is to defend or explain → Stop. Take ownership first. Explain second (and briefly).

PILLAR 5: BUILD ALLIES (NOT JUST RELATIONSHIPS)

The Political Mapping Exercise

At every property, identify

Who are the key decision-makers? (GM, Rooms Director, DoS, DoF&B)

Who has their ear? (Admins, long-tenured managers, HR)

Who are the influencers? (Respected team members, union reps)

Build relationships with all three groups.

How

Regularly check in: "How can I support your goals this quarter?"

Share wins: "Your advice on [X] really helped—thank you."

Be useful: Offer help on projects, share insights from your area

The Test

If you were fired tomorrow, would 3+ people advocate for you?

If no → You don't have enough allies.

THE RECOVERY: HOW I GOT BACK ON TRACK

I applied to 40+ properties. I was honest in interviews

"I was let go from my last role. I made political mistakes—I undermined leadership, went around my manager, and didn't take ownership when confronted. I've spent the past 3 months reflecting and building a framework to ensure I never repeat those errors. I'm a better leader because of it."

  1. properties hung up on me after that.
  2. properties called me back.

One hired me—as a Front Desk Agent (step down from Supervisor).

I took it. I needed to rebuild my reputation from the ground up.

Month 6 (Proving Myself)

I executed the framework religiously

Supported every leadership decision (even when I privately disagreed)

Respected chain of command (never went around my manager)

Built relationships with key stakeholders

Took ownership of every mistake immediately

Month 11 (Promotion to Supervisor)

My manager pulled me aside

"You've changed. I don't know what happened at your last property, but you're one of the most politically aware people on my team. I'm promoting you to Supervisor."

18 Months Later (Front Desk Manager)

I was promoted to Front Desk Manager at a larger property.

The GM who hired me said

"You have a reputation for being operationally excellent and politically savvy. That's rare."

The irony: I was fired for political incompetence. I became known for political awareness.

THE FRAMEWORKS YOU CAN STEAL

Framework #1: The Pre-Meeting Self-Check

Before any meeting with leadership, ask

What's my goal in this meeting?

How might my words be perceived?

Am I respecting chain of command?

If this goes wrong, can I own it?

Framework #2: The "Disagree and Commit" Protocol

When you disagree with a leadership decision

Step 1Voice disagreement privately to your manager (once)
Step 2If decision stands, commit fully and publicly
Step 3Execute as if it was your idea

Never: Undermine publicly or communicate half-hearted support

Framework #3: The Reputation Repair Plan

If you've damaged your reputation

Month 1: Take full ownership, apologize to those affected

Months 2-3Execute flawlessly on basic responsibilities (rebuild trust in competence)
Months 4-6Go above and beyond (take on projects, help others, demonstrate growth)
Months 7-12Request feedback: "How am I doing? What should I improve?"

Reputation recovery takes 12-18 months minimum. No shortcuts.

WHAT TO DO IF YOU'RE IN TROUBLE NOW

If you recognize yourself in this story

Step 1Stop making it worse (no more undermining, no more going around your manager)
Step 2Request a meeting with your manager: "I want to check in on how I'm doing. Are there any concerns I should be aware of?"
Step 3If they raise concerns, take ownership immediately (use the Ownership Script above)
Step 4Ask for specific feedback: "What would you like to see me do differently?"
Step 5Execute on that feedback religiously for 90 days

If you're already fired

Step 1Reflect honestly (what did you actually do wrong?)
Step 2Build the framework (how will you prevent this next time?)
Step 3Be honest in interviews (own the mistake, share what you learned)

Step 4: Rebuild from the ground up (even if it means a step down)