RE: About IETF communication skills

[<michael.dillon at bt.com>]

> Maybe IETF should be thinking about what actions and 
> policies, uniformly applied, will result in the most accurate 
> representation of its work to the community.

In my experience, the best action to take would be to advise,
or teach, people how to handle media interviews. Back when I 
used to regularly talk to journalists I had no problem with
their articles because I planned the interviews in advance. 
I made sure that I had no more than two or three key points
to make, I prepared a sound bite or two, and I repeated myself.

There is an art in taking complex technical material and
explaining it in layman's terms, but that is exactly what
you must do with journalists if you want them to accurately
represent your message. Even journalists who cover technology
are not technologists themselves. Their specialty is writing
and they can only write what you CLEARLY and consistently
explain to them.

It can be especially hard for people with a deep technical
understanding of something, complete with a multitude of 
corner cases, to summarize in laymans' terms and gloss
over the details. That's why I agree with Keith that some
IETF action would be beneficial here.

Note that one way to approach the issue is to hold official
press conferences at which only accredited members of the
press can ask questions. By doing this you focus attention
on a few people who would, hopefully, prepare for the event
and understand how to explain the work to ordinary people
like journalists and their readers. This doesn't prevent the
press from From ietf-bounces at ietf.org  Thu Jul 31 15:08:46 2008
Return-Path: <ietf-bounces at ietf.org>
X-Original-To: ietf-archive at megatron.ietf.org
Delivered-To: ietfarch-ietf-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DB01C3A699D;
	Thu, 31 Jul 2008 15:08:45 -0700 (PDT)
X-Original-To: ietf at core3.amsl.com
Delivered-To: ietf at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 689A23A699D
	for <ietf at core3.amsl.com>; Thu, 31 Jul 2008 15:08:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=1.000, 
	BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id j25lXSSYBWpB for <ietf at core3.amsl.com>;
	Thu, 31 Jul 2008 15:08:44 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150])
	by core3.amsl.com (Postfix) with ESMTP id 51E713A67FF
	for <ietf at ietf.org>; Thu, 31 Jul 2008 15:08:44 -0700 (PDT)
Received: from E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.62]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 31 Jul 2008 23:08:52 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: About IETF communication skills
Date: Thu, 31 Jul 2008 23:08:57 +0100
Message-ID: <C0F2465B4F386241A58321C884AC7ECC075688ED at E03MVZ2-UKDY.domain1.systemhost.net>
In-Reply-To: <48922EBE.3040804 at network-heretics.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: About IETF communication skills
Thread-Index: AcjzVKIDGhBfd64oQliuc6qPDfp23AAA4QVw
From: <michael.dillon at bt.com>
To: <ietf at ietf.org>
X-OriginalArrivalTime: 31 Jul 2008 22:08:52.0523 (UTC)
	FILETIME=[04533FB0:01C8F35A]
X-BeenThere: ietf at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf at ietf.org>
List-Help: <mailto:ietf-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces at ietf.org
Errors-To: ietf-bounces at ietf.org

> Maybe IETF should be thinking about what actions and 
> policies, uniformly applied, will result in the most accurate 
> representation of its work to the community.

In my experience, the best action to take would be to advise,
or teach, people how to handle media interviews. Back when I 
used to regularly talk to journalists I had no problem with
their articles because I planned the interviews in advance. 
I made sure that I had no more than two or three key points
to make, I prepared a sound bite or two, and I repeated myself.

There is an art in taking complex technical material and
explaining it in layman's terms, but that is exactly what
you must do with journalists if you want them to accurately
represent your message. Even journalists who cover technology
are not technologists themselves. Their specialty is writing
and they can only write what you CLEARLY and consistently
explain to them.

It can be especially hard for people with a deep technical
understanding of something, complete with a multitude of 
corner cases, to summarize in laymans' terms and gloss
over the details. That's why I agree with Keith that some
IETF action would be beneficial here.

Note that one way to approach the issue is to hold official
press conferences at which only accredited members of the
press can ask questions. By doing this you focus attention
on a few people who would, hopefully, prepare for the event
and understand how to explain the work to ordinary people
like journalists and their readers. This doesn't prevent the
press from attendinattending other meetings and it doesn't prevent 
IETF members from talking to the press. What it does do is
hold out the carrot of quality communication, and one hopes
that the press will appreciate the effort and make full use
of it. Indeed, the invitations should explicitly solicit
clarifying questions about anything that the journalist
has already begun working on.

--Michael Dillon
_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www.ietf.org/mailman/listinfo/ietf


g other meetings and it doesn't prevent 
IETF members from talking to the press. What it does do is
hold out the carrot of quality communication, and one hopes
that the press will appreciate the effort and make full use
of it. Indeed, the invitations should explicitly solicit
clarifying questions about anything that the journalist
has already begun working on.

--Michael Dillon
_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www.ietf.org/mailman/listinfo/ietf