[802SEC] RE: [802SEC] RE: [802SEC] On the use of press releases in general [Was: Motion to approve 802.22 press release]
John, I appreciate your concern, but I don't understand why you would characterize Carl's announcement as "non-real news".
Further, I think it is quite common for Press Releases to be picked up by trade journals and web-journals and broadcast around in many different flavors. For example, the "non-real news" about the convergence within TGn in 802.11 got very wide coverage and got a number of our execs to suddenly begin asking about when & where are we going to see 802.11n products. It may seem "non-real" for you, but it is very real to an industry that thrives on "new stuff is coming" reports. The press is always hungry for news to report, so anything that qualifies as a major milestone is "new news", which is of course just what they are looking for.
Thanx, Buzz
Dr. Everett O. (Buzz) Rigsbee
Boeing IT - SSG
PO Box 3707, M/S: 7M-FM
Seattle, WA 98124-2207
(425) 865-2443 Fx: (425) 865-6721
Cell: (425) 417-1022
everett.o.rigsbee@boeing.com
-----Original Message-----
From: John Hawkins [mailto:jhawkins@nortel.com]
Sent: Thursday, March 30, 2006 9:13 AM
To: Rigsbee, Everett O; EC Reflector 802
Subject: [802SEC] RE: [802SEC] On the use of press releases in general [Was: Motion to approve 802.22 press release]
Totally agree with you Buzz that we need to find ways to get standards activities in front of our execs. Couldn't have said it better myself.
But I don't think a press release accomplishes this. In fact, you make my point for me. If the intended audience is "the folks who read the news and might be interested" and if we want to "attract and maintain their interest" then we need to do something other than a press release. That is unless the target execs are in the habit of surfing to the IEEE website and reading the press releases there. That's the only affect these releases will have unless they constitute "real" news and a trade publication or online journal picks them up. If they do, the news may have a snowball's chance of being read by one of those targeted execs.
My (fairly narrow) point is that the more "non-real" news we put out in these press releases, the less likely the "real" news will get picked up when it does transpire.
j
-----Original Message-----
From: Rigsbee, Everett O [mailto:everett.o.rigsbee@boeing.com]
Sent: Wednesday, March 29, 2006 7:48 PM
To: Hawkins, John [WWP1:1847:EXCH]; EC Reflector 802
Subject: RE: [802SEC] On the use of press releases in general [Was: Motion to approve 802.22 press release]
John, I think you may be a bit off base on this one. The audience is not the press at all; it's the folks who read the news and who might be interested in this technology for their application. But to attract and maintain their interest you have to get and hold onto their attention. Most of our execs here at Boeing don't take any standards work very seriously unless they see reports about it in the press, particularly some articles that point out the potential applications and that real progress towards real products is being achieved. I have been trying to get some folks here in Boeing to pay attention to 802.22 but have had difficulty because no one has seen much about it in the press. So what Carl is trying to do is exactly what is needed: to get the word out that 802.22 is something real that will have important future applications, and that will be here in the not too distant future so start paying attention.
So I have to vote enthusiastically to approve this press release and I hope to see more news of Major Milestones as they happen. If we waited until we had completed standards to publicize them most would die from neglect and lack of interest before they ever got there, and there would be almost no market for such products to appeal to. To do effective standards work you do have to be able to surf the technology hype cycles that they tend to ride on.
So Hang Ten, Carl !!! :-)
Thanx, Buzz
Dr. Everett O. (Buzz) Rigsbee
Boeing IT - SSG
PO Box 3707, M/S: 7M-FM
Seattle, WA 98124-2207
(425) 865-2443 Fx: (425) 865-6721
Cell: (425) 417-1022
everett.o.rigsbee@boeing.com
-----Original Message-----
From: John Hawkins [mailto:jhawkins@NORTEL.COM]
Sent: Wednesday, March 29, 2006 2:44 PM
To: EC Reflector 802
Subject: [802SEC] On the use of press releases in general [Was: Motion to approve 802.22 press release]
Given the recent rash of press release approval requests, I wonder if we aren't "lowering the bar" a bit on what constitutes "news" i.e. press release-worthy items.
Carl and team have worked hard to get this far, and I'm not trying to minimize that fact. (Same goes for Steve and Stuart whose recent releases were approved). But as a marketing practitioner, I know that if you crow too often, the audience (usually the press) stops paying attention to you. Maybe I'm all wet and garnering press attention is not the goal in this case. Maybe the goal is to simply timestamp what we believe are important milestones.
But even so, I think we should agree ahead of time on a practice (dare I say "policy"?) of what types of events constitute worthy "news triggers" for an official release. I'd propose that new project approvals, forwarding drafts to sponsor, standards approvals, etc... make the grade.
Am I off base here?
john
-----Original Message-----
From: owner-stds-802-sec@LISTSERV.IEEE.ORG
[mailto:owner-stds-802-sec@LISTSERV.IEEE.ORG] On Behalf Of Carl R. Stevenson
Sent: Wednesday, March 29, 2006 5:26 PM
To: 'Paul Nikolich'; 'EC Reflector 802'
Subject: [802SEC] RE: [802SEC] Motion to approve 802.22 press release
Paul,
Already done (reviewed, edited, and approved by Karen McCabe)...
I guess you missed my statement to that effect in my motion message - but I know you've been busy today.
I think the text is clean and factual, but will, of course be open to comments from my EC colleagues.
Can I start the ballot?
Regards,
Carl
> -----Original Message-----
> From: Paul Nikolich [mailto:paul.nikolich@att.net]
> Sent: Wednesday, March 29, 2006 5:16 PM
> To: wk3c@WK3C.COM; EC Reflector 802
> Subject: Re: [802SEC] Motion to approve 802.22 press release
>
> Carl,
>
> Before you start the ballot, please have Karen McCabe review the
> release and make all necessary editorial edits to ensure it conforms
> to the style she would like to have. You may also want to collect
> some editorial comments from your EC colleagues and fold them into the
> text prior to EC ballot.
> That being said, I will delegate the conduct of the ballot to you
> Carl.
>
> Regards,
>
> --Paul Nikolich
>
>
> ----- Original Message -----
> From: "Carl R. Stevenson" <wk3c@WK3C.COM>
> To: "EC Reflector 802" <stds-802-SEC@IEEE.ORG>
> Sent: Wednesday, March 29, 2006 4:54 PM
> Subject: [802SEC] Motion to approve 802.22 press release
>
>
> > Move: That the EC approve the release of the attached press
> release on
> > 802.22's progress. (The attached draft has already been
> reviewed and
> > approved by IEEE (Karen McCabe).)
> >
> > Moved: Stevenson
> > Second: Shellhammer (Dr. Shellhammer has read the document
> and agreed to
> > 2nd my motion.)
> >
> > I request an EC e-mail ballot starting ASAP and running for
> 10 days, or
> > until all EC members have voted, whichever comes first. If
> Paul should
> > choose to delegate the conduct of this ballot to me, I will
> be happy to
> > accept the task.
> >
> > Informational - this DRAFT press release accurately states
> the current
> > status r 802.22 and points to the significant progress that
> 802.22 has
> > achieved by going from 10 initial proposals to a single
> merged proposal
> > between November 2005 and March 2006. I think that,
> coupled with Stuart's
> > press release indicating similar movement towards consensus
> in one of his
> > TGs, it is important to give 802 some positive press rather
> than simply
> > allowing them to feed on the occasional contentious deadlock as has,
> > unfortunately, been the case in the past.
> >
> > Regards,
> > Carl
> >
> >
> > ----------
> > This email is sent from the 802 Executive Committee email
> reflector. This
> > list is maintained by Listserv.
> >
>
>
>
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.