Page History

At-Large should abandon existing internal Working Groups, too many of which are currently focused on process, and a distraction from the actual policy advice role of At-Large. Their creation should in future be avoided. If absolutely necessary, any such group should be strictly task/time limited and policy focused, or its role taken on by volunteer pen holders assisted by policy capable staff.

Excessive amounts of At-Large Community time spent on process and procedure at expense of ALAC’s mandated responsibilities to produce policy advice and coordinate outreach and engagement activities. Too many internal working groups are a distraction.

The ALAC strongly objects to this recommendation.

Working Groups, under a variety of names, are the basic way that ICANN and its constituent parts discuss issues, address concerns, come to agreement and make decisions. The ALAC believes that they are core to its success, both in the formulation of its policy advice as well as in furthering its process development (as suggested by the Review Recommendations on outreach, collaboration tools and social media)

The At-Large community creates WGs for a number of reasons that together form the framework that allows and encourages participation by the At-Large community in the discussion and shaping of policy that can properly reflect the interests of end-users. Hence the existence of these WGs is not trivial and indeed it constitutes the grassroots of participation for end-users within the ICANN policy development process. It is through such WGs that new participants often become active contributors. The ALAC believes that they are core to its success, both in furthering its process development (as suggested by the Review Recommendations on outreach, collaboration tools and social media) as well as in the formulation of its policy advice.

The uses of WGs include: 

Policy-Related Tasks: These WGs are used to build policy recommendations and advice, merging and melding differing opinions and ensuring that all parties can contribute. The final statements are supported by the ALAC and the RALOs. WGs were critical to the ALAC’s ability to very effectively contribute to the New gTLD Process, the IANA Stewardship Transition Plan, and the new Accountability measures. These WGs are generally open to all participants in At-Large. 

Process-Related Tasks: These WGs, in general, carry out tasks on behalf of the ALAC; at times making decisions on behalf of the ALAC. Their tasks include providing: advice and decisions on ICANN special budget requests; advice and decisions on CROPP requests; deliberation and advice on outreach; as well as deliberation and development of capacity building programs. 

Outreach and Engagement: We have WGs which address needs such as: Tools (such as messaging and conference), Translation, Captioning; Social Media and Accessibility (ensuring that those with disabilities can participate equitably). Several of these have been sufficiently successful that they have been, or are in the process of being, transitioned to ICANN-wide projects (for example, ICANN Academy, Accessibility, Captioning). 

The At-Large Community, as does every SO/AC, has policy and process activities to address policy and process issues, to improve the effective functioning of their organisation. They constitute the base forum for end-users to voice their thoughts, discuss their concerns in relation to any given policy being discussed at ICANN, and frame agreements and strategies on how to positively impact the policy development process to benefit internet end-users. Open Working Groups are the backbone of At-Large in reaching consensus by providing bottom-up, grassroots input. 

There are also WGs internal to RALOs set up to respond to ALAC policy and process in particular regions. RALO WGs are the prime forum for individual members and ALSes to provide input. They highlight awareness of the diversity of regional approaches as well as taps into the skills and interests of individual and ALS members. 

In all cases, WGs can be dismantled as their tasks are completed. 

It should be noted here that the CCWG-Accountability subgroup on SO/AC Accountability is considering recommending that SO/ACs create an outreach WG to improve the performance of that function - one of the WGs that this recommendation is suggesting being abolished.