October 2026

  1. What Resilience Actually Means in UX Design (And the Four Things It Gets Mistaken For)

    Resilience gets used interchangeably with concepts like uptime, error handling, usability and test coverage. Here's what it actually means, and why the difference matters.

    Service Resilience

  2. When MVP Logic Strips Resilience From a Service

    MVP scoping cuts what is least visible, and resilience is the least visible thing in a build. Here is why minimum viable so often means minimum survivable, and how to scope differently.

    Service Resilience

  3. Why Resilience Cannot Be Retrofitted

    Adding resilience after a service is built costs more than designing it in, and produces a structurally weaker service. Here is what the retrofit actually costs, with the numbers.

    Service Resilience

  4. Why Resilience Degrades Across Releases

    Variation is not tested once and signed off. Every significant change reopens the combinations, and every release is a chance for a handled state to quietly stop being handled.

    Service Resilience

  5. How to Brief Developers on Structural Intent

    Developers fill design gaps by interpreting intent. Briefing them on structural intent, rather than screen specification, is what determines whether developer interpretations hold up.

    Service Resilience

September 2026

  1. How Conditional Logic Introduces Structural Fragility

    The more conditions your service handles, the more combinations it has never been tested in. Learn why conditional logic is a design problem rather than a development one, and how to own it.

    Service Resilience

  2. When Correction Flows Cost More Than the Original Error

    Users abandon services when correcting a mistake costs more than the mistake did. Here is how to spot correction flows that have become more expensive than the errors they exist to fix.

    Service Resilience

  3. Why Recovery Paths Get a Fraction of the Design Attention They Need

    Recovery paths carry a disproportionate share of user distress and support contact, and receive the least amount of design time. Here is why that imbalance persists and what changes when you correct it.

    Service Resilience

  4. What Users Need When They Return to an Unfinished Task

    The returning user is one of the most common behaviours in any digital service and one of the least designed for. Here is what a user needs when they come back, and why a save function is not enough.

    Service Resilience

August 2026

  1. The Happy Path Is a Hypothesis, Not a Foundation

    The happy path is the most tested part of your service and the least representative of how it is used. Treating it as a hypothesis rather than a foundation changes what the design process is for.

    Service Resilience

  2. Why Services Degrade at the Edges

    Services degrade where the design was most confident, not where it was most complex. Learn why fragility clusters at the edges of a journey and how to find it before your users do.

    Service Resilience