Are You Producing Outcomes, or Outputs?
I recently read a book by Joshua Seiden, one he wrote to help software product teams better prioritize their work according to its impact on the business.
In "Outcomes Over Output: Why customer behavior is the key metric for business success", Seiden argues that while software teams are often focused on trying to ship as many features as they can, they should instead be focused on shipping the right features. They should prioritize the Outcomes, which Seiden tells us are "A change in behavior that drives business impact".
And then it hit me.
This book is about Revenue . . .
