<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[My Site 4]]></title><description><![CDATA[My Site 4]]></description><link>https://eekcolei.wixsite.com/studiocollective/blog</link><generator>RSS for Node</generator><lastBuildDate>Sun, 05 Apr 2026 13:53:01 GMT</lastBuildDate><atom:link href="https://eekcolei.wixsite.com/studiocollective/blog-feed.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[When Progress Depends on Intervention, It’s a Conditions Problem]]></title><description><![CDATA[There’s a pattern I see in capable teams that looks like a people problem, but usually isn’t. Everyone is working. Everyone is smart. And somehow progress still depends on someone stepping in—again and again—to reset priorities, re-litigate decisions, translate what was “meant,” or stitch together work that should have held on its own. When that becomes normal, the system defaults to personal heroics: more effort, more meetings, more escalation. It can feel like leadership. It can look like...]]></description><link>https://eekcolei.wixsite.com/studiocollective/post/when-progress-depends-on-intervention-it-s-a-conditions-problem</link><guid isPermaLink="false">697276754a67d0390c08544b</guid><pubDate>Thu, 22 Jan 2026 19:11:51 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/b263ce_beebeb3cdfd149bcaa73caf0bcbc989f~mv2.jpg/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>eekcolei</dc:creator></item><item><title><![CDATA[Reframing Leadership as the Design of Conditions for Collective Intelligence: A Field Guide]]></title><description><![CDATA[Leadership is getting heavier. Not because leaders are less capable, but because many organizations have quietly redesigned the job into constant intervention. You can see it in everyday moments that have quietly become normal. Work pauses while a leader says, “Let me just go investigate,” and returns later with direction. Stakeholder conversations are delayed because the leader prefers to be the primary communicator, or wants to “check in first.” Teams keep circling back because priorities...]]></description><link>https://eekcolei.wixsite.com/studiocollective/post/reframing-leadership-as-the-design-of-conditions-for-collective-intelligence-a-field-guide</link><guid isPermaLink="false">69727654beedc8e89b0a9832</guid><pubDate>Thu, 22 Jan 2026 19:11:23 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/b263ce_f9f889dcd056409eacb092b725415674~mv2.png/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>eekcolei</dc:creator></item></channel></rss>