The Permission You Were Never Given

Names and identifying details have been changed to protect privacy.

Sofia came to me with a question she framed as a tactical one: how do you negotiate a promotion when your manager keeps moving the goalposts?

By the end of our first session, we'd established that the tactics weren't the problem.

She was a senior engineer in everything but name — running the architecture decisions, onboarding junior devs, driving the technical roadmap for a product line. Her manager kept describing her as "almost ready." She'd been almost ready for twenty-six months.

What we spent our sessions on wasn't how to ask for what she deserved. It was the question underneath that one: why had she kept waiting for someone else to confirm that she deserved it?

There's a specific dynamic I see often in women who've been in majority-male engineering environments for a while. They become extraordinarily good at reading the room — at sensing what's wanted, what's safe, what will land well. That skill is genuinely useful. It's also, in certain organizations, a way of outsourcing your own authority. You start to feel like your competence only counts once someone else has ratified it.

Sofia wasn't lacking skills or leverage. She was waiting for permission that was never coming.

We worked on the internal shift first: what would it mean to act as though the title were already yours? What decisions would you make differently? What would you stop hedging? She started showing up that way in meetings — not aggressively, just with less apology built into her posture.

Three months later she had a new job. Better title, significantly better pay, a team that had been actively recruiting her for a year. She'd turned them down twice because she was waiting to be deemed ready by the organization that was actively undervaluing her.

The permission was never coming. So she stopped waiting for it.