<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>predictes — Blog</title><description>predictes is an AI transformation partner: strategy, engineering and managed services that take AI from a slide to something running in your business.</description><link>https://predictes.com</link><language>en</language><item><title>Your AI use-case list has thirty items and no owner</title><link>https://predictes.com/blog/ai-use-case-list-with-no-owner</link><guid isPermaLink="true">https://predictes.com/blog/ai-use-case-list-with-no-owner</guid><description>Long use-case lists feel like progress and function as a way of avoiding a decision. What replaces them is shorter, harder to write and actually gets built.
</description><pubDate>Fri, 04 Sep 2026 00:00:00 GMT</pubDate><category>AI strategy</category><category>prioritisation</category><category>use cases</category><category>decision making</category></item><item><title>Adoption is a budget line, not a hope</title><link>https://predictes.com/blog/adoption-is-a-budget-line</link><guid isPermaLink="true">https://predictes.com/blog/adoption-is-a-budget-line</guid><description>Every transformation plan has a technology budget and an adoption paragraph. That imbalance predicts the outcome more reliably than anything about the technology.
</description><pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate><category>change management</category><category>adoption</category><category>programmes</category><category>budgeting</category></item><item><title>An agent is only as safe as the tools you gave it</title><link>https://predictes.com/blog/an-agent-is-as-safe-as-its-tools</link><guid isPermaLink="true">https://predictes.com/blog/an-agent-is-as-safe-as-its-tools</guid><description>Most attempts to make agents safe happen in the prompt. Almost all of the real safety comes from the tool layer, which is an engineering decision.
</description><pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate><category>AI agents</category><category>security</category><category>tool design</category><category>prompt injection</category></item><item><title>Design for the review, not for the answer</title><link>https://predictes.com/blog/design-for-the-review-not-the-answer</link><guid isPermaLink="true">https://predictes.com/blog/design-for-the-review-not-the-answer</guid><description>The metric that decides whether an AI feature saves anybody time is not accuracy. It is how long it takes a person to confirm or correct what it produced.
</description><pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate><category>UX</category><category>AI interfaces</category><category>review</category><category>trust</category></item><item><title>Build the evaluation harness before the feature</title><link>https://predictes.com/blog/build-the-evaluation-harness-first</link><guid isPermaLink="true">https://predictes.com/blog/build-the-evaluation-harness-first</guid><description>Without a way to score changes, an AI codebase gets slower every month. Teams feel it around month three and usually blame the wrong thing.
</description><pubDate>Fri, 07 Aug 2026 00:00:00 GMT</pubDate><category>evaluation</category><category>testing</category><category>LLM</category><category>regression</category></item><item><title>Most retrieval failures are definition failures</title><link>https://predictes.com/blog/most-retrieval-failures-are-definition-failures</link><guid isPermaLink="true">https://predictes.com/blog/most-retrieval-failures-are-definition-failures</guid><description>When search returns something technically related and practically wrong, the usual response is to tune the retriever. The usual cause is elsewhere.
</description><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate><category>ontology</category><category>retrieval</category><category>master data</category><category>definitions</category></item><item><title>The answer was not wrong. The document was three months old</title><link>https://predictes.com/blog/the-answer-was-wrong-because-the-document-was-old</link><guid isPermaLink="true">https://predictes.com/blog/the-answer-was-wrong-because-the-document-was-old</guid><description>Freshness is the quietest failure in an AI system. Nothing errors, nothing alerts, and the answers are perfectly consistent with a version of reality that has moved on.
</description><pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate><category>data quality</category><category>freshness</category><category>pipelines</category><category>monitoring</category></item><item><title>The AI policy people actually follow</title><link>https://predictes.com/blog/the-ai-policy-people-actually-follow</link><guid isPermaLink="true">https://predictes.com/blog/the-ai-policy-people-actually-follow</guid><description>Most AI policies are written to satisfy a risk register and are ignored within a month. The version that works is shorter, more permissive and considerably more useful.
</description><pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate><category>AI policy</category><category>governance</category><category>training</category><category>shadow AI</category></item><item><title>AI systems do not crash. They drift</title><link>https://predictes.com/blog/ai-systems-do-not-crash-they-drift</link><guid isPermaLink="true">https://predictes.com/blog/ai-systems-do-not-crash-they-drift</guid><description>Conventional monitoring watches for things that stop. The failure mode that matters here produces no error, no alert and perfectly formatted answers that are quietly worse.
</description><pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate><category>monitoring</category><category>drift</category><category>SLA</category><category>operations</category></item><item><title>Go and watch a shift before you write a line of code</title><link>https://predictes.com/blog/go-and-watch-a-shift-first</link><guid isPermaLink="true">https://predictes.com/blog/go-and-watch-a-shift-first</guid><description>Field systems are rejected for reasons that never appear in a requirements document, and every one of them is visible within two hours of standing where the work happens.
</description><pubDate>Fri, 03 Jul 2026 00:00:00 GMT</pubDate><category>field deployment</category><category>requirements</category><category>adoption</category><category>operations</category></item><item><title>When agents write the code, review becomes the bottleneck</title><link>https://predictes.com/blog/when-agents-write-the-code-review-is-the-bottleneck</link><guid isPermaLink="true">https://predictes.com/blog/when-agents-write-the-code-review-is-the-bottleneck</guid><description>Generation got ten times faster and review did not. Teams that measure only the first half accumulate under-reviewed code, and the debt arrives all at once.
</description><pubDate>Fri, 26 Jun 2026 00:00:00 GMT</pubDate><category>AI coding</category><category>code review</category><category>spec-driven</category><category>engineering practice</category></item><item><title>The night shift knows things nobody wrote down</title><link>https://predictes.com/blog/the-night-shift-knows-things-nobody-wrote-down</link><guid isPermaLink="true">https://predictes.com/blog/the-night-shift-knows-things-nobody-wrote-down</guid><description>Unattended production is rarely blocked by robotics. It is blocked by the judgement three experienced people carry, which exists nowhere a system can read.
</description><pubDate>Fri, 19 Jun 2026 00:00:00 GMT</pubDate><category>dark factory</category><category>tacit knowledge</category><category>context</category><category>unattended operation</category></item></channel></rss>