Recognition is not a vibes milestone. It is not the point where people are angry enough, excited enough, or tired enough to finally say something out loud. It is the point where the campaign's actual structure gets tested.
Why workers get pulled too early
When management is awful, the impulse to go public can feel completely reasonable. But anger and readiness are not the same thing. Going public too early can expose the strongest workers before the support underneath them is broad enough to hold.
What majority support actually means
- support is broad across the real workplace map
- not just one team, office, friend group, or chat cluster
- workers understand the issue and the risk
- people are willing to take a next step, not just agree privately
- the campaign is not built around one or two heroic people
Before a public move
- map support carefully
- clarify exclusion and classification questions
- compare how remote, hybrid, and in-person segments line up
- identify weak spots where management pressure will hit hardest
- decide what the public step is actually meant to accomplish
Common mistakes
- treating online enthusiasm as majority structure
- leaving contractors, remote workers, or quieter teams out of the map
- assuming recognition immediately solves pay, surveillance, or workload issues
- escalating because management is terrible rather than because the structure is ready
Better questions
- do we know where support is thin?
- are we strong across offices, time zones, and major teams?
- are workers clear on what comes after the public move?
- have we confused intensity with preparedness?