<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Tuned Predictions</title><link>https://www.tunedpredictions.com/blog/</link><description>Recent content in Blog on Tuned Predictions</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 26 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.tunedpredictions.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Retraining is a new candidate, not an automatic upgrade.</title><link>https://www.tunedpredictions.com/blog/retraining-is-a-new-candidate/</link><pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.tunedpredictions.com/blog/retraining-is-a-new-candidate/</guid><description>&lt;p>New outcomes give you more examples to learn from. They do not guarantee that the next model will be better. Treat retraining as another experiment with an explicit review before deployment.&lt;/p>
&lt;h2 id="check-what-changed-in-the-data">Check what changed in the data&lt;/h2>
&lt;p>Before evaluating a new candidate, understand the latest examples. Have labels become more consistent? Has the source changed? Are the new cases representative of the questions the model will face?&lt;/p>
&lt;p>A larger dataset can still contain incomplete outcomes or inputs that reveal the answer. Revisit the task definition and review the prepared examples whenever the source or business process changes.&lt;/p></description></item><item><title>Start with a question you can evaluate.</title><link>https://www.tunedpredictions.com/blog/start-with-a-prediction-question/</link><pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.tunedpredictions.com/blog/start-with-a-prediction-question/</guid><description>&lt;p>A useful prediction model starts with a question whose answer you can check. “Improve sales” is a goal. “Will this opportunity close within seven days?” is a task with an outcome and a time window.&lt;/p>
&lt;h2 id="define-the-outcome-first">Define the outcome first&lt;/h2>
&lt;p>Decide what counts as a positive outcome and when the answer becomes known. If a deal closes after the seven-day window, it is not a positive example for that question. Consistent labels make training and evaluation easier to interpret.&lt;/p></description></item><item><title>What to check before you deploy a model.</title><link>https://www.tunedpredictions.com/blog/evaluate-before-you-deploy/</link><pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.tunedpredictions.com/blog/evaluate-before-you-deploy/</guid><description>&lt;p>A completed training run gives you a candidate model. Whether it helps is a separate question. Answer it with examples the model did not train on and criteria that match your intended use.&lt;/p>
&lt;h2 id="keep-an-evaluation-set-aside">Keep an evaluation set aside&lt;/h2>
&lt;p>Held-out examples let you inspect performance on cases outside the training set. Check that duplicate or closely related records have not ended up on both sides of the split. For tasks that change over time, consider whether the test reflects the period in which the model will be used.&lt;/p></description></item></channel></rss>