When done properly, M&E begins with the grantee setting out clearly the objectives of the grant, the activities necessary to achieve the objectives, and the resources applied to make these activities happen. So, for example, blogging for Idea Lab is an activity. An objective might be to create a thriving community, or to help guide the way for community news in transition.
For our Knight project, the objective is a bit more specific: to create open source tools that make community news and information easy to visualize. Activities include mapping existing tools, surveying users for specific unmet needs, coding, testing, translating, demoing, fixing, etc. Our primary resource will be the Drupal community, which is also one of our project's main beneficiaries. Ideally, we will create a virtuous circle.
The grantee is expected to have a clear causal logic, setting out how the activities will achieve the objectives, and identifying verifiable measures to assess performance against targets at each level: resources, activities, and objectives. Especially objectives. It is important to do this well, because far too often the project gets underway and the grantee loses sight of the objectives. They end up obsessing about performance as it relates to activities and resources. This is natural because activities are much more easily controlled and measured than the messy causal chain leading to the objectives. The donor, meanwhile, is mostly interested in the objectives. These differing centers of attention are the root of most donor-grantee disputes.
By starting out so early on M&E -- essentially before the grant even begins -- Knight is demonstrating how these tools can be used for partnership and management, not merely bean-counting. Our opportunity as the grantee is to embrace their challenge of partnership.