#Machine Learning
Articles about Machine Learning — exploring patterns, best practices, and real-world implementations in production systems.
12 posts tagged with machine learning. ← All posts
Predicting who will leave is the easy half. The hard half is acting on it: treating the persuadable, respecting a budget, and proving the intervention actually kept anyone.
Predicting attrition and acting on it: churn features and labels, uplift vs propensity (treat the persuadable), and an agentic retention workflow that recommends and executes interventions with guardrails and holdout mea…
How to build next-best-action and product recommendations for financial services without crossing privacy or fair-lending lines.
Building next-best-action and recommendations for financial products: signals and feature stores, candidate generation + ranking, suitability/eligibility constraints, and cold-start — without crossing privacy or fair-len…
How to build a quant model that predicts up-or-down moves without quietly fooling yourself into a backtest that never survives contact with real markets.
Building a quant direction model without fooling yourself: feature engineering from price/volume, walk-forward (not random) cross-validation, avoiding look-ahead and survivorship bias, and why realistic backtests beat im…
When fraud labels are scarce or the attack is brand new, unsupervised anomaly detection buys you a signal before you ever have a training set.
When you have few or no labels: unsupervised anomaly detection.
Why accuracy lies, how to train on a needle-in-a-haystack, and picking a threshold by the money it saves.
Fraud is a needle-in-a-haystack problem.
Why a scorecard trained only on funded loans quietly overstates its own accuracy, and the inference techniques that pull the declined population back into view.
Why credit models trained only on approved-and-funded loans are biased, and the reject-inference techniques (reclassification, parceling, augmentation) that correct for the applicants you never observed.
How lenders turn a model's raw probability into the specific, legally required reasons a declined applicant must receive.
Turning model outputs into legally-required adverse-action reason codes. Global vs local explainability, SHAP values, mapping contributions to reason codes, and fairness checks (disparate impact) that regulators expect.
How WOE binning turns raw variables into monotonic, interpretable predictors on a log-odds scale, and how Information Value ranks which features earn a place in a regulator-defensible scorecard.
How WOE binning turns raw variables into monotonic, interpretable predictors, how Information Value ranks feature predictive power, monotonic binning, handling missing/rare bins, and why this discipline underpins regulat…
How lenders turn application and bureau data into a single, defensible number — and why the interpretable scorecard still wins in regulated lending.
The end-to-end credit-scoring pipeline: target definition (bad = 90+ dpd), feature engineering, WOE transformation, a logistic-regression scorecard, points scaling (PDO), and validation (KS, Gini, AUC).
A technically excellent model is worthless until it changes a number someone cares about. Here is how to design backward from that number.
Why technically excellent models never ship: no clear business metric, organizational buy-in, validation and model-risk sign-off, monitoring, and the prototype-to-production chasm.
Financial ML lives under regulators, adversaries, and money-denominated errors — so you design backward from a business metric, not forward from a model.
What sets financial ML apart from general ML: strict regulatory scrutiny and mandatory explainability, high-stakes and immediately quantifiable errors, messy multi-source data, non-stationarity, and adversarial actors.
Treating fraud, credit, and risk models as governed assets with a lifecycle, an inventory, and an audit trail regulators can actually read.
Development, independent validation, approval, monitoring, and retirement of risk/fraud/credit models under SR 11-7-style governance.
All posts on this site are written by Pratik Dhanave, an Agentic AI Architect with 7+ years building production distributed systems, multi-agent AI platforms, and cloud-native infrastructure. About the author → Each article includes working code, architecture diagrams, and references to the specific frameworks and standards discussed. Browse all posts or explore related topics using the tag cloud above.