Why Technical Assistance Often Fails (and What Actually Helps)

Technical assistance is meant to help systems improve. It’s designed to build capacity, clarify expectations, and support better outcomes over time. But too often, it doesn’t work the way it’s intended.

In this episode of Behind the Measures, Geremy Hurley explores why technical assistance often falls short, not because people don’t care or guidance is wrong, but because the way support is delivered doesn’t align with how systems actually function. The episode looks at the difference between guidance and support, why focusing on knowledge gaps misses deeper system constraints, and what happens when technical assistance becomes performative instead of effective.

This conversation goes deeper into what actually helps systems improve: meeting them where they are, understanding constraints, embedding improvement into real workflows, and treating technical assistance as a relationship rather than a transaction.

If you work in quality, performance, oversight, or improvement, and you’ve ever wondered why well-intended guidance doesn’t always lead to change, this episode will feel familiar.

The views expressed in this podcast are my own and do not represent the views of my employer or any affiliated organizations.