The situation
A machine learning program aimed to predict failures of an engine component across 50,000 customer vehicles, projecting $8M in warranty savings and an 80% cut in downtime per event. My first mandate was to establish feasibility.
There was no precedent to adapt, the assigned engineer went on leave as the program started, and leadership wanted the answer to be yes. Any no had to survive hard scrutiny.
What I did
- Built the domain knowledge. I worked with subject matter experts and sensor vendors to understand 16 sensors and the component health calculations behind them.
- Did the analysis hands-on. With data engineers I unified 200+ derived parameters, then ran the exploratory analysis myself in Python on Databricks, overlaying every component's behavior around real failures.
- Validated it before it left my desk. I walked the plots and the logic through the subject matter experts and the data scientists separately, and had each group confirm the conclusion from its own expertise, so what reached leadership was a cross-functional finding rather than a program manager's opinion.
The pushback
The reception was hostile in exactly the way I expected. Leadership challenged both the analysis and the tooling, asking whether I had used the most sophisticated data tools available. Because I had done the work hands-on, I could answer in the first person: the finding was about what the data contains, not what the tooling can do, and no algorithm can isolate a component-specific signature that does not exist in the sensor data.
Then I moved the frame to the risk they cared about most. Forcing a model onto this data would generate wrong failure predictions across 50,000 customer vehicles, and each false alarm or missed failure would cost far more in customer trust than the program could ever save. The conversation shifted from whether I had analyzed it correctly to what the responsible decision for the customer was.
Outcome
- Claimed entitlement
- $8M, 80% downtime cut
- Real entitlement on available sensor data
- Not reachable
- Implementation cost avoided
- ~$1M
- Program time redirected
- 6 months
- Wrong predictions that reached customers
- None
Leadership, the business stakeholders, and the customer all accepted the no-go. The method, meaning domain first, then the full parameter space, then a cross-component check and multi-discipline validation, became a template for pressure-testing AI investments before funding them.
Being right is a process, not a moment. The conclusion survived scrutiny because every layer under it, the domain knowledge, the data unification, the hands-on analysis, and the multi-disciplinary validation, had been built to survive scrutiny before the meeting ever happened.
What I would do differentlyPair the no-go with a data collection plan and a scheduled re-review, so the answer reads as not feasible yet, and here is what would change it.
How the analysis was run