Guided journeys
Scenario walkthroughs
Step-by-step flows that compose tools and prompts end-to-end — for new projects, user research, hand-offs to DevSecOps, and onboarding.
I'm starting a new project
A project lead in their first week. There's a brief, but no PRD yet, no research done yet, and no clear sense of who the users actually are.
8 stepsI'm joining a project midway
You've been brought onto a project that's already running. There's prior research, an existing PRD or operational scenario, possibly a prototype in flight. The goal isn't to redo the team's work — it's to get up to speed without restarting the loop.
6 stepsI need to hand off to DevSecOps
The interactive prototype has been through enough Test iterations to be validated. The developers in DevSecOps need to pick it up for production. The point of the Pipeline is that this isn't a 'throw it over the wall' moment — their technical assessment runs in parallel with the next Design pass.
6 stepsOur test results came back negative
DASH says the success criteria weren't met. The instinct is to argue the test was wrong. The discipline is to figure out where the failure actually lies — framing, design, or testing — before adjusting anything.
6 stepsI need to brief a new stakeholder
Someone new is coming into the conversation — a senior leader, another team's lead, or a partner team. They need to come up to speed without reading every artefact the team has produced.
6 stepsI have a finished feature — what now?
A team has shipped something and wants to know if it's working. The instinct is to celebrate or to move on to the next thing. The Pipeline asks: did it actually achieve what it was supposed to?
8 steps