![\"Yellow](\"\/neo\/wp-content\/uploads\/sites\/3\/2016\/07\/Duck-295x300.jpg\")
<\/p>\n<\/p>\n
Programmers have a process for solving coding problems called “Rubber Duck Debugging.” It emerged from the realization that when they explained a problem they were having in coding to non-programmer, suddenly the solution would come to them. Then they realized that they could get the same results by explaining the problem to a rubber duck (or some other inanimate object) and they wouldn’t have to bother someone.\u00a0 What they do is explain each line of code to a rubber duck, until they hit on the solution to their problem.<\/p>\n
How does this apply to evaluation planning?\u00a0 Cindy and I kind of did this yesterday (for full disclosure, I will admit that I was the rubber duck).\u00a0 We were walking through a complicated timeline for an evaluation process. It had a lot of steps. It was easy to leave one out. Some of them overlapped. We really<\/em> had to explain to each other how it was going to happen.<\/p>\n Rubber Duck Debugging can be employed at almost any stage of the evaluation planning process. Here are some examples:<\/p>\n Logic Models<\/span><\/p>\n When creating a logic model, you usually work from the right side (the outcomes you want to see), and work your way left to the activities that you want to do that will bring about the outcomes, then further left to the things you need to have in place to do the activities (here’s a sample logic model<\/a> from the NEO’s Booklet 2 Planning Outcomes Based Outreach Projects<\/em><\/a>).\u00a0 Once you’ve got your first draft of the logic model, get your rubber duck and carefully describe your logic model to it from left to right, saying “If we have these things in place, then we will be able to do these activities. If these activities are done correctly, they will lead to these results we want to see.\u00a0 If those things happen, over time it is logical that these other long term outcomes may happen.”\u00a0 Explain thoroughly so the duck understands how it all works, and you know you haven’t missed anything.<\/p>\n Indicators<\/span><\/p>\n Process Indicators: in the logic model section, you explained to your duck “If these activities are done correctly they will lead to these results.”\u00a0 What does “correctly” look like? Explain to your duck how things need to be done or they won’t lead to the results you want to see. Be as specific as you can.\u00a0 Then think about what you can measure to see how well you’re doing the activities.\u00a0 Explain those things to the duck so you can be sure that you are measuring the things you want to see happen.<\/p>\n Outcome Indicators: Looking at your logic model, you know what results you’d like to see.\u00a0 Think about what would indicate that those results had happened? Then think about how and when you would measure those indicators. Talk it out with the duck. In some cases you may not have the time, money or staff needed to measure an indicator you would really like to measure.\u00a0 In some cases the data that you can easily collect with your money, staff and time will not be acceptable to your funders or stakeholders.\u00a0 You will need to make sure you have indicators that you can measure successfully that are credible to your stakeholders. The rubber duck’s masterful silence will help you work this out.<\/p>\n Data collection<\/span><\/p>\n I think this is where the duck will really come in handy.\u00a0 To collect the data that you have described above, you will need to have some data collection tools, like questionnaires or forms. Once you’ve put together the tools, you should explain to the duck what data each question is intend to gather. When you explain it out loud, you might catch some basic mistakes, like asking questions you don’t really need the answers to, or asking a question that is really two questions in one.<\/p>\n Then you need a system for collecting the data using your tools.\u00a0 If it’s a big project, a number of people may be collecting the data and you will have to write instructions to make sure they are all doing it the same way.\u00a0 Read each instruction to the duck and explain why it’s important to the success of the project. Did the duck’s ominous silence suggest areas where someone might misunderstand the instructions?<\/p>\n I hope this is helpful to you in your evaluation planning, and maybe other areas of your life.\u00a0 Why use a rubber duck instead of something else? Well, they are awfully cute. And they come with a great song that you can sing when you’ve completed your plan: https:\/\/www.youtube.com\/watch?v=Mh85R-S-dh8<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Programmers have a process for solving coding problems called “Rubber Duck Debugging.” It emerged from the realization that when they explained a problem they were having in coding to non-programmer, suddenly the solution would come to them. Then they realized that they could get the same results by explaining the problem to a rubber duck… Read More »<\/a><\/p>\n","protected":false},"author":2959,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[27],"tags":[],"class_list":["post-4541","post","type-post","status-publish","format-standard","hentry","category-blog"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p8ICUo-1bf","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/news.nnlm.gov\/nec\/wp-json\/wp\/v2\/posts\/4541","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/news.nnlm.gov\/nec\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/news.nnlm.gov\/nec\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/news.nnlm.gov\/nec\/wp-json\/wp\/v2\/users\/2959"}],"replies":[{"embeddable":true,"href":"https:\/\/news.nnlm.gov\/nec\/wp-json\/wp\/v2\/comments?post=4541"}],"version-history":[{"count":1,"href":"https:\/\/news.nnlm.gov\/nec\/wp-json\/wp\/v2\/posts\/4541\/revisions"}],"predecessor-version":[{"id":6466,"href":"https:\/\/news.nnlm.gov\/nec\/wp-json\/wp\/v2\/posts\/4541\/revisions\/6466"}],"wp:attachment":[{"href":"https:\/\/news.nnlm.gov\/nec\/wp-json\/wp\/v2\/media?parent=4541"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/news.nnlm.gov\/nec\/wp-json\/wp\/v2\/categories?post=4541"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/news.nnlm.gov\/nec\/wp-json\/wp\/v2\/tags?post=4541"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}