What is this series about again?
We’re talking about systems design for NPOs. Answering the question: How should we think about operational improvements in nonprofits, given that there are so many moving parts?
In the first post in the series, we explored three ways to consider, at a high level, what it takes to capture and assess data for impact measurement. We identified the biggest categories of moving parts, and how they inform each other. In later series, we’ll dissect some the details. In this series, I want to stay higher-level and talk about designing solutions in general.
To recap the first post: Nonprofits are like any other organization. They have a reason for existing, they want to know if they’re doing what they think they’re doing, and their operations are the activities that support the reason for existing. That’s all formalized in a logic model, and results in a nice structure from which to enter into the operational considerations of data capture, efficiency, assessment and improvement.