Why Outcomes Over Outputs ?
▻https://hackernoon.com/why-outcomes-over-outputs-1735cc6c7b9a?source=rss----3a8144eabfe3---4
Why should teams create outcome/mission based roadmaps, converge on solutions later, focus on the problem-to-solve, experiment, limit planning inventories, avoid chasing story-point velocity, start together, limit handoffs, and [fifty other things] ?Better near, mid, and long-term business/customer/user/societal outcomes and a sense of impact…plain and simple. This is common sense (to some), of course, but I’m amazed by how often the calls for “outcomes over outputs” (and similar) ignore first principles. I fall into this trap often. The discussions are frequently framed in philosophy, “best practices”, maker advocacy, “theory of work”, and org design debates (e.g. “Teal”). This is important stuff, but almost orthogonal to outcomes over outputs. Or the talk is more “well, of course that’s how we (...)
#product-management #agile #leadership #ux #outcomes-over-outputs