Why You Should Break Down Outcomes, NOT Initiatives [Live Talk]

A common pattern I see in many of the product teams and companies I coach is that they’re doing a lot of incremental work but little-to-no iterations.
They have this big idea (often framed as an initiative) and become solely focused on breaking it down. The initiative becomes a series of epics, and that epic becomes a series of user stories, and so forth.
Now, this is great when you’re trying to achieve is something large - like moving from one infrastructure to another. But it's not ideal when we're working with uncertainty and trying to drive towards outcomes.
In this talk I did for global company last week, I walk through why great product teams break down outcomes, not initiative and how you can too!
LINKS:
🔸 Newsletter post on this topic: www.antmurphy....
🔸 (Part 2): www.antmurphy....
MORE FROM PRODUCT PATHWAYS
👩‍💻 Learn product online: www.productpat...
🧰 20+ Free Resources & Templates: www.productpat...
🅧 x.com/ProductP...
🟦 / productpathways
🗞️ Join 1,000s who read my newsletter: www.antmurphy....
p.s. If you'd like me to run a talk or workshop get in touch at antmurphy.me/

[@head4]

Awesome talk! What’s the visual tool you were using to sketch out your thoughts?

[@productpathways]

Thanks 🙏 glad the talk was valuable. The app I use if Freeform on the iPad: apps.apple.com/au/app/freeform/id6443742539