Continuous Improvement Program

From ICANNWiki
Jump to navigation Jump to search

The Continuous Improvement Program (CIP) is a proposed transformation organizational review by the Third Accountability and Transparency Review (ATRT3) Recommendation 3.6. ICANN is tasked with collaborating with each Supporting Organization (SO), Advisory Committee (AC), their stakeholder groups, and the Nominating Committee (NomCom) to establish this program.

Objectives

  • Develop an annual satisfaction survey and a regular assessment.
  • Publish summaries of continuous improvement at least every three years.

Development Phases

  • CIP Framework Development: Estimated to take 12 months, concluding by December 2024.
  • CIP Assessment Period 1: Expected to begin in 2024 and end in 2027.
  • CIP Assessment Period 2: Projected to start in 2028 and conclude at the end of 2030.

Holistic Review Implementation

In tandem with the CIP, ICANN is working on ATRT3 Recommendation 3.5, which calls for a Holistic Review. Both the CIP and Holistic Review will start as pilot programs, with CIP assessment results informing the Pilot Holistic Review.

CIP Community Coordination Group (CIP-CCG)

Purpose

  • Serve as a forum to exchange best practices, lessons learned, and share progress on continuous improvement activities.
  • Collaborate on community-wide implementation of ATRT3 Recommendation 3.6.

Responsibilities

  • Develop a shared understanding of Continuous Improvement.
  • Identify existing continuous improvement activities.
  • Agree on methodologies for effective continuous improvement programs.
  • Formulate a CIP Framework for implementation.

Community Involvement

  • Each community group, including NomCom, is requested to appoint a representative to the CIP-CCG.
  • Initial meeting planned for December 2023.

Functions

  • Experience-sharing and information forum, not a decision-making body.
  • May present joint proposals for discussion by the SOAC Chairs.

CIP-CCG Membership

SO/AC Affiliation Name Membership Level
At-Large Advisory Committee (ALAC) Cheryl Langdon-Orr Representative
Tommi Karttaavi Resignation Notice
Bukola Oronti Alternate
Governmental Advisory Committee (GAC) Tracy Hackshaw Representative
Root Server System Advisory Committee (RSSAC) Naveed Bin Rais Representative
Erum Welling Alternate
Generic Names Supporting Organization (GNSO) Council Damon Ashcraft Representative
Manju Chen Alternate
Nominating Committee (NomCom) Tijani Ben Jemaa Representative
African Regional At-Large Organization (AFRALO) Bram Fudzulani Representative
Chokri Ben Romdhane Alternate
Asian, Australasian, and Pacific Islands Regional At-Large Organization (APRALO) Amrita Choudhury Representative
Justine Chew Alternate
European Regional At-Large Organization (EURALO) Sebastien Bachollet Representative
Ricardo Holmquist Resignation Notice
Natalia Filina Alternate
Latin American and Caribbean Islands Regional At-Large Organization (LACRALO) Carlos Aguirre Representative
Christelle Vaval Alternate
Harold Arcos Temporary Alternate (June - August 2024)
North American Regional At-Large Organization (NARALO) Alan Greenberg Representative
Bill Jouris Alternate
GNSO Not-for-Profit Operational Concerns Constituency (NPOC) Caleb Ogundele Representative
Wisdom Donkor Alternate
GNSO Business Constituency (BC) Nenad Orlic Representative
GNSO ISPs and Connectivity Providers Constituency (ISPCP) Santanu Acharya Representative
GNSO gTLD Registries Stakeholder Group (RySG) Chris Disspain Representative
GNSO Intellectual Property Constituency (IPC) Lori Schulman Representative
Marco Martinelli Alternate
Security and Stability Advisory Committee (SSAC) Jeff Bedser Representative
Country Code Names Supporting Organization (ccNSO) Sean Copeland Representative
Irina Danelia Alternate
GNSO Noncommercial Users Constituency (NCUC) Benjamin Akinmoyeje Representative
Liubomir Nikiforov Alternate
GNSO Registrar Stakeholder Group (RrSG) Owen Smigelski Representative
Tom Barrett Alternate

Implementation and Coordination

The implementation of ATRT3 Recommendation 3.6 requires efforts by individual community groups and collective coordination. ICANN has put together terms of reference detailing the expected roles and responsibilities for the CIP Community Coordination Group. The community's implementation work will necessitate collaboration across different groups to address specific items that require coordinated effort.