<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span style="font-family: 'Verdana'; font-size: 13px; color: rgb(102, 102, 102);">Thank you James.&nbsp;<div class=""><br class=""></div><div class="">Speaking as a real life, actual CEO…I agree.<br class=""><div class="">
  <style type="text/css" class="">
    p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px}
    p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Verdana; color: #9443fb}
    p.p3 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Verdana; color: #9443fb; min-height: 16.0px}
  </style>
<p class="p1"><br class=""></p>
<p class="p1"><br class=""></p>
<p class="p2">Cheers,</p>
<p class="p3"><br class=""></p>
<p class="p2">Chris</p>


</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 18 Jul 2015, at 05:30 , James M. Bladel &lt;<a href="mailto:jbladel@godaddy.com" class="">jbladel@godaddy.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class="">

<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class="">

<div dir="auto" class="">
<div class=""><span class=""></span></div>
<div class="">
<div class="">The more I consider the idea of holding staff "accountable" to "The Community," the more convinced I am that this would fast become an organizational nightmare.&nbsp;</div>
<div class=""><br class="">
</div>
<div class="">Non-exec members of staff should be held accountable to their direct supervisor, and the chain of authority up to the CEO. It is not appropriate to insert the Community in that hierarchy, or to haul these folks in front of public inquiry committees. You
 have mentioned that the community would not make hire/fire decisions, so what is the point of this exercise, except to publicly shame the staff member, sully their professional reputation, and destroy their future career prospects? &nbsp;No sane person would want
 to work for ICANN if it means subjecting themselves to several thousand self-appointed bosses, who may or may not have any relevant expertise to judge the employee's performance. The near-term outcome would be an exodus of anyone with talent. &nbsp;And recruiting
 competent new hires would be difficult, expensive, or both.&nbsp;</div>
<div class=""><br class="">
</div>
<div class="">Executive employees are a different story, but even in their case I believe that community influence should be indirect, such as including a community review as a component of their annual performance review, or notifying the CEO if the exec no longer
 has the trust and confidence of the community. If the CEO repeatedly fails to act on this, the he or she should be shown the door.&nbsp;<br class="">
<br class="">
Thank you,
<div class=""><br class="">
</div>
<div class="">J.</div>
<div class="">____________</div>
<div class="">James Bladel</div>
<div class="">GoDaddy</div>
</div>
<div class=""><br class="">
On Jul 17, 2015, at 20:39, Kieren McCarthy &lt;<a href="mailto:kieren@kierenmccarthy.com" class="">kieren@kierenmccarthy.com</a>&gt; wrote:<br class="">
<br class="">
</div>
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">&gt;&nbsp;some personnel issues should remain confidential,&nbsp;
<div class=""><br class="">
</div>
<div class="">I don't understand why people keep putting this strawman out there. No one is suggesting, or indeed has ever suggested, that personnel issues be included in a proper accountability mechanism.&nbsp;</div>
<div class=""><br class="">
</div>
<div class="">&gt; Why would a strengthened ombudsman not be a good fit for this role?</div>
<div class=""><br class="">
</div>
<div class="">I'll give you three good reasons:</div>
<div class=""><br class="">
</div>
<div class="">1. The Ombudsman was created in 2004. Despite numerous efforts to make the role effective, it has never happened. Why keep making the same mistake?</div>
<div class=""><br class="">
</div>
<div class="">2. The Ombudsman is completely reliant on ICANN corporate. For access to people and documents, for resources, for salary, for technical support, for logistical support, for an office, for a room at ICANN meetings, for everything except his own body. And
 his role and what he can do is determined by ICANN's legal department in the rules that they wrote. The Ombudsman also signs a very strong confidentiality agreement with ICANN that effectively ties their hands on everything except illegal activity. See point
 1.</div>
<div class=""><br class="">
</div>
<div class="">3. An Ombudsman is a single person. And one completely reliant on ICANN. This provides an enormous degree of control by ICANN and very little freedom for the accountability role the Ombusdsman is supposed to fulfill. There are numerous people able to testify
 that ICANN corporate has no hesitation in applying significant pressure on individuals if they act in a way that it deemed a potential threat. All of those people are however under confidentiality agreements with ICANN.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">The only way to bring actual accountability to ICANN is to have people that are not dependent on ICANN and are not muzzled by confidentiality agreements asking the questions.&nbsp;</div>
<div class=""><br class="">
</div>
<div class="">And those people are... the 2,000 people that turn up to ICANN meetings. The community.&nbsp;</div>
<div class="">&nbsp;</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Kieren</div>
<div class=""><br class="">
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Thu, Jul 16, 2015 at 10:06 PM, David Cake <span dir="ltr" class="">
&lt;<a href="mailto:dave@difference.com.au" target="_blank" class="">dave@difference.com.au</a>&gt;</span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word" class="">Eberhard has a point.&nbsp;
<div class=""><br class="">
</div>
<div class="">There are legitimate reasons for staff to want to not answer some questions - some personnel issues should remain confidential, some security issues should have disclosure delayed until the problem has been fixed or mitigated, etc.&nbsp;</div>
<div class="">The Ombudsman should have access to any internal document, and the discretion and training to decide what is reasonable to release. Why would a strengthened ombudsman not be a good fit for this role?</div>
<div class=""><br class="">
</div>
<div class="">Regards&nbsp;</div>
<div class=""><span style="white-space:pre-wrap" class=""></span>David</div>
<div class=""><br class="">
</div>
<div class=""><span style="white-space:pre-wrap" class=""></span>(my first post to CCWG Accountability - hi everybody)</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">
<blockquote type="cite" class="">
<div class="">
<div class="h5">
<div class="">On 16 Jul 2015, at 2:03 pm, Dr Eberhard W Lisse &lt;<a href="mailto:epilisse@gmail.com" target="_blank" class="">epilisse@gmail.com</a>&gt; wrote:</div>
<br class="">
</div>
</div>
<div class="">
<div class="">
<div class="h5">
<div dir="auto" class="">
<div class="">Cool, another Ombudsman.</div>
<div class=""><br class="">
</div>
<div class="">el<br class="">
<br class="">
--&nbsp;<span class=""></span>
<div class=""><span style="font-size:13pt" class="">Sent from </span><span style="font-size:13pt" class="">Dr Lisse's iPhone 5s</span></div>
<div class=""><br class="">
</div>
</div>
<div class=""><br class="">
On Jul 16, 2015, at 04:05, Phil Corwin &lt;<a href="mailto:psc@vlaw-dc.com" target="_blank" class="">psc@vlaw-dc.com</a>&gt; wrote:<br class="">
<br class="">
</div>
<blockquote type="cite" class="">
<div class="">
<div class=""><p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="">How about an independent inspector general?<u class=""></u><u class=""></u></span></p><div class=""><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)" class="">&nbsp;</span><br class="webkit-block-placeholder"></div>
</div>
</div>
</blockquote>
[...]</div>
</div>
</div>
<span class="">_______________________________________________<br class="">
Accountability-Cross-Community mailing list<br class="">
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank" class="">Accountability-Cross-Community@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br class="">
</span></div>
</blockquote>
</div>
<br class="">
</div>
</div>
<br class="">
_______________________________________________<br class="">
Accountability-Cross-Community mailing list<br class="">
<a href="mailto:Accountability-Cross-Community@icann.org" class="">Accountability-Cross-Community@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br class="">
<br class="">
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite" class="">
<div class=""><span class="">_______________________________________________</span><br class="">
<span class="">Accountability-Cross-Community mailing list</span><br class="">
<span class=""><a href="mailto:Accountability-Cross-Community@icann.org" class="">Accountability-Cross-Community@icann.org</a></span><br class="">
<span class=""><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br class="">
</div>
</blockquote>
</div>
</div>

_______________________________________________<br class="">Accountability-Cross-Community mailing list<br class=""><a href="mailto:Accountability-Cross-Community@icann.org" class="">Accountability-Cross-Community@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community<br class=""></div></blockquote></div><br class=""></div></span></body></html>