<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Mederic Burlet · Writing</title>
  <subtitle>Mederic Burlet helps enterprise teams deploy AI into how they build software, from architecture to adoption. 700+ practitioners trained, 2-3x productivity gains, multi-agent and MCP systems.</subtitle>
  <link href="https://mederic.me/writing/atom.xml" rel="self"/>
  <link href="https://mederic.me/writing"/>
  <id>https://mederic.me/writing</id>
  <updated>2026-06-25T00:00:00.000Z</updated>
  <author><name>Mederic Burlet</name><uri>https://mederic.me</uri></author>
  <entry>
    <title>Why AI pilots stall before production</title>
    <link href="https://mederic.me/writing/why-ai-pilots-stall"/>
    <id>https://mederic.me/writing/why-ai-pilots-stall</id>
    <updated>2026-06-25T00:00:00.000Z</updated>
    <published>2026-06-20T00:00:00.000Z</published>
    <summary>AI pilots stall because they optimise for a demo, not for adoption. Production requires architecture, guardrails, and a change in how teams work, not a better model.</summary>
    <category term="ai-adoption"/>
    <category term="enablement"/>
  </entry>
  <entry>
    <title>Designing MCP systems for real teams</title>
    <link href="https://mederic.me/writing/mcp-systems-for-real-teams"/>
    <id>https://mederic.me/writing/mcp-systems-for-real-teams</id>
    <updated>2026-05-30T00:00:00.000Z</updated>
    <published>2026-05-30T00:00:00.000Z</published>
    <summary>Good MCP systems expose a few high-leverage tools with clear boundaries, not every API you have. Scope, access control, and observability matter more than autonomy.</summary>
    <category term="mcp"/>
    <category term="agents"/>
  </entry>
  <entry>
    <title>What 700 trained engineers taught me about adoption</title>
    <link href="https://mederic.me/writing/700-engineers-on-adoption"/>
    <id>https://mederic.me/writing/700-engineers-on-adoption</id>
    <updated>2026-05-12T00:00:00.000Z</updated>
    <published>2026-05-12T00:00:00.000Z</published>
    <summary>After training 700+ practitioners, the pattern is clear: adoption is a behaviour change, not a tooling rollout. Role-specific practice and internal champions are what make it stick.</summary>
    <category term="enablement"/>
    <category term="ai-adoption"/>
  </entry>
</feed>
