Reviving an M&E Community of Practice Without Mandatory Posting
OpenVoice is a global health NGO with 1,100 staff in 24 countries. Its monitoring and evaluation community of practice launched 18 months ago and has 400 members. Monthly active contributors have fallen from 85 to 23, and 12 people produce 70% of posts. Field staff say the platform is another reporting burden; the help they value most happens in informal WhatsApp groups. Leadership proposes badges, a weekly mandatory post for country M&E officers, and tying participation to performance reviews. A donor asks for 'community engagement metrics' in the next grant report. The KM advisor has one part-time community manager and no budget for a new platform. The advisor must respond to leadership without simply defending the community.
1. Diagnose the community's health. Which signals matter, and which are misleading?
Read the worked answer
Start by separating community health from platform activity. The 400-member count is a registration metric, not health. The fall from 85 to 23 contributors may reflect the end of launch novelty rather than decline. A core of 12 producing 70% of posts is consistent with a normal core-periphery structure; it becomes a risk only if the core is unrepresentative, overloaded, or closed to newcomers.
The more important signals are:
- Are field staff getting timely, useful answers to real M&E problems?
- Are methods or tools being reused or adapted across countries?
- Is the domain still salient to program quality, or has it become a reporting channel?
- Is the WhatsApp migration a sign that value is happening outside the platform?
The platform may be a broadcast and compliance space, while the actual community lives in WhatsApp. That is a design mismatch, not necessarily a member apathy problem. Misleading signals include member count, post count, and any metric that treats mandatory participation as engagement. Listen to country staff before redesigning.
2. Evaluate the proposed badges, mandatory weekly posts, and performance-review linkage. What would you recommend instead?
Read the worked answer
Mandatory weekly posting would produce compliance noise. It would dilute the signal, burden country officers who are already reporting, and make the platform less useful. Tying participation to performance reviews conflates community citizenship with job performance and can punish quiet experts who help privately. Badges can motivate some people, but they can also crowd out intrinsic helping and reward visible posting over useful response.
Recommend instead:
- Negotiate a clear community purpose tied to program quality, with a sponsor who uses the community's advice.
- Recruit and support a core group with explicit time, recognition, and a rotating facilitation role.
- Create a predictable rhythm: monthly peer review of real M&E products, quarterly methods clinic, and office hours rather than mandatory posts.
- Curate a digest from WhatsApp with contributor consent, so the informal value becomes visible without forcing migration.
- Fund at least 0.5 FTE coordination; the current part-time manager cannot sustain the rhythm alone.
If leadership wants accountability, use a charter with a sponsor, annual review, and defined issues the community is expected to address. That is different from policing posts.
3. Propose three engagement metrics and one counter-metric for the donor report. Explain what each can and cannot show.
Read the worked answer
Use metrics that describe value and risk, not volume.
- Responsiveness: percentage of member requests that receive a substantive response within five business days. This shows whether the community is useful, but not whether the answer was correct.
- Practice adoption: number of documented adaptations or reuses of M&E tools, guidance, or methods by country teams, with short case notes. This shows value, but it is self-reported and may overstate attribution.
- Peripheral reach: percentage of members who attend at least one event or read the digest per quarter. This shows reach beyond the core, but not depth of engagement.
Counter-metric: core-group workload and concentration. Track hours contributed by the top 12 contributors and the share of requests they answer. If concentration rises while responsiveness falls, the community is burning out its core. Also report unanswered requests as a service gap.
Do not report posts per member or mandatory participation rates as engagement. They measure compliance, not community.