In the old days, when we made physical products, setting project goals wasn’t that hard. But in today’s service- and software-driven world, “done” is less obvious. When is Amazon done? When is Google done? Or Facebook? In reality, services powered by digital systems are never done. So then how do we give teams a goal that they can work on?Mostly, we simply ask teams to build features—but features are the wrong way to go. We often build features that create no value. Instead, we need to give teams an outcome to achieve. Using outcomes creates focus and alignment. It eliminates needless work. And it puts the customer at the center of everything you do.Setting goals as outcomes sounds simple, but it can be hard to do in practice. This book is a practical guide to using outcomes to guide the work of your team.

在过去，当我们制作实物产品时，设定项目目标并不难。但在当今服务和软件驱动的世界，“完成”并不那么明显。亚马逊什么时候完工？谷歌什么时候完成？还是Facebook？实际上，由数字系统提供动力的服务从未完成。那么，我们如何给团队一个他们可以完成的目标呢？大多数情况下，我们只是要求团队构建特性，但特性是错误的。我们经常构建没有价值的特性。相反，我们需要给团队一个要实现的结果。使用结果创建焦点和一致性。它消除了不必要的工作。它把客户放在你做任何事情的中心，把目标设定为结果听起来很简单，但在实践中却很难做到。这本书是一个实用指南，使用结果来指导您的团队的工作。