<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Insights on AI For Human Expertise</title><link>https://aiforhumanexpertise.com/blog/</link><description>Recent content in Insights 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/blog/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>Deskilling Is Already Happening: Evidence Across Domains</title><link>https://aiforhumanexpertise.com/blog/deskilling-across-domains/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/deskilling-across-domains/</guid><description>&lt;h2 id="the-pattern-beneath-the-hype"&gt;The Pattern Beneath the Hype&lt;/h2&gt;
&lt;p&gt;It is tempting to treat the deskilling AI can cause as a future risk, something to worry about once the technology is more capable. The evidence says otherwise. Across very different fields, driven by the same human factors, the erosion is already measurable. The lesson from each domain is the same one, dressed in different clothes.&lt;/p&gt;
&lt;h2 id="what-deskilling-actually-looks-like"&gt;What Deskilling Actually Looks Like&lt;/h2&gt;
&lt;p&gt;Deskilling is rarely dramatic. It shows up in four recognisable ways:&lt;/p&gt;</description></item><item><title>The Cognitive Cost of Convenience</title><link>https://aiforhumanexpertise.com/blog/cognitive-cost-of-convenience/</link><pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/cognitive-cost-of-convenience/</guid><description>&lt;h2 id="the-ai-expertise-paradox"&gt;The AI Expertise Paradox&lt;/h2&gt;
&lt;p&gt;AI offers tremendous convenience and real productivity gains. The question that rarely gets asked is: at what cost to our skills?&lt;/p&gt;
&lt;p&gt;Here is a quick thought experiment. What happens tomorrow if your favourite AI system disappears? Who on your team still knows how to do the task without it? For a growing number of tasks, the honest answer is becoming uncomfortable.&lt;/p&gt;
&lt;p&gt;This is the paradox at the heart of how most organisations are adopting AI: &lt;strong&gt;the more we rely on it for convenience, the more our underlying skills may decline.&lt;/strong&gt; The gain is immediate and visible. The cost is gradual and easy to miss, right up until the moment you need the skill and find it has quietly gone.&lt;/p&gt;</description></item><item><title>The LLM Wiki: A Pattern for Smarter Organisational Knowledge Bases</title><link>https://aiforhumanexpertise.com/blog/llm-wiki-smarter-knowledge-bases/</link><pubDate>Sun, 05 Apr 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/llm-wiki-smarter-knowledge-bases/</guid><description>&lt;h2 id="a-better-pattern-for-organisational-knowledge"&gt;A Better Pattern for Organisational Knowledge&lt;/h2&gt;
&lt;p&gt;Andrej Karpathy - the AI researcher known for his work at OpenAI and Tesla - recently shared a pattern he calls the &amp;ldquo;&lt;a href="https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f"&gt;LLM Wiki&lt;/a&gt;.&amp;rdquo; It addresses a fundamental limitation in how most organisations use large language models for knowledge work today.&lt;/p&gt;
&lt;p&gt;The standard approach is retrieval-augmented generation (RAG): upload documents, the AI retrieves relevant chunks at query time, and generates an answer. It powers tools like ChatGPT file uploads and most enterprise search products. It works - but nothing accumulates. Every question forces the AI to rediscover knowledge from scratch, piecing together fragments across documents each time.&lt;/p&gt;</description></item><item><title>AI for Knowledge Transfer: The Opportunity Most Organisations Miss</title><link>https://aiforhumanexpertise.com/blog/ai-for-knowledge-transfer/</link><pubDate>Sun, 08 Mar 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/ai-for-knowledge-transfer/</guid><description>&lt;h2 id="ai-for-knowledge-transfer-the-opportunity-most-organisations-are-missing"&gt;AI for Knowledge Transfer: The Opportunity Most Organisations Are Missing&lt;/h2&gt;
&lt;p&gt;Across industries, the dominant conversation about AI is about augmentation: helping people work faster, automating repetitive tasks, and processing existing information more efficiently. That is valuable, and organisations are beginning to see the returns across areas like reporting, scheduling, and operational monitoring.&lt;/p&gt;
&lt;p&gt;But there is an equally important application that is largely overlooked, and in our experience building AI systems inside large organisations, one of the highest-value problems AI is actually well-suited to address.&lt;/p&gt;</description></item><item><title>AI Doesn't Just Miss Tacit Knowledge. It Can Destroy It.</title><link>https://aiforhumanexpertise.com/blog/welcome/</link><pubDate>Mon, 09 Feb 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/welcome/</guid><description>&lt;h2 id="the-standard-framing-gets-something-important-wrong"&gt;The Standard Framing Gets Something Important Wrong&lt;/h2&gt;
&lt;p&gt;The dominant logic behind most AI adoption is straightforward: find the task, automate the task, reduce the cost or time. It is a reasonable starting point. The problem is what it misses.&lt;/p&gt;
&lt;p&gt;Tasks do not exist in isolation. Behind most of the tasks worth automating is a body of expertise: judgement built over years, pattern recognition that operates faster than it can be explained, contextual awareness that no process document has ever fully captured. This is tacit knowledge, and it is almost never accounted for in the standard AI adoption model.&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><item><title>Five Questions to Ask Before Starting Any AI Project</title><link>https://aiforhumanexpertise.com/blog/five-questions-before-ai/</link><pubDate>Tue, 03 Feb 2026 00:00:00 +0000</pubDate><guid>https://aiforhumanexpertise.com/blog/five-questions-before-ai/</guid><description>&lt;h2 id="why-these-questions-matter-before-any-ai-project"&gt;Why These Questions Matter Before Any AI Project&lt;/h2&gt;
&lt;p&gt;Before starting any AI project, the questions that matter most are not technical; they are foundational. We&amp;rsquo;ve seen millions spent on AI initiatives that were doomed from the start, not because the technology was wrong, but because nobody paused to think critically about the fundamentals.&lt;/p&gt;
&lt;p&gt;Here are five questions we ask at the start of every engagement. They&amp;rsquo;re simple, but the answers are revealing.&lt;/p&gt;</description></item></channel></rss>