<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Strategy on Ilyas Hamdi</title><link>https://ilyashamdi.com/tags/strategy/</link><description>Recent content in Strategy on Ilyas Hamdi</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 26 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ilyashamdi.com/tags/strategy/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI build vs buy decision</title><link>https://ilyashamdi.com/writing/ai-build-vs-buy/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/ai-build-vs-buy/</guid><description>Build vs buy in AI is downstream of organizational position, not upstream of it. The decision answered without that context is mostly noise.</description></item><item><title>The implicit architecture of every modernization decision</title><link>https://ilyashamdi.com/writing/implicit-architecture-modernization/</link><pubDate>Tue, 19 Nov 2024 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/implicit-architecture-modernization/</guid><description>Every modernization arrives with a stated goal and a much larger implicit one. The modernization that fails is the one where the implicit architecture was never named.</description></item><item><title>The three stages every IDP goes through</title><link>https://ilyashamdi.com/writing/platform-engineering-internal-developer-platforms/</link><pubDate>Tue, 15 Oct 2024 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/platform-engineering-internal-developer-platforms/</guid><description>Most IDPs go through three painful stages: no users, wrong abstractions, and the moment someone realizes it has to be operated as a product.</description></item><item><title>What a cloud architecture review should produce</title><link>https://ilyashamdi.com/writing/cloud-architecture-review-output/</link><pubDate>Thu, 26 Oct 2023 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/cloud-architecture-review-output/</guid><description>Most cloud architecture reviews produce a deck that gets filed. A useful review produces decisions framed for the people who can make them.</description></item><item><title>The security posture question most organizations ask too late</title><link>https://ilyashamdi.com/writing/security-posture-too-late/</link><pubDate>Mon, 14 Aug 2023 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/security-posture-too-late/</guid><description>Four triggers force the question 'what's our security posture, actually?' Three are expensive. The fourth is the one to engineer for yourself.</description></item><item><title>The postponed decision is now the risk</title><link>https://ilyashamdi.com/writing/postponed-technology-decision/</link><pubDate>Wed, 08 Mar 2023 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/postponed-technology-decision/</guid><description>The most expensive technology decisions are the postponed ones. They accumulate cost in places that don't show up as line items.</description></item><item><title>What technical leaders get wrong communicating architecture upward</title><link>https://ilyashamdi.com/writing/communicating-architecture-upward/</link><pubDate>Thu, 22 Sep 2022 00:00:00 +0000</pubDate><guid>https://ilyashamdi.com/writing/communicating-architecture-upward/</guid><description>The same architecture decision can be approved by one audience and rejected by another in the same quarter. Which document each was reading is the difference.</description></item></channel></rss>