Thread regarding Verizon Communications Inc. layoffs

Transformation going wrong in CXO VCG

First, they let go of the very people who were delivering things. Teams and leaders who were delivering agentic solutions were let go.
The worst part is that they retained bootlicker SDs who wouldn’t deliver a single feature but were good at playing politics.

Those SDs retained their useless teams, many of whom have little to no exposure to technology beyond community college, and they are now responsible for designing some of the worst customer experiences. We are expecting to be AI first company with these kind of people.

But hey, thanks, Tanya and Nancy, for this brilliant display of leadership.


by
| 10 views | | 14 replies (last 12 hours ago) | Reply
Post ID: @OP+1m39zdy7s

14 replies (most recent on top)

This thread speaks facts. Even the directors under the SD are clueless

by
| | Reply
Post ID: @bt+1m39zdy7s

This is what happens when you promote uneducated line-men into leadership positions. You pay them so much that they are afraid to speak up because if they lose their job they know there is no other company d-mb enough to hire them and pay them even half of what Verizon does.

by
| | Reply
Post ID: @bf+1m39zdy7s

The CXO leadership team has become an exclusive club of white women where word salad is served generously, preferably with a side of flattery.

by
| | Reply
Post ID: @b3+1m39zdy7s

Facts. Notice how anyone that challenged Verizon and went against the status-quo is gone. Leaders that actually pushed back were let go and all that are left is overpaid yes-men.

by
| | Reply
Post ID: @b0+1m39zdy7s

Verizon must have a Wall Street type Bo-m Bo-m room based on who stayed?

by
| | Reply
Post ID: @av+1m39zdy7s

So true. Anyone who knew anything about the products and their use cases was summarily dismissed. Mind boggling.

by
| | Reply
Post ID: @an+1m39zdy7s

I agree with the OP, so many SDs don't know anything tech related or even know how to use current agent systems, but they are on all the calls. Blind leading the blind in Verizon for sure. Please Dan fire the AVP, VP, and SDs... they are all talking heads that have zero value.

by
| | Reply
Post ID: @ak+1m39zdy7s

This company has failed for this very reason. It is full of boot li---rs that are afraid to speak truth to power. Nancy, Tanya, Lyons and his stooges. All of these people say yes to all of the stupid ideas because they are afraid to push back and then they wonder why the company is failing,

by
| | Reply
Post ID: @ae+1m39zdy7s

@a8 Wow! I am just wondering who give them funding.. probably another stakeholder

by
| | Reply
Post ID: @a9+1m39zdy7s

@a3
It's good to have stakeholder input. I can remember being asked to help roll out multiple products that no one wanted because the developers made a beautiful product that worked great, but no one bothered to ask if anyone wanted it or needed it.
Spoiler: no one wanted it.
Too much stakeholder input is better than wasted time delivering a loss leader.

by
| | Reply
Post ID: @a8+1m39zdy7s

Welcome to the world of brown nosing.

by
| | Reply
Post ID: @a5+1m39zdy7s

@a3 I agree with you 100%. I am one of the stakeholders, and I am frustrated by the number of people I need in the room to give the developer the go-ahead to move the needle.

We need more technology driven people .. both on product and tech side.

by
| | Reply
Post ID: @a4+1m39zdy7s

I am not sure what the issue is with the perception of the leaders orchestrating these layoffs. Somehow it gets lost that developers produce the product in the end. I see meetings where it’s like 15 people. 12 will be managers and stakeholder types. Those 12 are dreaming up work that could take months to produce and iron out. The other 3 are the one’s that will then go build it. How did we get so lopsided in this ratio? 12:3 so 4:1 stakeholder:developer. And we wonder why the systems here are lacking? What’s to wonder?

Yet over the past years developer head count has taken huge cuts. Stakeholders have too don’t get me wrong! I’m simply saying it was 4:1 stakeholder:developer in 2020 and it’s 4:1 stakeholder:developer in 2026. I think this should be fixed.

Also the stakeholders are not particularly good in my experience. Some are phenomenal. However the majority do not even have access to the production and uat environments for the product they are supposed to own. They do not interface with the users of those products. All of that is also placed on the developers. GTS does far more user sessions than stakeholders. However GTS also has to go figure out how to build what needs to be built. Our stakeholders do not hold water much in regards to helping us define, document, plan the work.

If developers are outnumbered 4:1. And also expected to design, architect, take user issues, and test the code on their system, in UAT, and in production. Also deploy the code overnight. Why are we so surprised that our technology is not returning the results we desire?

by
| | Reply
Post ID: @a3+1m39zdy7s

What is this weird team called experience assurance ? They can let them all go and no one will miss them.

by
| | Reply
Post ID: @a2+1m39zdy7s

Post a reply

: