Taking Up Space

The meeting runs long because someone needed to repeat back what you just said, slightly louder, and receive a round of nodding agreement. If you’ve spent enough time in engineering rooms, you know the shape of it exactly: your idea, someone else’s credit, and an extra ten minutes nobody had budgeted for.

It isn’t always deliberate, and the absence of intent doesn’t make the pattern any easier to sit with.

It also doesn’t confine itself to meeting rooms. The same dynamic surfaces in Slack threads where a point you raised gets re-presented as a new suggestion an hour later, in design documents where your thinking gets absorbed and distilled into someone else’s summary, in code reviews where a pattern you introduced gets cited back to you as a useful reference. The meeting is simply where it’s most legible.

The professional default

Working in a large engineering organisation involves a kind of code switching that rarely gets named directly. The “professional” register that most tech teams operate in isn’t neutral. It maps onto a specific set of behaviours, confident assertion, flat affect, a certain conversational directness that reads as authority, that were largely built by and for men. It functions as the baseline, but it isn’t one.

In practice, this means softening assertions you’re already certain of, because the direct version of the same statement reads poorly in a way it wouldn’t coming from someone else in the room. It means phrasing things as questions when you already know the answer. It means monitoring your tone in real time during meetings, spending attention on calibration that your colleagues aren’t spending, because the cost of misjudging the register falls on you and not on them.

Adopting the default reduces friction. Meetings go better, ideas land more cleanly, people read you as credible and collaborative. The cost is that you’re sustaining a performance of yourself that isn’t quite you, and the fatigue from that is cumulative and specific in a way that’s genuinely difficult to describe to people who’ve never had to do it.

The longer you sustain it, the more unremarkable it becomes, and the harder it gets to notice what the performance is actually costing.

What follows you home

There’s a physical dimension to this that rarely gets named. When you need to be heard and taken seriously in a room where authority is assumed for some people and must be continuously demonstrated by others, the temptation is to pitch your voice lower, to flatten the natural expressiveness out of it, to match the tonal register of the people who get listened to without having to work for it. Especially when you’re the one who actually has the answer. Especially in those moments when it should be obvious that you do, and somehow it still isn’t. You adjust, because the alternative is being talked over for the third time in the same meeting.

But that register doesn’t always stop at the door. Spend enough days performing authority and the people in your personal life start to encounter that version of you instead. You’re coming across as commanding. As bossy. As someone harder and more closed-off than they expected. None of those descriptions feel right, because they’re describing a mode you developed for a completely different context, to survive a completely different set of pressures. What reads as credible and assured in a meeting reads as cold somewhere else, and you’re left managing a perception that was never really yours to begin with.

The self-monitoring tax

What compounds this is the feedback loop it creates. When you hedge, your ideas land with less force. When they land with less force, the instinct is to hedge more aggressively next time, to pre-empt the dismissal before it arrives. After enough iterations, hedging becomes the default register, and somewhere in that process you can start to genuinely believe the qualified version is the correct version.

It isn’t. It’s just the version that learned to make itself smaller.

The monitoring itself carries a weight that never surfaces in any productivity metric. Every thread of attention spent tracking how something is landing, whether an adjustment is needed, whether the tone is reading as intended, is attention drawn away from the actual work. It’s invisible overhead that accumulates across every meeting, every review, every message you softened before sending. Your colleagues aren’t running that process. You are, constantly, and the toll is real even when nobody’s measuring it.

The cost of being overridden

There’s a more concrete form of damage than invisible overhead, and it’s the kind that ends up in your performance record. When your input gets talked over or dismissed, the work continues without it. Decisions get made on the basis of what was heard, not what was said. And then, somewhere down the line, the problem you flagged materialises, or the direction that was chosen turns out to be wrong, and everything has to be unpicked and done again.

The rework is real. The wasted time is real. What’s particularly unpleasant about this is that the rework then reads as failure. You were in the room. You were involved. The project ran into trouble and had to double back, and from above that looks like the team didn’t know what it was doing. The person who had the least authority to redirect things, whose concern was talked over before it could land, absorbs a disproportionate share of that impression.

You end up carrying the cost of being dismissed twice: once in the moment when it happens, and again in the aftermath when the consequences get attributed to your competence rather than to the decision that ignored you.

The longer arc

The immediate damage is one thing. The compounding damage is another. Incident by incident, rework by rework, the impression that you’re not quite certain of what you’re doing accumulates quietly in the background of your career. Performance reviews draw on the year’s evidence. Promotion decisions draw on perception. Salary conversations happen in the context of the professional reputation you’ve built, and that reputation is shaped in part by the moments where your input was dismissed and the fallout landed on your record anyway.

The cost isn’t just the bad quarter or the project that had to be unpicked. It’s the senior engineer title that takes longer to arrive, the pay band that doesn’t reflect the work, the sponsorship that goes to someone whose ideas were heard the first time. None of it is dramatic or obvious in any single instance. It’s the slow compounding of a hundred small dismissals into a career trajectory that doesn’t quite match the capability behind it.

When you name it

Then there’s what happens when you try to say any of this out loud.

You’re imagining it. You’re too sensitive. You’re reading intent into something that was perfectly innocuous. The person who talked over you is lovely, actually, and means well, and this isn’t really about gender, is it, because that seems like a stretch. Have you considered that the reason your idea didn’t land was something else entirely?

The dismissal that happened in the meeting gets repeated in the conversation about the meeting, and the second dismissal is often more wearing than the first. At least in the meeting, the subject was the work. In the debrief, the subject is your perception, your reliability as a narrator of your own experience. Being talked over is one thing. Being told that what you observed didn’t happen the way you observed it is something else entirely, and it carries its own particular exhaustion.

Confidence as a gendered currency

Men in tech are rewarded for arrogance in ways that women aren’t, and the distinction worth drawing isn’t between arrogance and genuine expertise. It’s between hollow, performative confidence that hasn’t been earned and the real thing, and the uncomfortable part is that the room’s response doesn’t track this distinction at all. Men get the warm reception for the bold claim delivered without substance. Women get the complicated reception for the substantiated view delivered with conviction. The asymmetry isn’t at the edges; it’s the whole shape of the thing.

When a man swings confidently in a room, there’s a particular quality to how other men receive it. It reads less like tolerance and more like genuine pleasure. They lean in, match the energy, reach enthusiastically for alignment. You can watch it happen in real time. The arrogance isn’t just forgiven; it’s enjoyed, rewarded with an animated, engaged response that the most careful and well-reasoned contribution in the room doesn’t reliably get.

When a woman delivers the same thing, the temperature drops. Confidence reads as aggression. Certainty reads as inflexibility. The same words from the same position carry different weight depending on who’s saying them, and the gap between those two receptions is not something you can bridge by adjusting your tone.

I spent a long time trying anyway. Soften the delivery here, add a qualifier there, frame the assertion as a question in this context and a suggestion in that one. The effort was real and the failure was consistent. It didn’t make the ideas land better; it made them easier to dismiss, which is the opposite of what I was trying to achieve. At some point I had to sit with the uncomfortable realisation that I had been working very hard on a problem that was never mine to solve.

Calibration is the wrong frame entirely. The standard isn’t one you can optimise your way into meeting, because it shifts in response to who’s applying it. What looks like a bar to clear is a moving target, and the energy spent chasing it is energy taken from the actual work.

Claim the expertise you have, without apology and without the trailing qualification that signals you’re checking whether it’s acceptable to hold it. If that reads as arrogance in a room where the same behaviour from someone else would read as confidence, that’s information about the room.

Take up the space. Stop managing other people’s discomfort with it.