First GNSO Organizational Review

The First GNSO Organizational Review (GNSO1) was initiated in 2008, with implementation of improvements continuing throughout 2012.

Background

Article 4.4 of the ICANN Bylaws requires periodic review of all supporting organizations and advisory committees, as well as the Nominating Committee. The bylaws state three objectives for the review:

1. to determine whether that organization, council or committee has a continuing purpose in the ICANN structure;
2. if so, whether any change in structure or operations is desirable to improve its effectiveness; and
3. whether that organization, council or committee is accountable to its constituencies, stakeholder groups, organizations and other stakeholders.

Organizational reviews are conducted by independent examiners, selected through a competitive bidding process. The independent examiner works in consultation with a working group assembled by the board, who will act as implementation shepherds once the final report of the independent examiner is submitted. The review parameters are set by the ICANN Board, and those parameters as well as other avenues of inquiry are typically included in the request for proposals (RFP) for independent examiners. Reviews can take anywhere from three to five years to complete. The full review process includes seven phases, including the implementation of recommendations from the review. Reviews must be conducted at least every five years, measuring from the date that the final report of the previous review was accepted by the ICANN Board. The Generic Names Supporting Organization (GNSO) is one of the supporting organizations subject to Article 4.4 review.

It is notable that the GNSO1 review began with a review of reviews: the GNSO had previously been reviewed by the London School of Economics Public Policy Group in 2006, and by Patrick Sharry in 2004. These prior reviews were incorporated into the work process of the GNSO1 Review working group.

Initiation

The board assembled a GNSO Review Working Group of the Board Governance Committee, and approved its charter, in March 2007 The working group was charged to answer the traditional Article 4.4 (as amended at the time) questions: does the GNSO have a continuing purpose within the ICANN structure; and if so, what can be done to improve its effectiveness? The charter document goes further, tasking the working group to develop a "comprehensive proposal" to improve the effectiveness of the GNSO.

Review of Prior Assessments

The working group focused on three previous reviews in its information-gathering process: the Patrick Sharry review of 2004; the GNSO's own self-assessment, performed as part of the preliminary work to commission Sharry's report; and the review prepared by the London School of Economics Public Policy Group in 2006.

GNSO Self-Assessment

The GNSO, in preparing the Terms of Reference for the its 2004 review, conducted a self-review process. The self-review described a number of policy development successes, including updates to the transfer policy, WHOIS, and deletion policy. The GNSO made three categories of recommendations:

1. Recommendations re: the ICANN Bylaws: maintain GNSO Council compostion of 3 representatives from each constituency; amend the policy development process bylaws to state that PDP timelines are flexible, and may be set and revised by the GNSO Council to reflect the work being considered and status updates from the working group.
2. Recommendations re: staff support: multiple requests for staff support around the policy development process, task forces, and work of the GNSO Council; make legal staff available to the GNSO Council, task forces, and subcommittees, and in particular for review of policy recommendations and other policy statement for compliance with bylaws and contractual obligations; and create monitoring, compliance, and complaint policies related to gTLDs.
3. Actions required of the GNSO Council: Ensure that legal advice from ICANN staff is in writing and allow registrars or registries to submit the opinion of their counsel; ensure that policies are ready to be implemented upon approval; establish key metrics for measuring the success of a given party; encourage community-wide participation in the policy development process.

2004 Review by Patrick Sharry

Sharry, a strategic planning and change management consultant, reviewed the GNSO Council, without reference to the self-assessment described above, using interviews with GNSO Council members and others, as well as a review of policy and process documentation prepared by the GNSO for that purpose. The report reached many of the same conclusions as the GNSO's self-assessment. Sharry found, in particular, that ICANN staff support of GNSO activities fell "well short of the standards outlined in the bylaws." The review also found substantial gaps between the adoption of policy proposals and the implementation of those policies, with minimal attention devoted to compliance or tracking of the success of the implementation. Sharry provided recommendations for improving the GNSO's core functions, but was also complementary of both the Council's commitment and dedication, as well as its leadership.

As part of its background documentation for the broader community, the improvements implementation team summarized the similarities between the GNSO's self assessment and Sharry's report:

These reviews shared a common approach in certain respects: (i) allowing for more flexibility in the PDP process; (ii) ensuring strong Staff support for policy development; and (iii) developing better mechanisms for public participation and discussion.

Generic Names Supporting Organization. Develops and recommends to the Board substantive policies relating to generic top-level domains and other responsibilities set forth in the Bylaws (ICANN Bylaws).

Policy Development Process