{"id":11833,"date":"2026-11-13T12:30:00","date_gmt":"2026-11-13T12:30:00","guid":{"rendered":"https:\/\/www.cotocus.com\/blog\/?p=11833"},"modified":"2026-11-13T12:30:00","modified_gmt":"2026-11-13T12:30:00","slug":"machine-learning-project-expectations-primer","status":"publish","type":"post","link":"https:\/\/www.cotocus.com\/blog\/machine-learning-project-expectations-primer\/","title":{"rendered":"Machine Learning Project Expectations: Beginner Primer, Glossary"},"content":{"rendered":"

Sooner or later, someone outside your team will ask when the model will be “done” and how accurate it will be. If you have not answered those questions before work begins, the answers will be invented for you. Setting machine learning project expectations early is the cheapest form of risk management a beginner can practise. This primer lists what to say, in what order, and defines the handful of terms that make the conversation easier.<\/p>\n

Start with the honest shape of a project<\/h2>\n

Many first-time sponsors picture machine learning as a switch: feed in data, flip it on, receive answers. The real shape is a loop. Data is gathered and cleaned, a model is trained, results are checked, problems are found, and the cycle repeats. Early results are usually unimpressive, and that is normal.<\/p>\n

The first expectation to set is therefore about shape. Tell stakeholders that the project will move in rounds, and that each round will produce something they can see, even if the first few are rough. This keeps the mood steady when the first demo does not look like the final product.<\/p>\n

The five things to say before you begin<\/h2>\n
    \n
  1. What the model will do.<\/strong> One sentence about the task, such as sorting support tickets or forecasting weekly demand. Be specific about the decision it supports.<\/li>\n
  2. What it will not do.<\/strong> Name the tempting jobs that are out of scope, for example making final decisions without human review.<\/li>\n
  3. When people will see progress.<\/strong> A rhythm of demos and updates, rather than a single big date.<\/li>\n
  4. What you need from them.<\/strong> Access to data, time from subject experts and someone to judge whether outputs make sense.<\/li>\n
  5. What happens after launch.<\/strong> Models need watching and refreshing, so the project does not end on release day.<\/li>\n<\/ol>\n

    Mini-glossary for beginners<\/h2>\n

    You do not need a long vocabulary, only a shared one. These terms cover most conversations.<\/p>\n