AT-LARGE GATEWAY
At-Large Regional Policy Engagement Program (ARPEP)
At-Large Review Implementation Plan Development
Page History
...
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 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 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 finalisationfinalization.
This task is expected to be completed by 18 December 2018.
...
To access the Issue you would like to view, click the Toggle cloak > You will see that a demonstration model Item #1 has been started. But this is only draft and for demonstration purposes only.
...
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 discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#2 Toggle Cloak
Cloak | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
| 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#3 Toggle Cloak
...
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
Issue #3
Lead: Holly Raiche
...
- Consider further use of staff as proofreaders for non-native English speakers
- Consider use of staff as translators for non-english participants in advice development
- Consider further use of staff to present issues on webinars
- (JC) Consider capacity of staff in being the librarian for At-Large's policy repository
- (JC) Consider knowledge of staff in actual issues of policy considered by At-Large
- (JC) Consider capacity of staff in monitoring and applying commentary contributions by At-Large community members through various tools / channels, as well as usage of tools for facilitating such contributions
- (JC) Performance review
|
...
Proposed implementation steps:
...
- (JC) Identify what policy support activities ALAC / At-Large needs first
...
- (JC) Performance review
...
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
...
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the 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 |
Issue #5
Lead: Tijani Ben Jemaa
...
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.
...
(MH) Collaboration and coordination with Issue Teams #12, #13,and #15 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?
(AC) Agree with Maureen’s comment on metrics. A detailed rubric should be in place.
(AC) What is the objective of the Capacity Building Program?
What metrics are we using to ensure this.. therefore this item has to be linked to the Metrics item #16 as well
...
Proposed implementation steps:
...
ARIWG Prioritization and Dependencies - Issue#6 Toggle Cloak
...
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
Issue #6
Lead: Sebastien Bachollet
...
Proposed implementation steps:
...
ARIWG Prioritization and Dependencies - Issue#7 Toggle Cloak
...
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
Issue #7
Lead: Javier Rua-Jovet
...
(MH) Collaboration advised due to relationship of this issue with Item issue #1 - Quality vs quantity of policy advice
...
Proposed implementation steps:
...
ARIWG Prioritization and Dependencies - Issue#8 Toggle Cloak
Cloak | |
---|---|
NOTE: text in cells below shown in colour is DRAFTonly, for discussion by the ARIWG Issue #8 Lead: John Laprise | 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 | 3.3.2. (High resource needs; High risk; #2 priority) |
ARIWG comments | (MH) This item highlights how we can use social media to enhance the work that is being done in O&E, so that some collaboration with the task teams working on areas #5, #12. #13 and #15 would be appropriate Also to the communication channels item #10, looking at effective ways to disseminate important messages out to the wider public as well as the At-Large Community | 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? |
Issue #4 Lead: Maureen Hilyard | Leadership Team (ALT), which is not mandated by ICANN Bylaws, concentrates in the established leadership too many decision-making and other administrative powers which should be spread among the members of the ALAC. |
---|---|
Final Proposal as approved by the Board | 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 | 1:1:1 (Low resource needs : Low risk ; 1st priority group) |
ARIWG comments | This leadership model has been developed by the incoming Chair to offer a visual representation of the new At-Large Leadership Team (ALT), as part of her preparation for future Leadership of At-Large. The ALT now includes Regional Leaders, to encourage more interaction between the ALAC and the leaders of our regional member organisations. The objective is also to ensure that decisions and other important messages from the ICANN Board (through our At-Large Board representative) and from other constituencies of ICANN (through the ALAC Liaisons) are relayed more directly to Regional Leaders and will more easily filter to the At-Large Community through RALO meetings and outreach and engagement opportunities. This issue also relates to Issue #2 which also included a comment regarding a perception of unchanging leadership which seems a little out of context in its current position. (NA) Fitting ALT into the following At-Large structure, as it is still not the case per the document below https://www.icann.org/sites/default/files/assets/alses-beginners-guide-02jun14-en.pdf (NA) Re-considering the ALT leadership team to be different than the ALAC members. Reasoning: to bring more leaders into ALT, ALAC, At-Large, RALO structure and reduce the work load and volunteer burnout of the current ALAC members. |
Status of improvement effort / staff lead | |
Activities, if any, on which implementation is dependent, or that are dependent on implementation of this recommendation | Introduction of the organigram to all the members to get buy in to the organisational model and the purposes behind making the information more transparent. This is proposed to take place during the Development Session of the ALAC , Regional Leaders and Liaisons which will be held at the conclusion of ICANN63 in Barcelona. This session will also give implementation issue teams a chance to discuss their plans for the items they have been assigned, with each other and to get feedback Other organisational teams (CPWG and O&E leads will be able to share some goals and objectives for their working teams during 2019, especially as we lead up to ATLASIII. |
Who will implement the recommendation: ICANN community, ICANN Board, ICANN Organization, other? | ICANN Staff in conjunction with the ALAC/At-Large Leadership |
Anticipated resource requirements (FTEs, tools) | |
---|---|
Expected budget implications | |
Proposed implementation steps: |
ARIWG Prioritization and Dependencies - Issue#9 Toggle 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
|
Issue #9
Lead: John Laprise
...
(MH) This task is related to Activity Item #8 about using social media to assist At-Large with its outreach attempts to attract more participants into our policy development areas and how we can do this more effectively
(AC) Also linked to Capacity Building Program as a transversal objective to build O&E, besides disseminating information.
...
Proposed implementation steps:
...
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 Issue #10 Lead: Dev Anand Teelucksingh | There are a multitude of communications channels used by At Large. This has led to fractured and undocumented communications. |
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 | 3.3.1. (High resource needs; High risk; #1 priority) | 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#13 Toggle Cloak
Cloak | |||||
---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
Lead: Olivier Crepin Leblond 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.
| The ALAC will proceed with its plans as approved by the Board, pending appropriate funding. As with all At-Large activities, there will be an increased focus on tracking and metrics. | ||||
Prioritization | 3.3.1. (High resource needs; High risk; #1 priority) | ||||
ARIWG comments | (MH) ATLASIII, ICANN66 Montreal, Canada in November 2019 will be dependent on the outcomes of this implementation plan. The Metrics Issue #16 also relates to this task. | 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#12 Toggle Cloak
| |||||||||
Cloak | |||||||||
---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG Issue #12 Lead: Cheryl Langdon Orr | ALAC input to a coordinated ICANN Outreach sub-optimal. | ||||||||
Final Proposal as approved by the Board | 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. | ||||||||
Prioritization | 3.3.1. (High resource needs; High risk; #1 priority) | ||||||||
ARIWG comments | (MH) Collaboration and coordination with Issue Teams #5, #13,and #15 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 (AC) At-Large on the Road approach... | 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? | Joint implementation - At-Large O&E S/C needs support from GSE especially when it comes to Community Outreach |
---|---|
Anticipated resource requirements (FTEs, tools) |
Proposed implementation steps:
ARIWG Prioritization and Dependencies - Issue#13 Toggle Cloak
|
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
| |||||||||||
Cloak | |||||||||||
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG Issue #13 Lead: Glenn McKnight | 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 | 2.2.1 (Medium needs; medium risk; #1 priority group) | ||||||||||
ARIWG comments | (MH) Collaboration and coordination with Issue Teams #5, #12,and #15 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 | 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#14Issue#15 Toggle Cloak
Cloak | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
| 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#15 Toggle Cloak
| ||||||||||||||||||||||||||||
Cloak | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
ARIWG Prioritization and Dependencies - Issue#16 Toggle Cloak
Cloak | |||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NOTE: text in cells below shown in colour is DRAFT only, for discussion by the ARIWG
|
...