Historical Resolution Tracking Feature » Acceptance of At-Large2 Review Final Implementation Report
Important note: The explanatory text provided through this database (including the summary, implementation actions, identification of related resolutions, and additional information) is an interpretation or an explanation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanations or interpretations modify or override the Resolutions themselves. Resolutions can only be modified through further act of the ICANN Board.
Acceptance of At-Large2 Review Final Implementation Report
Whereas, on 27 January 2019 the Board accepted the At-Large Review Implementation Plan and directed the At-Large Advisory Committee to provide the Board with regular reporting on the implementation efforts.
Whereas, the At-Large Review Implementation Working Group , with At-Large Advisory Committee approval and oversight, provided the Board via the OEC with semi-annual updates on the progress of implementation efforts until such time that the implementation efforts conclude.
Whereas, the At-Large Review Implementation Working Group submitted a Final Implementation Report to the OEC on 30 June 2020, detailing the completion of implementation of the recommendations arising out of the second At-Large Review and documenting that two recommendations are not yet fully implemented.
Whereas, the OEC acknowledged that the outstanding steps of the At-Large's implementation work have dependencies beyond the control of the At-Large and/or contain aspects of continuous improvements.
Whereas, the OEC recommends that the Board accept the At-Large2 Review final implementation report issued by the At-Large Review Implementation Working Group and approved by the At-Large Advisory Committee on 23 June 2020, thereby completing the second At-Large Review.
Whereas the OEC recommends that the Board request that the ALAC provide a written or oral update to the OEC by 31 December 2020 on the two recommendations for which implementation is not yet fully completed and, if not completed by then, every six months thereafter until all implementation is completed.
Resolved (2020.09.10.08), the Board accepts the At-Large2 Review final implementation report of the second At-Large Review issued by the At-Large Review Implementation Working Group, which marks the completion of this organizational review in accordance with Bylaws Article 4 Section 4.4. The Board encourages the At-Large Advisory Committee to continue monitoring the impact of the implementation of the recommendations from the second Review of the ALAC as part of its continuous improvement process.
Resolved (2020.09.10.09), the Board acknowledges the At-Large Review Implementation Working Group's implementation work aimed at improving the At-Large's effectiveness, transparency, and accountability, in line with the proposed timeline as set out in the adopted At-Large2 Review Implementation Plan.
Resolved (2020.09.10.10), the Board requests the At-Large Advisory Committee to provide the OEC with a written or oral progress update on the two remaining issues "Member Engagement and Criteria" and "Absence of consistent performance metrics" by 31 December 2020. In the event that implementation is not completed by 31 December 2020, the ALAC shall continue to provide such updates to the OEC on a six-monthly basis until such time that the implementation efforts conclude.
Why is the Board addressing the issue?
ICANN organizes independent reviews of its supporting organizations and advisory committees as prescribed in Article 4 Section 4.4 of the ICANN Bylaws, to ensure ICANN's multistakeholder model remains transparent and accountable, and to improve its performance.
This action completes the second At-Large Review and is based on the final implementation report, as adopted by the At-Large Advisory Committee (ALAC), the final report of the independent examiner, ITEMS International, as well as the At-Large Review Implementation Working Group's (ARIWG) assessment of the recommendations as adopted by the ALAC. Following the assessment of all pertinent documents and community feedback by the Organizational Effectiveness Committee (OEC), the Board is now in a position to consider and accept the Final Report.
The Board, with recommendation from the OEC, considered all relevant documents, including the Final Report, the At-Large Review Working Party Feasibility Assessment and Prioritization of Recommendations by Independent Examiner ("Feasibility Assessment"), and accepted the final report issued by the independent examiner on 23 June 2018. The Board adopted the Feasibility Assessment. Additionally, the Board directed the ALAC to: draft an implementation plan for the adopted recommendations with a realistic timeline that took into account the continuously high community workload and consideration of the prioritization proposed by the ARIWG; publish the plan no later than six (6) months after the Board's adoption of the Feasibility Assessment; ensure that the implementation plan includes definitions of desired outcomes and a way to measure current state as well as progress toward the desired outcome; and report back regularly to the Board on its implementation progress. On 27 January 2019, the Board accepted the Implementation Plan provided by the ARIWG and approved by the ALAC on 27 November 2018, and directed the ARIWG to provide semi-annual updates to the OEC until such time that the implementation efforts have concluded.
The ARIWG submitted its final implementation report to the OEC on 30 June 2020. The report showed that implementation of all items was complete with the exception of two areas: "Member Engagement and Criteria" [issue ID #2] and "Absence of consistent performance metrics" [issue ID #16]. On issue ID #2, the cross-regional At-Large Structure (ALS) Mobilization Working Party has yet to complete "reviewing the entire body of rules and processes associated with ALSes. Once finalized, these will need to be reviewed by the RALOs, ratified by the ALAC, and then submitted for Board approval." A Bylaws change may also be required to "clarify the changes being made in respect to ALSes". On issue ID#16, the ALAC is awaiting the "implementation of a CRM tool throughout ICANN org". Membership data will then be transferred to that tool to help professionalize the At-Large member management, including the effective capturing of relevant metrics.
The OEC considered these issues during its deliberation of the final implementation report. The OEC noted that some aspects of the outstanding implementation have dependencies that are beyond the control of the At-Large or contain aspects of continuous improvements. Therefore, the OEC recommended it is appropriate for the Board to accept the final implementation report, formally concluding the second At-Large organizational review. The OEC also recommended to the Board that it request the At-Large report to the OEC on the outstanding implementation steps, ensuring accountability over the conclusion of the entire implementation process.
The Board agreed with the OEC's recommendations.
What is the proposal being considered?
The proposal being considered is that the Board accepts the Final Report of the ARIWG in order to conclude the second organizational review of the At-Large. The proposal also includes that the Board request the ALAC to provide progress updates to the OEC on the outstanding implementation steps on two recommendations.
Which stakeholders or others were consulted?
The Board, through the OEC, consulted with the ARIWG, who was responsible for the implementation, and monitored the progress of the review as well as the progress of the implementation of review recommendations.
What concerns, or issues were raised by the community?
The implementation work conducted by the ALAC followed its standard best practices to ensure transparency and accountability. No concerns were voiced by the community.
What significant materials did the Board review?
The Board reviewed relevant Bylaws sections, Organizational Review Process documentation, At-Large2 Review Implementation Plan, and the ARIWG reports to the Board.
What factors did the Board find to be significant?
The Board found several factors to be significant, contributing to the effective completion of the implementation work:
Convening a dedicated group that oversees the implementation of Board-accepted recommendations.
Adherence to the implementation plan that included a timeline for the implementation, definition of desired outcomes, as well as ways to measure current state as well as progress toward the desired outcome.
Timely reporting on the progress of implementation.
The ARIWG reported in the final implementation report that two recommendations are not yet fully implemented. Following recommendations by the OEC, the Board noted that some aspects of the outstanding implementation have dependencies that are beyond the control of the At-Large and acknowledged that some of the remaining implementation steps are part of ongoing continuous improvements efforts. Based on this, the Board accepted the Final Report, formally concluding the second At-Large organizational review, while requesting an update on the outstanding implementation steps by 31 December 2020, and, if not completed by then, every six months thereafter, until the implementation is completed.
Are there positive or negative community impacts?
This Board action is expected to have a positive impact on the community by acknowledging and highlighting an effective completion of implementation of At-Large2 Review Recommendations.
Are there fiscal impacts or ramifications on ICANN (strategic plan, operating plan, budget); the community; and/or the public?
This Board action is anticipated to have no additional fiscal impact to that noted in the Board's acceptance of the At-Large Review Implementation Plan. The ramifications of this resolution on the ICANN organization, the community and the public are anticipated to be positive, as this Board action signifies an important milestone for organizational reviews.
Are there any security, stability or resiliency issues relating to the DNS?
This Board action is not expected to have a direct effect on security, stability or resiliency issues relating to the DNS.
How is this action within ICANN's mission and what is the public interest served in this action?
The Board's action is consistent with ICANN's commitment pursuant to section 4.1 of the Bylaws to ensure ICANN's multistakeholder model remains transparent and accountable, and to improve the performance of its supporting organizations and advisory committees. This action will serve the public interest by fulfilling ICANN's commitment to maintaining and improving its accountability and transparency.
Is public comment required prior to Board action?
No public comment is required.