Three jobs that get conflated
Stakeholders often ask for a model when they actually want one of three different things: a prediction (what number, what label), an explanation (why this prediction), or a decision (what action). Each job has a different success metric and a different deployment shape.
Why this matters
An accurate predictor can still be a bad decision tool if the threshold is wrong, the action is misaligned, or the user cannot tolerate the false-positive cost. A great explanation can still be a bad decision tool if the explanation does not point to a feasible intervention. A confident decision system without inspection is a liability when it errs.
Designing for the right job
Write the job sentence first: given X, predict Y, then take action Z when probability exceeds threshold T. If the team cannot finish that sentence, you are not ready to model. The threshold and action belong on the design doc, not in the deploy script as a magic number.