In social media, I find that themes seem to develop that carry through for a week or so. For me, the theme that I am experiencing on Facebook this week is high school bands; my friends are talking about whether or not they were “band geeks” and who are some famous former high school band geeks. I, personally, was a high school “choir geek,” but as the proud mother of two proud (former) high school band geeks, I certainly jumped on the band wagon as a band parent, chaperoning for many years.
All of these Facebook posts about band participation got me thinking about jumping on band wagons. We do it all the time. We do it with fashion; we do it with technology; and, yes, we do it with program evaluation. We read or hear about some new way of collecting or analyzing information and, “poof,” our current processes are suddenly second rate. We are magically transformed into following a new process.
Changing our processes can be a good thing or a bad thing. Often, it depends on how much information we have about the new process. Here are some things that we might want to consider before jumping in:
– What motivated the process developers to create this new process? What were the problems with the old process that they were trying to resolve? How similar are their issues to the issues motivating us to look for a new process?
– What resources (financial, technological, personnel) did the process developers have at their disposal? Do we have the same resources? Can we readily acquire the resources that we will need?
– What went well with the new process? What internal or external factors in the situation of the developers influenced their success? How similar are these factors to our situation?
– What challenges did the process developers face? How did they overcome those challenges? What do they wish they were doing (or could be doing) differently? How difficult was it to make course corrections, and did that influence the results of the process? Will we face the same challenges, and if so, how might we be able to overcome them?
– What was the developer’s process for developing the process? Did they build on someone else’s idea? What changes did they make, and why? Should we be asking the previous four bulleted points about some other process?
You get the idea. We sometimes get information about seemingly great processes and jump on the band wagon without completely analyzing the situation. When it works, it is great. When it doesn’t, we are back on the sidelines looking for a new band wagon.
For example, I am currently looking at jumping on a band wagon of doing quality assurance reviews of “aged” cases. I think that the regular QA questions (was eligibility done in a timely fashion, etc.?) will not be particularly insightful, especially in figuring out why the case has been open for years, but perhaps there are other factors in the assessment/eligibility process that might have foreshadowed the need for an unusually long rehabilitation journey. Have any of you looked at aged cases? How did you select them (based on the case’s age alone or also based on money spent)? Do you have a process for that? Do you have an evaluation instrument? Looking at the bullet points above, I need to look at a range of factors before I leap onto the band wagon!
Have you jumped on any band wagons? What were the results (good or bad)? Do you feel that you had the time to fully research your decision? Is there a program evaluation idea/process that you are considering, but about which you would like more information? We can help each other! Leave you comment and questions below; check back to see if someone has asked a question that you can answer. Let’s use this blog as a forum for professional development.
