3 ms·

> ahem: you told us to migrate to your platform _Someone_ at $LARGE_CORPORATION told you to migrate, but clearly this team didn't. They have no idea who you a

> ahem: you told us to migrate to your platform _Someone_ at $LARGE_CORPORATION told you to migrate, but clearly this team didn't. They have no idea who you are, what you're working on, what your timelines are, what the priority of this work is relative to other things happening at the company, or whether there's other things you can be doing in the meantime. Yet they actually did some diligence, got it approved (after 2 days even), and got it on their roadmap. As others have mentioned, you need to invest in figuring out how to get things done at $LARGE_CORPORATION. Acquisitions are a dime a dozen and certainly do not pre-empt things like security or compliance. This could be a great opportunity to dig in and develop a better understanding. At large companies communication and alignment is generally more difficult to solve than any of the actual technical challenges. You may not like it and choose to leave, but at least try to develop an understanding so you can take that lesson with you.

PeterisP 5y ago
Also, changing the app itself is an option. The $LARGE_CORPORATION infrastructure works for other apps, if it doesn't work for the acquired app, it's not a given that the infra must add features but perhaps rather the app should be restructured according to $LARGE_CORPORATION habits. Sure, it will take work, but if according to OP the alternative is to wait a full quarter, then changing the app might be possible in that time.
fuzzfactor 5y ago
I think I give about the same advice, so I put this here When life gives you Bozos, enjoy the circus while you're there. Get the most out of it. This may very well be your best opportunity to deeply determine exactly what this sluggish bureaucracy needs to overcome this type of weakness and result in improved performance by an excellent margin, or maybe a multiple. Even if you don't get to deploy many of your ideas under the current situation, it's always good to know how to turn bigger companies around. In case you do get into a position where that may be expected of you someday. Develop the qualities that are most needed by this size org and if there is very little uptake then you just keep becoming more valuable to another outfit and more able to avoid places where they actually don't get as much done as they should.

PeterisP 5y ago

Also, changing the app itself is an option. The $LARGE_CORPORATION infrastructure works for other apps, if it doesn't work for the acquired app, it's not a given that the infra must add features but perhaps rather the app should be restructured according to $LARGE_CORPORATION habits. Sure, it will take work, but if according to OP the alternative is to wait a full quarter, then changing the app might be possible in that time.

fuzzfactor 5y ago

I think I give about the same advice, so I put this here When life gives you Bozos, enjoy the circus while you're there. Get the most out of it. This may very well be your best opportunity to deeply determine exactly what this sluggish bureaucracy needs to overcome this type of weakness and result in improved performance by an excellent margin, or maybe a multiple. Even if you don't get to deploy many of your ideas under the current situation, it's always good to know how to turn bigger companies around. In case you do get into a position where that may be expected of you someday. Develop the qualities that are most needed by this size org and if there is very little uptake then you just keep becoming more valuable to another outfit and more able to avoid places where they actually don't get as much done as they should.