Have you ever sat there wondering why you were doing some bit of work? What value it actually produced? That may be because one of the least understood Agile values is "Working software over comprehensive documentation".

Both teams and leaders are constantly distracted by the tangible, yet limited value, outputs because they are easier to measure, provide a false sense of progress, and are more fully within their control. Come find out why outputs suck people in, how to shift focus to outcomes, and many of the small obstacles that get in the way. Outcomes refer to the impact or result of a particular action or effort, whereas outputs refer to the tangible products or services that are produced as a result of that action or effort. Outcomes are considered to be more important because they measure the effectiveness of the action or effort in achieving the desired result, whereas outputs simply measure the quantity or quality of the products or services produced. In other words, outcomes are a measure of success, while outputs are a measure of activity.

Over the last 17 years, I've been striving to guide teams and organizations in mindsets and behaviors. I've had the opportunity to work with both front-line workers as well as senior executives across small startups and multi-national organizations. My specific passion is creating human-centered organizations, leveraging my experience in both Lean and Agile. ​As part of the transformation initiatives that I lead, I regularly provide training, coaching and workshop facilitation on topics like: vision/mission definition, organizational design, teamwork, product design workshops, Lean/Agile training, team and leadership coaching. This talk will leverage my experience to help attendees better prioritize outcomes over outputs.