0.5 is almost never the right threshold
Default 0.5 is a convention, not a recommendation. The right threshold depends on the cost of false positives, the cost of false negatives, and the operating capacity of the team. Move the threshold to match the business, then defend the choice with a number, not a vibe.
Three honest threshold strategies
- Cost-minimizing — set the threshold where expected cost is minimum.
- Recall at precision floor — pick the threshold where precision ≥ P (often used when team capacity is fixed).
- Top-K capacity — score everyone, take the top K, and let downstream act on those K (always a thresholded ranking under the hood).
Logging and monitoring the threshold
Once you ship a threshold, log it next to the model version. Drift can change the right threshold even when the model is unchanged; monitor the actual operating point against the intended one weekly.