Often efforts to change techniques or processes are met by "But its working, why change now?" Usually the impetous for change comes from someone who does not believe it is working. The organization may be producing products but is it producing them fast enough using sufficiently few resources with appropriate quality? In this issue of Strategic Software Engineering I want to explore what we mean by "working" and why different people have different perspectives.