Hi all, During today’s call, I noted that there have been some discussions on the list and in Hyderabad but not sure if the issue has been dropped or settled. I raised my concern over this newly created role reporting to ICANN’s General Counsel. My concern is twofold: potential conflict of interest and risks associated with concentration of power. I advocated for a separate Compliance & Ethics office be created within ICANN and would welcome thoughts and feedback from this group. There is no shortage of debate and diverse views on whether legal and compliance functions should be separate but thought this article (or the excerpt) might be of interest. https://globalcompliancenews.com/independence-day-the-separate-and-equal-com... Moreover, a joint Society of Corporate Compliance and Ethics (“SCCE”) and NYSE Governance Services survey released in September 2014 found that only 8% of the 249 organizations surveyed placed overall responsibility for the ethics and compliance program with the general counsel or chief legal officer, while 56% placed it with a compliance and/or ethics officer.[4] Among the entities surveyed, only 18% of the individuals responsible for compliance reported to the general counsel, while 38% reported to the CEO, and 19% to the board of directors. Accordingly, well over half of the entities surveyed maintain compliance departments separate from, and certainly not under the direct control of, the general counsel. An annual benchmarking survey conducted by Deloitte and Compliance Week reveals a similar trend. Of the 364 respondents participating in their 2015 Compliance Trends Survey, 59% reported having a stand-alone CCO, representing a 9% increase from the survey’s 2014 findings and a 22% increase from the 2013 findings. Additionally, in 57% of the participant companies, the CCO reports directly to the CEO or board of directors. Kind regards, Pam Little From: accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org] On Behalf Of MSSI Secretariat Sent: Thursday, January 05, 2017 5:31 PM To: ws2-staff_acct@icann.org Cc: CCWG Accountability Subject: [CCWG-ACCT] Notes, recordings, transcript for WS2 Staff Accountability Subgroup Meeting #6_ 05JAN17 Hello all, The notes, recordings and transcripts for CCWG Accountability WS2 Staff Accountability Subgroup Meeting #6 – 05 January 2017 will be available here: https://community.icann.org/x/wp3DAw A copy of the notes may be found below. Thank you. Kind Regards, Yvette Guigneaux Multi-Stakeholder & Strategic Initiative Assistant ICANN | Internet Corporation for Assigned Names & Numbers 12025 Waterfront Drive, Playa Vista, CA 90094 yvette.guigneaux@icann.org | www.icann.org[icann.org] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DgMGaQ&...> _____ NOTES 1. Meeting start items - review of agenda and other administrative items 2. Review and discussion of responses to Questions from ICANN - noted that some of the responses to the questions may lead to recommendations for the group to consider. - need to provide some responses to the quetions posed in the response noted documents available to the staff to describe codes and they are posted on ICANN.org web site, wondered if those documents are available for the community to review/read, assumption that they are not currently available for the community - are they private to the employess and not visible to the community? - noted the need for further review of the response - concerns raised that ICANN has a lot of process and documents in place, but who is looking into the practice of the process and what are the consequences of not following the process in place, example what happens when CEO exceeds power delegated to him, noted are things as good as ICANN would like us to believe - concerns on the devils in the details Action (Karen): see if it would be possible to have a follow-up discussion with HR - concerns expressed on the Compliance Officer being under the General Counsel's office. Action (Pam Little): send email to the list with suggestions on the Compliance Officer Questions for follow-up: - Are the staff documents/codes noted in the response privet to staff only or are they public for community review? 3. Discussion of CCWG Staff Accountability working draft draft 1.2 (Document A) - document seems to be longer than expected. - document is meant to look at the relationship between the Board, the community and the staff. - there might be perceived conflicts of interest. - there appears to be different expectations from the community of the roles of staff, board and community. - there is a basic gap between what is said and what happens in reality. - not sure what was descriptive and what was normative in this document. - concern over the isolation of the board, and isolation of the 3 groups from each other. - document is a first draft, and needs more work from the group. - competing interests within the ICANN community makes it challenging for staff to be held accountable Action (subgroup): review and edit the document by the middle of next week (Wednesday, Jan 11), add comments but also add drafting changes in suggestion mode. Jordan and Klaus will then edit the document before the next call. For document B: - hiring process should be more open 4. Schedule check - Goal is to try and close document A by the next meeting - Avri will be working on document B next week, and will send the URL to the group - sticking to the schedule discussed in the last call: · Call 19 January (19h UTC): Test agreed changes to draft Document A. Work through draft Document B · Call 2 February (13h UTC): Test agreed changes to draft Document B. Finalise Document A for CCWG Plenary. Can send A to CCWG Plenary. · Call 16 February (05h UTC): Finalise Document B for CCWG Plenary. Both Documents to CCWG Plenary · Call 2 March (19h UTC): (if necessary - incorporate feedback from Plenary?) · Face to Face Plenary - 10 March 5. AOB - Concerns raised over the fact that very limited group of people are participating. We can try to get more people involved through the plenary. -Suggestion to get emails of participants and send the URL link to participants.