Outcomes Over Output

About this book

Outcomes Over Output, by Josh Seiden, starts from the idea that every project needs a goal, or a team can't tell when it's done. The book notes that setting goals was simpler in older engineering work, but with software it's harder to tell when the work is done. The book argues that teams are usually asked to build features, which often add no value, and that they should be given an outcome to achieve instead. Setting goals as outcomes is harder in practice than it sounds, so the book is written as a hands-on guide to steering a team's work with outcomes.