<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Ameioud: Notes</title>
  <subtitle>Short notes by Reda Ameioud</subtitle>
  <link href="https://ameioud.com/feed/notes.xml" rel="self"/>
  <link href="https://ameioud.com"/>
  <updated>2026-05-25T00:00:00Z</updated>
  <id>https://ameioud.com/notes/</id>
  <author>
    <name>Reda Ameioud</name>
    <email>R.Ameioud7@gmail.com</email>
  </author>
  <entry>
    <title>Note — May 25, 2026</title>
    <link href="https://ameioud.com/notes/on-procurement-timelines/"/>
    <updated>2026-05-25T00:00:00Z</updated>
    <id>https://ameioud.com/notes/on-procurement-timelines/</id>
    <content type="html">&lt;div style=&quot;font-family: Georgia, &#39;Times New Roman&#39;, serif; font-size: 16px; line-height: 1.6; color: #2f2f2f; max-width: 600px; margin: 0 auto;&quot;&gt;&lt;p&gt;Procurement timelines are almost always underestimated in the same direction. The technical work — writing specs, running tenders, evaluating bids — takes roughly as long as people expect. The organizational work — getting alignment on what you actually want before the process starts — takes two to three times longer.&lt;/p&gt;
&lt;p&gt;The result is that the timeline slips not because the procurement ran badly, but because it started before the internal work was finished. This is fixable. It just requires treating stakeholder alignment as part of the procurement process rather than a prerequisite to it.&lt;/p&gt;
&lt;/div&gt;</content>
  </entry>
  <entry>
    <title>Note — May 19, 2026</title>
    <link href="https://ameioud.com/notes/on-vendor-lock-in/"/>
    <updated>2026-05-19T00:00:00Z</updated>
    <id>https://ameioud.com/notes/on-vendor-lock-in/</id>
    <content type="html">&lt;div style=&quot;font-family: Georgia, &#39;Times New Roman&#39;, serif; font-size: 16px; line-height: 1.6; color: #2f2f2f; max-width: 600px; margin: 0 auto;&quot;&gt;&lt;p&gt;Vendor lock-in is usually framed as a risk to manage. In practice most organizations accept it passively and only discover the cost when it is too late to renegotiate from a position of strength.&lt;/p&gt;
&lt;p&gt;The decision that creates lock-in is rarely labeled as such. It is a procurement choice that optimizes for implementation speed, or a renewal that is easier than running a new tender. The lock-in is just the accumulation of those choices, each reasonable at the time.&lt;/p&gt;
&lt;/div&gt;</content>
  </entry>
  <entry>
    <title>Note — May 12, 2026</title>
    <link href="https://ameioud.com/notes/on-defense-spending-and-capacity/"/>
    <updated>2026-05-12T00:00:00Z</updated>
    <id>https://ameioud.com/notes/on-defense-spending-and-capacity/</id>
    <content type="html">&lt;div style=&quot;font-family: Georgia, &#39;Times New Roman&#39;, serif; font-size: 16px; line-height: 1.6; color: #2f2f2f; max-width: 600px; margin: 0 auto;&quot;&gt;&lt;p&gt;Europe&#39;s defense spending numbers look serious on paper. The real question is whether the industrial base can absorb the money fast enough to produce capability rather than backlogs.&lt;/p&gt;
&lt;p&gt;Defense procurement is not like procurement in other sectors. Lead times are long, suppliers are few, and the supply chain has spent thirty years being optimized for peacetime volumes. Throwing budget at that structure does not compress the timeline. It creates a queue.&lt;/p&gt;
&lt;/div&gt;</content>
  </entry>
  <entry>
    <title>Note — May 5, 2026</title>
    <link href="https://ameioud.com/notes/on-data-and-decisions/"/>
    <updated>2026-05-05T00:00:00Z</updated>
    <id>https://ameioud.com/notes/on-data-and-decisions/</id>
    <content type="html">&lt;div style=&quot;font-family: Georgia, &#39;Times New Roman&#39;, serif; font-size: 16px; line-height: 1.6; color: #2f2f2f; max-width: 600px; margin: 0 auto;&quot;&gt;&lt;p&gt;Most organizations have more data than they can act on and less information than they need. These are related problems but they require opposite solutions.&lt;/p&gt;
&lt;p&gt;The first gets fixed by reducing what gets measured to what actually changes behavior. The second gets fixed by investing in the synthesis layer -- the people and processes that turn data into a recommendation someone can act on. Most digital transformation programs address the data problem and ignore the synthesis problem entirely.&lt;/p&gt;
&lt;/div&gt;</content>
  </entry>
</feed>
