You’re smart, capable, and focused on outcomes.

We’ve been there, done that, and know what works.

Jimmy offers practical advice to help you to wrangle your real-world challenges to become an Outcomes Engineer.

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!

Next event: Chatting about Projects, Products & Business Analysis with Adrian Reed, 7:30am 21 March

Register now

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!

reflections

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.

14 minute read

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.

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!

  • analyse

    Value/effort map

    Work out what to work on next.

  • document

    Acceptance criteria

    Define a feature in yes or no terms.

  • visualiseanalysedocument

    Story map

    Document an entire system’s functionality.