<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by scripts/prerender.mjs from src/data/posts.js. -->
<rss version="2.0">
  <channel>
    <title>Soriela — Field Notes</title>
    <link>https://soriela.com/blog/</link>
    <description>Notes from building the reporting layer: where project reporting breaks down, and what the people accountable for delivery do about it.</description>
    <language>en</language>
    <item>
      <title>Why your status report is always three days out of date</title>
      <link>https://soriela.com/blog/status-report-three-days-late/</link>
      <guid>https://soriela.com/blog/status-report-three-days-late/</guid>
      <description>The reporting lag isn't a discipline problem. It's an architecture problem — and it starts the moment your portfolio outgrows a single tool.</description>
      <pubDate>Tue, 25 Aug 2026 09:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
