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 #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.
Prioritization1: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.

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:

Many of the issues raised have already been addressed in some way by the Incoming Chair. The following steps have been covered:

1. An Organigram has been developed to show a new At-Large Leadership model that is more inclusive and collaborative, as well as being more transparent and accountable. 

2. The Organigram demonstrates how leadership roles are dispersed among ALAC and Regional Leaders, as well as to key leads who take responsibility for the core tasks of At-Large - namely, Development of Policy Advice; Outreach and Engagement; and Organisational Matters 

3. Regional Leaders  have been incorporated into what is now the At-Large Leadership Team to enable them to share in ALAC discussions about key issues, and then to share any key messages with their regional members.

4. At-Large Leadership team meetings will be open to the ALAC and the public unless there are specific, usually personnel, issues to be discussed (as per any ALAC meeting). These matters will be discussed in camera.

5. A specific page on the At-Large Website will display the organigram which will be regularly updated with regards to current Working Groups and appointees to various roles that are allocated by the vote of the ALAC.

6. Roles and responsibilities of the different levels of leadership within At-Large will be more clearly defined on a page set aside for this purpose on the website, and available to all.

7. Staff will be assigned to the steps #5 and #6 as per Implementation Task #1 which is related to At-Large Wikis and the Website, and the work of At-Large.. 

Continuous Improvement(s)Staff will update the wiki spaces related to this task regularly as any changes are made to the ALAC and to other personnel and working groups or other activities related to the charts and other information
Metrics

Any changes to personnel involvement will be recorded on the wiki spaces within one month of the change taking place

How long will it take to implement this plan?Implementation will take place immediately after the Barcelona meeting. Once loaded onto the website, it will be updated as required. Ongoing



ARIWG Prioritization and Dependencies - Issue#5

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.
Prioritization3.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?
Anticipated resource requirements (FTEs, tools)
Expected budget implications

Proposed implementation steps:


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

(MH) This task is related to Activity Item #8

Issue #9

Lead: John Laprise


Need for increased At-Large Community awareness and staff training regarding the use of social media.
Final Proposal as approved by the Board
The ALAC will request additional staff skill development in the area of social media, and to work cooperatively with ICANN Communications social media specialists.
Prioritization2.2.2 (Medium needs; medium risk; #2 priority group)
ARIWG comments

(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

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?

...

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.

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

(MH) This item also highlights how we can use what communication channels are available to disseminate important messages out to the wider public as well as the At-Large Community.

Some collaboration with the social media items (#8 & #9) but also with the task teams working on areas #5, #12. #13 and #15 would be appropriate, to enhance the work that is being done in O&E

As well as some metrics to assess the effectiveness of any communication channels that we implement.

ARIWG commentsStatus 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?

...

Cloak

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

Issue #11

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.
Final Proposal as approved by the Board

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.

Prioritization3.3.1. (High resource needs; High risk; #1 priority)
ARIWG commentsStatus of improvement effort / staff leadActivities, if any, on which implementation is dependent, or that are dependent on implementation of this recommendation

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

...