Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »


#RecommendationRequestSourceStatusDate Requested:Date DeliveredPurpose of the request
16Various recommendations apply. Staff to assemble a mapping of recommendations to relevant Operating Procedures.#71(info) Request received

 


This will serve as a starting point to assist NomComRIWG with plans for future proposed modifications of the Operating Procedures, based on the implementation work.
15N/AICANN70 Prep week session: Does the NomComRIWG have the ability to conduct multiple choice questions during the webinar presentation? What version of Zoom will be using, same buttons as on plenary call?#70(tick) Request completed. The Zoom room for the webinar will be the same as for NomComRIWG plenary calls. It will be possible to conduct multiple choice questions.

 

 

Improve interaction with the audience during the webinar.
14

Rec. 19: ICANN staff and the recruiting consultant, along with NomCom members, should leverage the detailed job description and desired competencies and experience to develop a marketing plan to better target prospective candidates. Consult with the wider ICANN community what additional non-confidential, non-identifiable data points should be collected and published

Rec. 23Consult with the wider ICANN community what additional non-confidential, non-identifiable data points should be collected and published

Obtain statistics on conversion from viewing job description to application, this would be useful feedback on the success of processes undertaken and how recruitment is done. #70(info) Request received

 



13Rec. 23Consult with the wider ICANN community what additional non-confidential, non-identifiable data points should be collected and publishedConfirm what diversity means out of Work Stream 2, reference the particular categories that were identified part of that work track and the metrics associated with the key diversity categories. NomComRIWG wants to cross-reference to the definitive set of categories and note that those additional metrics should be measured against that established criteria.#70(info) Request received 

 



12Rec. 24An empowered body of current and former NomCom members should be formed to ensure greater continuity across NomCom’s, and in particular, to recommend and assist in implementing improvements to NomCom operations.Annual Reports: NomCom Support Staff to confirm whether publishing annual reports is a standard practice, and when was the last one to be submitted.#69(info) Request submitted 

 



11Rec. 24An empowered body of current and former NomCom members should be formed to ensure greater continuity across NomCom’s, and in particular, to recommend and assist in implementing improvements to NomCom operations.Request to ICANN org to create a sandbox where NomComRIWG can start building a future parent page portal to link all NomComs across years and help institutional memory with a collection of links and documents classified by year, and where the standing committee work can be seen. #69(info) Request submitted 

 



10Rec. 25Improve NomCom selection decisions by assessing the performance and needs of all bodies receiving NomCom appointees.

Request to get a blank copy of the Board's self-assessment template

#68(info) Request submitted 

 



9Rec. 16Implement and codify a system for providing feedback to the NomCom regarding the contributions and participation of members up for re-appointment by the NomCom.

Request to ask NomCom support staff if they are aware of any questions generated in the recent past by the NomCom to the Board regarding feedback on re-applying NomCom appointees

#68(info) Request submitted 

 



8Rec. 13Publish a “Process Diagram” and codify key elements of the NomCom process. Each year, the NomCom should be required to highlight and explain process changes to the ICANN community in an open session.

Develop process maps for:

  • ICANN staff tasks to support the NomCom 
  • Election of NomCom members
  • Rec.1: Job Description and Appointment Process
  • Interactions with consultants
  • Interactions with candidates
  • Interactions with appointing bodies
  • Interactions with receiving bodies
  • Rec 2,3: Setting up and delivering trainings to the NomCom
  • Rec. 11, 12: Input on NomCom budget and staffing resources (includes. Standing Committee and NomCom leadership input)
#67(info) In Progress - Per meeting #69 action item, shared latest version of the NomCom Lucid chart with NomCom support staff for review and to add any milestones that they believe are missing.

 



7Rec. 13Publish a “Process Diagram” and codify key elements of the NomCom process. Each year, the NomCom should be required to highlight and explain process changes to the ICANN community in an open session.

Creation of an extensive document repository to help with the institutional memory of the NomCom

#67(info) Request submitted 

 



6Rec. 21The NomCom should use a standardized tool to evaluate and prioritize candidates, based on desired competencies and experience as determined annually. This tool will not replace qualitative assessments of candidates.

Schedule a discussion with HR to find out if they could suggest some assessment tools

#67(info) Request submitted 

 



5Rec. 13Publish a “Process Diagram” and codify key elements of the NomCom process. Each year, the NomCom should be required to highlight and explain process changes to the ICANN community in an open session.

Request to conduct an interview with ICANN NomCom staff.  To be thorough, let's follow a bottoms-up approach of identifying the interactions that NomCom staff have with the following:

For the past 3 years, please describe your Interactions with the following departments and bodies:

  1. ICANN Legal
  2. ICANN Finance Department
  3. ICANN Travel Department
  4. ICANN Human Resources
  5. ICANN IT Department
  6. Any other ICANN Department or staff not included above
  7. with the ICANN Board (some overlap with the above)
  8. with SOs/ACs that appoint members to the NomCom
  9. with receiving bodies that receive appointees from the NomCom
  10. with external consultants (i.e. training, recruitment, evaluation)
  11. with NomCom Candidates
  12. with NomCom Leadership
  13. with NomCom rank-and-file
email

(info) Request submitted 

Plenary call #69 - upon discussion with NomCom Support Staff, decision reached to have them review the existing lucidchart and add any steps missing in the process map. 

 


The NomComRIWG would like to interview NomCom staff understand how they work today and make it their baseline to start implementing recommendation 13. The end goal is to prepare a predictable model (process map) for incoming and serving nomcom members to understand how these communications run. 
4N/A

Second version of draft Standing Committee Charter; and second version of Introduction to the Proposed Bylaw Changes and Transition Article submitted for ICANN org Legal Department review. LINK

#63

(info) Standing Committee Charter currently under ICANN org Legal Department review.

(tick) ICANN org Legal Department provided comments on Proposed Bylaws Changes

 


NomComRIWG wants both documents to be forwarded to the OEC for their review and input.
3Rec. 12NomCom leadership should have input on the NomCom budget and staffing resources.

Schedule a meeting to receive feedback from Finance department on their suggestion and mechanism for implementing this recommendation.

#63(info) Request submitted 

 



2

Rec.11: The senior staff member supporting NomCom should be accountable to and report to the office of the CEO.

Schedule a meeting in January 2021 with the office of the CEO to receive feedback on how they would like to implement recommendation 11.

#63(info) Request submitted 

 



1N/ASubmit Introduction to Proposed Bylaws Changes for ICANN org Legal Department input.email(tick) ICANN org Legal Department provided comments for the working group to review.

 

 

NomComRIWG wants ICANN org legal department input on amendments.
  • No labels