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 #1

Lead: Jonathan Zuck


Quality vs Quantity of ALAC Advice
Final Proposal as approved by the Board

Staff, under the direction of At-Large leadership, has already begun to rework the website and Wiki to ensure that our “Policy Advice” pages are accurate and understandable. This will continue as volunteer and staff resources allow. We will also ensure that as documents are published, the classification of the document is clear.

Prioritization1:1:1 (Low resource needs : Low risk ; 1st priority)
ARIWG comments

(MH) This activity could relate to Activity Item #7 with regards to working groups.

 (AC) re 4. c. Using the newly formed policy working group (CPWG) as an initial filter and in turn to make make recommendations to the community on prioritization (NOT SURE I Understand the idea) Thanks for the question Alfredo! What I'm proposing is that instead of every call for public comment simply announced to the community by staff, prompting individuals to take up things of personal interest, we bring each public comment before the CPWG and discuss it's relevance to end users and, only if deemed relevant to our particular perspective, do we make a call for drafters. Make sense?

(NA) I could see two fold of the “Outreach an Engagement”, Outreach is one and Engagement is two.  Handling the Outreach, RALOs with its community of active ALSes to take part of the outreach within their ALSes members and to their wider community. 

Then, awareness of at-large and ALAC work comes before any community members to start in policy engagements. Or create a system of shadow mentor to those who wanted to get directly into policy work.  

Status of improvement effort / staff leadAlready underway, continuous improvement to continue / HU; EE
Status of improvement effort / staff leadAlready underway, continuous improvement to continue / HU; EE
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 Activities, if any, on which implementation is dependent, or that are dependent on implementation of this recommendationWho will implement the recommendation: ICANN community, ICANN Board, ICANN Organization, other?ICANN Staff in conjunction with ALAC/At-Large Leadership
Anticipated resource requirements (FTEs, tools)Staff up to 0.2 FTEs in Dec 2018 through to Dec 2019
Expected budget implicationsNothing additional beyond already allocated resources to At-Large.

Proposed implementation steps:

  1. Nov 2018 convene analysis and review of issue and status of improvements to date micro-team with staff allocated, penholders for this issue <insert link to wiki page> and ARIWG member volunteers as desired.
  2. Identify the specifics of processes and practices used to date.
  3. Identification of opportunities for process improvement or modification
  4. Development of proposal for reenvisioning any processes and practices to be discussed by ALAC / At-Large and those utilising ALAC advice.
  5. Documentation process renewal proposal as agreed and prioritised developed into a project plan. Noting which milestones are intended to be reached by Dec 2019, and what is to be undertaken under review and continuous improvement planning.

(NA) suggesting 6. Staff to provide a summary documenting all contributors (at-large individuals and/or  ALAC members), once the comment  period of certain policy is closed. (reasoning, it might work as incentives for individuals)

Continuous Improvement(s)
  1. Continue and expand the development of webinars to educate the at-large community on the policy considerations of the ICANN community
  2. Draw a bright line distinction between individual and at-large policy advice
  3. Ensure that at-large representatives to WGs and PDPs are aware of and clear on those distinctions when speaking for the at-large
  4. Reimagine the process of advice prioritization by
    1. Focusing on the perspective of the typical end user (as defined by activities not specific groups of end users)
    2. Being disciplined NOT to develop advice when there is no unique "end user" perspective to bring to the discussion (like an amicus brief)
    3. Using the newly formed policy working group (CPWG) as an initial filter and in turn make recommendations to the community on prioritization
    4. Seek feedback from regional leaders on prioritization advice
  5. Reimagine the process of advice/policy development by
    1. Using the CWPG to formulate an initial perspective on a particular ICANN policy area
    2. Use the regional leaders to socialize and receive feedback on that perspective
    3. only THEN identify a pen holder to draft advice from THAT perspective
    4. finally, submit that draft for open comment by the at-large community
  6. Reimagine the participation of non-English speakers in at-large policy/advice development by
    1. Continue to develop "issue briefs" in multiple languages to assist in education of non-English speakers
    2. Employ simultaneous translation on CPWG calls
    3. Continue and expand staff use as proofreaders for non-English fluent drafters before drafts are made public
    4. Employee translators for drafts drafted in a language other than English
Metrics
  1. Number of advice drafts that result from this process (as opposed to the current process of random volunteers)
  2. Number of attempts to get feedback of the larger community
  3. Quantity of respondents to attempts to seek feedback
  4. Number of at-large community participants in policy/advice development
  5. Number of non-fluent English speakers engaged in policy/advice development
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 #2Uneven contribution of At-Large to a coordinated ICANN strategy for ‘Outreach and Engagement’. Missed opportunities for coordination with other constituencies and ICANN staff. (JC: is this the correct issue statement?)

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.limited time and energy to devote to At-Large activities.


(NA) I could see two fold of the “Outreach an Engagement”, Outreach is one and Engagement is two.  Handling the Outreach, RALOs with its community of active ALSes to take part of the outreach within their ALSes members and to their wider community. 


(NA) Awareness programs of at-large and ALAC work comes before any community members to start in policy engagements.

(NA) Create a system of shadow mentor to those who wanted to get directly into policy work.  

Status of improvement effort / staff lead
Activities, if any, on which implementation is dependent, or that are dependent on implementation 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.

(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.

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

8. (NA) A targeted policy development training program to at-large staff goes hand-in hand with at-large community development or capacity building program. Reasoning the peer learning and discussions enhances the learning.  


9. (NA) Review the job description of at-large staff to develop separate positions /roles with clear organizational structure.



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
  2. (JC) Consider capacity of staff in being the librarian for At-Large's policy repository
  3. (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
  4. (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
  5. (JC) Performance review
  6. Consider further use of staff as proofreaders for non-native English speakers
  7. Consider use of staff as translators for non-english participants in advice development
  8. Consider further use of staff to present issues on webinars
Continuous Improvement(s)


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

...