So what's all this about then?
It's the Job to be Done. Everything else is the process.
Brief - identify - requirements - gut reactions - examples - end goals.
Research - personas - journey maps - storyboards - needs - expectations - uses
Do you want some content with that?
Content - who, what, when, where, why - animations - loading - exit - pause - errors
The red wire connects to the green wire?
Wireframe - layouts - style guides - paths - red routes - interactions - vibe - blocking
Style guides - feeling - vibe - standards.
Does it do what we want?
When is a process done? Does it get the job done? Is it efficient and understandable? Either the new experience and tasks we've designed are implemented without any fanfare or it's a new product and it's time to tell people about it.
It should go without saying, at the end of each stage we should try and talk to actual end-users, they're the ones who really matter after all.
To quote the great Lars Ulrich "What the fuck does that mean anyway, done?"