For 15-minute non-fiction book summaries of best-selling books, check out sumizeit.com.

TL;DR

For my entire career, I'd never had a female boss — so when I was reassigned to one, I honestly didn't know what to expect. A year later, I can tell you the problem was never her gender. It was her management. Impossible deadlines, "just use AI," a fake-anonymous survey, feedback weaponized against me, a month of throwaway work, and total indifference when I was sick — until the work she'd ignored for a year saved the company millions. Here's the full story, and what it taught me about surviving a manager who only believes what she sees with her own eyes.

The Reassignment

I still remember the exact moment I found out.

It was a Tuesday, a calendar invite I hadn't requested, a title that read "Team Transition — Quick Sync." I sat in the meeting nodding while the words rearranged my world: new manager, effective next week. And buried in my own reaction was a quiet, slightly embarrassing realization — in my entire career, I had never once had a female boss.

I want to be honest about that, because it's where the story starts. I didn't know how to feel. Not dread, exactly. Just an awareness that I was walking into something unfamiliar, and that I had no map for it. I told myself the only sensible thing: a good manager is a good manager, and I'd give her every benefit of the doubt.

What I learned over the following year had nothing to do with gender and everything to do with how one specific person chooses to lead. But I didn't know that yet. On that Tuesday, I just closed my laptop, took a breath, and decided to make the best of it.

The Clock That Never Made Sense

The first cracks showed up in the timelines.

She'd assign me a task — something genuinely complex, the kind of thing that has hidden depths you only discover once you're elbow-deep in it — and attach an expectation that it be finished in a fraction of the time it actually required. Not an aggressive-but-fair deadline. An impossible one.

When the work inevitably took longer, she didn't ask the question a good manager asks: What's blocking you? What do you need? Instead, one afternoon, she tilted her head and said the line I'll never forget.

"Why didn't you just use AI to get it done?"

I sat there for a second, genuinely unsure how to respond. As if the careful, layered problem in front of me would simply dissolve if I typed it into a chatbot. As if expertise and judgment were a slow, quaint alternative to a magic button I'd stubbornly refused to press. It was the first time I understood that, to her, the difficulty of my work was not real. Only the deadline was real.

The Chorus That Spoke for Her

The second thing I noticed was that she never seemed to form an opinion about my work from my work.

She formed it from other people. Feedback never arrived as "I noticed" or "I think." It always came wrapped in a vague, faceless chorus: "The team thinks X." "People have been saying Y." I'd sit across from her trying to figure out who, exactly, this team was, and what I could possibly do about an accusation with no author.

It created a strange, paranoid weather in the office — a sense that the way to get ahead wasn't to talk to each other but to talk about each other, to her, in private. Every conversation started to feel like it might end up quoted back to me later, stripped of its name, presented as the consensus of the room.

Then came the survey.

She passed around what she called an anonymous survey, asking each of us to grade her as a manager. I want to stress the word anonymous, because it was doing a tremendous amount of dishonest work. The survey was not anonymous. Anyone paying the slightest attention could see that. And I, foolishly trusting the premise, answered honestly. In one box, I wrote something gentle and constructive: I wished the team were more collaborative.

In our very next one-on-one, she pulled out that feedback like a prosecutor producing evidence.

"So," she said, leaning back. "You mentioned collaboration." And then she proceeded, point by point, to list all the ways I wasn't collaborative. My own constructive note, handed back to me as an indictment. I learned the lesson instantly and permanently: feedback, in her world, was not a gift. It was a trap with my name on it.

Different Rules for Me

Favoritism is one of those things you feel long before you can prove it.

It showed up in small, deniable ways. My pull requests would get review comments — normal, healthy, this-is-how-engineering-works comments — and she'd treat the very existence of feedback on my code as a failure. As if my work should arrive flawless and merge untouched, while everyone else got the ordinary back-and-forth of professional review without it being treated as a character flaw.

I'd watch a colleague get the same kind of comments I got, and nothing happened. No raised eyebrow. No quiet note in the file she clearly kept on me. The standard simply bent depending on who was standing under it.

And underneath all of it ran the deepest problem of all: she did not listen to me. I'd explain something — clearly, I thought — and watch it bounce off. I'd explain it again. Sometimes a third time, in a third way, before the idea finally landed. Words, coming from me, seemed to carry almost no weight. I started to feel like a radio playing in another room: technically audible, easy to tune out.

A Month of Throwaway Work

If you want to understand what bad management actually costs, count the throwaway work.

It started with the tickets. The JIRA tickets she handed me were frequently wrong — outdated information, requirements that no longer matched reality, instructions that pointed at a version of the project that had quietly ceased to exist. I'd build exactly what the ticket said, only to discover the ticket had been lying to me.

The worst stretch was a full month. An entire month of my life poured into a project I'd been explicitly told to build — which turned out to be the wrong project entirely. Not late. Not flawed. Wrong. Work that went straight into the bin, thirty days of effort that existed only as a lesson in how badly a team can be steered.

Another time, I was handed a ticket and got to work, and only when the designer happened to look over did the truth surface.

"Wait," the designer said, frowning at my screen. "That's not what I asked for at all."

The requirements in my ticket and the thing the designer actually wanted were two different products. I had been moments from shipping another pile of throwaway work, saved only because someone outside the chain of command stumbled into the conversation at the right time. The pattern was unmistakable: the information flowing down to me was unreliable, and I was the one who paid for it in wasted weeks.

The Manager Who Only Believes Her Own Eyes

Here is the thing that defined working with her, the single trait that explained almost everything else: she only believed what she saw with her own eyes.

Words didn't work. Explanations didn't work. Evidence I described didn't work. The only way to convince her of anything was to engineer a situation where she witnessed it directly and could no longer deny it. Until that moment, my account of reality was treated as opinion at best, excuse-making at worst.

Nowhere was this clearer than with the work I'd inherited from my previous manager. For a solid year, she dismissed it. It wasn't a priority. It wasn't interesting. It wasn't, in her framing, important. I kept maintaining it anyway, because I understood — from the boss before her — what it actually did for the business.

Then it saved the company millions of dollars.

Suddenly, overnight, the project I'd been quietly carrying for a year became important. The thing she'd waved off was now, in her retelling, a strategic priority she'd recognized all along. I didn't get an apology. I didn't need one. But I did file away the lesson, hard and clear: with this manager, a year of being told your work doesn't matter can be erased in a single afternoon by a number large enough to make her look up. Only the visible, undeniable result counted. Everything before it was noise.

The Day I Was Sick

I could have absorbed all of the rest. The deadlines, the chorus, the trap survey, the throwaway months — those were exhausting, but they were professional problems, and professional problems you can grind through.

What I couldn't forgive was how she handled me being sick.

My previous manager, when I told him I wasn't well, would lean in and problem-solve with me. "Okay," he'd say, "let's figure out how to make this work. What can we move? What can wait?" Being human wasn't a liability to him; it was just a variable to plan around.

I told my new manager, more than once, that I was sick. It registered as nothing. When I finally tried to take time off to recover, her response was not concern. It was a question, delivered flat:

"Why are you taking time off when we have an important production release?"

I told her, again, that I was sick. She didn't care. The release was real to her; my body was not. And rather than lighten the load so I could heal, she did the opposite — she handed me even more work, as if illness were a performance problem to be managed with additional tasks. That was the moment something in me went quiet and final. You can disagree with a manager about deadlines and ticket quality and feedback style. But the way someone treats you when you're at your most human tells you everything you'll ever need to know.

What I Actually Learned

So let me be clear about the lesson, because it isn't the one the setup might suggest.

I started this story admitting I'd never had a female boss and didn't know what to expect. A year later, I can tell you with total confidence: this was never about her being a woman. It was about a specific set of management failures that would have been just as corrosive coming from anyone. Plenty of people have wonderful managers of every gender. Plenty have suffered under terrible ones. The variable that mattered was never gender — it was whether the person listened, trusted, and led with any humanity.

What I took away is a checklist I now carry into every working relationship. A good manager asks what's blocking you before assuming you're the block. A good manager forms opinions from your work, not from an anonymous chorus. A good manager makes feedback safe to give, not dangerous. A good manager gives you reliable information and owns it when it's wrong. And a good manager, above all, treats you like a person when you're sick, scared, or struggling — because how someone leads in those moments is the truest thing about them.

If you're living through a version of this right now, here's what I'd tell you: document everything, protect your energy, and remember that a manager who only believes what she sees is telling you exactly how to survive her — show her the undeniable result, and let the work speak when your words can't. And if you want a faster way to get sharper at managing up and handling difficult people, the books that helped me most are summarized in about fifteen minutes each at sumizeit.com. Sometimes the right idea at the right moment is the difference between enduring a hard year and being quietly destroyed by it.

I survived mine. The work spoke in the end. And I walked away knowing exactly what kind of leader I never want to be.

For 15-minute non-fiction book summaries of best-selling books, check out sumizeit.com.