- Term for Deceptive Logic
- In what context can kiniira mean 'pleased'?
- ことに… at the end of a sentence
- Must one have intent that a specific food will fulfill the third meal for them?
- The 70 weeks in Daniel 9
- What is “the day of the LORD” found in Isaiah 212 and elsewhere and when does/did it occur?
- Seagull S6 acoustic guitar feels very hard to play
- Customize SharePoint 2013 multiple choices field
- Process service call after sending response
- Forum Advanced solution on Drupal 8
- How to execute the code at certain time without relying on Cron
- Forum URl Alias
- Is it possible to alias paths for contextually generated page views?
- Images field is not loaded in node page in different language as default
- What do you optimize for? Sharpe ratio, profit factor, profit/drawdown, etc
- How does the 'selective liquidity taking' theory explain concavity of a market impact?
- The Top Ten Elements You Won't BELIEVE Are In This Array
- Throttle submissions to ExecutorService
- Media player subtitles in WPF - Part 2 Handlers and notifications
- Media player subtitles in WPF - Part 1 Processing and storing
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?