Here’s what I love about this definition:

1) It clearly conveys that a logic model is a visualization of how your program operates, and

2) It helps teams see that a logic model can actually streamline their work and make sure everyone is on the same page.

​The image below from the CDC is another great way to think about what a logic model can do.

So instead of an annoying task you have to complete for grant funding, think of a logic model as a dynamic map of your program and how you will collaboratively work towards achieving your goal. 

Recently, I introduced this new way of thinking to a school district team I’m working with.

I’m designing a data dashboard (learn more here!) for them so that all of their family-serving teams can share data and serve their district’s families more efficiently. (I’m really excited about this.)

When we met with each team individually, they were all saying the same things about how they engage with families and what data they already or want to track. 

Yet, collectively, they couldn’t see the forest for the trees. They didn’t know how similarly each team was operating!

Let me be clear: this wasn’t because they were not communicating or working together. It’s because they didn’t have a framework to guide their collective work and show where there was overlap across project teams.

So we got to work. Using Google Slides, we did an interactive work session where the teams brainstormed what they would put in each part of a logic model. Below is a screenshot of their “Activities” brainstorm.​

Then we did a virtual “gallery walk” so they could see how much overlap there was. See how many “I do this too” stars there are in the image? 

After this, it took no time to put together their ideas into a more traditional logic model format.

If your team is currently struggling with making a logic model, don’t be afraid!

Reframing how we think about logic models can go a long way towards making them purposeful, usable tools to make our family engagement work more effective.