From Problem-Solving to Purpose-Fulfilling
We deconstruct outdated systems to make space for what's next. Not optimizing within constraints, challenging the constraints themselves.
A quiet day, so this issue is short. A web standard for vector graphics is back in front of implementers, a design publication offers a guide to naming UI components, and a service design piece asks what changes when the customer is an AI agent.
The SVG Working Group published the snapshot and invites developers to implement it.
Why it mattersReported: the snapshot was published on 6 Oct 2026 and implementers are invited to build against it. Opinion: for design teams this is a prompt to check the icon pipeline against browser support, not an urgent change.
Go deeperA hands-on guide to naming UI components, with references, conventions and structures.
Why it mattersReported from the article listing only (Cosima Mielke, 6 Oct 2026). Uncertain: the full article could not be opened, so this is a listing-level read. Opinion: naming is design system governance, and it matters more once machines read the system.
Go deeperLoyalty tiers and emotional journey maps lose pull when an agent judges offers on rules, data and price.
Why it mattersReported (Sue Duris): she advises machine-readable content, reliable APIs and plain-language policies, while still designing for the person who approves. Uncertain: the page states no date. This is an opinion piece.
Go deeperShip on a fixed schedule, and let features that are not ready wait for the next departure.
Why it's relevantReported (Pol Piella, an older evergreen piece): use feature flags and pick cadence from your own velocity data. Opinion: a director can delegate cadence by setting the scope-freeze rule instead of feature dates.
Go deeper