Commentary

Michael Hickins
 

Give Twitter, Google Credit for Swine Flu Flop... But

It's pretty clear that the swine flu had a limited run in the United States in large part thanks to the swift and accurate dissemination of information.

It's pretty clear that the swine flu had a limited run in the United States in large part thanks to the swift and accurate dissemination of information.Far from seeing the recent swine flu scare as an over-reaction fueled by pulse-quickening Google maps and Tweets, public health officials can tip their caps to people making Google iMaps and Tweeting to help raise awareness and prevent the spread of this disease.

John Brownstein, a physician at Children's Hospital in Boston who mashed up Twitter with his HealthMap swine flu tracking service, noted last week that "people are using our service for informational purposes."


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

There are those, like Chuck Raasch, who are taking away the wrong lesson:

Twitter, Facebook, YouTube and similar sites can be powerful connectors for the good, but they can also unleash weapons of mass misinformation. Public relations professionals say government and business communications plans carefully constructed during the avian flu threat in 2005-2006 were obsolete when this latest pandemic threat arrived.

The key here is that existing communications plans were obsolete. In hindsight, it might be easy to say that everyone over-reacted, but the disease could easily have spread and gone unnoticed in certain areas were it not for the digital social media, leading to death rates seen in Mexico -- where Tweeting was largely absent until it was too late.

And unlike curmudgeons like John Dvorak, I think the absence of catastrophe (like the Y2K bug) is a testament to the hard work and the timely existence of certain technologies -- not a let-down. The again, I don't rubberneck at highway accidents either, and I don't love train wrecks.

That said, we need to make sure that Twitter, and all those other mobile technologies that allow us to work more productively from more places than ever, don't actually get us in worse trouble than we already are. The incessant demands from bosses to give quick answers and the speed with which computers can make investment decisions -- despite circuit-breakers put into effect to stop them -- can bring down an entire economy or simply ruin a business deal.

Michael Granville, a New York architect I've called friend for over 25 years, told me he's worried that we're in danger of sacrificing our ability to think things through on the altar of doing things fast -- and that electronic communication technologies facilitate this process, supplanting other, more deliberative modes of work. He wrote in an email, "you can't build a building shooting emails back and forth between BlackBerries. At some point, time needs to be spent contemplating how to do the task, testing the alternatives on paper (or on screen), etc. But the endless blur of electronic stimuli is crowding out this process. Our facility to respond quickly becomes an impediment to responding carefully and well."

Maybe our challenge, then, is to put these technologies to the best possible use, while resisting the temptation to respond without thinking, simply because we can.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links