Weekly Edition  /  Vol. 01 No. 1403 Oct 2026Read time 7 min  /  Front  /  Archive

UN—DESIGN

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.

Building got cheap, and nobody rebuilt the thing that decides what gets built. Design systems trusted by everyone and used by nobody. Agentic stacks grown into mud. Journey insight with no address to go to.

Edited by Bruno Monteiro  ·  un-design.org

The Jist

Thirty seconds. 7 stories. Each line maps to an item below.
  1. Luke Wroblewski's answer to twenty years of unread design system docs: agents read them every single time, so the system becomes a steering layer, not a library.Phase 03
  2. NN/g studied people building agentic systems with no engineering background and found 1997's big ball of mud reborn, because abundance removed every reason to prioritise.Phase 02
  3. zeroheight's 2026 report: 91% of teams trust their design system, 38% say it is actually adopted, 61% say they do not have enough people.Phase 01
  4. NN/g proposes PACED, a framework for deciding when disclosing AI involvement helps and when it costs you.Phase 03
  5. Gartner's strategic planning assumption: by 2028, 30% of service orgs will run a staffed journey management office. The other 70% keep doing projects.Phase 04
  6. Apple's revised EU business terms took effect 01 October, splitting fees into a new structure every EU-distributing team now has to model.Phase 04
  7. Figma made Weave tools publishable to the Community and added a Figma node, which turns in-house design utilities into distributable artifacts.Phase 03
Four phases. Click one to read only what belongs to it.
Showing all items.
01
The Signal
7 items / past 7 days
AI in Design Phase 03 / Intelligence-Centered Redesign LukeW / 01 Oct

The design system's real reader was never a designer

Luke Wroblewski's point lands like a verdict: design teams spent decades begging people to read the documentation, and agents read it every single time.

Why it mattersWhen agents write most of the front-end code, the design system stops being reference material and becomes a steering layer: tokens, an AGENTS.md file and a live design system page that agents inspect before they touch anything. On his recent projects the code became the source of truth and the Figma file became downstream. That inverts twenty years of handoff assumptions, and it means an out-of-date design system is now an active source of drift rather than a passive embarrassment.

Go deeper
Research Phase 02 / Strategic Deconstruction NN/g / 02 Oct

Abundance rebuilt the big ball of mud

NN/g watched non-engineers build elaborate agentic systems and recognised the 1997 anti-pattern exactly, because nothing was forcing anyone to prioritise.

Why it mattersParticipants could not locate the files their own systems depended on. One ran every session out of his Downloads folder after a crash. One was told by his own model that he was stuck in a prerevenue infrastructure loop, refining the system instead of using it. The diagnostic NN/g offers is brutally portable to a product org: if you wanted to change how the system works, would you know what to change? If the answer is no, the AI is the sole navigator and you are hoping.

Go deeper
Hard Data Phase 01 / Systemic Discovery zeroheight Design Systems Report 2026

91% trust it. 38% use it.

The fifth zeroheight report, drawn from 147 practitioners, puts a number on the gap everyone has been describing anecdotally: trust and adoption have fully decoupled.

Why it mattersAlongside that split: 61% of design system teams say they do not have enough people, 16% of systems are maintained by exactly one person, and 61% of teams are five people or fewer. 56% are using AI, only 15% say it is living up to the hype. Five of the ten most-used weekly tools are now AI tools. Read together with the LukeW piece, the data says the bottleneck was never component quality. It was mandate.

Go deeper
Content Design Phase 03 / Intelligence-Centered Redesign NN/g / 25 Sep

When to say AI touched this

NN/g's PACED framework treats AI disclosure as a design decision with a cost curve, not a compliance checkbox.

Why it mattersHow people react to being told AI helped make something varies with audience, context, and the nature and degree of the use. That is a content design problem sitting inside a trust problem, and it is about to appear in release notes, in-app copy, support replies and store listings across every product org. Deciding it once, deliberately, beats having each team improvise.

Go deeper
Journey Management Phase 04 / Adaptive Implementation Gartner via TheyDo

Journey insight finally gets an owner, or a department

Gartner's assumption: by 2028, 30% of customer service and support organisations will embed a journey management discipline with a fully staffed journey management office.

Why it mattersThe report names the failure honestly. Insight does not have anywhere to go. Journeys span three teams and therefore belong to none. The prescribed fix is structural: full-time journey managers owning one or two journeys each, reporting initially to the head of service, with cross-functional authority from day one. Whether that is a cure or a parallel bureaucracy is the open question, and it is this week's best provocation.

Go deeper
Platform Phase 04 / Adaptive Implementation Apple Newsroom / effective 01 Oct

Apple's new EU terms are live as of Thursday

The revised business terms for EU app distribution took effect on 01 October, which means the modelling exercise is no longer hypothetical.

Why it mattersIf any part of your app reaches EU users, the fee structure your business case assumed changed this week. Separately, from September the age-rating questionnaire requires a social-media capability declaration on every new submission or update, including notarisation for alternative distribution. Neither is glamorous. Both will quietly break a release if nobody owns them.

Go deeper
Tooling Phase 03 / Intelligence-Centered Redesign Figma Release Notes / Sep

Figma turns internal tools into shippable artifacts

Weave tools became publishable to the Figma Community in mid-September, and a new Figma node wires designs straight into Weave workflows.

Why it mattersThe unit of design output keeps moving up a level: first files, then components, then systems, now tools. A team that builds a Weave utility for its own motion or image pipeline can now distribute it. Expect the same org politics that design systems have, one layer higher, and sooner than anyone has governance for.

Go deeper
No items in this phase under 01 The Signal. That absence is data too.
02
Close to Your Work
3 items / mobile product leadership
People Management Phase 02 / Strategic Deconstruction Marty Cagan, SVPG / 25 Sep

Cagan calls the manager cull temporary

His argument: the flight from management to individual contribution is real, necessary and short-lived, and skilled leadership is becoming a competitive advantage rather than an overhead.

Why it's relevantYou just hired a Director of Mobile Product to manage the PM/PO layer, which is the opposite bet to the one the headlines are making. Cagan gives you the argument for it in a form you can hand upward: the principle that experts lead experts, the observation that some companies are already reversing their manager reductions, and the claim that as build cost falls, vision, strategy and team topology decisions matter more. Worth reading before your next exec conversation about the shape of the org, not after.

Go deeper
Mobile Quality Phase 04 / Adaptive Implementation Luciq 2026 Mobile App Performance Playbook

The numbers that turn crash-free into a rating

Median crash-free sessions sit at 99.95%, top performers at 99.99%, laggards at 99.77%, and the report maps those bands straight onto store ratings.

Why it's relevantThis is the translation layer between your engineering dashboard and your exec conversation. Roughly 99.7% crash-free to hold three stars, roughly 99.85% to clear 4.5. iOS median 99.91% against Android 99.80%. And the non-fatal tolerances you probably have no SLO for: ANRs and OOMs around 10 per 10K sessions, hangs around 200, forced restarts around 250. Set these as release gates with your new director and the quality conversation stops being a matter of taste.

Go deeper
App Store Policy Phase 04 / Adaptive Implementation Google Play / live 30 Sep

Android developer verification is now in force

Verification took effect on 30 September, requiring legal name, address, government ID and contact details against every developer account.

Why it's relevantThe vast majority of Play accounts were migrated automatically, which is exactly why this is worth one explicit check rather than an assumption. If any part of your estate ships through a secondary account, a contractor's account, an acquired team's account or a sideloaded internal build, find out this week whether it is verified. Unverified means cannot publish or update, and discovering that mid-incident is the expensive version.

Go deeper
No items in this phase under 03 Close to Your Work. That absence is data too.
03
The Library
Standing follow list

Craft & Interface

  • Awwwards — sites of the day
  • The FWA — experimental web
  • Mobbin — mobile pattern library
  • Godly — curated web design
  • Core77 — industrial design
  • LukeW — mobile and AI interface strategy

Research & Service Design

Product Leadership

Mobile Platform & Delivery