[council] ICANN staff

[Adrian Kinderis]

Thanks Rita.

“No formal org chart”? Huh? Seems crazy that an organization the size and structure of ICANN doesn’t have one that is “at-the-ready”.

I look forward to seeing it on the website soon.

I also appreciate your feedback from those discussions.

Thanks.

Adrian Kinderis


From: Rodin Johnston, Rita [mailto:Rita.Rodin at skadden.com]
Sent: Sunday, October 31, 2010 1:58 PM
To: Adrian Kinderis; 'council at gnso.icann.org'
Subject: Re: [council] ICANN staff


Hi adrian/all - it is a great question. there has been some concern at the board level as well re staff turnover and available resources for icann's workload.

At the bd meeting this past wednesday/thursday, rod addressed these issues, and indicated that we would be presented with an org chart next week at the retreat in palo alto to continue discussions. My understanding is that there is no formal org chart, but that once it is prepared and shown to the board, it will be posted on the icann website.

That should provide more information for us all, and a better understanding of vulnerabilities, if any, to be remediated. Thanks.

________________________________
From: owner-council at gnso.icann.org
To: Council GNSO
Sent: Sat Oct 30 21:14:56 2010
Subject: [council] ICANN staff
Chuck,

Quick question.

Is it the Council’s place or business to question the status of staffing at ICANN?

I may be reading this wrong but there seems to have been a spike in staff turnover in the last 12 months.

I could be wrong and this could simply be a case of normal activity but it causes some concern to me when we have a particularly important 12 months. I am sure we would all like to ensure that ICANN is appropriately staffed, with talented and importantly, DNS experienced people to progress the strategic plan and that the existing staff are supported and managed through this stressful period.

As I say, I am not sure it is our place to question or comment.

Perhaps we could notify our representatives on the Board that we believe it to be an issue, if indeed we deem it to be one?

Thanks.

Adrian Kinderis



------------------------------------------------------------------------------ ****************************************************

To ensure compliance with Treasury Department regulations, we advise you that, unless otherwise expressly indicated, any federal tax advice contained in this message was not intended or written to be used, and cannot be used, for the purpose of (i) avoiding tax-related penalties under the Internal Revenue Code or applicable state or local tax law provisions or (ii) promoting, marketing or recommending to another party any tax-related matters addressed herein.
**************************************************** ****************************************************

This email (and any attachments thereto) is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this email, you are hereby notified that any dissemination, distribution or copying of this email (and any attachments thereto) is strictly prohibited. If you receive this email in error please immediately notify me at (212) 735-3000 and permanently delete the original email (and any copy of any email) and any printout thereof.

Further information about the firm, a list of the Partners and their professional qualifications will be provided upon request.
**************************************************** ==============================================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/council/attachments/20101031/64875c0a/attachment.html>