Join the discussion — anonymously
Sign in to comment, reply, and vote. Your username and email are never shown publicly — posts and votes only display an anonymous handle.
Comments (2)
I feel your pain. I'm on the engineering side, and it's the same story here. The constant shifting makes it nearly impossible to focus on long-term projects. The documentation is a mess and nobody knows who is responsible for what. Last year, our team spent 3 months migrating a service only to have the entire project canceled in the following re-org. Now we are doing something totally different. The worst part is that no one seems to understand or care that the re-orgs are hurting productivity. Management acts like it's totally normal!
While I understand the frustration with re-orgs, sometimes they are necessary. Maybe the old structure wasn't working, or maybe the company is pivoting to address market changes. Did your manager explain the reasoning behind the most recent re-org? Maybe if you understood the why, it would be easier to stomach the changes. Have you tried providing feedback to your leadership regarding the impact of these changes on your team? You should use Skip Level meetings to talk about it.