Page History

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.

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

(ED) Maureen: Do you mean outcomes of this item #11 when you say "outcome of this implementation plan? (—ED)

(Satish) I have the following submissions about ATLAS and Regional Meetings:

• Currently, ATLAS and Regional Meetings are independent events, with no direct feedback loops between them
• It would be good to co-

• ordinate the five regional meetings/GAs with ATLAS meetings so that there is uniformity of (a) vision; (b) goals; (c) activities; (d) metrics; and (e) evaluation of outcomes. ATLAS and GAs should be viewed effectively as parts of the same process and not just as independent, unconnected events.
• In particular, ATLAS meetings should consider specific inputs/questions arising out of Regional Meetings as well as regional processes, and provide guidance back to the RALOs on the consensus arrived at on these issues.
• There appears to be some amount of fatigue at the level of ALSes in multiple RALOs. The combination of ATLAS and GAs, together with other activities, should consider the key issues of how to reactivate ALSes and integrate them–together with individual members–into all At-Large processes.

(ED) Dependent on Item #16 - Metrics. These are necesarry to define who participates or not in these meetings (ATLAS or General Assemblies). In addition, Metrics are used to determine how sucesfull/un-sucessfull the event was. (—ED)

(HR) Tie metrics to review aims - policy participation, comms metrics. Maybe develop metrics for regional participation in ICANN (Policy, technical, outreach) with merics for GAs as well as ATLAS meetings

(ED) Additional budget for General Assemblies and ATLAS (every 5 years) are needed. A multi year budget allocation should be prepared and included in ICANN budget core. (—ED)

(HR) agree - GAs will have own themes but may be commonalities between GAs

(ED)

1. Revise past ATLAS and General Assemblies results.

2. Verify recomendations and lesson learned to improve next iterations

3. Assemble a Working Group to manage the coordination of these events

4. Determine timelines, budget requirements, outcome expectations and metrics for each event

(—ED)(HR - agree)

(ED)

1. Continue to revise metrics to align expectations fro each event

2. Use leasson learned from previous events to continue improving outcomes

3. Continue to outreach to new volunteer to work in the coordination/excution of these events to learn how things are done and to start collaborating with other ICANN departments.

(---ED)