ICANN ICANN Email List Archives

[bc-gnso]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [bc-gnso] ICANN staff exodus

  • To: Philip Sheppard <philip.sheppard@xxxxxx>, "bc-GNSO@xxxxxxxxx" <bc-GNSO@xxxxxxxxx>
  • Subject: RE: [bc-gnso] ICANN staff exodus
  • From: Phil Corwin <pcorwin@xxxxxxxxxxxxxxxxxx>
  • Date: Mon, 19 Jul 2010 14:40:32 +0000

Agree that it is not appropriate to mention staff changes in the DAG comment 
letter.

Has ICANN really lost "much of its senior management team"? I know that Brent 
and Giza are leaving, but are there others? In any event, unless there's an 
epidemic of such departures, and unless we know the specific reasons for them, 
it is inappropriate to assert that they indicate problems with the new CEO -- 
in fact, my experience is that most large organizations see some significant 
staff turnover in the year after a new CEO comes on board.


Philip S. Corwin
Partner
Butera & Andrews
1301 Pennsylvania Ave., NW
Suite 500
Washington, DC 20004

202-347-6875 (office)

202-347-6876 (fax)

202-255-6172 (cell)

"Luck is the residue of design." -- Branch Rickey

________________________________
From: owner-bc-gnso@xxxxxxxxx [owner-bc-gnso@xxxxxxxxx] on behalf of Philip 
Sheppard [philip.sheppard@xxxxxx]
Sent: Monday, July 19, 2010 4:17 AM
To: bc-GNSO@xxxxxxxxx
Subject: [bc-gnso] ICANN staff exodus

I support NOT commenting in our proposed paper on DAG4 paper on the recent 
staff exodus.
An organisation that loses much of its senior management team within months of 
the arrival of a new CEO is an organisation within which something is wrong.

I suggest the BC ex comm discuss whether they believe the BC should make a 
general comment or perhaps a letter on this issue (or maybe a letter just on 
compliance).

Philip



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy