The retry lane for failed Direct Debit was the first time our ops lead and I used the same nouns. I still think the homework load in week five is heavy if you have a day job.
Sam — Glasgow, attended Signal to Screen
Flagship course
Signal to Screen
Eight weeks of live teaching on User Journey Mapping for Apps. You work from evidence in a product you already own. We do not grade pretty diagrams; we grade whether a stranger could run a sprint from your map.
Informational fee: £1,480 per seat · £4,200 for a three-seat studio table. No checkout on this site.
Learning outcomes
You will build a multi-lane map that includes install, authenticated use, payment, and at least one recovery path after a failed state.
You will write annotations that cite a clip, a ticket, or a store review, so stakeholders cannot dismiss the map as opinion.
You will facilitate a 40-minute critique where engineering, support, and design mark disagreements on the paper itself.
You will leave with a one-page “map contract” describing what the artefact is for — and what it is not allowed to decide.
Modules
1. Evidence intake without theatre
How to sample recordings and tickets so you are not mapping the loudest customer. Includes a limitation: we do not teach statistical sampling at research-ops depth.
2. Lanes, time, and emotional load
Drawing waits as duration. Plotting anxiety without turning the map into a mood board.
3. Permissions, identity, and the quiet no
Camera, notifications, and biometrics as journey events. Mapping the person who refuses and still needs the job done.
4. Money, failure, and retry
Failed cards, 3-D Secure, and “try again tomorrow”. The module most teams underestimated last year.
5. Support, email, and the second device
When the journey leaves the app. SMS codes, help-centre articles, and the colleague who finishes the task on desktop.
6. Critique, contract, and hanging the map
Facilitation scripts, photographing the wall, and converting the artefact into a backlog that does not swallow the original story.
Instructor
Helen Calloway
Helen ran service-design rooms for two UK fintechs before joining Service Anchorcore. She still maps one live flow each quarter so the teaching does not freeze around last year’s examples.
What people said after module four
★★★★☆ · “Permissions as events” stopped us treating the camera prompt as a one-off tooltip.
App review snippet, course alumni channel
Questions we hear before enrolment
Do we need Miro or a particular tool?
No. Paper is preferred in the first fortnight. Digital boards are allowed after the critique module, once the story has survived handwriting.
Is this suitable if we only have web, not a native app?
Partly. The method travels, but examples assume a phone in someone’s hand. Web-only teams often take First-run cartography instead.
What will this course not do?
It will not produce a statistically defensible conversion model, and it will not replace a researcher on a regulated medical product. If you need clinical validation, hire that specialist; our maps would over-claim.