A game about contradiction becomes a masterclass in layering conflicting experiences for intentional meaning.
Using the indie game Indika as a case study, this piece introduces 'PX Contrast' — a framework for deliberately layering conflicting player (or user) experiences to produce intentional multiple interpretations. It argues that contradiction in design isn't a flaw to smooth over but a tool for depth and meaning.
Practical, no-fluff guidance on finding mentors and actually making the relationship work.
The article challenges common misconceptions that hold designers back from seeking mentorship, then walks through how to choose the right mentor, fulfill your responsibilities as a mentee, and properly close out a mentorship. It emphasizes showing mentors that their advice led to concrete action and learning.
A clear-eyed case for why semantic HTML isn't a constraint but a creative foundation.
The piece reframes web standards through three lenses: writer, engineer, and artist. It argues that separating content structure from visual presentation isn't limiting — it's what lets design decisions actually hold up across contexts, devices, and assistive technologies.
Skip the wireframes. Start writing the conversation your interface needs to have.
The article argues for designing interfaces by writing out the real-life conversation you'd want a product to have with a user before touching any UI. It introduces an emotion-driven goal-writing exercise to clarify what a page should make someone feel before deciding what it should say or show.
The field keeps rebranding but 'UX' stubbornly survives. Here's the data on why.
NN/g analyzed job titles and role labels across the industry and found that despite years of predictions, no single term has successfully replaced 'UX.' Labels like 'product design' and 'product research' have grown in use, but 'UX' remains the dominant umbrella term practitioners and employers actually reach for.
Robin Rendle on why a design system that designers work around is not actually a design system.
Riffing on an Ethan Marcotte essay, Rendle argues that a design system is only as good as its usefulness under real deadline pressure. If designers are regularly bypassing it to ship, that's not a process failure — it's a signal the system itself has broken down. Short, pointed, and honest.
A Google UX researcher's field notes on what hospitality design gets right that apps still miss.
A Google researcher documents how luxury hotels like the Burj Al Arab orchestrate experience across sensory, spatial, and temporal layers that digital products rarely consider. The piece extracts a practical UX framework from hospitality principles — anticipatory service, environmental coherence, and recovery rituals — and argues designers should study physical spaces as seriously as they study competing apps.
The Figma class action reframes consent as a design decision — here's a practical test for your own tools.
The Figma class action lawsuit centers not on copyright but on defaults: the company allegedly switched on AI model training over customer files without explicit consent. The author argues that default settings are a design decision with ethical weight, and offers four diagnostic questions any team can apply to evaluate whether a tool's data practices deserve their trust.
Concise framing of one of the most underrated tensions in interface design right now.
UI density is defined as the amount of information and value a UI delivers within a given space and time. The piece explores how designers balance information richness against cognitive load, and why density decisions are often driven by product philosophy rather than user research.
A grounding personal account of why web accessibility still fails the majority of people who need it.
The author recounts watching a visually impaired friend struggle for 15 minutes to book a train ticket, unable to navigate mislabeled buttons and unreadable image names. Using that as a lens, the piece examines why 95.9% of the world's top million sites still fail accessibility standards, and what that means for designers who ship those products.
A practitioner breaks a sacred JS rule on purpose and explains exactly why it was the right call.
Victor Ayomipo walks through a real scenario building a screenshot extension where deliberately blocking the browser's main thread produced better results than the conventional async approach. He explains the tradeoffs clearly, making the case that blanket rules don't survive contact with specific product constraints.
Sharp diagnosis of why teams default to shipping features instead of testing assumptions.
The article argues that product teams fall into a 'feature trap' by mistaking the act of building for the act of validating. The urge to ship is instinctive and often overrides disciplined thinking about what actually needs to be learned. It outlines five key considerations for breaking this pattern.
A new anti-design manual asks whether 20th-century typography rules still deserve their grip on us.
Matter Of has published an anti-design manual that challenges whether the typographic conventions codified in the 20th century still hold relevance today. Combining essays, images, and experimental typography, it investigates how inherited rules shape — and potentially constrain — contemporary graphic and digital design practice.
Real quotes from 32 design leaders on handling compressed timelines — the craft question, not the AI hype.
Kai Wong surveys 32 design leaders about responding to pressure to ship faster, drawing on a Greek rhetorical framework to argue that process optimization is the easy part. The harder challenge is protecting design quality and team judgment when speed becomes the default metric. The piece surfaces candid quotes and patterns across leadership styles and org types.
Accessibility errors are up 10% in 2026 — and AI tools aren't the fix. Practical techniques inside.
The issue reports that average accessibility errors per page rose from 51 to 56.1 between 2025 and 2026, pushing back on the assumption that AI tooling will close the gap. It highlights concrete accessibility techniques, tools, and guidelines practitioners can apply now, alongside a session on sustainable design.
The real source of truth for a component isn't in Figma or your codebase.
The article argues that design system components should be defined by a contract — a shared spec that sits between Figma and code — so both copies stay honest and in sync. It references Southleft's open-source repo as a practical starting point and makes the case that this approach becomes more urgent as AI-generated code enters the workflow.
A clear-eyed look at when dropdowns hurt more than they help in forms.
Dropdowns hide options behind a click, adding friction and slowing decisions. NNG walks through the narrow scenarios where they're actually appropriate, and surveys the alternatives — radio buttons, autocomplete, steppers — that often serve users better. Concrete guidance with research backing.
A provocation: the design community is obsessing over how to build when the harder question is what to build.
Now that AI has commoditized building, the author argues designers are still fixated on craft and tooling debates instead of shifting focus to purpose, value, and what actually gets made. The real competitive edge has moved from execution to judgment about what's worth designing at all.
A personal essay on how efficiency-obsessed design is quietly killing the texture of everyday experience.
The author reflects on how optimizing for speed and task completion has eroded the quality of lived digital experience. Drawing on personal observations, they make a case for designing with novelty, wandering, and play as legitimate goals rather than inefficiencies to be eliminated.
A sharp argument for why design judgment is the one thing you can't outsource or automate.
The piece argues that as AI commoditizes output, taste — the ability to make considered aesthetic and strategic judgments — becomes the true differentiator for designers. It warns against design-by-committee cultures where no single person owns quality, and makes the case that organizational taste must be cultivated and protected, not distributed.
Brad Frost maps what a mature design system actually looks like inside a large, complex organization.
Frost argues that design systems in big orgs aren't a single artifact but an ecosystem of interconnected systems, tokens, and teams. He breaks down how a 'core' system feeds into product-level systems, and why understanding those relationships is critical to governance, contribution models, and long-term maintenance.
A designer reflects on why producing more output is not the same as building better products.
The author argues that the ease of generating more with AI makes the quality-over-quantity principle harder to practice, not easier. Using the experience of switching from a cluttered product to a focused one, they make the case that restraint and intentionality in design decisions matter more now than ever.
Practical, specific advice on why your UX maps aren't landing and how to fix that.
The video identifies four common presentation failures with complex UX maps: surprising audiences with unfamiliar formats, using jargon, presenting without context, and treating the session as a deliverable hand-off rather than a collaborative conversation. The fix is prep, plain language, and framing the map as a thinking tool.
The foundational essay that changed how designers think about building component-based systems.
Brad Frost introduces the Atomic Design methodology, arguing that we should design systems of reusable components rather than individual pages. Drawing on chemistry as a metaphor, he breaks UI down into atoms, molecules, organisms, templates, and pages — a framework that became foundational to modern design systems thinking.
A practitioner with seven years in AI products asks: what are we actually designing now?
Drawing on seven years designing AI products and agentic retail experiences at Walmart, the author examines how chat, voice, and autonomous agents are dismantling first principles of UX. When users delegate tasks rather than navigate flows, the traditional interface model breaks down and designers must rethink what their craft even means.
Useful counterpoint to the usual linear "build then govern" design system story.
NN/G proposes a six-dimension maturity model that treats design-system growth as multidimensional rather than a straight-line progression. Instead of a single score, teams can assess health across axes independently — useful for identifying exactly where a system is lagging and where to focus investment next.
A sharp reminder that trendy UI patterns can actively harm vulnerable users who need calm, not novelty.
Kat Homan argues that UI trends optimized for engagement and novelty are often at odds with what mental health apps actually need: reduced cognitive strain, trust, and a sense of refuge. She introduces a practical evaluation framework designers can use to audit whether a given visual or interaction pattern supports or undermines those goals.
Covers the messy pre-concept phase most brand process articles skip entirely.
The article walks through the research and alignment work that happens before any visual concepts exist — surfacing hidden stakeholder assumptions, building shared language around what a brand should communicate, and translating strategic direction into a visual foundation. It addresses the common gap between brand strategy and what a designer is actually asked to create.
A candid look at why earning a promotion and actually growing into it are two different things.
A design manager reflects on a designer who was correctly promoted but never truly stepped into the role. The piece examines the gap between scope growth and behavioral growth, and what it takes for a title change to actually stick in practice.
On why the loud announcement is the simple bit — the slow grind after is the real work.
The article argues that launching something new or declaring a big change is the straightforward part; the real challenge is the unglamorous, iterative work that follows. It frames the 'morning after' as the true test of any design or product initiative.