As the Agency Subject Matter Expert on Results Frameworks, I needed some way to interact with those who would be most affected by the concept - field mission staff and partners. RFNET turned out to have value as the only Agency informal dialogue on the reforms of the Agency's programming procedures, ADS 200-203. "RFNET" known by most USAID staff, and quoted during NEP training, but most would not know origin of term. It has had about 400 members plus/minus over its life, with about 45% inside AID, and 55% outside. At its height it had extensive use outside of the 400 subscribers; some missions subscribed corporately and posted selected postings on their own intranet, or emails to staff. Originally approved by the DAA for Africa, and funded through 2000 by AFR/SD/NRM. In 2001, RFNET moved to PPC/PC. Total number of messages: approximately 1,200 since inception.
Primary Objectives
Provide a venue for dialogue to help with "rolling design" of the RF concept and other aspects of ADS 200
Help to improve morale on the part of field staff and partners, who felt unconnected to the top-down aspects of the new programming procedures
Help to provide answers for field staff
Help to bridge divide between USAID staff and partners.
Share best practices and field experiences
What Went Right...
Launching the CoP
Received DAA approval, and blessing at Bureau-wide meeting (as part of rollout of the Agency reforms). BUT DAA also approved its existence purely as an off-line community - no requirement for a Direct Hire supervisor, review committee or planning document. Funding from AFR environmental funds, based on a liberal view of the topic.
Not only had demand, but had ready made content.
It was clear from comments that many of AID's field staff had a strong affinity for the list
Defined the topic, not the community. (i.e. didn't say it
was for PDOs, or ag officers, but that it was dealing with
program procedures. This then led to self-definition of interest
- those closest to using the procedures gravitated to it,
without having to "sell" the community.
Sustaining the CoP
Enthusiasm never waned; core membership constant. Demand for topic and COP still, in my view, is very strong.
Very low cost, other than "donated" staff time.
While time consuming the RFNET website was used as an archive. "Best picks" - essentially synthesized threads - were well-received.
Lessons Learned
It takes commitment, but it should not be too formalized. Bureaucratic formality kills willingness to speak up "in draft"
Would have been useful to have been able to get some seconded time for co-editors/leaders, but not too much time.
Focus on the dialogue, not writing up static "best practice" responses.
Do NOT limit COPs just to AID staff, unless it is truly an internalized function.
Be careful that CoPs do not try to be both organic and centrally defined. Very hard to build in enthusiasm.
