Archegina

The Pink Tax on Tech Promotions

There is a special kind of email that lands in women’s inboxes in tech. It usually starts with we see so much potential in you and ends with a vague reference to a growth opportunity. Between those lines lies a translation you will be doing more work at roughly the same pay and we will call it development instead of exploitation.

Welcome to the pink tax on tech promotions where women often pay extra in emotional labor stretch assignments and invisible responsibilities just to stand still.

Growth opportunity or just more work

The script is familiar. A woman is told she is a natural leader so she is asked to mentor the new hires run the team rituals tidy up documentation and smooth over interpersonal conflicts. None of this appears in her job description or her performance review goals. All of it shows up in how smoothly the team runs.

Then a promotion cycle comes around. She hears we really value everything you do but we would like to see more impact on high visibility initiatives. Translation your work only counts if it suits our definition of impact which suspiciously looks like the already visible work typically done by men.

Meanwhile her male colleague gets promoted for crushing an individual project. He did not mentor anyone. He did not organize anything. He just did the piece with his name on it and loudly.

The hidden premium women pay

In technology women are often nudged toward the glue work. They are asked to take notes facilitate meetings onboard new teammates and keep track of decisions. All vital tasks. All rarely recognized as promotion worthy.

There is also the expectation that women be team players. When a leader says we need someone to step up it is amazing how often eyes drift toward the woman who seems reliable. She will feel guilty saying no. She will not let the team fail. She will figure it out.

So she agrees. She stays late. She diffuses conflict. She translates requirements between business and engineering. She handles every We just need someone organized conversation. Then she is told during review time that she needs to better prioritize and avoid burnout as if the mountain of unpaid leadership she carried was a personal hobby.

That is the pink tax on career advancement. You pay in time and emotional energy. The receipt is missing.

How the pink tax shows up in promotion conversations

Let us talk about the phrases you hear as a female technologist gunning for promotion.

You are not quite there yet but this next year will be big for you. You just need to prove yourself a bit more. No one ever defines more.

You are so valuable where you are. We do not want to lose you in this role. It sounds flattering. It is code for you are holding together a mess we do not want to fix structurally.

This is a stretch opportunity that will position you well next cycle. Somehow next cycle keeps moving like the cloud migration timeline.

We need you to show more leadership. You point to all the mentoring cross team problem solving and initiative you did. They say yes but we mean capital L leadership the kind that conveniently looks just like what your male counterpart gets to do during business hours.

The result is a career treadmill. You run. You sweat. The scenery barely moves.

How to tell if you are paying the pink tax

A few diagnostic questions.

Are you regularly asked to take on responsibilities that are framed as good exposure but do not come with updated title pay or clear metrics

Are you doing significant work that does not map directly to the competency framework used for promotions in your company

When you look at the last few promotions on your team do the men appear to have done more visible individual contributor work while women did more team support work

If you answer yes to most of these welcome to the club you never asked to join.

Negotiating the real value of growth

You cannot single handedly dismantle systemic bias. But you can stop subsidizing it quietly. The key is to treat every growth opportunity like a contract negotiation not a favor.

First get explicit. When someone offers you extra responsibility ask what title level is this work typically associated with. How will success be measured. How will we document that I took this on.

Second set time limits. I am willing to lead this initiative for two quarters with the expectation that we review scope and impact before extending. This signals you are strategic not endlessly available.

Third tie it to promotion criteria. If your company has a career ladder print it. Literally. When they say we have a growth opportunity say I want to make sure this maps to the expectations for the next level. Which competencies does this demonstrate.

If they cannot answer that question you have discovered unpaid administrative labor disguised as development.

Saying no without tanking your reputation

Women are often punished socially for refusing unpaid work. You might be called difficult not a team player or too focused on yourself. Which is weird because career ladders are individual by design.

You can decline gracefully while still being collaborative.

You can say this sounds like an important effort but my current workload is fully committed to these high priority projects. If this is a critical need we should discuss deprioritizing something else or adjusting my role formally.

You can offer alternatives. I cannot lead this but I can help define the scope and process so someone else can pick it up. That shows you care about the work without automatically being the one who owns it.

Most importantly do not apologize for protecting your time. Men do not.

Mentoring without becoming the unpaid parent of the team

Women in tech tend to be magnets for mentoring requests especially from junior employees and particularly from other underrepresented folks. It is important work. It is also time consuming and rarely measured.

You do not have to stop mentoring. You do have to make it sustainable.

Group your mentoring. Run monthly office hours instead of fifteen scattered coffee chats.

Make your mentoring visible. Mention it in your self review. I mentored five junior engineers this year and supported two in achieving promotions.

Ask leaders to recognize it. When they say we value your impact you can say part of that impact is consistent mentoring which helps with retention and performance. How does that factor into our promotion discussion.

If the answer is some version of it does not you have clarity.

Helping other women spot and resist the pink tax

As a counselor you are going to see this pattern over and over. She was told to be patient. She was given big responsibilities but not the authority or title to match. She was asked to prove it twice.

You can arm women with scripts.

Before accepting anything they can ask what is the scope what are the success metrics and how will this be reflected in my role definition.

During performance season they can say I am doing work at level X. I would like my title and compensation to reflect that. Here are concrete examples.

When being told to wait one more cycle they can respond I appreciate the feedback. What specifically is missing that someone at the next level today already demonstrates and what projects will allow me to show that in the next three to six months.

You are not teaching them to be aggressive. You are teaching them to invoice.

Companies can do better and it is in their interest

If you ever get a chance to advise leadership here is the business case. The pink tax burns out your best people. When women keep doing the glue work without reward they leave. Replacing them costs more than promoting them fairly ever would.

You can recommend a few structural fixes.

Include glue work and mentoring in formal promotion criteria.

Audit who is doing the invisible work on each team and redistribute.

Require that stretch assignments come with written expectations and a path to recognition.

Most importantly train managers to recognize that saying she is not quite ready yet without specifics is not feedback. It is bias with better grammar.

The pink tax is not just about money. It is about constantly asking women to over perform to be seen as equal. That is not a growth opportunity. That is a slow leak in your pipeline of leaders.

Resistance Is Not Futile It Is Exhausting

If you have ever tried to roll out a new tool process or system in a technology organization you already know resistance is not futile it is immortal. It survives leadership emails all hands meetings and even the dreaded mandatory training. It especially thrives in that one manager who proudly announces we have always done it this way as if that were a compelling argument for anything other than paper timesheets.

As a woman leading organizational change in tech you are not just fighting legacy processes. You are also navigating politics fragile egos and the unspoken rule that the person who touches the workflow first becomes the unofficial help desk forever.

The cult of we have always done it this way

You meet them in every department. The veteran engineer guarding a homegrown script like it is a family heirloom. The finance lead who has a twenty year old spreadsheet that must be handled with reverence. The operations manager whose personal email folder structure predates the cloud.

They are not villains. They are the human embodiment of risk aversion and cognitive load. Change means admitting that their hard won expertise in the old system might not transfer. That feels like disrespect even when you swear you are not implying that.

So they say we have always done it this way which loosely translates to

I know how to survive like this.

I do not trust that your new thing will actually work.

I suspect I will do extra work while everyone else keeps their habits.

Your job is to hear all of that and still move the organization forward without screaming into a pillow during lunch.

The emotional side of technology change

Tech people like to pretend they are rational beings driven by data throughput and clean APIs. Then you suggest replacing a beloved legacy tool and suddenly you are leading a support group.

The emotions are real.

Fear I will look incompetent when I have to ask how to do basic things in the new system.

Loss My custom macros my shortcuts my weird workaround that only I know.

Status I used to be the expert. Who will want my advice now.

Identity I am the person who knows how to fix this. If this goes away who am I here.

Women in change roles are often expected to soothe these feelings while also delivering outcomes on a deadline. You become part project manager part counselor and part villain in someone else’s narrative.

How to handle the we have always done it this way crowd

First stop trying to win them over with only logic. Logic is necessary but not sufficient. You can quote productivity gains adoption metrics and best practice frameworks until your slide deck crashes. People do not change because you are right. They change because staying the same becomes more uncomfortable than moving.

Start by getting specific. Ask them what exactly works for you in the old way. They will tell you that it is not just the tool it is the speed the shortcuts the sense of control. Then you can design the new way so it honors at least some of those needs.

Next take away the illusion of optionality. Nothing kills a change like leadership saying we are all in on this new platform and then leaving the old one available forever just in case. That just in case becomes the default the minute anything feels hard.

You do not have to be cruel. You just have to be clear. For example on this date we will retire the old system and you will not be able to log in. Here is what we are doing to get you ready before then.

Then give them a role. People resist hardest when they feel powerless. Invite your loudest critics to be pilot testers or design partners. Tell them we need your expertise to make sure this does not suck. Suddenly they have skin in the game beyond complaining in the hallway.

Protecting your sanity and your calendar

As a female change manager your calendar is where good intentions go to die. Everyone wants a one on one to express their concerns. Leaders want status updates and reassurance. Teams want training sessions that magically fit into their current workload plus production outages.

You cannot say yes to all of this and remain functional. So you design for scale.

Create office hours. Instead of a hundred scattered meetings hold open sessions where anyone can drop in with questions. This concentrates the chaos into predictable windows and lets people learn from each other.

Use champions. Identify people in each team who secretly kind of like the new system but do not want to be called keeners. Train them first give them insider info and let them be the local go to humans. They are your distribution network for sanity.

Standardize your responses. The tenth time someone asks is this really happening you should have a crisp two sentence answer that is firm kind and not negotiable.

The joy of being blamed for everything

Here is the part no one tells you. If the rollout goes badly it is the change managers fault. If it goes well the technology gets the credit. You become the person who forced people to learn a new thing and then vanish from the story once they cannot imagine living without it.

Also if anything breaks during the transition even if it has nothing to do with your project people will mention it in the same breath. We lost access to the file share and also that new tool she brought in is confusing. Apparently causality is optional.

You cannot fix this but you can reframe it. Your success metric is not universal love. It is adoption. It is reduced workarounds. It is the number of people who stop emailing you about the old way.

You are not here to win a popularity contest. You are here to drag your organization out of process Jurassic Park with as few casualties as possible.

When leadership is your biggest blocker

Sometimes the loudest resistance does not come from frontline staff but from leaders who say they support the change while quietly undermining it. They skip training. They ask for exceptions. They tell their teams just keep doing what works for now.

If you are a woman in the change role you might feel reluctant to call this out. You have been conditioned to be collaborative nice and grateful for executive sponsorship even when it is mostly just a logo on your slide.

You are allowed to be direct. Ask leaders to model the behavior you need. Spell it out.

We need you to use the new dashboard not the old report in your staff meetings.

We need you to publicly celebrate teams that adopt early.

We need you to stop approving work that uses the old templates.

Then show them the impact of their behavior. When you continue using the old system it signals that the change is optional and adoption drops. We will miss our targets if that continues.

You are not being difficult. You are doing your job.

Celebrating the small wins

Change work is exhausting partly because the big rewards come late. The early days are all friction and complaints. By the time people have settled into the new reality there is usually a new initiative on the horizon and you are back at the whiteboard.

So celebrate the tiny victories.

The first time someone says oh that is actually easier in the new system.

The day a manager quotes one of your training metaphors like they invented it.

The sprint where no one asks how to find the new tool in the app launcher.

Write them down. Keep a brag doc. You are building resilience for the next round.

You are not alone and you are not crazy

If you have ever sat in your car after work wondering whether you are overreacting to constant micro resistance you are not alone. You are doing emotional heavy lifting that does not show up on any project plan.

You are managing fear disguised as sarcasm.

You are deescalating conflict between teams who would rather blame each other than look at the system.

You are holding leaders accountable to their own stated goals.

That is real work. It is not soft. It is not secondary. It is what makes every technology transformation either succeed or quietly die in a shared drive folder.

Resistance is not futile. It will always be part of the process. But it does not have to break you. You can acknowledge it design around it and sometimes even recruit it. And on the days when it is especially exhausting remember this if no one hated your change it was probably not significant enough to matter.

Deciphering Developer Done

In project management there is a mythical state called done. Gantt charts depend on it roadmaps worship it executives demand it. In theory done is a binary condition the work is either finished or it is not. Then you talk to developers. Suddenly done has more flavors than a trendy ice cream shop and none of them taste like closure.

If you are a woman project manager in tech your job is apparently to translate all of this into PowerPoint friendly bullets while somehow not sounding shrill when you ask so is this actually ready.

Let us investigate the many meanings of done in the wild.

Done number one it works on my machine

This is the classic. The code builds the tests pass and the feature works flawlessly on the sacred laptop of the developer. In their world this is victory. In your world you are one environment away from discovering that the staging server is three Node versions behind and the database schema is from a previous geological era.

When a developer says it works on my machine what they really mean is I have completed the part I personally can control and I emotionally need this to be done please do not hand me a Jira ticket about DNS.

Your move as project manager is to gently expand the concept of done until it includes at least one environment that other humans can access.

Done number two the happy path works

This version of done usually appears with a demo. The developer walks you through a flawless click path through the new feature. The buttons are clicking the data is saving and you start thinking you might actually make your deadline.

Then you ask what happens if a user does something weird enters nonsense data loses wifi mid transaction or tries the feature on a device from this decade. The developer blinks. The demo did not include weird user behavior. The demo assumed users were thoughtful sober and familiar with dropdown menus.

Happy path done means the feature technically exists if everyone behaves. It does not mean the feature survives real customers on a Monday morning before coffee.

Done number three code complete

Code complete is like the dress rehearsal before opening night. All the lines are there the cast has stopped improvising and if nothing goes wrong you might actually ship. Developers love saying code is complete because it suggests finality without the pesky requirement of users.

In practice code complete means

There is code in the repository that technically corresponds to the feature.

The developer has stopped adding new functionality except for the small tweaks they are still totally making.

The next phase bugs will reveal all the assumptions no one tested.

Code complete done is a milestone worth celebrating but it is not the same as we can turn this on for customers without holding our breath.

Done number four it compiles

This is the minimal viable done. The code compiles it does not crash on launch and nothing is obviously on fire. This level of done is sometimes reached at 2 am after a heroic debugging session that involved swearing at dependencies and bargaining with the CI pipeline.

It compiles done is technically accurate and practically useless. It tells you that the software exists as a physical concept not that it behaves like a product.

Done number five I did my part

This flavor is more emotional than technical. A developer will say it is done to mean I finished the part of the work I believe was assigned to me. Whether the design matches UX or the data is wired up or the feature is discoverable by actual users is someone else’s department.

You will hear it in sentences like the backend is done. The front end is done. The service integration is done. You will also notice that somehow the end to end experience is not done and no one can use the feature without a guided tour and several prayers.

Your job is to gently but firmly redefine done as something that exists beyond individual silos. You can start by asking okay but can a user do the thing we promised them in the scope statement.

Done number six it is behind a feature flag

This is the Schrodinger’s cat of done. The code is in production but hidden behind a switch. If the feature flag is off it technically does not exist. If it is on it may or may not work and you may or may not know it is breaking things.

Feature flag done can be useful when you want to separate deployment from release. It can also become an excuse to push half baked work to production under the comforting illusion that we will turn it on after we polish it.

Three sprints later no one remembers what the flag does and the only documentation is a vaguely named toggle in a dusty config file.

Done number seven QA will catch it

This one usually arrives late in the sprint. A developer says it is done and quickly adds QA will catch anything else. This is the software equivalent of saying I cooked dinner someone else can worry about food poisoning.

In a healthy process QA is a safety net not a primary detection system for everything we did not feel like testing. When done depends entirely on QA you will get bugs that read like haikus. Does not work sometimes. Failed in staging. User angry.

You can push back with a clear definition of what ready for QA means. At minimum developers should be able to answer what did you test how and what should we focus on.

Done number eight it is in staging

Work in staging occupies a strange limbo. It is so close to real yet still technically not your fault when it breaks. Staging done means the feature has left the nest of local development and is navigating the many horrors of shared environments.

Of course staging environments in real life are often held together with duct tape expired certificates and a database clone from last summer. Still if it works in staging you are at least in the same galaxy as production.

Done number nine it is in production please do not roll back

At last the feature ships. It is in production and you are watching metrics like a hawk while pretending to be calm in status meetings. This is release done the state executives think of when they ask is it done yet.

In theory this is the final boss of done. In practice there are hotfixes rollbacks and mysterious error logs that only appear under load. The feature may be technically live but if you need a runbook a therapist and three senior engineers to keep it running you are in a fragile form of done.

Done number ten we met the acceptance criteria I think

Every project manager has lived the moment when someone points to the user story acceptance criteria and says look technically we met all of these. Then you see the feature and your soul leaves your body.

The user can perform the required action but the workflow is weird the performance is sluggish and the edge cases are held together with if statements and optimism. Technically you are done. Practically you are drafting a follow up story titled improve user experience based on feedback.

This is why your original acceptance criteria matter. If they were vague you get vague done. If they were specific and collaborative your odds of actual done increase dramatically.

Done number eleven done for this sprint

This is the agile flavored version of I am as finished as I am going to be before the demo. Done for this sprint means the work moved far enough to count toward velocity even though everyone knows there will be follow up tasks that mysteriously appear next week.

It is not malicious. It is the natural result of planning on incomplete information while executives demand predictable timelines. Just remember that progress meters do not care whether done for this sprint eventually turned into done for real. You do.

Done number twelve I have mentally moved on

Sometimes developers declare something done because they are emotionally done with it. They have wrestled with the bugs argued about scope and read one too many contradictory comments in the code review. Even if there are loose ends they are ready to move on.

You will recognize this version by the tone. It is done usually means I will only touch this again if someone escalates and I cannot duck the meeting.

That is your cue to decide which remaining gaps are truly critical and which can be deferred without turning into future landmines.

Done number thirteen not started but heavily contemplated

This is the honest procrastinator version. The work is not actually started but the developer has thought deeply about it perhaps even sketched a solution on a whiteboard somewhere. In their mind they have already solved it. In Jira the status is still To Do.

You might hear it as this should not take long I have already worked through the tricky parts in my head. You now have to resist the urge to ask why the tricky parts did not somehow type themselves into the repo.

Done number fourteen blocked but emotionally complete

Finally we reach the existential version of done. The work is blocked by something outside the developers control security approvals missing APIs ambiguous product decisions. The developer has done everything they can do so they declare it done in spirit.

For your timeline this is not helpful. For their sanity it is necessary. The best you can do is track blocked done separately from actual done so no one is surprised when the date does not move just because people feel finished.

How to make done mean something again

As a female project manager in tech you are often the only person brave enough to say I hear that it is done can we define what that means. You will be called detail oriented which is code for the only adult in the room.

You can protect yourself and your team by doing a few things.

First write a simple shared definition of done per team. It does not have to be perfect. It just has to be real. For example for a customer facing feature done means implemented peer reviewed tested in at least one non local environment verified by QA and documented for support.

Second bring engineers into the planning of done. Ask them up front what would you need to consider this truly finished. You will get more realistic timelines and fewer unpleasant surprises.

Third use humor. When someone offers the fifteenth flavor of done raise an eyebrow and say okay so is this done done or tech done. People will laugh and then clarify and you get the truth.

And finally remember that your job is not to shame developers for their versions of done. Your job is to align them with reality deadlines and customers. It is messy work but without it your roadmap is just a fantasy novel with a burn rate.

I Do Not Have a Job Description I Have a Fire Extinguisher

Somewhere buried deep in the bowels of your company’s HR system there is probably a dusty PDF that claims to describe the Chief of Staff role. It likely mentions strategic alignment, executive support, and cross functional coordination in very respectable fonts. That is adorable. In technology, the real job description for a Chief of Staff to a CEO could be summed up as follows you are the person everyone pings when something catches fire and the CEO is pretending to be in airplane mode.

If you are a woman doing this job, there is an added twist. Apparently you are also a licensed mind reader.

The first sign that your job is not going to match the HR template is day one when the CEO says something like I am so glad you are here I really needed someone who just gets it. You ask what it is. They smile vaguely at the horizon and say you know the stuff. That is when you realize you have not joined a company you have joined a scavenger hunt with no clues and no map and you are still expected to get it right.

The job description that never was

On paper the Chief of Staff in tech is a strategic partner to the CEO helping drive execution of key initiatives managing information flow and making sure priorities stick longer than the company snack budget. In reality the job is more like this

You are the human router. Every random idea question or panic is forwarded to you with a crisp can you handle this.

You are the unofficial chief therapist. You help the CEO decide whether they are annoyed with a person a problem or the fact that they skipped lunch.

You are the memory of the organization. If you forget it it did not happen.

You are also the organizational translator. You explain engineering to sales sales to engineering finance to everyone and the CEO to themself.

You do all this while being calm organized and available and preferably also pleasant. Some days it feels like you are the only person standing between the company and a full on Slack meltdown.

When your CEO thinks you are omniscient

There is something about the title Chief of Staff that makes executives assume you are plugged into the matrix. You will hear questions like

Do we still have that vendor we used in 2019 for that mobile thing

What did we decide about the pricing strategy for the new product

Why is that director unhappy and how do we fix it before my 3 pm

The subtext is always you already know this right. Meanwhile you have been in the role for six weeks and are still trying to remember which Tom is Tom in security and which Tom is Tom who broke production last year.

The mind reading expectation shows up most clearly in meetings. Executive meetings are your natural habitat but also your main source of secondhand stress. You watch the CEO say something like we need to be more customer obsessed and everyone nods solemnly. Then they leave and interpret that in exactly seven different ways.

Engineering hears we are pivoting the roadmap next week.

Sales hears we are slashing discounts and calling it discipline.

Product hears we are going to do a survey.

No one wants to ask what exactly did you mean by that because they think they should already know. This is where you come in as the designated clarifier of vibes and translator of executive metaphors into sentences that normal people can act on.

Defining the role before it defines you

The biggest trap for any Chief of Staff is letting the role turn into an infinite catch all. If you do not define it it will happily consume your evenings weekends and personality. You will become known as the person who can get things done which is flattering right up until you realize that everyone else has started outsourcing their thinking to you.

So how do you define the role in a world where the CEO really does want a mind reader It starts with three boundaries

First separate executive thinking from executive logistics. You are there to help the CEO think better not to become their full time travel agent snack coordinator and personal reminder app. You can design systems so those things run smoothly without personally hand holding every calendar entry.

Second separate strategic work from random work. Strategic work ties directly to company priorities and is worth your attention. Random work is anything that starts with hey quick question and ends with you accidentally owning a project you had never heard of until three minutes ago. You can still be helpful without being the default project manager for every orphaned idea.

Third separate confidential from secret. As Chief of Staff you will know everything from upcoming layoffs to who is seriously thinking about quitting. You are expected to be a vault not a gossip magazine with a laptop. But being discreet does not mean you have to sit silently while people walk into avoidable disasters. There is a middle ground where you protect confidentiality and still nudge people away from danger.

The gender twist

Now let us layer in the part where you are a woman in tech. Suddenly the same invisible labor you are already doing can be mistaken for caretaking. When you quietly smooth out conflicts help someone prepare for a big presentation or follow up so that decisions do not evaporate you may get called nurturing. That is a cute word for work that is actually operational risk management.

The gender bias shows up in subtle ways. When your male counterpart in another org sends a crisp summary email he gets called strategic. When you do it someone says you are so organized. When a man interrupts a meeting to clarify a decision he is decisive. When you do it you are very assertive and should watch your tone with that one senior vice president.

There is also the assumption that as a woman you are naturally good at feelings which quickly becomes you own employee morale. One minute you are reviewing the quarterly operating plan and the next someone has dragged you into a thirty minute impromptu therapy session in the hallway because you are easy to talk to. Emotional labor counts as labor. It is part of your job but it should not be all of your job.

How to stop being the company sponge

The Chief of Staff who says yes to everything eventually burns out. The trick is to be helpful without becoming the company sponge who absorbs every unsolved problem. Some practical tactics

Make the invisible visible. Once a quarter write a crisp one pager of what you actually own as Chief of Staff strategic planning executive cadence leadership offsites board prep critical cross functional initiatives. Share it with the CEO and key leaders. People take boundaries more seriously when they are documented.

Name the tradeoffs. When someone tries to hand you a random project respond with happy to advise but if I fully own this it means we delay progress on executive priorities. Which would you prefer. People suddenly develop an interest in project ownership when you make tradeoffs explicit.

Delegate with scaffolding. You can still be the person who makes things happen without doing every task yourself. Design simple templates for decision docs meeting agendas and status updates. Empower others to run with them. You are building a system not just solving today’s panic.

Use your access wisely. Your superpower is not that you know everything it is that you know who needs to know what and when. Protect the CEOs attention like it is a shared resource because it is. Sometimes the most valuable thing you can do is keep something off their plate entirely.

The art of saying no without losing influence

Chiefs of Staff live and die by influence. You do not have positional authority over most people yet you are expected to get them to do things they are not excited about on timelines they did not choose while smiling. That means your no has to be carefully calibrated.

You can say no with data. We have twenty two active projects touching the CEO’s office right now. If we add this we will miss our board commitments. Which one would you like to pause.

You can say no with humor. I would love to take that on but my time turner is currently on backorder.

You can say no with a redirect. I am not the best person to own this but I can help you structure it and find the right sponsor.

Every no that protects your focus increases your ability to say yes to the things that actually matter. The CEO might barely notice but the company will feel it when priorities start sticking and decisions do not evaporate by Friday.

Being the mind reader without losing your mind

At some point you will accept that part of your job really is pattern matching your CEOs brain. You will know their tells when they are bored when they are worried when they are pretending not to be furious. You will learn to schedule hard conversations in their good time slots and to never ever put a budget review after back to back external meetings.

The trick is to do this without turning into a shadow version of them. Your job is to be a thought partner not a mimic. You do not have to agree with their every instinct. In fact your unique value often lies in being the one person who can say I know you want to do X but have you considered the fact that Y will set engineering on fire and not in the good innovation way.

When you do your job well no one quite knows how. They just know that things feel smoother more intentional less chaotic. That is the paradox of the Chief of Staff role your best work is often invisible. You do not get public recognition for the crisis that never happened.

So if you are a female Chief of Staff in tech and you feel like your job description is basically I carry a fire extinguisher and a crystal ball you are not imagining things. The role is messy ambiguous and occasionally absurd. It is also one of the few places in the company where you can truly see how all the pieces fit together. You are not just putting out fires. You are quietly redesigning the wiring so maybe tomorrow there are fewer sparks.

You may never get a clean bullet pointed job description. But the next time someone asks what exactly you do here try this I make sure we do not burn down the company while we are building it.

From Calendar Queen to Ops Brain: How Women Admins Are Quietly Running Tech Companies

On paper, you are an administrative assistant. In reality, you are the unofficial operations chief for at least three executives and half their teams. You see everything. You know everyone. You can feel a political storm coming three calendar invites ahead.

For years, your work has been framed as “support.” Helpful, appreciated, and treated as somehow less strategic than the work performed by the people whose chaos you are constantly containing. The stereotype is calendar wrangling, travel booking, and ordering snacks.

Here is the truth. Modern admins in tech are quietly running the machine. You are the routing layer for decisions, the protector of time, and frequently the only person who actually understands how information, people, and priorities move through the system. That is operations, not errands.

Your View of the Company Is Unique

Executives see their domain. Managers see their teams. You see the entire choreography.

You know which leaders trigger panic when they add “Can we chat?” to a subject line. You know which projects are slipping before they show up red on dashboards because you can see who is canceling prep meetings. You can tell when a “quick catch up” is actually a quiet performance intervention.

That vantage point is power. When you use it thoughtfully, you become an indispensable node in the organization’s nervous system.

Stop Minimizing Your Work

The language used to describe admin work is often subtly diminishing. “Just scheduling.” “Just logistics.” “Just helping.”

Translate what you do into business terms and the picture changes.

You are managing executive bandwidth, which is one of the scarcest resources in the company.
You are triaging information flow so that decisions are made in the right order by the right people.
You are reducing context switching and meeting overload, which directly impacts productivity and burnout.

If you frame your work this way, it becomes clear you are not simply a “calendar queen.” You are an operations brain, optimizing time and attention across complex systems of people.

Claiming Titles That Reflect Reality

Titles will not fix everything, but they do influence how people perceive and compensate you. If your responsibilities look like operations, program coordination, or chief of staff lite, it is reasonable to push for a title that reflects that.

Some examples you can propose:

Executive Operations Partner
Business Operations Coordinator
Office of the CEO or Office of the VP Specialist
Program and Operations Assistant

Pair that ask with a simple one page summary of your actual scope. Include not just tasks, but decisions you make, risks you manage, and projects you have quietly kept on track.

You are not asking for charity. You are asking for alignment between the work you are doing and the way the company describes it.

Turning Access into Influence

You are in the room, or just outside the room, for many conversations that others never see. The question is what you do with that access.

Influence does not mean gossip. It means:

Flagging when your executive’s schedule is unsustainable and suggesting changes.
Noticing when the same few people are always excluded from key discussions and gently asking whether they should be invited.
Suggesting small process improvements that remove bottlenecks you see every day.

You can also grow your influence by learning the language of the business. Read the strategy docs. Skim the quarterly reports. Learn enough about the products and customers that you understand why a meeting matters, not just where it belongs.

People listen differently to someone who can say, “If we move this partner review, we will delay the integration decision that affects Q3 targets.” That is not scheduling. That is operational awareness.

Asking for Raises with Data, Not Apologies

Many admins are underpaid relative to the scope of their impact, especially women who are socially conditioned to be grateful just to be included.

When asking for a raise, skip the apologetic framing. Come with:

A clear description of how your role has expanded over the last year.
Specific examples where your work prevented mistakes, improved processes, or saved time for high cost leaders.
Benchmark data for similar roles in your region or industry when possible.

Tie your request to retention. Training someone to replace you would be expensive, disruptive, and risky. Paying you fairly is the more rational option. Say that in your own words, calmly, without flinching.

Your Career Path Does Not Have to Be Linear

Some admins love the role and want to keep becoming more senior in it. Others see it as a launchpad into operations, project management, HR, chief of staff, or even product work. All of those paths are legitimate.

Your skills are portable. Coordination, communication, prioritization, people reading, operational thinking. Those are the core of many higher paid roles. If you want to move, treat your current role as paid intelligence gathering. Learn everything you can about how the business actually works.

Then, when the right opportunity appears, you are not “just an admin” asking for a shot. You are the person who already understands more about how the place runs than half the applicants.

Rest as a Career Strategy: Why Saying No Is Now a Competitive Advantage in Tech

Somewhere between the third “urgent” ping of the day and the second “quick favor” that is not quick at all, a quiet thought appears. What if the most radical thing you did for your career this year was sleep more.

Not as self care wallpaper. As strategy.

In a field that worships speed, many women in tech were trained to compete by outworking everyone. Stay later. Answer faster. Say yes more. Be the reliable one. The problem is that AI, automation, and global teams have now created an environment where work can literally expand to fill all available time. There is no finish line. There is only whatever is left in your inbox before your forehead hits the keyboard.

If you want to stay in this industry long enough to enjoy the power you are building, rest is not optional. It is infrastructure.

Cognitive Performance Is Now Your Real Edge

AI can already produce first drafts, generate code, summarize research, and crunch data. It cannot yet consistently replace your judgment, pattern recognition, or ethical sense. Those higher order skills are where your value lives now.

The catch. Those skills degrade quickly when you are exhausted. Sleep deprivation and chronic stress reduce decision quality, creativity, and emotional regulation. You become easier to manipulate, more likely to agree to bad timelines, and less able to spot the political and technical risks that your role requires you to see.

So when you protect your rest, you are not being “soft.” You are defending the very cognitive edge that keeps you employable and promotable in an AI shaped environment.

The Invisible Load Women Carry

Many women in tech are not just doing their own jobs. They are also doing unofficial team emotional support, unpaid mentoring, diversity work, and often a double shift at home. That invisible load can turn a supposedly reasonable workload into a 150 percent capacity reality.

The result is that saying yes at work often means quietly saying no to yourself. No to recovery. No to hobbies. No to reflection. Over time, that trade makes you less effective, not more loyal.

A more honest model is that your time and energy are finite resources that must be allocated. You would never let a cloud infrastructure bill run uncontrolled without alarms. Treat your nervous system with at least that level of respect.

Saying No Without Starting a War

The fear is real. Many women hesitate to set boundaries because they worry about being seen as difficult, uncommitted, or not a “team player.” The key is learning how to say no in a way that is clear, respectful, and tied to business outcomes, not defensiveness.

Some practical phrases:

“Here is what is on my plate this week. Which of these would you like me to deprioritize to make room for this new request?”
“I can take this on next sprint. If it is urgent for this week, we may need an additional resource.”
“If we compress the timeline that much, here is specifically what will be at risk. Are we comfortable with that trade off?”

You are not refusing to help. You are refusing to pretend that capacity is infinite. Over time, people learn that you are serious about scope and that your yes actually means something.

Rest as Reputation, Not Weakness

Ironically, the people in tech who seem the most in control of their time are often the ones we respect the most. The senior leader who does not answer messages at midnight. The architect who refuses to join every meeting and yet is always sharp when it matters.

They have trained others to treat their focus as valuable. You can do the same, even from a non executive level. It starts with small, consistent signals. Not answering Slack during your off hours. Actually taking your paid time off. Declining meetings that have no clear purpose.

You are sending the message, “I do my best work when I am not chronically depleted.” That is a brand worth cultivating.

Designing Your Own Rest Rules

Everyone’s life constraints are different, so there is no universal template. Instead, define a few non negotiables:

A minimum amount of sleep you will aim for most nights, even if it means letting some non critical tasks wait.
One or two days a week where you do not book early morning or late evening meetings.
Clear vacation time where you are genuinely offline, with coverage arranged in advance.
A personal “red line” for how many back to back high pressure weeks you will tolerate before requesting help or renegotiation.

Write these down. Share some version of them with people who need to know. Adjust when reality kicks you in the shins, but treat them as defaults.

Rest is not a treat you receive when you have earned it by breaking yourself. It is part of the cost of doing business with your brain.

Planning in Dog Years: Building a Three Year Strategy in a World That Changes Every Three Months

Three year plans in tech used to feel ambitious. Now they feel slightly comedic. By the time your slides are polished, a new AI platform has launched, a regulator has woken up, and your main vendor has decided to pivot into an entirely new business model.

If it feels like every year is seven years of change, you are not wrong. Welcome to planning in dog years.

As a woman leading strategy and planning in tech, your job is not to predict the future perfectly. It is to make sure your organization can survive the part where you are inevitably wrong. That means scenario thinking, portfolio bets, and the courage to kill work that no longer fits reality, even when people are attached to it.

Replace Illusion of Certainty with Range of Outcomes

Traditional strategic planning loves linear stories. Year one, we invest. Year two, we scale. Year three, we harvest. Nice, tidy, and completely detached from how modern tech markets behave.

Instead of promising one neat outcome, smart planning in 2026 sketches a range. Best case, expected case, worst case. You define what you will do in each scenario before you get there, when you are still calm and politically sane.

This kind of thinking is especially important around AI platform dependencies and regulation. Models will evolve. Licensing terms will change. New rules will appear. The only truly unrealistic plan is the one that assumes nothing major will shift.

Your value as a strategist is not in claiming certainty. It is in teaching your leadership team how to think in probabilities without shutting down from anxiety.

Portfolio Bets, Not Single Moonshots

The era of staking your survival on one giant bet is over for most companies that do not have unlimited cash. The smarter approach is a portfolio of smaller, asymmetrical bets. Some will fail cheaply. Some will muddle along. A few will carry the returns for the rest.

In practice, that means:

A mix of horizon one work that pays off now, horizon two experiments that might pay off soon, and horizon three explorations that are mostly learning.
Not every shiny AI idea gets funded as a full program. Some get framed as “option building” experiments.
Clear thresholds for what graduation from pilot to product actually means.

Your planning documents should read less like a promise and more like an investment memo. What are we trying, why, at what cost, and what evidence will push us to expand or stop.

Create Explicit Kill Criteria

Tech organizations are very good at starting things and remarkably bad at stopping them. The result is ghost projects that linger on roadmaps far longer than anyone believes in them.

You can change that by insisting on kill criteria at the start of every major initiative. Not just success metrics. Exit conditions.

For example:

“If we do not hit X adoption by Y date, we either pivot or fold.”
“If regulatory risk crosses a certain threshold, we pause and re assess.”
“If the AI vendor fails these reliability checks three times, we stop building on them.”

Writing this down in advance saves you from twelve painful alignment meetings later where everyone knows a project should end, but no one wants to be the one to say it. You are doing your future self a favor.

The Emotional Side of Strategy

Strategy work is often presented as analytical and clean. In reality, it is deeply emotional. You are making calls about which teams will get funding, which products will be sunset, and which pet ideas will quietly die. People take that personally.

As a woman in planning, you may find that people bring extra emotion to you. They expect you to soften bad news, protect their teams, or “find a way” when the numbers are clear.

There is a balance to hold here. You can be humane without being evasive. You can acknowledge the real loss in strategic trade offs while still making them. Over time, your reputation will be built on whether people believe you tell the truth, even when the truth is that something they care about is not a good bet anymore.

Planning as a Continuous Habit, Not a Season

The biggest shift in 2026 planning is moving from annual events to continuous practice. You cannot afford to treat strategy as something you do once a year at an offsite and then forget.

Make planning lighter and more frequent. Quarterly portfolio reviews that revisit bets in light of new data. Mid cycle adjustments that are explicit, not stealthy. Clear communication about what has changed and why.

You are teaching the organization that changing the plan is not failure. It is the whole point. The world moved, so you moved. That is competence, not chaos.

You Do Not Need a Women in Tech Panel, You Need a Succession Plan: Sponsorship Over Soundbites

Somewhere right now, a conference organizer is sending another email that begins with “We would be honored if you could join our Women in Tech panel to share your inspiring journey.”

It will be scheduled at 4 p.m. on day two, in the medium sized room. There will be a pastel slide template. Someone will say “lean in.” There might be cupcakes.

Panels like this are not useless. They can encourage, connect, and signal that women exist in the building. But let us be honest. Visibility is not the same as power. If your company can fill a panel with women but cannot fill a leadership team with them, you do not have a visibility problem. You have a succession problem.

The Difference Between Being Seen and Being Promoted

Many organizations confuse “supporting women in tech” with “putting women on stage occasionally to inspire others.” Panels, marketing campaigns, social posts, mentoring circles. These things can be positive. They can also function as very polite distraction.

What changes outcomes is not how often women are quoted. It is how often they are chosen.

Chosen for stretch roles.
Chosen for P and L responsibility.
Chosen for line roles instead of perpetual staff roles.
Chosen for real budget authority, not just influence without decision rights.

If the only place women are consistently visible is on culture content and diversity slides, you have branding, not equity.

Sponsorship Is Not the Same as Mentorship

Mentorship is advice. Sponsorship is risk.

Mentors talk to you. Sponsors talk about you in rooms you are not in. They attach their reputation to your advancement. They say, “She should lead that team” or “She is ready for that role” when it actually costs them something if you fail.

Women in tech get plenty of mentorship. Coffee chats. Feedback sessions. Book recommendations. What they get far less frequently is sponsorship that leads to concrete, career changing opportunities.

If you are a woman leader, you have more power here than you might realize. You can decide that you are done only offering vague encouragement and begin actively placing women into succession pipelines. That means:

Putting names on shortlists for roles that were not written with them in mind.
Giving them high visibility projects that are measured in money and outcomes, not only in “team culture.”
Saying, out loud, to peers and HR, “She is my successor for this role and I want her on the formal list.”

If there is no formal list, that tells you exactly how fragile the company’s talent strategy really is.

Succession Planning Is a Feminist Act

It sounds dry. Succession planning. It belongs in HR manuals and board reports, right?

In practice, it is one of the most powerful levers you have to change who actually ends up with institutional power.

Without a real plan, the default is always to promote the most visible, best networked, least “risky” candidate. That often means whoever already looks like the current leadership archetype. Very often, that is not a woman, and definitely not a woman from an underrepresented group.

By insisting on documented successors, development plans, and time bound commitments, you are forcing the system to admit what it is doing. You are asking, “Who is next?” and “Why is it always the same profile?”

You are also protecting your own legacy. Leadership that truly cares about inclusion does not just open doors while they are in the chair. They ensure that someone different gets to sit in the chair later.

Actionable Steps for Women Leaders

If you are already in senior tech leadership, here is how to move from soundbites to structural change.

Ask for the current succession slate for your organization. Count how many women are listed for mission critical roles. If the number is near zero, treat that as a risk, not an observation.
Pick two or three women you believe could step into bigger roles within the next three years. Talk to them about their ambitions. Ask what support they actually need.
Use your political capital to get them access. That means budget responsibility, complex projects, and executive exposure. Not just more mentoring.
When you are offered a speaking slot or panel, occasionally trade it for a behind the scenes ask. For example, “I will join this fireside chat if we can also discuss the director level promotions pipeline for women afterward.”

Is that fair that you have to negotiate like this? No. Is it strategic? Yes. You are already doing emotional labor. You might as well convert some of it into policy.

Stop Accepting Symbolic Gestures as Progress

There is a certain kind of initiative that looks great in a press release and accomplishes almost nothing. You know the type.

Internal awards that come with a nice plaque and no pay raise.
Spotlight articles on the company blog that celebrate “women trailblazers” while leaving pay gaps untouched.
Working groups that are allowed to brainstorm but not to approve budgets.

You do not have to be ungrateful. You can simply be honest. “This is nice. It is not sufficient.”

Ask for concrete metrics. Promotion rates. Pay equity ratios. Representation in staff plus line roles. Representation in technical fellow or distinguished engineer ranks, not just people management. If those numbers are not moving, the energy is in the wrong place.

Panels can start conversations. Succession plans change who writes the agenda for the next decade.

Your Career Ladder Is Now a Jungle Gym: Designing a 2026 Career in Tech When Roles Will Not Sit Still

Careers in tech used to be sold like staircases. First junior, then mid, then senior, then manager. Attractive in theory, slightly boring in practice, and very easy to put in a slide deck.

In 2026, your career looks less like a staircase and more like a jungle gym that someone built during a hackathon. Lateral moves, contract projects, AI adjacent roles, temporary leadership gigs, portfolio careers. You are not climbing one ladder anymore. You are choosing which structure is worth hanging from next.

If you are a woman in tech, this instability can feel like both a threat and an invitation. The threat is obvious. Titles are messy, paths are unclear, and companies are reorganizing faster than you can update your LinkedIn. The invitation is quieter. You have more leverage than ever to design work that fits your life, not just your manager’s headcount plan.

The Old Narrative Is Dead. Stop Trying to Revive It.

There is still a persistent fantasy that if you just work hard, stay loyal, and keep saying yes, you will be rewarded with a neat sequence of promotions. That story was shaky before. Now it is pure fiction.

Tech roles are fragmenting. AI has created new categories like prompt engineering, AI operations, AI product strategy, and model governance. Project work dominates, and many teams are funded quarter by quarter instead of in five year plans. Stability is the exception, not the rule.

So the better question is no longer “What is my path here?” It is “What am I building in myself that stays valuable no matter what org chart I am currently trapped inside?”

Think less in titles and more in transferable stacks. Influence skills. Technical literacy. Domain expertise. Network depth. If those grow, your options grow, even if your current company cannot imagine a path beyond your current box.

The Three Modes of a Modern Tech Career

Most of the women I counsel cycle through three main modes in their career. Sometimes intentionally, sometimes reluctantly.

IC Mode
Deep maker energy. You are hands on with the work, close to the tech and the details. Great for building credibility, skills, and portfolio. Risk: getting stuck being the “doer” while others collect the strategic air cover.
Management Mode
You are leading humans, projects, or both. Success is measured less in your individual brilliance and more in team output. Great for impact and influence. Risk: emotional burnout, politics, and losing touch with the underlying tech if you are not careful.
Adjacency Mode
You orbit the core tech work in roles like product operations, AI strategy, developer experience, data governance, or internal consulting. Great for breadth and seeing the whole system. Risk: people underestimate you because you are not coding or shipping features directly.

In 2026, the smartest women are not picking one and locking in forever. They are treating these as modes they can move between on purpose. For example, three years in IC mode to build depth, then a pivot into management or AI adjacent work to expand influence and income.

The magic move is not staying in one lane. It is learning how and when to switch.

Pivoting Without Starting from Scratch

One of the biggest fears women have is that leaving a path will erase their progress. If they step out of management to return to IC work, it will look like a demotion. If they leave engineering for AI product strategy, they worry they will be seen as “less technical.”

Here is the reality. Careers are being evaluated more like product portfolios. What matters is the story of value, not the linear shape of your titles.

You can pivot without starting over if you:

Keep one thread consistent. For example, always staying close to data, to infrastructure, to user experience, or to AI capabilities.
Translate your last role in the language of your next. A manager of infrastructure teams becomes a reliability strategist or platform operations lead. A business analyst becomes an AI informed workflow designer.
Document outcomes instead of responsibilities. Recruiters and hiring managers are now scanning for impact, not just tenure.

The question you want your resume and portfolio to answer is “What did she change?” not just “What did she own?”

Designing Around Life, Not Just Ambition

Nonlinear careers are not just a response to market chaos. They can also be a feature, especially for women who are juggling caregiving, health, or simply a desire to not burn out by 38.

There will be seasons when you want maximum acceleration. Bigger scope, higher pressure, faster promotions. There will be other seasons where sustainability matters more than title. Remote friendly roles, contract work, or project based consulting can buy you time and flexibility without removing you from the game.

You do not have to justify these shifts to anyone except yourself. A career is long. A two year step back from high visibility leadership is not a failure. It is a strategic pause. That pause can be the reason you stay in the industry long enough to actually reach the power levels you want later.

The Jungle Gym Strategy: Practical Moves

If the ladder is gone, here is how to move smartly on the jungle gym.

Identify two or three “north star” skills that you always keep investing in, no matter your title. For example, AI fluency, stakeholder influence, or platform architecture.
Every 12 to 18 months, ask whether your current role is still feeding those skills. If not, plan a pivot. Internal if possible, external if necessary.
Keep a lightweight portfolio. Screenshots, case studies, internal docs, talk outlines, GitHub snippets. This is your evidence file.
Stay within one or two domains long enough to become known. Bouncing wildly between e commerce, healthcare, and fintech can slow your momentum if you never stay long enough to gain reputation.

Think like a founder, even as an employee. You are the product. Companies are customers. Some will churn. Some will be long term. What matters is that the product keeps improving on your terms.

You Are Allowed to Want Power

There is one more thing I wish more women admitted out loud. It is okay to want real power, not just interesting work.

Not social media visibility. Not being invited to the token “women in tech” panel. Actual decision rights. Budget control. Succession potential. Equity that matters.

Your career design in this jungle gym era should include an honest look at power pathways. Who gets promoted where you are now. Who gets stretch roles. Who gets executive coaching. Who is quietly being shaped for head of function or C level roles.

If you do not see women like you in those paths, you have options. You can ask for what you need to be on one. You can move to a company that is already building those paths. Or you can opt out of playing for top titles and optimize for freedom and money instead. None of those options are inferior. They are simply different strategies.

The point is not to passively wait for someone to hand you a ladder that fits. It is to design your own structure and treat companies as temporary climbing frames, not permanent homes.

The Emotional Labor Nobody Budgeted For: Women Change Managers Holding the Culture Together

There is a line on the project budget for licenses, consultants, hardware, and maybe a sad little bucket called “communications.” There is never a line called “emotional fallout from yet another reorg that no one asked for.”

That unbudgeted cost is you.

If you are a woman in organizational change management in tech, you already know your real job is not just rollout plans and stakeholder maps. It is holding the entire emotional climate of the organization together while executives present yet another transformation as an exciting opportunity for innovation and employees quietly google “how much to retire in a small village.” Change stress is strongly linked to burnout and exhaustion, and support from managers is one of the few things that can buffer it.

Welcome to the invisible middle of modern tech transformation. You live between the slideware optimism at the top and the Slack channel despair at the bottom. You are the translator, the shock absorber, and occasionally the person everyone secretly expects to heal institutional trust issues. No pressure at all.

Your Official Job vs Your Actual Job

On paper, your responsibilities sound very rational.

You are supposed to:

Assess change impacts and risks.
Build communication and training plans.
Map stakeholders and resistance points.
Prepare leaders to sponsor the change.

In reality, your daily work looks more like this:

Interpreting a vague executive decree into something humans can understand without panicking.
Coaching a line manager through their own fear so they can pretend to be confident in front of their team.
Rewriting a tone deaf email that begins with “In today’s fast changing world” and ends with “some roles will be impacted.”
Listening to a quietly furious engineer who just lost their favorite system to an AI powered replacement initiative.

Studies have found that organizational change significantly increases stress, emotional exhaustion, and burnout, especially when employees feel a lack of control and clarity. Guess who is in the middle trying to create control and clarity that did not exist in the first place.

You are not just managing adoption. You are managing the emotional consequences of leadership decisions that were made three layers above your pay grade.

The Unpaid Role: Chief Feelings Officer

Women in tech already take on a disproportionate amount of invisible emotional labor, from mentoring to culture work to informal conflict resolution. If you also happen to be a change manager, the job practically weaponizes that tendency.

You become the person people cry to after town halls.
You become the one who “just has a way” of calming down panicked teams.
You become the one asked to “help the VP sound more human in their communications.”

None of that is on the job description, but all of it is expected.

The hidden message is clear. Leadership will own the vision. You will own the feelings.

The problem is that this emotional load is not neutral. It is exhausting. Research on change shows that managers and middle leaders often experience high emotional exhaustion because they carry both pressure from above and distress from below. For women, who are already more likely to be cast into delicate leadership situations or “glass cliff” roles, the risk is multiplied.

The Script You Know By Heart

Every major tech change program follows a familiar emotional script. You could almost design a template.

Phase 1: Leadership excitement
Everyone in the C suite is buzzing about “transformational opportunities” and “unlocking value through AI, automation, or platform modernization.” There are slide decks. There are big words. There is a mysterious McKinsey graph that no one can quite explain.

Phase 2: Middle management confusion
Managers privately message you: “What does this actually mean for my team?” They have no answers, but they are expected to reassure everyone that everything is fine.

Phase 3: Employee anxiety
Rumors start before formal comms. Someone finds an old job posting for a role that sounds suspiciously like what they are doing now. The Slack side channels light up.

Phase 4: Your calendar explodes
You are suddenly in back to back “quick chats” with managers, HR, and random employees who somehow got your name. You are updating FAQ documents, running listening sessions, patching over ambiguous decisions, and gently begging leaders to stop improvising in public.

Phase 5: Blame and amnesia
If adoption is slow or morale dips, someone says, “We need better change management.” If revenue rises a quarter later, no one says, “That was great change management.” The success is absorbed into “good leadership.”

This cycle repeats with every reorg, platform shift, or AI initiative. The emotional work of cushioning the impact and rebuilding trust falls to the same people, over and over. Often women. Often you.

Tech Change Is Not Just Technical

Executives love to pretend that change resistance is a training problem. Just teach people the new tools. Just explain the strategy. Just show the benefits.

The reality is that resistance is rarely about the technology. It is about grief and identity.

The architect who spent a decade building the old platform is not “resistant.” They are grieving the quiet erasure of their craftsmanship.
The operations lead who is told AI will “augment, not replace” their team does not need a webinar. They need someone to acknowledge that their job security feels suddenly conditional.
The senior IC who built influence around a now deprecated system is not confused by change. They are watching their internal status evaporate overnight.

Research shows that major changes can trigger stress, burnout, and even incivility when people feel loss of control and unclear futures. The human brain does not care that the new CRM is on a more modern stack. It cares that the social rules of survival just changed again.

You understand that. You build space for it in your plans. You make room for listening, not just broadcasting. You help leaders see that “resistance” is often a rational response to cumulative uncertainty.

And often, you are doing this while processing your own reaction to the change too.

Why Women Get Pulled Into This Work

There is a reason so many women end up in change and transformation roles. Tech is finally realizing that successful change requires communication, empathy, and cross functional collaboration in addition to technical chops. Those are strengths women have always used to survive in male dominated environments. Suddenly, they are being labeled as leadership skills.

But there is a catch.

The same traits that get you chosen as the “natural” change leader also make you the default emotional buffer. You are good with people, so everyone assumes you will handle the messy parts. The tense conversations. The emotional reactions. The quiet resentment that no survey ever fully captures.

Meanwhile, your male counterparts are more likely to be attached to “strategy” and “architecture” while you are attached to “engagement” and “adoption.” The latter is just as critical, but usually less visible and less valued when promotion decisions are made.

So you become vital to the transformation, but still peripheral in the power structure of the organization. That tension is not an accident. It is structural.

You Are Not the Company Therapist

The cruel irony is that the more capable you are at emotional labor, the more of it people send your way.

Suddenly you are:

Coaching managers on how to deliver news that leadership should be owning themselves.
Sitting in “casual one on ones” that are really low cost therapy sessions about job insecurity.
Editing communications from senior leaders that were clearly written in a rush between flights.

You start your week with a full calendar of “quick syncs” that are never quick and rarely synced.

At some point, you have to decide where your job ends and where the organization’s responsibilities begin. You are not responsible for healing the cultural damage done by years of poor leadership decisions. You are responsible for making change more transparent, more humane, and more coherent.

There is a difference.

How to Protect Your Own Energy

You cannot pour from an empty emotional tank, and you definitely cannot run change programs out of one. Protecting your energy is not indulgence. It is risk mitigation.

Try a few of these guardrails:

Define scope explicitly
When you join a new initiative, ask directly: “What is in scope for change management, and what is leadership accountable for themselves?” Put it in writing. Refer to it when people attempt to outsource their courage to you.
Redirect emotional spillover
When an employee wants answers you genuinely do not have, resist the urge to improvise. Say, “I do not want to guess about that. This is a question leadership needs to answer, and I will bring it to them.” You are not the official rumor control center.
Time box the extra support
It is tempting to leave yourself endlessly available. Do not. Protect deep work blocks. Offer structured forums such as listening sessions or office hours instead of ad hoc vent sessions all day long.
Get yourself real sponsorship
You need an executive who understands your impact and is willing to say it out loud in rooms you are not in. Formalize that. Ask to be included in key decision discussions early instead of being invited in after the fact to tidy the narrative.
Treat your burnout as a data point
If you are emotionally exhausted, it is not just a personal weakness. It is a sign that the organization is leaning too hard on a tiny number of people to absorb the emotional cost of structural choices. Bring that feedback into retrospectives. Name it as a risk.

Make the Invisible Work Visible

One of the hardest parts of this role is that your biggest wins are often things that did not happen.

The conflict that never escalated.
The rumor that died quickly because you designed a better communication sequence.
The attrition spike that never materialized because you coached managers early.

You cannot always prove those wins directly, but you can get better at capturing the signals.

Track engagement in your sessions, not just attendance.
Track shifts in sentiment over time in surveys and listening tools.
Document escalations prevented through early intervention.
Tell specific stories in leadership forums about where change support made a tangible difference.

Women are often penalized by the fact that their contributions live in the category of “soft” skills, even when those skills keep projects and people afloat. Reframing your work in business terms is not bragging. It is a survival strategy.

You Are Not Neutral. You Are Strategic.

Change managers are often treated as neutral facilitators, floating slightly above the politics of the org. Do not believe that myth.

You have a point of view. You sit at the intersection of strategy and reality. You hear what leadership wants and what people can actually tolerate. You see where the cultural cracks are forming long before they show up on a dashboard.

That perspective is not just helpful. It is strategic.

Use it to:

Flag when the pace of change is outstripping people’s ability to absorb it.
Challenge leaders to own uncomfortable messages instead of delegating them.
Influence sequencing of initiatives to avoid compounding stress on the same teams.
Advocate for actual support structures, like psychological safety work, not just pizza and town halls.

Companies that treat change as a purely technical exercise eventually pay the price in disengagement, cynicism, and turnover. Companies that listen to the people in your role avoid some of that pain.

So stop thinking of yourself as “just supporting the rollout.” You are shaping the conditions in which that rollout either sticks or quietly dies. That is real power, even if it does not come with your own keynote slide.

Holding the Culture Together Without Breaking Yourself

There will be days where it feels like you are personally responsible for the emotional climate of several hundred people. You are not.

You are, however, one of the few people explicitly trained to name what others are feeling but cannot articulate yet. To design processes that respect human limits. To push for clearer, kinder, more honest communication in environments that are addicted to spin.

That matters more than anyone will admit in a quarterly earnings call.

The goal is not to be the unshakeable, always available emotional anchor for everyone. The goal is to be the person who helps the organization grow the capacity to handle change better over time, so that less of it sits on your shoulders alone.

You deserve rest. You deserve backup. You deserve a budget that reflects the gravity of what you are actually doing. Until then, protect your energy like the critical asset it is.

Because while everyone else is obsessing over the tech stack, you are the one holding the human stack together. If that collapses, nothing else ships.