{"id":3810,"date":"2011-10-11T00:00:00","date_gmt":"2011-10-11T07:00:00","guid":{"rendered":"https:\/\/www.carnegiefoundation.org\/?p=3810"},"modified":"2026-02-11T10:55:42","modified_gmt":"2026-02-11T18:55:42","slug":"what-we-need-in-education-is-more-integrity-and-less-fidelity-of-implementation-2","status":"publish","type":"post","link":"https:\/\/www.carnegiefoundation.org\/what-we-need-in-education-is-more-integrity-and-less-fidelity-of-implementation-2\/","title":{"rendered":"What We Need in Education is More Integrity (and Less Fidelity) of Implementation"},"content":{"rendered":"
\n
\n\n

October 11, 2011 | By Paul LeMahieu<\/strong><\/p>\n\n\n\n

For many years, educational researchers have worked with program designers and implementers in pursuit of what has been called fidelity of implementation<\/em>. Simply put, this has involved the application of numerous tools and procedures designed to ensure that implementers replicate programs exactly as they were designed and intended.<\/p>\n\n\n\n

There is a simple and immutable logic to this urge to strictly control implementation. It is compelled by the methodologies (and their attendant mindset) that warrant programs as effective. The manner in which we validate \u201cwhat works\u201d in education involves research methodologies that privilege explanatory power as their primary purpose. To arrive at valid explanations, the methodologies necessarily abstract problems and programmatic solutions from their contexts.<\/p>\n\n\n\n

The result is an empirical warrant, offered in the form of significant effect size indices, that represent impacts that just weren\u2019t actually observed anywhere. What they are is the average effect across the many individual implementations subsumed within the research. The analysis that informs our sense of \u201cwhat works\u201d does not measure anything that actually happened anywhere. Neither does it represent a measure of impact that is likely to be realized in any subsequent implementation.<\/p>\n\n\n\n

Programmatic solutions simply cannot be implemented outside of their contexts.<\/p>\n\n\n\n

But what typical R&D thinking does is compel us to pursue fidelity of implementation<\/em>. The traditional empirical warrant justifying a program as effective holds only in so far as the program is replicated exactly as tested. And so, exact reproduction is made necessary \u2013 despite the fact that it is not likely to produce the same effects or even be possible to accomplish.<\/p>\n\n\n\n

The issue is that problems simply don\u2019t exist and programmatic solutions simply cannot be implemented outside of their contexts. The real challenge of implementation, then, is to figure out how to thoughtfully accommodate local contexts while remaining true to the core ideas to ensure improvements in practice that carry the warrant of effectiveness.<\/p>\n\n\n\n

What we need is less fidelity of implementation<\/em> (do exactly what they say to do) and more integrity of implementation<\/em> (do what matters most and works best while accommodating local needs and circumstances).<\/p>\n\n\n\n

This idea of integrity in implementation<\/em> allows for programmatic expression in a manner that remains true to essential empirically-warranted ideas while being responsive to varied conditions and contexts.<\/p>\n\n\n\n

What does it take to achieve\u00a0integrity in implementation<\/em>? The answers permeate all of the current work of the Carnegie Foundation, including the reconceptualization of the education research enterprise such that it better addresses real problems of practice and generates knowledge that genuinely improves practice (i.e., the application of\u00a0improvement science and improvement research) and the redefinition of the human organization that pursues education R&D (the formation of\u00a0networked improvement communities<\/a>\u00a0that continuously test their practice to ensure that proposed changes are, in fact, improvements).<\/p>\n\n\n\n

Just how this is done is being explored and documented in the Foundation\u2019s work. While much more needs to be learned, tested, and shared, some focal areas are clearly emerging as requiring serious and thoughtful attention if implementation with integrity<\/em> is to be realized. The first of these is in the nature of programmatic design (and even the design process itself). The second is in the manner in which implementation is pursued.<\/p>\n\n\n\n

Simply put, when we design for implementation with integrity, we design differently \u2013 both the process and the characteristics of the resulting programs. While much will be elaborated in subsequent postings here, some considerations include:<\/p>\n\n\n\n