Writing about advocacy-centered programming is fundamentally different from writing about direct services, because advocacy isn’t just about helping individuals navigate systems; it is about transforming those systems altogether.
Communicating this work in ways that funders both understand and are willing to fund can be challenging. Advocacy doesn’t easily translate into metrics like “number served,” and the change being pursued often unfolds over years–or even generations. When you are working to dismantle oppressive systems, push for policy change, and build collective power, you are not just describing program outcomes–you are articulating a vision for justice.
That’s why advocacy-centered programming calls for a different kind of logic model than direct service programming.
For a more robust, advocacy-centered logic model, download this FREE resource, featuring inputs, activities, outputs, outcomes, and long-term impact, plus a real-world example of an advocacy program, to help you clearly map your path to systemic change.