<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Innovation on Bil Arikan</title><link>https://bil.arikan.ca/tags/innovation/</link><description>Recent content in Innovation on Bil Arikan</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://bil.arikan.ca/tags/innovation/index.xml" rel="self" type="application/rss+xml"/><item><title>What AI Builders Inside Large Orgs Actually Deal With When They Are Not Developers, Engineers, or Technologists</title><link>https://bil.arikan.ca/posts/they-called-it-a-bedroom-project/</link><pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate><guid>https://bil.arikan.ca/posts/they-called-it-a-bedroom-project/</guid><description>The first time an AI prototype I built got dismissed as a &amp;lsquo;bedroom project&amp;rsquo;, it felt personal. By the third time, I started to see a system. In this post I name the patterns AI builders hit inside large enterprises &amp;mdash; provenance attacks, role-legitimacy challenges, capture mechanisms, balkanised AI efforts, and the shape-shifter&amp;rsquo;s double bind &amp;mdash; show that each one is documented in organisational research, and lay out the tactics I have tested for getting past the dismissal hump.</description></item></channel></rss>