<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Platform Engineering - Tag - Lee Wynne</title><link>https://leewynne.com/tags/platform-engineering/</link><description>Platform Engineering - Tag - Lee Wynne</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 26 Mar 2026 17:09:59 +0000</lastBuildDate><atom:link href="https://leewynne.com/tags/platform-engineering/" rel="self" type="application/rss+xml"/><item><title>Build for Consumability, The Provider to Consumer Model That Makes AWS Scale.</title><link>https://leewynne.com/posts/build-for-consumability-provider-consumer-model-aws/</link><pubDate>Thu, 26 Mar 2026 17:09:59 +0000</pubDate><author>Lee Wynne</author><guid>https://leewynne.com/posts/build-for-consumability-provider-consumer-model-aws/</guid><description><![CDATA[<div class="featured-image">
                <img src="/images/posts/provider-consumer-model.jpg" referrerpolicy="no-referrer">
            </div><p>Most platform teams think their job is to build infrastructure. They&rsquo;re wrong. Their job is to build infrastructure that other teams can consume without thinking about it.</p>
<p>The difference matters more than most organisations realise. A platform team that builds a beautifully architected AWS landing zone but makes it painful to consume has built a bottleneck, not a platform. And in a large enterprise (where dozens of product teams need to ship features against real deadlines) bottlenecks don&rsquo;t just slow you down, they breed shadow IT, workaround architectures, and the kind of ungoverned sprawl that keeps security teams awake at night.</p>]]></description></item></channel></rss>