When I've helped organisations become more outcome/product orientated, more often than not, I've moved them away from 'epics' and 'user stories' and towards things like one-pagers, opportunities, hypotheses, etc. Why? Because they’re are better tools for facilitating outcome thinking and experimentation.

The first rule of scaling agile is DON’T. Instead, descale the work and organisation instead. But how? you ask. One of the best books on building an agile organisation is not about agile at all. Instead, it’s a story about building an adaptive and responsive organisation. Free from jargon, buzzwords and trying to shove the latest ‘model’ or methodology down your throat.

IBM a few years back stated that 84% of Digital Transformations fail — although there is a lot of “grey” area around what constitutes as “failure” still 84% is a staggering number! What interests me the most is why this is the case? As a fellow coach Tanner Wortham brilliantly provoked “If this agile thing is so great, then why doesn’t it always stick?”

What's the difference between Product Management and Product Ownership? Are they the same thing, or different?  It’s ok, no one seems to know. Rather we find the answer lies in where it all began - where they came from.