Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Cloak

NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG

Issue #2Uneven contribution of At-Large to a coordinated ICANN strategy for ‘Outreach and Engagement’. Missed opportunities for coordination with other constituencies and ICANN staff.

Final Proposal as approved by the Board

Lead: Bastiaan Goslings

At-Large is increasingly focusing on individuals (both unaffiliated At-Large Members as well as members within
each ALS) instead of just ALS voting representatives. Four of the five (RALOs) allow individual members and the fifth, LACRALO, has already approved the concept and is developing the detailed rules. We will also use the ALSes to communicate with those within an ALS who may have an interest in ICANN.

RALOs have also started to identify experts on ICANN topics within their ALSes and among individual members and to increasingly engage them in ALAC’s policy work. Thus, a bi-directional flow of ICANN information continues to be strengthened.

These activities will require the production of information that is truly understandable (as identified in a recent ALAC-GAC Joint Statement) and available in multiple languages. As some of this will need to be created by At-Large staff, additional resources may be needed. We would suggest that At-Large Staff continue to work together with At-Large Leadership in looking for effective methodologies to coach and onboard new policy volunteers and leaders to facilitate the development of their skills and encourage them to stay and deepen their knowledge and expertise. Regarding the perception of unchanging leadership, statistics reporting involvement will be published

Prioritization3.3.1. (High resource needs; High risk; #1 priority)
ARIWG comments

(MH) Do we need to review our application forms for ALSes and Individual members to ensure that we have active participants in our At-Large activities? Otherwise we are planning to put an inordinate amount of work in to reach whom we assume are potential participants who aren't actually there. In APRALO we have 20 names of which only about 3 or 4 are active. I never see others at our meetings etc, so why do they join? are they participating in ICANN Learn?

(JC) I think there are several aspects to be considered. 1/ Membership application – we need to do better in asking why orgs and people join a RALO – would this then become a criteria in assessing applications? 2/ Identification of experts and willing & able contributors from within ALSes and individual membership – has the adopted method(s) been successful in each RALOs, why? why not? 3/ Establish clear, member-friendly mechanisms for continued engagement, mechanisms which everybody knows apply – who does what with whom? how is it done? 4/ Then, yes to looking for effective methodologies to coach and onboard new policy volunteers and leaders. All with the understanding that everybody has limited time and energy to devote to At-Large activities.

Status of improvement effort / staff lead
Activities, if any, on which implementation is dependent, or that are dependent on implementation of this recommendationimplementation of this recommendation(JC) Baseline standardization of RALO membership criteria and application process (including assessment), subject to the remits of ICANN Bylaws applicable to ALAC.
Who will implement the recommendation: ICANN community, ICANN Board, ICANN Organization, other?(JC) ALAC, RALO LT, AT-Large Staff
Anticipated resource requirements (FTEs, tools)
Expected budget implications

Proposed implementation steps:

(JC) I sort of alluded to proposed steps in ARIWG comments box.

Continuous Improvement(s)
Metrics
How long will it take to implement this plan?

...

Cloak

NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG

Issue #3

Lead: Holly Raiche


Staff resources are disproportionately concentrated on administrative support. Staff should have greater capacity to support preparation of policy advice.
Final Proposal as approved by the Board
Continue to look for opportunities to utilize and develop the skills of At-Large support staff while ensuring that the positions taken by At-Large represent solely those of users. Ensure that the volunteer community has sufficient support services so as to best utilize their volunteer time. This may require a shift or development of skills among At-Large Staff as well as additional staff.
Prioritization3.3.1. (High resource needs; High risk; #1 priority)
ARIWG comments
  1. Consider further use of staff as proofreaders for non-native English speakers
  2. Consider use of staff as translators for non-english participants in advice development
  3. Consider further use of staff to present issues on webinars
  4. (JC) Consider capacity of staff in being the librarian for At-Large's policy repository
  5. (JC) Consider knowledge of staff in actual issues of policy considered by At-Large to enable them to be effective points of reference for queries, past positions, webinars etc
  6. (JC) Consider capacity of staff in monitoring, distilling and applying commentary contributions by At-Large community members collected through various tools / channels, as well as usage of tools for facilitating such contributions
  7. (JC) Performance review
Status of improvement effort / staff lead
Activities, if any, on which implementation is dependent, or that are dependent on implementation of this recommendation
Who will implement the recommendation: ICANN community, ICANN Board, ICANN Organization, other?(JC) ICANN Org for HR aspects, ALAC for actual implementation, with supervision also provided under CPWG leadership (or any other WG dealing with ALAC policy)
Anticipated resource requirements (FTEs, tools)
Expected budget implications

Proposed implementation steps:

  1. (JC) Identify what policy support activities ALAC / At-Large needs first
Continuous Improvement(s)


Metrics
  1. (JC) Performance review
How long will it take to implement this plan?

...