Hi team,
I wanted to give you a heads up that starting Monday, we'll be moving to the new pod structure we discussed at last month's all-hands. This means some of you will be reporting to new leads, and we're consolidating the Berlin and Amsterdam teams under one workflow.
I've looped in HR to update the org chart. I know the Works Council had some questions about this, but we're on a tight timeline and can't wait for their full review—we'll catch them up after the transition settles.
Please start moving your projects into the new Slack channels by EOD Friday. Let me know if you have questions.
Thanks,
Jordan
Legal Risk
Announcing implementation before consultation is complete violates Works Council rights. Decisions made without proper consultation can be declared invalid and reversed.
Legal Risk
Changes affecting employees across multiple countries often trigger additional consultation requirements. Each country's Works Council may have separate rights that must be addressed.
Legal Risk
Dismissing the consultation process exposes the company to legal challenges. Works Councils have statutory rights that cannot be bypassed due to business timelines.
Relational Risk
This signals to the Works Council that their input isn't valued—damaging trust and making future collaboration more difficult.
Relational Risk
Retroactive notification isn't consultation. This approach breeds resentment and often results in the Works Council pushing back harder on future initiatives.
Operational Risk
When Works Councils feel sidelined, they're more likely to formally object or escalate—creating the exact delays this approach was trying to avoid.
Operational Risk
Using deadline pressure to skip process creates the exact delays you're trying to avoid. If the Works Council escalates, this project stalls—and pulls leadership into crisis management.