<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Team-Capacity on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/team-capacity/</link><description>Recent content in Team-Capacity on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 19 Oct 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/team-capacity/index.xml" rel="self" type="application/rss+xml"/><item><title>Capping In-Flight Change</title><link>https://drlongnecker.com/blog/2026/10/what-we-stopped-to-make-room/</link><pubDate>Mon, 19 Oct 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/10/what-we-stopped-to-make-room/</guid><description>&lt;p&gt;Picture a product team in the second week of a quarter. So far this quarter, they&amp;rsquo;ve been handed a new planning cadence, a revised on-call rotation, a changed launch checklist, and a request to start using an AI assistant in their daily work. Each change makes sense, though each came out of a different meeting with its own owner and its own deadline.&lt;/p&gt;
&lt;p&gt;Ask the lead how the team is doing and you&amp;rsquo;ll hear &amp;ldquo;it&amp;rsquo;s fine.&amp;rdquo; Ask which of the changes is working and you&amp;rsquo;ll get a nervous (or blank) stare. That pause is a capacity question because with so many changes at once, they&amp;rsquo;re probably not sure of the answer.&lt;/p&gt;</description></item></channel></rss>