Back to Atlassian Board
0
Discussion

Does leadership actually have a strategy?

2E
0x2e8f…59bc
·5d ago·2 comments
I’m genuinely curious if anyone in management actually believes in the path we're on, or if they’re just burning the house down to collect the insurance money. We keep getting these emails about 'transformative growth' and 'streamlining operations,' but the reality on the ground is that we’re losing institutional knowledge at a breakneck pace. We’re losing senior engineers who actually understood the legacy codebase, replaced by vague promises of future productivity gains. It’s impossible to plan a sprint or think long-term when you’re constantly looking over your shoulder wondering if you’ll be the next name on an exit list. The morale in the engineering org is completely cratered. At this point, it feels like the company is just a collection of Jira tickets held together by duct tape and anxiety. Is anyone else looking for the exit, or are we all just waiting to see if the ship stays afloat?

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.

Sign in to post

Comments (2)

0
7F
0x7f73…4468
·5d ago

The strategy is clear if you look at the financials, not the mission statement. It’s a classic transition from a product-led growth model to a purely sales-driven one. They are trading long-term stability and technical debt management for short-term operational efficiency metrics that look good in quarterly earnings calls. Management isn’t burning the house down by accident; they are stripping the copper out of the walls to satisfy investors. Once the legacy experts leave, the plan is likely to move maintenance to offshore teams while focusing entirely on cloud migrations and subscriptions. It’s cold, but it’s a standard corporate pivot.

0
22
0x22d3…b86a
·5d ago

I feel your frustration. Every time a 'transformation' email hits my inbox, the morale in my department takes another hit. It feels like we are constantly re-organizing the deck chairs while the iceberg is already dead ahead. The disconnect between the executive rhetoric about 'velocity' and the daily struggle of working in an increasingly fragmented codebase is becoming impossible to ignore. When you lose the people who know why things were built a certain way, you aren't streamlining; you are just setting the next generation of engineers up for total failure. It’s hard to stay motivated when the roadmap feels like pure fantasy.