<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Alexandre Leonardo — Reflections</title>
    <link>https://www.alexandreleonardo.pt/en/reflexoes</link>
    <atom:link href="https://www.alexandreleonardo.pt/en/feed.xml" rel="self" type="application/rss+xml" />
    <description>Essays on digital transformation, information systems and the public sector.</description>
    <language>en</language>
    <lastBuildDate>Wed, 09 Sep 2026 08:13:07 GMT</lastBuildDate>
    <item>
      <title>Sprints in a world where code is written in minutes</title>
      <link>https://www.alexandreleonardo.pt/en/reflexoes/repensar-sprints-era-ia</link>
      <guid isPermaLink="true">https://www.alexandreleonardo.pt/en/reflexoes/repensar-sprints-era-ia</guid>
      <pubDate>Tue, 18 Aug 2026 09:00:00 GMT</pubDate>
      <description>The sprint was designed to manage a scarce resource: human execution time. When an agent writes, tests and reviews a feature in minutes, that assumption no longer holds and the ceremonies start imposing artificial waits. A reflection on what changes in management when the bottleneck moves from production to decision.</description>
      <category>Artificial Intelligence</category>
      <category>Project Management</category>
      <category>Agile</category>
      <category>Software Development</category>
    </item>
    <item>
      <title>The State that cannot measure itself</title>
      <link>https://www.alexandreleonardo.pt/en/reflexoes/estado-que-nao-se-mede</link>
      <guid isPermaLink="true">https://www.alexandreleonardo.pt/en/reflexoes/estado-que-nao-se-mede</guid>
      <pubDate>Sun, 14 Jun 2026 09:00:00 GMT</pubDate>
      <description>We know how many people use a public service, but almost never whether it solved their problem - and without that measurement there is no way to tell whether the AI now being pushed everywhere brings value. The proposal is to flip the order: use AI itself to build the measurement we never had, before using it to automate.</description>
      <category>Data</category>
      <category>Measurement</category>
      <category>Public Sector</category>
      <category>Artificial Intelligence</category>
    </item>
    <item>
      <title>Will AI replace civil servants?</title>
      <link>https://www.alexandreleonardo.pt/en/reflexoes/ia-empregos-setor-publico</link>
      <guid isPermaLink="true">https://www.alexandreleonardo.pt/en/reflexoes/ia-empregos-setor-publico</guid>
      <pubDate>Sun, 12 Apr 2026 09:00:00 GMT</pubDate>
      <description>Starting from Anthropic's study on AI's impact on the labour market, this reflection explores what happens when we apply that logic to Portuguese public administration: the paradox between a shortage of people and a surplus of automatable roles, the problem of attraction and exit, and why the current model does not work.</description>
      <category>Artificial Intelligence</category>
      <category>Public Sector</category>
      <category>Public Administration</category>
      <category>Labour Market</category>
    </item>
    <item>
      <title>Migrating legacy systems in the public sector: what nobody warns you about before you start</title>
      <link>https://www.alexandreleonardo.pt/en/reflexoes/migrar-sistemas-legados-setor-publico</link>
      <guid isPermaLink="true">https://www.alexandreleonardo.pt/en/reflexoes/migrar-sistemas-legados-setor-publico</guid>
      <pubDate>Sat, 14 Mar 2026 09:00:00 GMT</pubDate>
      <description>Before replacing a system that has been running for 15 or 20 years, it is worth understanding what it solved. This reflection explores the risk of undervaluing legacy, the importance of listening to those who maintained it, and the tension between respecting what exists and knowing when to cut.</description>
      <category>Legacy Systems</category>
      <category>Public Sector</category>
      <category>Digital Transformation</category>
      <category>Project Management</category>
    </item>
    <item>
      <title>Reforming public procurement: accelerating with AI is not enough, we need to change what we buy</title>
      <link>https://www.alexandreleonardo.pt/en/reflexoes/reforma-contratacao-publica</link>
      <guid isPermaLink="true">https://www.alexandreleonardo.pt/en/reflexoes/reforma-contratacao-publica</guid>
      <pubDate>Sat, 07 Feb 2026 09:00:00 GMT</pubDate>
      <description>Introducing AI to speed up public procurement may make the problem more visible, but it does not solve it. The biggest friction lies in what gets contracted, how success is defined, and how delivered value is measured.</description>
      <category>Public Procurement</category>
      <category>Artificial Intelligence</category>
      <category>Public Sector</category>
      <category>Digital Transformation</category>
    </item>
    <item>
      <title>"Build or buy" in the public sector: AI is changing the rules of the game</title>
      <link>https://www.alexandreleonardo.pt/en/reflexoes/construir-ou-comprar-ia-setor-publico</link>
      <guid isPermaLink="true">https://www.alexandreleonardo.pt/en/reflexoes/construir-ou-comprar-ia-setor-publico</guid>
      <pubDate>Thu, 15 Jan 2026 09:00:00 GMT</pubDate>
      <description>AI makes “build” a practical option in the public sector by reducing friction and dependency, while demanding stronger architecture, governance, and technical accountability.</description>
      <category>Artificial Intelligence</category>
      <category>Public Sector</category>
      <category>Digital Transformation</category>
      <category>Governance</category>
    </item>
    <item>
      <title>Why building information systems in the public sector is different—and what rarely gets discussed</title>
      <link>https://www.alexandreleonardo.pt/en/reflexoes/por-que-projetos-falham</link>
      <guid isPermaLink="true">https://www.alexandreleonardo.pt/en/reflexoes/por-que-projetos-falham</guid>
      <pubDate>Sun, 28 Dec 2025 09:00:00 GMT</pubDate>
      <description>Digitising public processes without simplifying them only computerises old problems. The real challenge is keeping a simple path for most users while giving dignified routes to exceptions, without killing the MVP or betraying universality.</description>
      <category>Digital Transformation</category>
      <category>Public Sector</category>
      <category>Public Services</category>
      <category>Service Design</category>
    </item>
  </channel>
</rss>
