- Ws2-staff_acct - lists.icann.org

Links on Staff Accountability Wiki
by Jeff Neuman Feb. 8, 2017

Feb. 8, 2017

All, The Wiki page for WS2 Staff Accountability are a little messed up. Almost all of the links point to ICANN's Delegation of Authority Guidelines as opposed to Questions from Staff awaiting responses, etc.) Jeffrey J. Neuman Senior Vice President |Valideus USA | Com Laude USA 1751 Pinnacle Drive, Suite 600 Mclean, VA 22102, United States E: jeff.neuman(a)valideus.com<mailto:jeff.neuman@valideus.com> or jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com> T: +1.703.635.7514 M: +1.202.549.5079 @Jintlaw

1 0

Fwd: Response for WS2 Sub Group on Staff Accountability.
by avri doria Feb. 6, 2017

Feb. 6, 2017

-------- Forwarded Message -------- Subject: Response for WS2 Sub Group on Staff Accountability. Date: Sat, 4 Feb 2017 16:47:37 +0000 From: Karen Mulberry <karen.mulberry(a)icann.org> To: avri doria <avri(a)acm.org>, Jordan Carter <jordan(a)internetnz.net.nz>, ws2-diversity(a)icann.org <ws2-diversity(a)icann.org> CC: León Felipe Sánchez Ambía <leonfelipe(a)sanchez.mx>, Mathieu Weill <mathieu.weill(a)afnic.fr>, Thomas Rickert (thomas(a)rickert.net) <thomas(a)rickert.net> Dear CCWG Accountability WS2 Subgroup on Staff Accountability, Please find attached here policies which relate to staff’s accountability. These will be posted shortly on _ICANN.org_ for broader community access. These policies are: · Anonymous Hotline · Confidentiality · Conflict of Interest · Employee Conduct & Work Rules · Equal Employment · Fraud · Open Door · Outside Business Interests · Prohibition of Workplace Harassment The ICANN CEO is responsible at the overall level for the ICANN organization staff member’s accountability, as noted in prior responses as well. In relation to staff accountability, there are many ways that ICANN holds staff accountable to these employment policies. Adherence to these policies is a fundamental expectation underlying the work of every ICANN Organization Staff member. As to adherence, ICANN Organization’s management, led by the CEO, is responsible for managing all staff members’ adherence to policies. The policies themselves set out reporting chains, and investigatory processes that are each followed. There are multiple ways to ensure adherence and it is through the management chain, and well-established Human Resource practices, that potential violations from the policies are reported and investigated. The Complaints Officer, once established, could serve an important role in identifying violations of employment policies. Under ICANN’s new Bylaws, the community’s ability to directly hold staff accountable are also enhanced, through the availability of a broadened IRP and Reconsideration. While the Office of the Ombudsman does not have jurisdiction over HR matters, community complaints of unfairness of staff members can be taken to the Ombudsman. In addition, as the policies also identify issues that could result in violations of laws, the applicable legal systems and California Attorney General also could reach ICANN organization staff member conduct. ICANN is governed by California laws and regulations, U.S. Federal laws and regulations (including laws related to ICANN’s tax exempt status), law and regulations of other places that it has employees, and is guided by best practices under those schemes. All staff members are regularly informed of staff policies through the annual confirmation process, training programs and intranet blogs, as well as at any point when an issue or question is raised that addresses one of the policies. Employment policies are always available to staff through ICANN’s intranet. We hope the information is helpful. The point person for future questions on human resources is Diane Schroeder, who is happy to participate on sub-group team calls if requested. /Karen Mulberry/ Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

Re: [Ws2-staff_acct] [Ws2-diversity] Response for WS2 Sub Group on Staff Accountability.
by Pam Little Feb. 4, 2017

Feb. 4, 2017

It seems this thread has been mis-posted to ws2-diversity(a)icann.org so I am posting it to ws2-staff_acct(a)icann.org. I believe the "Anonymous Hotline" is meant to work as a whistle-blower policy. Maybe a name change is in order? Kind regards, Pam -----Original Message----- From: ws2-diversity-bounces(a)icann.org [mailto:ws2-diversity-bounces@icann.org] On Behalf Of Lousewies Vanderlaan Sent: Sunday, February 05, 2017 7:15 AM To: Karen Mulberry Cc: ws2-diversity(a)icann.org; Thomas Rickert (thomas(a)rickert.net) Subject: Re: [Ws2-diversity] Response for WS2 Sub Group on Staff Accountability. Does this include our Whisteblower policy? Sent from my iPad > On 4 Feb 2017, at 08:47, Karen Mulberry <karen.mulberry(a)icann.org> wrote: > > Dear CCWG Accountability WS2 Subgroup on Staff Accountability, > > Please find attached here policies which relate to staff’s accountability. These will be posted shortly on ICANN.org for broader community access. > > These policies are: > · Anonymous Hotline > · Confidentiality > · Conflict of Interest > · Employee Conduct & Work Rules > · Equal Employment > · Fraud > · Open Door > · Outside Business Interests > · Prohibition of Workplace Harassment > > The ICANN CEO is responsible at the overall level for the ICANN organization staff member’s accountability, as noted in prior responses as well. In relation to staff accountability, there are many ways that ICANN holds staff accountable to these employment policies. Adherence to these policies is a fundamental expectation underlying the work of every ICANN Organization Staff member. > > As to adherence, ICANN Organization’s management, led by the CEO, is responsible for managing all staff members’ adherence to policies. The policies themselves set out reporting chains, and investigatory processes that are each followed. There are multiple ways to ensure adherence and it is through the management chain, and well-established Human Resource practices, that potential violations from the policies are reported and investigated. The Complaints Officer, once established, could serve an important role in identifying violations of employment policies. Under ICANN’s new Bylaws, the community’s ability to directly hold staff accountable are also enhanced, through the availability of a broadened IRP and Reconsideration. While the Office of the Ombudsman does not have jurisdiction over HR matters, community complaints of unfairness of staff members can be taken to the Ombudsman. > > In addition, as the policies also identify issues that could result in violations of laws, the applicable legal systems and California Attorney General also could reach ICANN organization staff member conduct. ICANN is governed by California laws and regulations, U.S. Federal laws and regulations (including laws related to ICANN’s tax exempt status), law and regulations of other places that it has employees, and is guided by best practices under those schemes. > > All staff members are regularly informed of staff policies through the annual confirmation process, training programs and intranet blogs, as well as at any point when an issue or question is raised that addresses one of the policies. Employment policies are always available to staff through ICANN’s intranet. > > We hope the information is helpful. The point person for future questions on human resources is Diane Schroeder, who is happy to participate on sub-group team calls if requested. > > Karen Mulberry > Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN > > <mime-attachment> > <Codes and Policies related to staff accountability.zip> _______________________________________________ Ws2-diversity mailing list Ws2-diversity(a)icann.org https://mm.icann.org/mailman/listinfo/ws2-diversity

1 0

Notes, recordings, transcript for WS2 Staff Accountability Subgroup Meeting #8_ 2 February 2017
by MSSI Secretariat Feb. 2, 2017

Feb. 2, 2017

Hello all, The notes, recordings and transcripts for CCWG Accountability WS2 Staff Accountability Subgroup Meeting #8 – 2 February 2017 will be available here: https://community.icann.org/x/MgC4Aw A copy of the notes may be found below. Thank you. With kind regards, Brenda Brewer, Projects & Operations Assistant Multistakeholder Strategy & Strategic Initiatives (MSSI) Internet Corporation for Assigned Names and Numbers (ICANN) Notes (including relevant portions of chat): 1. Intro: agenda review, attendance, SOI check Audio only: Jeff Neuman, Greg Shatan, George Sadowsky. Roll call will be taken from AC room. No SOI updates. 2. Update on working draft Document A version 1.3. Jordan is rapporteur on this document (main item at 16 Feb meeting) Document, open to comments and suggested edits, can be found at: https://docs.google.com/document/d/1wGRrJZ-i7WA0uYBIHaB5Q3ssqfRmbAcgHJwlQ6s… Marked up from previous version available for review: https://docs.google.com/document/d/1wXuZw-VFeMLT3B5UHLU_nY1SWyzp6-VLeVZF1FY… Very few people have edited the document so far. Document will be kept open on-line one more week, and will be reviewed by the subgroup during the next call, on Feb 16. 3. Detailed Discussion of Responses to Staff questions https://docs.google.com/document/d/1ELuw6i3mGAjnZBe0Vc_lraNQrWw5m_I6UyipEHa… • Avri: Answers have been mostly contributed by Klaus. Encourage others to contribute. Not sure if we have alignment between document A and the answers provided here. • Julf Helsingius: Yes, ICANN.org tends to promote ICANN, not the community • Jeff Neuman: FYI - The registries have some thoughts on Question 1 that we will be submitting. The registries have been in discussion with ICANN staff. There have been situations where ICANN has tried to push their views without going through the multistakeholder process. • Jeff: Why did ICANN respond to our questions with more questions? what is ICANN going to do with these answers? seems very defensive from ICANN to answer our questions with more questions. Does it mean they won't participate in these discussions unless we answer their questions? • Greg Shatan: this discussion shows the challenge of staff accountability. Difficult to balance out accountability and transparency and necessity to make business decision. • George Sadowsky: speaking as board liaison for this group. I am in LA, so I can try to better understand what is going on here and reach out to staff. • Phil Corwin: I haven't had the same experience but I don't represent contracted parties. I would like to see listed under question 1 a specific example, ie request for reconsideration filed in 2016. • Avri: there are many bilateral issues, I'd like to encourage people to voice them out. • George: are these isolated incidents? • Philip Corwin: At a certain point a series of isolated incidents constitutes a clear pattern of behavior experienced by a broad cross section of the community • Jeff Neuman: http://schd.ws/hosted_files/icann572016/a6/I57%20HYD_Sun06Nov2016-Board%20w… ,[schd.ws] starting on page 30 and continuing pretty much to the end we talk about the seemingly adversarial relationship between the contracted parties and the ICANN staff • Philip Corwin: In regard to question 3, perhaps we should ask staff to identify specific instances in which they have not been treated in a respectful manner, because I can't recall witnessing any. 4. Discussion/Seeking feedback on First Draft Document B Avri is rapporteur on this document https://docs.google.com/document/d/1UnkJuukv0px-CfIDgLrjdDZa2CpBvSahPvAXdYY… Avri: encouraging people to contribute to this document too. 5. Schedule check We have slipped on our schedule. Jordan and I need to recalibrate. 6. AOB

1 0

Reply to staff staff questions
by Klaus Stoll Feb. 1, 2017

Feb. 1, 2017

Dear working group members Greetings. Please find attached my first draft to reply to the staff questions. I wanted to just condense the text from text a but then thought it would be stupid to repeat everything. The key is that in the point of view of ICANN.org and its staff, the community role is now to support and aid ICANN.org and it's staff and not how it should be the other way round). I have decided to send you now what I have, otherwise I will write another 5 pages and my language. Hope it helps in one way or another Yours Klaus PS: Sorry I did not upload the text to the Google doc. I simply could not find it.

2 1

Notes, recordings, transcript for WS2 Staff Accountability Subgroup Meeting #7_19January 2017
by MSSI Secretariat Jan. 23, 2017

Jan. 23, 2017

Hello all, The notes, recordings and transcripts for CCWG Accountability WS2 Staff Accountability Subgroup Meeting #7 – 19 January 2017 will be available here: https://community.icann.org/x/xJ3DAw A copy of the action items and notes may be found below. Thank you. With kind regards, Brenda Brewer, Projects & Operations Assistant Multistakeholder Strategy & Strategic Initiatives (MSSI) Internet Corporation for Assigned Names and Numbers (ICANN) Action Items · Participants to read A and B document by EOB Monday and provide comments for drafting team- JC to send reminder to list. · Staff to provide answer to sub-group on access to documents by 27 January 2017. · Klaus Stoll to draft answers to Staff Questions for consideration by group by 27 Janaury 2017. Notes (11 participants at start of call) 1. Intro: agenda review, attendance, SOI check Jordan Carter: Avri Doria will not be able to join the call today. 2. Detailed discussion-seeking feedback on working draft Document A v 1.3Document, open to comments and suggested edits, Jordan Carter: JC,AD and KS have cleaned up the document from the 5th of January - still needs a lot of tidying up to get it to first reading. Asking participants to post comments on the clean version of the Google doc https://docs.google.com/document/d/1wGRrJZ-i7WA0uYBIHaB5Q3ssqfRmbAcgHJwlQ6s… Klaus Stoll: Would ask everyone to read the document and comment so we can go into a final editing. Jordan Carter: (presentation of the structure document). Klaus Stoll: The first three sections are a rehash of existing document - as such asking a reader to go through 6 pages of introduction - so maybe we could bring our recommendations more at the beginning could be better. Jordan Carter: If a good idea we should be clear about what is standard and what is editorial from us. Anything on the Role Descriptions? (none). Anything on relationships? Pam Little: 1.3.1 Root or just the DNS? Jordan Carter: we should use standard language. Jeff Neuman: Community does not implement policy - is this correct and we should note the gNSO work on this. Jordan Carter: please share that link. So the language is not quite right yet. Back to Relationships section 2. Jeff Neuman: I will try to find a good reference Jordan Carter: Section 3 - any comments. Pam Little: second para - ending - "some important differences" could be removed as we are talking about similarities here. Jordan Carter: Section 4 - this needs quite a bit to tightening up. this gets close to the scope of this group and should be looked at in this light. Section 5 - Recommendations - I disagree with the financial indepence recommendation (registries and registrars should not fund ICANN). Pam Little: @Jeff - ICANN provided a detailed response to our questions. Jeff Neuman: I agree with removal of that bullet point Alan Greenberg: how would this funding recommendation work? Klaus Stoll: This financial relationship sometimes leads to conflicts and so we should look at better way to fund us to avoid this. Jeff Neuman: @Klaus - But you are assuming there is a problem Jeff Neuman: where is the evidence of that? Alan Greenberg: Agree there is an issue but would not resolve it this way. This resolution makes no sense as is. Klaus Stoll: If we do the second part we would be out of the scope of this sub-group. Jordan Carter: There is something there that could put pressure on staff to dealing with those participants who fund the company. Alan Greenberg: No problem with identifying the issue but the recommendation does not make sense. Jeff Neuman: We need to identify sources of information for sections 1 and 2 - otherwise causes confusion for the reader. Jordan Carter: the original longer version of this did have that and we have to bring some of that back. Phil Corwin: Agree that the financial recommendation does not make sense. Second the funds to come from registrants up though registrars and registrants. The funds are used to get a variety of participants in ICANN. We need a document that will identify remedies for issues with staff. Jordan Carter: That is for document A. Klaus Stoll: It would be good to make these comments in the documents would be very helpful. Jordan Carter: reminder to participants to please read and comment the document. 3. Initial discussion / seeking feedback on First Draft Document B - Avri is rapporteur on this Jordan Carter: Waiting for access to documents. Bernard Turcotte: Staff should have a response on thiss by the end of next week. Jordan Carter: We will not go into detail on this document here while we wait for access to the ICANN documents which would inform our work in drafting this further. https://docs.google.com/document/d/1UnkJuukv0px-CfIDgLrjdDZa2CpBvSahPvAXdYY… 4. Volunteers for response to Staff Questions Avri has prepared a document for answers to the questions that staff asked the group Jordan Carter: Who would like to volunteer to draft some further answers? Klaus Stoll: The answer to these questions are mostly in sections 4 and 5 of our document. I could spend some time to attempt a draft answer for us to consider. Jordan Carter: Great thanks. Cheryl Langdon-Orr (CLO): we need to send / resend the links to docs again to our Cheryl Langdon-Orr (CLO): list with reminder to contribute 5. Schedule check Jordan Carter: https://docs.google.com/document/d/1Ftd-Ps_qF46pf_iXf5foGjdUfCq64-St_43inFe… --- this is our Next Steps Jordan Carter: We are running a little late vs this schedule. We may not have docs A and B to the plenary prior to Copenhagen but should have one ready for Copenhagen. 6. AOB 1. Jordan Carter: AOB (none) – Adjourned Action Items: · Participants to read A and B document by EOB Monday and provide comments for drafting team- JC to send reminder to list. · Staff to provide answer to sub-group on access to documents by 27 January 2017. · Klaus Stoll to draft answers to Staff Questions for consideration by group by 27 Janaury 2017.

1 0

Please Contribute to these documents
by Jordan Carter Jan. 20, 2017

Jan. 20, 2017

Hi everyone This email hopes to encourage you to READ and COMMENT or share THOUGHTS or OPINIONS on the documents we are working on: *Document A - relationships between ICANN Board, Staff and Community* A clean version of the doc - please comment on this one: https://docs.google.com/document/d/1wGRrJZ-i7WA0uYBIHaB5Q3ssqfRmbAcgHJwlQ 6scHZY/edit (Marked up from previous version at: https://docs.google.com/document/d/1wXuZw-VFeMLT3B5UHLU_nY1SWyzp6- VLeVZF1FY0UDk/edit) For Doc A it would be super helpful if you can add thoughts by end of Monday - a redraft will happen after that. Document B - systems etc at ICANN side - first draft Please add comments and thoughts: https://docs.google.com/ document/d/1UnkJuukv0px-CfIDgLrjdDZa2CpBvSahPvAXdYYTeHk/edit Response to Staff Questions Here is a place to help add answers https://docs.google.com/document/d/1ELuw6i3mGAjnZBe0Vc_ lraNQrWw5m_I6UyipEHaRJxc/edit Your input is vital! thanks all Jordan -- Jordan Carter Chief Executive *InternetNZ * +64-4-495-2118 (office) | +64-21-442-649 (mob) | Skype: jordancarter jordan(a)InternetNZ.net.nz | www.InternetNZ.nz *A better world through a better Internet*

2 1

Draft Agenda for 19 Jan call at 19h UTC
by Jordan Carter Jan. 19, 2017

Jan. 19, 2017

Hi all Please find below a draft Agenda for our next meeting, coming up in fifteen hours or so. Apols for the late circulation. Speak soon, Jordan CCWG WS2: Staff Accountability Draft Agenda - 19 January 2017 at 19h UTC (this agenda as a Google Doc: https://docs.google.com/document/d/1mxzAO2dIEpvV8N31tauknrT2dHatsqRRLHb27EF…) 1. Intro: agenda review, attendance, SOI check 2. Detailed discussion / seeking feedback on working draft Document A version 1.3. Document, open to comments and suggested edits, can be found at: https://docs.google.com/document/d/1wGRrJZ-i7WA0uYBIHaB5Q3ssqfRmbAcgHJwlQ6s… Marked up from previous version at: https://docs.google.com/document/d/1wXuZw-VFeMLT3B5UHLU_nY1SWyzp6-VLeVZF1FY… 3. Initial discussion / seeking feedback on First Draft Document B Avri is rapporteur on this document Available: https://docs.google.com/document/d/1UnkJuukv0px-CfIDgLrjdDZa2CpBvSahPvAXdYY… 4. Volunteers for response to Staff Questions Avri has prepared a document for answers to the questions that staff asked the group, available at: https://docs.google.com/document/d/1ELuw6i3mGAjnZBe0Vc_lraNQrWw5m_I6UyipEHa… Who would like to volunteer to draft some further answers? 5. Schedule check 6. AOB -- Jordan Carter Chief Executive *InternetNZ * +64-4-495-2118 (office) | +64-21-442-649 (mob) | Skype: jordancarter jordan(a)InternetNZ.net.nz | www.InternetNZ.nz *A better world through a better Internet*

1 0

Document A (Board Staff Community) second draft
by Jordan Carter Jan. 18, 2017

Jan. 18, 2017

Hi all In prep for our meeting Thursday 19 January at 19h UTC, Avri and Klaus and I have been prepping a second draft of the Document A paper. This will be a main agenda item at the call. You can find a clean copy here: <https://docs.google.com/document/d/1wGRrJZ- i7WA0uYBIHaB5Q3ssqfRmbAcgHJwlQ6scHZY/edit#> Marked up from the last version, w lots of comments etc (and thus quite slow): <https://docs.google.com/document/d/1wXuZw-VFeMLT3B5UHLU_nY1SWyzp6- VLeVZF1FY0UDk/edit> We think it needs a thorough edit to make it clearer and simpler to grab the key concepts, as at the moment it is quite long and opaque. *From this Thursday's call it would be great to get feedback and input from people, and your agreement to the possibility of another further edit. From there, the document can go into the CCWG once we do an online check for contentment.* What are your thoughts? Jordan -- Jordan Carter Chief Executive *InternetNZ * +64-4-495-2118 (office) | +64-21-442-649 (mob) | Skype: jordancarter jordan(a)InternetNZ.net.nz | www.InternetNZ.nz *A better world through a better Internet*

1 0

Staff's questions to subgroup on Staff Accountbity
by avri doria Jan. 17, 2017

Jan. 17, 2017

hi, Just wanted to remind us that we have a set of questions from the staff pending response: from: <https://community.icann.org/download/attachments/59643290/Staff%20accountab…> Questions for the community: * What are some concrete examples of concerns that the community has with regards to staff accountability? Are the concerns about individual service delivery/individual staff, or about the potential that staff might cause a violation of ICANN policies, processes, or Bylaws? * In the staff accountability group, there have been suggestions that people within the ICANN Organization are afraid to speak to the community. Can you provide more detail to support these suggestions? Is the reluctance to speak based on perceptions of how the ICANN Organization will respond, or how the community will respond? * ICANN expects all people within the ICANN Organization to be respectful to the community in interactions. If the community is not treated with respect, that would clearly be an issue about which ICANN should be made aware. What is the expectation for the community in addressing members of the ICANN Organization? * Do you think that there should be areas where people in the ICANN Organization should be directly accountable to the community? What would this look like, and how could it be done in a way that does not interfere with the employer relationship? Are the enhancements of the Reconsideration and IRP Process, where staff action can be challenged directly, sufficient to address the subgroup’s concerns? How does one prevent inconsistent feedback to ICANN.org employees? --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 1