Thread regarding Ford layoffs

FNV4 epic failure

FNV4 is done? Hahahahahaha

So with this epic failure, what has D Field managed to achieve in his time at Ford? GE2, canceled. FNV4, down in flames. Next will be TE1 moved out to 2030. I've heard that it is actually canceled, but they are delaying in order to avoid the cancelation costs.

Seriously, Ford could not manage to deliver a zonal electric architecture that Rivian was able to do with just a quarter of the size team that Ford threw at the task?

If they wanted to actually turn this company around they would fire every LLx associated with FNV4, starting with Doug. All GSRs should be required to apply to and interview for open positions to stay on the Ford payroll.

by
| 17247 views | | 55 replies (last May 29, 2025) | Reply
Post ID: @OP+1jsybqq5q

55 replies (most recent on top)

No clear requirements, too many people who wanted things designed their way, no ownership and meeting after meeting with no conclusion, and to top off this cluster f**k cake, cluesless management. It was sonbad that I dont think FNV4 is even going to become a case study in business school.

by
| | Reply
Post ID: @ck+1jsybqq5q

Oh sh-t management from
BlackBerry acquisition

🚩⛳️⛳️🚩🚩⛳️⛳️🚩⛳️⛳️🚩

by
| | Reply
Post ID: @cj+1jsybqq5q

@c5+1jsybqq5q

I deadass think this was ford posting. I know they got footprints but I just have a gut feeling they are trying to connect similarities on some things

I don’t know what the angle is

by
| | Reply
Post ID: @cf+1jsybqq5q

Mr gsr are you against test driven development? It sounds like they are shooting for robustness mixed with gherkin formatting from lord farquad. But who is the architect if you’re doing TDD? Tdd is more yolo, minus the business cases and shieeeeet or are they writing BDD cases respectfully im confused asf u just threw a bunch of random sh-t while complaining but I don’t understand any faults

by
| | Reply
Post ID: @ca+1jsybqq5q

@am+1jsybqq5q "They just happened to manage the amazing team under them and took all the credit."

The amazing teams in other companies that, despite their managers, were able to deliver, and we took the managers, and left the workers. That's why most managers here at Ford are just another obstacle to defeat in order to do a proper job.

by
| | Reply
Post ID: @b0+1jsybqq5q
Can anyone inside the architecture teams tell us why this has been such a debacle? Unbelievable waste of time and resources

Changing requirements all the time. No communication in advance. No impact to changes understood before approved. It was just garbage in, so garbage came out.

by
| | Reply
Post ID: @ay+1jsybqq5q

Amen to OP.

If you told me three years ago we would still be dependent on a furniture company CEO's decisions until 2030, I would've questioned your logic. But, here we are. Billions of dollars of NRE and very little to show for it. JF has demonstrated in the most damaging way that his upper management elites do not know how to deliver. We keep spending millions on these outside talent hires and they are NOT the people actually doing the groundbreaking work. They just happened to manage the amazing team under them and took all the credit.

by
| | Reply
Post ID: @am+1jsybqq5q

You need to build support to reach for the sky,
just trying to jump and get there is too much.
Everything is new, and a lot of the opinionated people are pushing in an unproven directions.

by
| | Reply
Post ID: @ah+1jsybqq5q

Too many NDAs so nobody knew what the other was or wasn’t doing.
Complete failure of leadership starting with DF and JF.

by
| | Reply
Post ID: @ag+1jsybqq5q

Ease up on the GSRs. This was a monumental failure of leadership. I'm in the trenches on this. The struggle for years on this has been a build vs buy problem. Management basically let competing teams work on each of these, hoping one would come up with a winner.

This doubled costs (dirty little secret) and resulted in both teams getting distracted by what the other team was doing. Oh and then purposely not sharing findings with each other in the spirit of competition.

So several years and millions of dollars later, you ended up with 2 FNV4 architectures that were only partially complete.

There were some very smart people in these trenches. Management's multi-personality nature on this is where the failure occurred.

OP was right about firing all LL5+s involved. LL6s and GSRs should be transferred to other teams.

by
| | Reply
Post ID: @ac+1jsybqq5q

Isnt most of rivian made up of ex-ford employees??

by
| | Reply
Post ID: @ab+1jsybqq5q

I don’t know. Fire all LLxs and all GSRs, sounds like just disassembling the company to me.

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

I find the talent pool at all levels very sub par. They'll never be able to beat Tesla and Rivian unless they hire real good people rather than converting contractors from really poor services company.

by
| | Reply
Post ID: @a7+1jsybqq5q

From architecture/software pov we were told to delay (hold off) on new feature development due to incomplete requirements. This been going on since early last year which now cost us big time. I blame incompetent LL6+ in this org for this mess

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

Can anyone inside the architecture teams tell us why this has been such a debacle? Unbelievable waste of time and resources

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

Post a reply

: