TODAY'S PRESSURE POINTS

Bryan Zmijewski makes the point that design only creates real value when it changes how the business works, not just what gets made. His chart shows the gap between teams that “do design” in scattered, reactive ways and teams that use design as a connected system tied to decisions, priorities, and outcomes.

DEEP CUT: This isn’t a design problem, it’s an influence problem. Late, disconnected design improves output but not outcomes.

Luke Wroblewski points out that as AI agents start doing more on their own, the way we manage software needs to change. Familiar tools like boards, dashboards, inboxes, and lists still help, but they start to break when agents act independently. His breakdown shows where each pattern works and where it falls short as complexity grows.

DEEP CUT: Most teams are trying to fit autonomous behavior into interfaces built for manual control. The opportunity is not picking the “right” UI, it’s recognizing when the model itself no longer fits how the system behaves.

Bethany Gilleeney breaks down Model Context Protocol (MCP) in a way that actually makes sense for designers. Instead of treating design and development as separate steps, MCP connects them by making design systems readable by AI and code. That shift moves feedback earlier, reduces translation errors, and keeps teams working from the same source of truth.

DEEP CUT: Teams struggle because translation happens too late. By the time issues show up, the context is gone and fixes are slower. 

READER BONUS 

QUICK ACTIONS