Skip to main content

Am I Being Respectful and Constructive?

Anybody who has volunteered to coach an amateur or school team knows what it is like to have the crowd scream insults or profanity at them. The attack comes across without fail as a personal attack; one of bullying and intimidation of the volunteer coach. The fact the coach is devoting skills and valuable personal time to the organization is clearly not something the spectator considers.

ICANN thrives on volunteerism. Without the devotion and sacrifice of the people who support ICANN, and their participation (often as volunteers) in the multistakeholder model and bottom-up policy development, ICANN would simply not survive. Some participants move on to accept leadership challenges, a choice motivated by the commitment and activism that keeps ICANN alive. They choose to become the "coach" of the team. They have demonstrated the skills and knowledge to lead, and usually through elections, are offered the opportunity.

Remember the volunteer coach?

This phenomenon raises a very interesting and debatable question: Should leadership have a thicker skin? Well, to a certain point, in my opinion, yes. The volunteer/participant is now in a position of authority and is expected to have the competencies to handle critique, dissent, aggressive questioning of decisions, and many other challenges to their leadership. But should they be forced to tolerate and mitigate abusive criticism? Negativity? Counterproductive, irritating or frivolous comments? I think we can all agree the answer is no.

Let's take a moment to think about constructive criticism.

Constructive Criticism: Criticism or advice that is useful and intended to help or improve something, often with an offer of possible solutions ( So how does one give or promote constructive criticism? I think the answer is in the definition: "… useful… intended to help… with an offer of possible solutions."

I am not asking people to go easy on leadership. Hold them accountable for their decisions. Demand transparency. Enforce application of policy. They understand the leadership role they have taken on and they expect you to hold them to their duty.

So, before criticizing their actions or decisions, I would ask you to consider this: make them feel you want to be part of a solution rather than merely an opponent. Change their perception of your criticism so that rather than becoming defensive they become receptive and welcome your input.

But above all, and this is not negotiable, treat them with respect. By offering constructive criticism rather than simply criticizing, you are treating the leadership with respect. You are legitimately challenging them and at the same time demonstrating an interest in opening a conversation with them about improvement or change. Comments should focus on the problem not the people. They have been elected to lead, undermining that leadership with mere criticism is destructive. Everybody's goal should be the success of the team, the group, the community and ultimately ICANN's service to the world.

So, before you hit send, or before you speak, I would like you to ask yourself a very simple question: Is my message respectful and constructive?

Live the ICANN Expected Standards of Behavior that asks you to "Respect all members of the ICANN community equally, behave in a professional manner and demonstrate appropriate behavior."


    Cheryl Langdon-Orr  19:47 UTC on 03 February 2017

    Herb,. Thanks so much for your considered, sensitive and very sensible 'words of wisdom' on this important topic... I am saying that on behalf of the numbers of valuable volunteers I have seen over the years ( almost 50 btw) so sadly and seriously effected by callous and inconsiderate behaviour towards them, from others regardless of whether it has been deliberate, misdirected, ignorant or not... What you describe is a key piece of the considerate and collaborative approach we need to use to ensure we all 'value volunteers' who are of course such a rare and valuable asset to ICANN and so many other vital organisations...

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as"""" is not an IDN."