Why you need Outcome-Oriented, Continuous Transformation, Everywhere
The phrase “outcome-oriented, continuous transformation, everywhere” describes my approach to Agile Transformation. This post explains what I mean by that.
TASTE Impacts, Outcomes and Outputs
As part of preparing material for the Agendashift and X-Matrix Masterclass I’m running with Mike Burrows next month, I started thinking about how the idea of Impact, Outcome and Output (that blog is from 2012) could be overlaid onto the TASTE approach. Back then I described the relationship between them as: Outputs create Outcomes which have Impact Give the outcome-oriented perspective of …
Impact, Outcome and Output
As I alluded to in the previous post, one of the changes in thinking, and in particular language, for me recently is the idea of impact. Specifically that impact is different from outcome which is itself different from output. I’ve differentiated outcome from output for some time, as have others, but I believe impact is a further step in understanding …
Outcomes and Sync Steps
I met up with Jean Tabaka last week for a coffee and we chatted over various things, including Lean, Kanban, “The Don”, Tufte, and Systems Thinking. One of the other areas was around the origins and original intents of Scrum. Jean mentioned an early paper(*) by Jeff Sutherland, written before the current terminology became standard, where he described his process …