Two numbers landed in front of me this week and they refuse to sit quietly together.
Number one: in an August 2024 survey of 1,900 tech workers on the anonymous career site Blind, 67% said they were likely to join a union if their employer had one.
Number two: union membership across tech occupations sat at roughly 3.5% in 2025. Narrow it to professional and technical services and the US Bureau of Labor Statistics puts it at 1.3%.
Two thirds want in. One in thirty is in.
Most tech leaders read the second number and relax. Wrong read. The gap between those two figures is not your safety margin. It's a warning light with a long fuse.
Nobody Wakes Up Wanting a Union
Here is what I've learned across three decades of building software teams. Engineers are, as a group, allergic to process they didn't ask for. They hate meetings. They hate forms. They hate anything with a committee attached.
So think about what it takes to move an engineer from "leave me alone, I'm shipping" to "I would like a third party to negotiate my working conditions."
Nobody arrives there on a whim. They arrive after a long stretch of asking politely and getting nothing.
Union interest is not an ideology problem. It's a feedback mechanism of last resort. Your people tried the normal channels first. The one-to-one. The skip-level. The engagement survey with the beautiful dashboard nobody acted on. When all of those produce silence, workers go looking for a channel you are unable to ignore.
The Demands Read Like a Manager's Job Description
Pull up what tech workers organize around and the list is boring:
- Tell us before you cut jobs, not after
- Publish the pay bands
- Give us a say in how AI reshapes our work
- Stop treating on-call as unpaid overtime
- Make the workload survivable
Read the list again. Not one item is exotic. Not one needs a lawyer. Every single one sits inside the normal authority of an engineering manager with a spine.
LeadDev's reporting on tech organizing found burnout and job insecurity at the top of the motivation list, alongside the collapse of the perks era. When the salary, the security, and the work-life balance thinned out together, dismissing unions got harder.
I'd put it more bluntly. Your team is asking for the basics of being managed well. If they need a collective bargaining agreement to get it, the failure is yours.
The 99.5% Problem
My own research turned up a figure I keep coming back to. 99.5% of survey respondents said they'd had one or more types of bad boss.
Not 40%. Not 70%. Effectively everyone.
Now layer the Gallup finding on top: only 21% of employees are engaged at work, as I've written about over on Step It Up HR.
So we have a workforce where nearly everyone has been managed badly, four in five are disengaged, and two thirds would sign a union card tomorrow. Those three numbers are the same number wearing different hats.
What the Talk Costs You Before Anyone Signs Anything
Leaders fixate on the vote. The vote is late in the story. The damage happens in the months before it, and you pay for all of it whether or not a single card gets signed.
Organizing talk starts in DMs. It starts because people compared notes and found a pattern. By the time it reaches a group chat, three things have already shifted.
Information stops flowing upward. Nobody tells you the estimate is fantasy. Nobody flags the architecture decision heading for a wall. Bad news stops arriving early, which is the only time bad news is useful.
Discretionary effort drops. Not the contracted work... the extra. The unprompted refactor. The runbook written on a Friday afternoon. The person who stays on the bridge call because they care how it ends.
Your strongest people leave first. They always do. Options make exit cheap, and the ones with the most options are the ones you most need. The union conversation carries on without them, and you're left negotiating with a team you've already weakened.
None of it shows up on a dashboard. All of it shows up in your delivery six months later, where you'll blame estimation.
Why Leaders Reach for the Lawyers First
Watch what happens when organizing starts. The reflex is legal counsel, union avoidance consultants, and a run of mandatory meetings about "our direct relationship."
The National Labor Relations Board has ruled against both Amazon and Tesla for obstructing organizing efforts. Apple was found to have threatened workers considering a union. Money and lawyers, aimed squarely at the symptom.
Consider the arithmetic. A company will spend six figures fighting recognition rather than answer the question sitting underneath it: why do our people no longer trust us to be fair without a contract forcing it?
Fighting the union is fighting the smoke alarm.
Structure Is Not the Enemy of Speed
The old objection goes like this. Unions slow us down, and speed is our advantage.
I've heard it my whole career and I've never seen the receipts. Microsoft signed its first US union contract in 2025 with ZeniMax QA workers, and now has over 2,000 game workers organized under the CWA. The company still ships. Structured negotiation with your workforce is not slower than the alternative, which is attrition, rehiring, and rebuilding institutional knowledge every eighteen months.
You already accept structure everywhere else. Code review. Change control. Incident postmortems. SOC 2. You accepted all of it because unstructured decisions produced worse outcomes.
The one place you insist on unlimited discretion is how you treat the people doing the work. Ask yourself why.
Do the Boring Thing Instead
None of this is an argument for or against unions. Workers make their own decision on it, and it isn't your call.
It's an argument about signal. If organizing talk reaches you, the diagnosis is already written.
Here's the work, and none of it needs approval from legal:
Publish the pay bands. If your bands don't survive daylight, fix the bands.
Say the layoff number out loud. Vague reassurance ahead of a cut destroys more trust than the cut itself.
Put AI displacement on the table. Your team knows what agents are doing to junior work. Silence reads as a plan they've been excluded from. Naming it honestly beats a slide about "augmentation."
Cost your on-call. If nobody has ever measured the hours worked outside working time, you're funding your uptime with unpaid labor.
Act on one survey item, visibly. One. Named, dated, done. A single closed loop outweighs a year of anonymous forms.
Make refusal safe. A team unable to say no to a deadline will say no somewhere else eventually, and you'll like the second venue a lot less.
The Question Worth Sitting With
Public approval for unions in the US hit 68% in 2025, up from 48% in 2009. Younger workers lead it. The engineers you're hiring right now grew up watching layoffs arrive by email while executive pay climbed straight through the same quarter.
The 3.5% membership figure is not proof you're safe. It's proof the paperwork hasn't caught up with the sentiment yet.
So the question for Monday morning is not "how do we stay union-free."
It's this. If your team had a formal, protected way to tell you what's broken, what would they say... and why haven't you built one yourself?