AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
At-Large Review Implementation Plan Development
Page History
Introduction to this workspace:
Welcome to the At-Large Review Implementation Prioritisation Prioritization and Dependencies Workspace. The Board approved sixteen proposals suggested by the ALAC to resolve as a result
During the process of the At-Large Review.
The Organisational Effectiveness Committee has provided templates that are expected for each individual item, detailing the steps that At-Large will undertake to address each of these issues.
An Issues Team led by At-Large leaders will detail these steps as discussed by their work teams, and will bring these to the Implementation Working Group for comment and finalisation.
, the ALAC committed to eight review implementation activities (1, 2, 3, 4, 7, 9, 13 and 16) which the Board agreed to in their Resolution dated 23 June 2018.
There were an additional five issues (5, 6,, 8, 10, 11) raised in the At-Large Review which the ALAC considers important but are continuously being addressed as part of At-Large's ongoing activities.
Three issues (12, 14 and 15) will be focused upon as applicable but there is no immediate ongoing activity.
The Organizational Effectiveness Committee has provided templates that are expected for each individual item, detailing the steps that At-Large will undertake to address each of these issues.
An Issues Team led by At-Large leaders will detail these steps as discussed by their work teams, and will bring these to the Implementation Working Group for comment and finalization.
This task This task is expected to be completed by 18 December 2018.
...
Key related workspace: ARIWG Plan Development
To access the Issue you would like to view, click Edit (above)
Issues #1 - #16:
...
Please note issues committed to by the ALAC and approved by the Board are highlighted in green.
ARIWG Prioritization and Dependencies -
...
Issue#1
Toggle Cloak |
---|
Cloak | |||||||
---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for demonstration purposes and discussion within by the AIRWG ARIWG
| |||||||
Status of improvement effort / staff lead | Already underway, continuous improvement to continue / HU; EE | ||||||
Activities, if any, on which implementation is dependent, or that are dependent on implementation of this recommendation | None noted as at end Sept 2018 | ||||||
Who 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 implications | Nothing additional beyond already allocated resources to At-Large. | ||||||
Proposed implementation steps: |
| Continuous Improvement(s) | Metrics |
ARIWG Prioritization and Dependencies - Issue#2 Toggle Cloak
...
NOTE: text in cells below shown in colour is DRAFT only for demonstration purposes and discussion within the AIRWG
...
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
...
Proposed implementation steps:
...
ARIWG Prioritization and Dependencies - Issue#3 Toggle Cloak
...
|
NOTE: text in cells below shown in colour is DRAFT only for demonstration purposes and discussion within the AIRWG
...
Proposed implementation steps:
...
ARIWG Prioritization and Dependencies - Issue#2
Toggle Cloak
Cloak | |
---|---|
NOTE: text in cells below shown in colour is DRAFT only, for demonstration purposes and discussion within by the AIRWG | |
Final Proposal as approved by the Board - Issue #4 | The ALAC Chair will work with members of the ALAC and staff to better communicate the role and activities of the ALT ensuring that it is clear what the ALT does and does not do. | Prioritization | ARIWG comments | 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? | Anticipated resource requirements (FTEs, tools) | Expected budget implications | Proposed implementation steps: | Continuous Improvement(s) | Metrics |
ARIWG Prioritization and Dependencies - Issue#5 Toggle Cloak
...
NOTE: text in cells below shown in colour is DRAFT only for demonstration purposes and discussion within the AIRWG
...
To the extent allowed by ICANN’s mission and available funding, members of At-Large and the At-Large organizations will continue to, and potentially increase, our involvement
with other I* organizations as a method for increasing the visibility of At-Large, exploring areas for mutual collaboration and for attracting additional At-Large volunteers.
At-Large will continue to work closely with GSE Staff to contribute to regional outreach plans and to encourage participation in a cross-community, cross-organizational fashion.
...
Proposed implementation steps:
...
ARIWG Prioritization and Dependencies - Issue#6 Toggle Cloak
...
NOTE: text in cells below shown in colour is DRAFT only for demonstration purposes and discussion within the AIRWG
...
Proposed implementation steps:
...
ARIWG Prioritization and Dependencies - Issue#7 Toggle Cloak
...
NOTE: text in cells below shown in colour is DRAFT only for demonstration purposes and discussion within the AIRWG
...
ARIWG
|
ARIWG Prioritization and Dependencies - Issue#3 Toggle Cloak
Cloak | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#4 Toggle Cloak
Cloak | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#5 Toggle Cloak
Cloak | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#6 Toggle Cloak
Cloak | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#7 Toggle Cloak
Cloak | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#8 Toggle Cloak
Cloak | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFTonly, for discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#9 Toggle Cloak
Cloak | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#10 Toggle Cloak
Cloak | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#11 Toggle Cloak
Cloak | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#12 Toggle Cloak
Cloak | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#13 Toggle Cloak
Cloak | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#14 Toggle Cloak
Cloak | ||||||||
---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
...
Proposed implementation steps:
...
ARIWG Prioritization and Dependencies - Issue#8 Toggle Cloak
Cloak | |
---|---|
NOTE: text in cells below shown in colour is DRAFT only for demonstration purposes and discussion within the AIRWG | |
Issue #8 | Social media and other Internet-based tools could be used more effectively, and at minimal cost, to continuously survey and channel end-user input into ICANN policy making processes. |
Final Proposal as approved by the Board | We will continue to investigate opportunities to use Social Media and other online tools that prove useful to bring end-users’ voices to ICANN and vice -versa. However, we caution against seeing social media and online tools as a substitute for other means of participation. We are eager to work with ICANN Organization to understand ICANN’s interests in this area, and the tools available to integrate and communicate our work more effectively. | Prioritization | ARIWG comments
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? | |
Anticipated resource requirements (FTEs, tools) | |
Expected budget implications | |
Proposed implementation steps: | |
Continuous Improvement(s) | |
Metrics | |
How long will it take to implement this plan? |
ARIWG Prioritization and Dependencies - Issue#9Issue#15 Toggle Cloak
Cloak | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for demonstration purposes and discussion within by the AIRWG ARIWG
| The ALAC will request additional staff skill development in the area of social media, and to work cooperatively with ICANN Communications social media specialists. | Prioritization | ARIWG comments | 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? | Anticipated resource requirements (FTEs, tools) | Expected budget implications | Proposed implementation steps: | Continuous Improvement(s) | Metrics |
ARIWG Prioritization and Dependencies - Issue#10 Toggle Cloak
Cloak | |
---|---|
NOTE: text in cells below shown in colour is DRAFT only for demonstration purposes and discussion within the AIRWG | |
Issue #10 | While broadly popular, Global ATLAS meetings every 5 years have been difficult to organize and short on effective results. More frequent regional meetings would be more effective in encouraging both policy input and outreach while familiarizing more of At Large with workings of ICANN. |
Final Proposal as approved by the Board | The ALAC Technology Taskforce regularly reviews various communications tools with the aim of improving At-Large participation. The At-Large Community is very diverse and the selection of any new tools must accommodate this diversity. We will also need to continue to investigate how we can overcome the lack of affordable communications for many of our participants and future participants. | Prioritization | ARIWG comments |
by the Board | As noted previously, subject to available funding, we do look for opportunities to explain At-Large and attract new participants at non-ICANN events. When opportunities have arisen where funds are available to bring a targeted group to an ICANN meeting with a good potential for future involvement, we have done so. |
---|---|
Prioritization | 3.3.1. (High resource needs; High risk; #1 priority) |
ARIWG comments | (MH) Collaboration and coordination with Issue Teams #5, #12,and #13 which are also to do with Outreach, will be required (MH) before we go further with our current O&E and capacity building programmes, have we really assessed the effectiveness of our current approaches to ensure that our programmes are actually achieving the proposed objectives and impacting the target groups that we want them to reach? What metrics are we using to ensure this.. therefore this item has to be linked to the Metrics item #16 as well (MH - in bylaws: The ALAC, which plays an important role in ICANN's accountability mechanisms, also coordinates some of ICANN's outreach to individual Internet users. (NA) with reference to “When opportunities have arisen where funds are available to bring a targeted group to an ICANN meeting with a good potential for future involvement, we have done so.” was there a measurement of the success rates of these program? How many of those benefited from these programs continued to be engaged in ICANN SO/ACs? (NA) A rubric is needed to make sure those invited would be worth the investment. (JH) More collaboration with Local GSE who attend many events and could provide ALSes with additional opportunities to outreach and engage at a local level with minimal travel needed. |
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 |
Proposed implementation steps:
, other? | |
---|---|
Anticipated resource requirements (FTEs, tools) | |
Expected budget implications | |
Proposed implementation steps: |
|
Continuous Improvement(s) | |
---|---|
Metrics | |
How long will it take to implement this plan? |
ARIWG Prioritization and Dependencies -
...
Issue#16 Toggle Cloak
Cloak | |
---|---|
NOTE: text in cells below shown in colour is DRAFT only, for demonstration purposes and discussion within the AIRWG | Issue #11 | While broadly popular, Global ATLAS meetings every 5 years have been difficult to organize and short on effective results. More frequent regional meetings would be more effective in encouraging both policy input and outreach while familiarizing more of At Large with workings of ICANN
...
As noted in Issue 5, the ALAC supports such external activity to the extent that funding is available and it coincides with ICANN’s mission. Increases in such funding would be appreciated, but in light of the FY19 draft budget, we are now in a mode of trying to minimize impact of the proposed cuts to such activities.
...
Proposed implementation steps:
...
ARIWG Prioritization and Dependencies - Issue#13 Toggle Cloak
Cloak | |
---|---|
NOTE: text in cells below shown in colour is DRAFT only for demonstration purposes and discussion within the AIRWG | |
Issue #13 | Need more systematic RALO participation in regional events |
Final Proposal as approved by the Board | At-Large Staff working with relevant departments to develop a single location which will point to travel funding opportunities and documentation of what resources were ultimately distributed, to the extent supported by those ICANN entities providing funding and reports. | Prioritization | ARIWG comments |
Issue #16 Lead: Maureen Hilyard | Absence of consistent performance metrics. |
---|---|
Final Proposal as approved by the Board | The ALAC |
Proposed implementation steps:
ARIWG Prioritization and Dependencies - Issue#12 Toggle Cloak
...
NOTE: text in cells below shown in colour is DRAFT only for demonstration purposes and discussion within the AIRWG
| Who will implement the recommendation: ICANN community, ICANN Board, ICANN Organization, other? | Anticipated resource requirements (FTEs, tools) | Expected budget implications | Proposed implementation steps: | Continuous Improvement(s) | Metrics |
---|
ARIWG Prioritization and Dependencies - Issue#14 Toggle Cloak
...
NOTE: text in cells below shown in colour is DRAFT only for demonstration purposes and discussion within the AIRWG
...
It is the understanding of the ALAC that At-Large may only be funded from ICANN operational funds.
...
Proposed implementation steps:
...
ARIWG Prioritization and Dependencies - Issue#15 Toggle Cloak
...
NOTE: text in cells below shown in colour is DRAFT only for demonstration purposes and discussion within the AIRWG
...
As noted previously, subject to available funding, we do look for opportunities to explain At-Large and attract new participants at non-ICANN events. When opportunities have arisen where funds are available to bring a targeted group to an ICANN meeting with a good potential for future involvement, we have done so.
...
Proposed implementation steps:
...
ARIWG Prioritization and Dependencies - Issue#16 Toggle Cloak
| ||||||||||||||
Cloak | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only for demonstration purposes and discussion within the AIRWG | ||||||||||||||
Issue #16 | Absence of consistent performance metrics. | |||||||||||||
Final Proposal as approved by the Board | The ALAC has had a Metrics WG and an ALS Review Taskforce, both of which largely went into stasis during the IANA Transition and Accountability efforts. It is proposed to revive this activity as part of the At-Large Review Implementation. The ALAC notes that regional differences make it more difficult to have uniformity over participation metrics, but agrees that is an important target. The ALAC notes that collecting such statistics is a staff-intensive operation. | Prioritization | ARIWG comments | 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? | Anticipated resource requirements (FTEs, tools) | Expected budget implications | Proposed implementation steps: | Continuous Improvement(s) | Metrics