New to outcomes engineering?
Outcomes engineering is the label we put on the art of navigating all the nonsense and actually getting stuff done. And we know just how hard that can be!
So whether you’re an analyst, a developer, a product manager, or a coach of some kind – if you’re trying to get stuff done – you’re all welcome here!
Latest thinks …
We spend quite a bit of time mulling how all this works gestures vaguely all around. And every month we write down what we’re thinking about. The result? A Jimmy think!

What’s Next for Jimmy: From Business Analysis to Outcomes Engineering
Since giving up the BA title I've been wrestling with what to do next with Jimmy. Shelve the experiment? Or go all in?
Well I've found my answer. This is my statement of intent. This is what's next.
Jimmy methods
The Jimmy methods are the things that we have found to be true across multiple domains, programmes, and environments. You don’t always apply them in the same way — right-size isn’t the same size everywhere — but if applied thoughtfully, will help you to be seriously effective.
Right-size the rigour
Match your process to the risk and the stakes.
Think big, move small
Understand the context; take manageable steps.
Jimmy tools
There’s a technique that you can use to tackle every dilemma, and a tried and true Jimmy tool for the ones we use the most!
Value/effort map
Work out what to work on next.
Acceptance criteria
Define a feature in yes or no terms.
Story map
Document an entire system’s functionality.