At the urging of my friend and colleague Barb Berry, I recently read Michael Quinn Patton‘s book Developmental Evaluation.
It has been a long time since I have read a professional text with as engaging a style and tone.
What challenges me about Patton’s book is that it addresses evaluation work at a high level of sophistication. It assumes readers are capable evaluators and explores the practice of evaluation in a way that focuses on the why? rather than the how. True the book offers lists of possible evaluation frameworks and describes cases and examples of how complexity concepts may be applied by evaluators, their clients, and collaborators. But, even though I am a dabbler in the field of evaluation, I appreciated not being told what to do and rather being able to reason my way to what might work in a given situation.
The book has resonated as I have gone about my week observing an innovative program and offering just-in-time developmental feedback to the people involved. It has primed me to attend to the emergent, unanticipated outcomes and situations and the obstacles that they have created for people.
Patton’s book will resonate for anyone who is working to develop a social innovation. It persuades me that there is value for an insider/outsider evaluator on high stakes innovation programs. Patton’s book will appeal to innovators who are already inclined towards complexity, systems thinking, and other outside-in ecological ways of looking at growing a product, service or program. Cynefin practioners may appreciate Patton’s application of Snowden and Boone.
For pioneering service and strategy designers, developmental evaluation offers ways to evaluate the impact of service and strategy prototypes and innovations. If a future goal of service design agencies is to take service designs all the way to implementation and evaluation, developmental evaluation should feature on user research teams’ learning plan.