<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Strategy on AI For Human Expertise</title><link>https://aiforhumanexpertise.com/categories/strategy/</link><description>Recent content in Strategy on AI For Human Expertise</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sat, 11 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aiforhumanexpertise.com/categories/strategy/index.xml" rel="self" type="application/rss+xml"/><item><title>Which Doors Should Machines Walk Through?</title><link>https://aiforhumanexpertise.com/blog/which-doors-should-machines-walk-through/</link><pubDate>Sat, 11 Jul 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/which-doors-should-machines-walk-through/</guid><description>&lt;p&gt;Jeff Bezos gave managers a simple test for how much care a decision deserves. Some decisions are two-way doors: walk through, dislike what you find, and walk back out at little cost. These should be made quickly, by individuals or small teams, because caution buys nothing. Others are one-way doors: irreversible, or nearly so, and worth slow deliberation and senior sign-off. His warning was that growing organisations tend to apply the heavyweight, one-way process to everything, and grind to a halt as a result.&lt;/p&gt;</description></item><item><title>Constrained Generation Is Symbolic AI Smuggled Into LLMs</title><link>https://aiforhumanexpertise.com/blog/constrained-generation-is-symbolic-ai/</link><pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/constrained-generation-is-symbolic-ai/</guid><description>&lt;h2 id="the-toolkit-most-practitioners-already-reach-for"&gt;The Toolkit Most Practitioners Already Reach For&lt;/h2&gt;
&lt;p&gt;Anyone who has shipped a language-model application beyond the prototype stage has, at some point, used constrained generation. The shape of the encounter is consistent. The model produces text that is almost right and occasionally wrong in ways the consumer cannot tolerate. Someone on the team reaches for one of a small set of tools: Outlines, lm-format-enforcer, the JSON-schema mode in their model API, a regex post-filter, a structured-output decoder. The wrong answers stop. The system ships.&lt;/p&gt;</description></item><item><title>From RAG To KAG: The Structured-Knowledge Upgrade</title><link>https://aiforhumanexpertise.com/blog/from-rag-to-kag-the-structured-knowledge-upgrade/</link><pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/from-rag-to-kag-the-structured-knowledge-upgrade/</guid><description>&lt;h2 id="rag-solved-one-problem-and-created-another"&gt;RAG Solved One Problem And Created Another&lt;/h2&gt;
&lt;p&gt;Retrieval augmented generation became the default architecture for grounding language model outputs in 2023 and 2024, and for good reason. It addressed the most obvious failure mode of out-of-the-box large language models, which was producing fluent text on topics the model did not actually have current or correct information about. RAG pulls relevant documents into the model&amp;rsquo;s context at inference time. The model can cite them. Hallucinations drop. Useful systems get built.&lt;/p&gt;</description></item><item><title>A Five-Role Diagnostic For Any AI Agent</title><link>https://aiforhumanexpertise.com/blog/a-five-role-diagnostic-for-any-ai-agent/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/a-five-role-diagnostic-for-any-ai-agent/</guid><description>&lt;h2 id="most-agent-problems-have-a-diagnostic"&gt;Most Agent Problems Have A Diagnostic&lt;/h2&gt;
&lt;p&gt;When an AI agent fails in production, the conversation almost always turns to the model. The team waits for a bigger model, a better-tuned variant, a different vendor, a new context window. Sometimes the team turns to prompts instead: more careful instructions, more examples, a sharper system message. Most failures are neither. They are failures of structure, and the structure question is a thirty-year-old framework most engineers have never read.&lt;/p&gt;</description></item><item><title>The Harness Is Where Symbolic AI Returned</title><link>https://aiforhumanexpertise.com/blog/the-harness-is-where-symbolic-ai-returned/</link><pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/the-harness-is-where-symbolic-ai-returned/</guid><description>&lt;h2 id="the-standard-story-about-ai-agents-misses-half-the-system"&gt;The Standard Story About AI Agents Misses Half The System&lt;/h2&gt;
&lt;p&gt;The dominant story about building AI agents is straightforward: take a language model, prompt it well, give it tools, and let it loop. The model is doing the work. Everything else is plumbing.&lt;/p&gt;
&lt;p&gt;This story is incomplete in a way that has practical consequences. The plumbing is not plumbing. It is a body of design decisions that determines whether the agent works in production, fails silently, or quietly degrades over time. And some of it, the parts that earn the name, is doing what symbolic AI has always tried to do: making reasoning explicit, checkable, and tied to a model of the world.&lt;/p&gt;</description></item><item><title>Designing AI That Protects Expertise</title><link>https://aiforhumanexpertise.com/blog/designing-ai-to-protect-expertise/</link><pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/designing-ai-to-protect-expertise/</guid><description>&lt;h2 id="erosion-is-a-design-choice-not-a-destiny"&gt;Erosion Is a Design Choice, Not a Destiny&lt;/h2&gt;
&lt;p&gt;The first two posts in this series made an uncomfortable case: AI can quietly erode the very expertise it depends on, and across domains &lt;a href="https://aiforhumanexpertise.com/blog/deskilling-across-domains/"&gt;that erosion is already happening&lt;/a&gt;. It would be easy to read that as an argument against AI. It is not.&lt;/p&gt;
&lt;p&gt;AI systems do not have to deskill the people who use them. That outcome is the result of design decisions, usually unexamined ones. Make different decisions and the same technology can preserve expertise, and in some cases actively strengthen it. This post is about those decisions.&lt;/p&gt;</description></item><item><title>Why Most AI Projects Fail and How to Beat the Odds</title><link>https://aiforhumanexpertise.com/blog/why-most-ai-projects-fail/</link><pubDate>Sat, 07 Feb 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/why-most-ai-projects-fail/</guid><description>&lt;h2 id="why-ai-projects-fail-three-root-causes"&gt;Why AI Projects Fail: Three Root Causes&lt;/h2&gt;
&lt;p&gt;The numbers are stark: research consistently shows that around 80% of AI projects fail to deliver meaningful business value. Not because the technology doesn&amp;rsquo;t work, but because organisations approach AI the wrong way.&lt;/p&gt;
&lt;figure class="not-prose stat-callout" role="figure"&gt;
 &lt;div class="stat-callout-inner"&gt;
 &lt;div class="stat-callout-number"&gt;80%&lt;/div&gt;
 &lt;div class="stat-callout-text"&gt;
 &lt;p class="stat-callout-label"&gt;of AI projects fail to deliver meaningful business value.&lt;/p&gt;
 &lt;p class="stat-callout-source"&gt;Research consensus across recent industry studies.&lt;/p&gt;
 &lt;/div&gt;
 &lt;/div&gt;
&lt;/figure&gt;

&lt;p&gt;After working across dozens of AI initiatives, we&amp;rsquo;ve identified three root causes that explain the vast majority of failures.&lt;/p&gt;</description></item></channel></rss>