<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>Edward McFowland · AI Fault Line</title><link>https://aifaultline.com/authors/edward-mcfowland/</link><description>New papers by Edward McFowland in the AI Fault Line guide, and news naming them.</description>
<item><title>Paper: Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of Artificial Intelligence on Knowledge Worker Productivity and Quality</title><link>https://aifaultline.com/research/p/doi-10-1287-orsc-2025-21838/</link><guid>https://aifaultline.com/research/p/doi-10-1287-orsc-2025-21838/</guid><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><description>A preregistered experiment with 758 Boston Consulting Group consultants finds that GPT-4 access improved performance on realistic tasks inside AI&#x27;s capabilities but worsened it on a task just outside them. The authors call this uneven pattern a &quot;jagged technological frontier&quot; that can run through a single knowledge workflow.</description></item>
<item><title>Paper: Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of AI on Knowledge Worker Productivity and Quality</title><link>https://aifaultline.com/research/p/doi-10-2139-ssrn-4573321/</link><guid>https://aifaultline.com/research/p/doi-10-2139-ssrn-4573321/</guid><pubDate>Sun, 01 Jan 2023 00:00:00 +0000</pubDate><description>In a field experiment with several hundred Boston Consulting Group consultants completing realistic case tasks, access to GPT-4 raised completion speed and quality substantially for tasks within the model&#x27;s capability frontier, but consultants using AI on a task just outside that frontier were markedly more likely to produce wrong answers than those without it. The &#x27;jagged frontier&#x27; finding — that AI&#x27;s capability boundary is uneven and hard for users to perceive in the moment — has become a touchstone for warnings that AI productivity gains are highly task-dependent rather than universal.</description></item>
</channel></rss>
