Skip to content

Comment on Honda: 2 years of ml vs 1 month of prompting - heres what we learned

Comments

And yet, the source problem still remains. The company has a shitty way of reporting quality issues in relation to parts and assemblies.

Being an automaker, I can almost smell the silos where data resides, the rigidly defended lines between manufactures, sales and post-sales, the intra-departmental political fights.

Then you have all the legacy of enterprise software.

And the result is this shitty warranty claims data.

As someone that also worked at a large automakers, I think you’re making large, unfounded assumptions.

Warranty data flows up from the technicians - good luck getting any auto technician to properly tag data. Their job is to fix a specific customer’s problem, not identify systematic issues.

There’s a million things that make the data inherently messy. For example, a technician might replace 5 parts before they finally identify the root cause.

Therefore, you need some sort of department to sit between millions of raw claims and engineering. I would be curious what kind of alternative you have in mind?

Silos are the root of all evil.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.