<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Leadership on Mansoor</title><link>https://mansoor.io/leadership/</link><description>Recent content in Leadership on Mansoor</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mansoor.io/leadership/index.xml" rel="self" type="application/rss+xml"/><item><title>How to run an AI initiative that actually ships</title><link>https://mansoor.io/leadership/how-to-run-an-ai-initiative/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://mansoor.io/leadership/how-to-run-an-ai-initiative/</guid><description>&lt;p&gt;Most enterprise AI initiatives stall not because the technology doesn&amp;rsquo;t work, but because of how they&amp;rsquo;re run.&lt;/p&gt;
&lt;h2 id="start-with-the-problem-not-the-technology"&gt;Start with the problem, not the technology&lt;/h2&gt;
&lt;p&gt;The most common failure mode is a team that has decided to &amp;ldquo;do AI&amp;rdquo; before they&amp;rsquo;ve identified a specific problem worth solving. They run workshops, evaluate vendors, and build proofs-of-concept — but without a clear, measurable outcome to optimize for, nothing ships.&lt;/p&gt;
&lt;p&gt;The discipline is forcing the question early: what is the specific decision or task we&amp;rsquo;re trying to improve, how do we currently measure it, and what would success look like in six months?&lt;/p&gt;</description></item></channel></rss>