|
|
|
|
|
by yieldcrv
179 days ago
|
|
As someone that pivoted to agentic work and quit the job that tried to get the existing team to do agentic work: All companies are structuring like this, and some are more equipped to do it than others Basically the executive team realizes the corporate hierarchy is too rigid for the lowly engineers to surface any innovation or workflow adjustments above the AI anxiety riddled middle management and bandwagon chaser’s desperate plea for job security, and so the executive creates a team exempt from it operating in a new structure Most agentic work impacts organizations that are outside of the tree of that software/product team, and there is no trust in getting the workflow altered unless a team from upon high overwrites the targeted organization we are at that phase now, I expect this to accelerate as executives catch on through at least mid-summer 2026 |
|
I think the biggest issue with Meta here, is how much visibility they have to adjacent orgs, which is not too surprising given the expenditures, but still surprising. It should be a separate unit and the expenses absolutely thought of as separate from the rest of the org(s).