Design services that hold up when people don't behave the way your journey assumed.
Three disciplines for finding the fragility in a service before it ships: stress-testing structure before build, designing recovery as a first-class journey, and auditing a live journey for variation.
You nominate a real journey in your first lesson, and you finish holding a documented resilience specification for it.
Reframe the problem
The complicated parts of a service get scrutinised during design. They attract review, testing effort and senior attention, which means they end up robust.
The failure points turn up somewhere else; appearing in the steps nobody worried about, because the feeling of certainty is what stops you looking for the gaps.
That isn't an engineering problem or a QA problem. A service that behaves unpredictably when someone pauses, returns, corrects a mistake or arrives in a state nobody specified is failing at a design level. The good part is that this means that we can design for it.
This course teaches the three disciplines to help you do that, and where each one lives as part of your process in a delivery timeline.
What you'll produce
In the introduction you'll nominate a journey you're working on now. Every exercise in this course applies to it. By the end you won't be holding a bunch of notes, you'll be holding seven design artefacts to support your live service.
An assumption inventory. What each step assumes about the user's situation, and what the service currently does when that assumption is wrong.
A conditional state ledger. The states your conditional logic actually produces, grouped by behaviour, including the ones nobody wants to think about.
A specified default for the states nobody designed, converting unpredictable failure into predictable failure.
A Correction Cost Test result on one existing correction flow, showing where the cost accumulates and whether it's high enough that users abandon instead of fixing.
A recovery journey specification for one specific failure, not a generic error state.
A prioritised variation audit with three test tasks written for a real testing budget.
A structural intent brief your developers can use when they hit a state neither of you anticipated.
Plus a deferral statement for the next time the your delivery timeline gets compressed and assuring service resilience is first on the chopping block.
Five reusable templates and a full worked example set are included.
Are you between projects?
Two fallback journeys are provided, a benefits eligibility checker and a utilities switching service, so you can still do every exercise.
You've been designing digital services for two or more years and you work on the transactional kind of journey. Applications, eligibility checks, multi-step processes, anything with save and return.
You've watched something ship that tested well and behaved badly. You've had the conversation where support raises a problem nobody designed for and nobody can say what the service is supposed to do in that state.
You work with developers, and you've seen your reasoning fail to survive the handover.
This isn't for you if you're new to UX, or you want a general overview of resilience as a concept. It assumes you can already map a journey and run a usability test. It covers what to do with those skills when the journey is genuinely complex.
One lesson. Around five minutes to read, fifteen minutes to complete the exercise. Do not skip the exercise, because everything after this module runs against what you choose here.
Three lessons. Around thirty minutes to read, no exercises. This is the only conceptual module in the course, and it exists to make sure you are looking in the right place before you start doing the work.
Four lessons. Around forty minutes to read, and an hour and a half to two hours of exercise work. This is the first of the three disciplines, and the one that pays back fastest.
Five lessons. Around 1 hour to read, and 1.5 hours of exercise work. The second discipline, and the largest module in the course.
Three lessons. Around 30 minutes to read, and 45 to 60 minutes of exercise work.
Three lessons. Around 30 minutes to read, and 45 to 60 minutes of exercise work. The point at which the work stops being yours, and the first of the two places resilience is normally lost.
Two lessons. Around 20 minutes to read, and 20 to 30 minutes of exercise work.
No lessons and no exercises. What the eight exercises have left you with, the one thing worth doing with it this week, and the argument underneath all of it.
Written lessons, self-paced. Everything unlocks immediately, so you can work through it in order or go straight to the discipline you need this week.
Around 8 to 10 hours including the exercises. The exercises are the course, so the time is spent on your own journey rather than on watching someone else's.
All templates and the worked example set are available as downloads for you to keep.
No. This course stands alone. The two overlap at one point: module 4 uses the Variation Audit and points at Designing Behavioural Journeys for the testing method behind it, which you can take or leave. If you want both, the bundle costs less than buying them separately.
That course is about modelling the structure of a journey. This one is about what that structure does when it meets real behaviour, and how to keep it intact through delivery and scope cuts.
Two fallback journeys are provided, a benefits eligibility checker and a utilities switching service. Every exercise works with either.
Module 2 in particular is about reallocating time rather than adding it. The assumption work replaces polish that gets thrown away when the structure turns out to be wrong.
Module 6 is specifically about that. It's placed at the end deliberately, because you're already convinced. It's the argument for the person who isn't.
Yes. 14 days, no questions.
6 modules. 20 lessons. 8 exercises. 5 templates.
One journey of your own, documented.