- Will the Ford-Fulkerson method return any value if the residual network is ignored?
- What is the recurrence form of Bubble-Sort
- Is Timsort more efficient than merge sort and why?
- On $BPP$ as oracle and $BPP$ with oracle?
- Computational power difference between all interconnected qubit vs few interconnected qubit
- Universal Hash Function
- Can publisher alter or invent writing and attribute that to the author without consultation?
- NFL fields missing team logo
- How much does a full/empty jetboil canister weigh?
- Could ketosis be therapeutic for ADHD based on the neuro-energetic theory of attention?
- Why does NDSolve work with an initial condition but not a final condition?
- Generalization of the probability of union
- DynamicModule with ExampleData
- Using Manipulate and ListLinePlot
- How to solve 3D heat equation with Neumann B.C
- How does hypercalcemia shorten the Q-T interval?
- Question on the concept of mitochondrial Eva
- Units of parameters in epidemiological model
- Help me identify these two ants
- Are humans the only animal that requires “clean water”?

# How do you overcome results oriented thinking from a client?

I am working with a client on a special project that I am going to obfuscate in this question. Basically, I'm trying to overcome some short-term, results-oriented thinking from my client.

Let's say you have a model to forecast the performance of a racehorse. Your model tells your client to sell racehorse X because the probability of its performance is low (<10%). The horse is sold and said racehorse goes on to win 3 races. Your client says, "See, we should have never let go of that racehorse! The model is wrong!"

As data scientist we can understand that anomalies happen and that this horse may have also lost some races - we were just on the wrong side of probability this time. But how do you overcome those objections with the client? How do you turn short-term thinking into a long-term outlook of predictive modeling?