Latest / The Feed & The Thread / The Feed & The Thread - August 14, 2026
Transcript
- 0:00Traditional design leadership is actually creating burnout. Wait,
- 0:03so rigid planning is the problem? Yes, because treating
- 0:06teams like machines breaks them when things change, and we need
- 0:10to talk about swarm dynamics.
- 0:15Welcome to The Feed and The Thread, brought to you by
- 0:18Chicago Camps. Leadership By Design is on Thursday and
- 0:20Friday, September 17 and 18 and tickets are available now! And
- 0:23while you're at it, get caught up on UX fundamentals with five
- 0:26minute UX at five em UX dot com. The Feed & The Thread is
- 0:29available online at feed and thread dot com to submit your
- 0:32feeds, or download our app for all the feeds and threads
- 0:35delivered right to your pocket.
- 0:44We often treat structure and agility as opposites, forcing
- 0:47leaders to choose between rigid control and chaotic freedom. But
- 0:50what if the best systems borrow from nature, where order emerges
- 0:54without a central commander? Darren Yeo at UX Design.cc
- 0:57argues in "Rethinking design leadership with swarms and
- 1:00flocks" that mechanical leadership creates brittleness
- 1:03in volatile markets. He proposes Structured Emergence, which
- 1:06combines the agility of starling flocks with the endurance of
- 1:09geese formations. This approach avoids the disconnect of pure
- 1:13emergence and the single point of failure in lone-leader
- 1:16models. It suggests that true resilience comes from
- 1:19distributed intelligence, not top-down command. Vitaly
- 1:22Friedman at Smashing Magazine details the stakes in "New EU
- 1:25Guidelines For AI Labelling" regarding new EU AI labeling
- 1:28rules starting in twenty twenty- six. The guidelines require
- 1:31clear labels for deepfakes and AI-generated text on public
- 1:34interest matters, applying globally to any entity serving
- 1:38EU citizens. Crucially, content with substantive human editorial
- 1:41control doesn't need labeling, drawing a sharp line between
- 1:44automation and authorship. This distinction protects human-led
- 1:48work while demanding transparency for fully automated
- 1:51generation. Scott Berkun announces his tenth book in "Big
- 1:54news: new book announcement", shifting from design theory to
- 1:57personal wisdom. He aims to distill two decades of
- 2:00experience into a guide for people who typically dislike
- 2:03self-help genres. The book moves beyond professional frameworks
- 2:06to address broader life questions, having developed
- 2:09quietly on his Substack before this wider release. It offers a
- 2:12pragmatic take on living well, without the usual rules or
- 2:16prescriptive tone. Other articles today from Rosenfeld
- 2:19Media on hiring trends, UX Planet on Claude design tips,
- 2:22and Intercom on evaluating AI releases.
- 2:31Practitioners are wrestling with a quiet tension today between
- 2:34rigid control and chaotic freedom, searching for systems
- 2:37that allow order to emerge naturally rather than being
- 2:40forced from the top down. Over on r/web_design, a developer
- 2:43introduced a local server tool designed to handle include
- 2:46pages, aiming to simplify the testing of static site
- 2:49components. It's a small workflow optimization, but it
- 2:51highlights a bigger truth about developer experience. When we
- 2:54remove the friction from local testing, we aren't just saving
- 2:58time, we're creating space for better decisions. The tool
- 3:00itself might be niche, but the intent reflects a growing desire
- 3:04for environments that support experimentation without breaking
- 3:07the build. It's about building guardrails that feel like
- 3:10support, not barriers. In r/UserExperienceDesign, someone
- 3:13asked a deceptively simple question about whether every new
- 3:16feature actually makes an app better. It's a necessary
- 3:19challenge to the industry's addiction to expansion. We often
- 3:22confuse adding functionality with adding value, but
- 3:24accumulation usually leads to complexity. The real work isn't
- 3:27in building more, it's in refining what's already there.
- 3:30This question forces us to look at our product roadmaps and ask
- 3:33if we're solving problems or just creating more surface area
- 3:37for user confusion. Restraint is a design skill. Over on
- 3:39r/web_design, a beginner is asking how to use AI tools like
- 3:42Claude to build a clothing design preview feature for their
- 3:45printing business. It's a fascinating glimpse into how
- 3:48non-technical creators are approaching complex interactive
- 3:51features. They're not just asking for code, they're asking
- 3:54for a bridge between their vision and technical reality.
- 3:57The tension here's between the promise of AI assistance and the
- 4:00practical limits of current tools. It reveals a shift in who
- 4:03gets to build, but also the steep learning curve that
- 4:06remains. In r/web_design, another designer seeks guidance
- 4:09on structuring a philosophy website to cover history,
- 4:12schools, and books. It's a classic information architecture
- 4:15problem dressed up in academic content. The challenge is making
- 4:18dense knowledge feel accessible without oversimplifying the
- 4:21subject. It's not just about navigation, it's about creating
- 4:24a mental model that helps users find meaning in a vast amount of
- 4:27text. Good structure here doesn't dictate the path, it
- 4:30illuminates the choices. The common thread isn't about
- 4:33choosing between structure and agility, but finding the sweet
- 4:36spot where clear constraints actually enable creative
- 4:39freedom.
- 4:47Chicago Camps is hosting Leadership By Design on Thursday
- 4:49& Friday, September 17 & 18. It's an online event, so you can
- 4:53join from anywhere in the world! Tickets are free, thanks to the
- 4:56generosity of the community! If it's within your budget, you can
- 4:59purchase a general admission ticket for only twenty six
- 5:02dollars - with limited early bird tickets at only fifteen
- 5:05dollars. Get tickets now at Chicago Camps dot org.
- 5:15The EU's new labeling rules draw a hard line at substantive human
- 5:18editorial control, which feels like a legal definition of
- 5:20authorship we've been avoiding in design for years. It's a
- 5:23useful boundary, but it assumes that human control is a binary
- 5:26switch. In practice, most of us are working in the gray zone
- 5:29where we curate, tweak, and approve AI outputs without
- 5:32writing the base code or text. Exactly, and that's why the
- 5:35thread about the local server tool for static sites feels
- 5:37connected. It's not just about speed; it's about creating an
- 5:40environment where the human can intervene meaningfully before
- 5:43the build breaks. If the tool handles the friction, the
- 5:46designer handles the judgment. I see it differently. The tool
- 5:49removes friction, yes, but it also risks automating the moment
- 5:52where we usually catch our own errors. If the local environment
- 5:55is too smooth, we might skip the critical review step because the
- 5:58system looks perfect. That's a valid risk, but the EU
- 6:01guidelines suggest that if you're editing, you're
- 6:03responsible. So the tool isn't replacing judgment; it's forcing
- 6:06us to define what judgment actually looks like in a
- 6:09workflow that's mostly automated. Right, so the skill
- 6:11isn't just using the tool. It's having the discipline to stop
- 6:14and ask if the output aligns with the intent, even when the
- 6:17code runs clean. We're moving from a craft of creation to a
- 6:20craft of verification. And verification only works if we
- 6:23treat it as a distinct, valuable output, not just a final
- 6:25checkbox before shipping.
- 6:29That's The Feed and The Thread for today. We'll catch you next
- 6:32time!