The Feed & The Thread - June 16, 2026

We're designing the board, not the game. So the interface is just a distraction. And that means your AI product might be a hollow shell. We need to fix the logic.

Welcome to The Feed and The Thread, brought to you by Chicago Camps. Leadership By Design is on Thursday and Friday, September 17 and 18 and tickets are available now! And while you're at it, get caught up on UX fundamentals with five minute UX at five em UX dot com. The Feed & The Thread is available online at feed and thread dot com to submit your feeds, or download our app for all the feeds and threads delivered right to your pocket.

We keep polishing the interface while the system underneath breaks. That disconnect costs us trust and clarity every day. Adrian Levy at UX Design.cc makes this case in "The board is not the game". He argues we mistake screens for the actual experience. We design cards and pieces, but we skip the rules that drive behavior. That oversight creates products that feel disjointed and shallow. We need to define the incentives, not just the layout. Salesforce is acquiring Fin for three point six billion dollars. That's the news in "Salesforce signs definitive agreement to acquire Fin" from Eoghan McCabe at Intercom Blog. Fin pivoted early to customer agents using large language models. Leadership stays put to guide that strategy forward. This deal signals that conversational AI is now core infrastructure, not just a feature. Artemii Lebedev at Codrops explores "Designing A Better Lou: Reducing Cognitive Load Through Design, Content, and Systems". He shows how to reduce cognitive load in healthcare design. Clarity comes from aligning content, design, and system architecture. Progressive disclosure prevents information overload effectively. Simplifying the journey requires rigorous work behind the scenes. Other reads today from CSS-Tricks on new CSS functions and UX Design.cc on designing human control over AI.

There's a quiet erosion happening in our profession today. We're polishing the interface while the system underneath breaks, and that disconnect costs us trust every single day. Over on r/UXDesign, a designer is parsing micro- behaviors to see if they're being subtly demoted after a workplace conflict. They're tracking name ordering in documents and gaze bias in meetings, looking for signs of diminished status. This highlights the tension between informal management styles and the need for clear professional standing. When leadership relies on silence and subtle cues instead of direct feedback, the interface of the workplace becomes unreliable. We can't design for clarity if our own organizational structures are opaque. In r/UXDesign, someone is grappling with the zero percent progress bar problem at launch. They want to avoid empty restaurant syndrome, where a blank bar makes a crowdfunding platform look dead or untrustworthy. The goal is to create excitement despite low initial activity. This is a classic case of optimizing the visual layer while ignoring the underlying data reality. If the system has no traction, no amount of UI polish can manufacture trust. We're trying to mask a broken foundation with better graphics. Also on r/UXDesign, the conversation has shifted to how AI tools like Claude Code are altering the handover process. One designer stopped pixel-pushing in Figma entirely, focusing instead on research and feeding prompts to AI for functional prototypes. This suggests a convergence of UX and product management roles. The workflow is changing faster than the definitions of our jobs. We're building new interfaces for thinking, but we haven't agreed on what the system underneath should actually do. A freelance designer on r/UXDesign is weighing a twelve-month contract against isolation and high workload. They have a better offer with fewer hours but lower pay, creating a conflict between financial stability and well- being. This isn't just a career dilemma, it's a systemic failure. We're asking people to sustain burnout for the sake of immediate cash flow. The interface of the job market looks stable, but the support structure is crumbling. Finally, an intern on r/UXDesign feels like the worst ever after struggling with component variants in a large IoT app. They're overwhelmed by the complexity and fear they won't be rehired. This reveals a gap in how we onboard new talent. We're handing them complex systems without teaching the underlying logic. We expect them to navigate the interface before we explain how the engine works. That's a recipe for failure, not learning. We're spending too much time fixing the skin of the problem and not enough time repairing the bone.

Chicago Camps is hosting Leadership By Design on Thursday & Friday, September 17 & 18. It's an online event, so you can join from anywhere in the world! Tickets are free, thanks to the generosity of the community! If it's within your budget, you can purchase a general admission ticket for only twenty six dollars - with limited early bird tickets at only fifteen dollars. Get tickets now at Chicago Camps dot org.

The Salesforce acquisition of Fin signals that conversational AI is now core infrastructure. But the thread on the zero percent progress bar reveals we're still trying to polish empty interfaces. We're building high-tech systems on low-trust foundations. That disconnect is the real issue. We design cards and pieces while ignoring the rules that drive behavior. If the system has no traction, no amount of UI polish can manufacture trust. We're masking broken foundations with better graphics. Exactly. Adrian Levy argues we mistake screens for the actual experience. We define incentives poorly, then blame the layout for the disjointed feel. The cognitive load isn't just visual. It's structural. So we stop optimizing for the launch day aesthetic and start optimizing for the data reality. If the progress bar is empty, show why. Don't hide the lack of activity behind a fake sense of momentum. Transparency builds more trust than a smooth animation ever could. But organizations reward the smooth animation. They see the polished interface and assume the product is healthy. The incentive structure pushes us to hide the cracks rather than expose them. Then we change the incentive. We make clarity a metric, not just a nice-to-have. When we align content, design, and system architecture, the interface stops being a mask and starts being a mirror. A mirror that reflects the actual state of the system. And that reflection is the only thing that actually scales. That's The Feed and The Thread for today. We'll catch you next time!