Outcomes over outputs

A recent round of discussion between Jeff Patton and Marty Cagan on product teams vs feature teams is worth your time if you work in an organisation trying to modernise your design and development process.

Outcomes over outputs

A recent round of discussion between Jeff Patton and Marty Cagan on product teams vs feature teams is worth your time if you work in an organisation trying to modernise your design and development process.

A recent round of discussion between Jeff Patton and Marty Cagan on product teams vs feature teams is worth your time if you work in an organisation trying to modernise your design and development process.

The crux of it revolves around knowing the difference between focusing on outcomes or outputs.

Jeff has written an extensive review and explanation here, I won't rehearse it. This debate is key to understanding how to lift quality and unlock the benefits of design in product development.

As Jeff notes, knowing isn't going to magically break teams out of a service delivery mindset, but the first step is making the conversation explicit and starting a conversation about it.

How do you play the long game?

We've found 4 common modes of strategic change, each with their strengths and weaknesses.

Our simple tool helps you discover your default mode, and how to pick the mode you need right now.

Long Game Modes
The 4 Modes of Strategic Change
Path

+61 (0) 422 634 520

hello [at] pathventures.io

81-83 Campbell St, Surry Hills, NSW 2010

ABN 64 653 180 824

Acknowledgment of Country

We acknowledge the Gamaragal and Gadigal people of the Eora Nation, the traditional owners of the land on which we live and work, and pay our respects to the Elders both past, present and emerging.

Acknowledgment of Crisis

We acknowledge the context of crisis in our time. Recognising that our actions today have consequences beyond our species and generation, we acknowledge our responsibility to include these considerations in our lives and work.