<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Portfolio · Paul Brown · Building capability, not dependency · Product &amp; Flow Practitioner</title><link>https://paulisthrivving.xyz/tags/portfolio/</link><description>Writing on flow, forecasting, and building delivery systems that work. By Paul Brown, Partner at Thrivve Partners.</description><generator>Hugo</generator><language>en</language><managingEditor>sayhi@paulisthrivving.xyz (Paul Brown)</managingEditor><webMaster>sayhi@paulisthrivving.xyz (Paul Brown)</webMaster><lastBuildDate>Mon, 17 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://paulisthrivving.xyz/tags/portfolio/index.xml" rel="self" type="application/rss+xml"/><item><title>The queue nobody owns.</title><link>https://paulisthrivving.xyz/writing/queue-nobody-owns/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><author>sayhi@paulisthrivving.xyz (Paul Brown)</author><guid>https://paulisthrivving.xyz/writing/queue-nobody-owns/</guid><description>Eight teams were queuing behind one component, and its oldest item had been open 89 days against a service level expectation of 23. Every one of those initiatives reported green in the same cycle, because RAG status attaches to initiatives and this risk lives between them. Your delivery problem starts long before anything reaches a delivery team.</description><category>Flow and Delivery</category><media:content url="https://paulisthrivving.xyz/writing/queue-nobody-owns/feature.png" medium="image"/></item></channel></rss>