Follow me on
Twitter

Services
Bio
Contact
What Works Now
NEW Expanded Edition
PRESS RELEASES FROM HELL and How to Fix Them
The Traditional Press Release Is Dead! The Made-for-the-Internet Release is News Now.
Buy this Report.
REALITY PR STRATEGY: Everything You Need to Know to Get Free (or Really Cheap) Publicity Now. Before you spend another dime on PR, Buy this Report.


Microsoft Uses Wal-Mart Flog Defense in Wikigate

bonehead.pngMicrosoft is in the news again in what many are calling another ethics brouhaha. I think it's just another bone-headed marketing move from a company that still thinks it can pay or push or bluff its way into message control. Like many big companies and their PR firms, they just don't get social media.

Now, Microsoft is using the Wal-mart flog defense -- that it was an unauthorized move by a low-level employee, that no offer of payment was involved. And I'm Queen Elizabeth.

The story: Microsoft offered to pay O'Reilly author and blogger Rick Jelliffe, who blogs about XML issues, to change some Wikipedia entries concerning the OpenDocument Format (ODF) and Microsoft's Office Open XML.

No big deal, says Jeliffe. Very big deal says Slashdot, CNN, and scores of others.

Wikipedia, to their credit, refused to allow the paid updates. Not, I'm sure, that others aren't getting paid to write Wikipedia entries and not blabbing about it.

So what should Microsoft have done? They should have asked half a dozen well-respected geek Microsoft observers to look at the entries and provide written opinions on whether they needed to be corrected. Then they should have compiled all those responses and presented them to Wikipedia. And they should have blogged about the fact that they did that.

And the real bottom line is that Microsoft should concentrate on making products so great that their customers will love and defend them. And they should fire their PR firm. They are getting really bad advice lately!

As David Pogue pointed out in his January 1 column, this is far from Microsoft's first PR scandal. They just don't learn.


Categories: Business Ethics
BL Ochman | Jan 25 07 8:04 | TrackBack (0)

Comments

It's important to understand that it wasn't Microsoft's PR team that did this, but its/a techy. Had an experienced PR been involved, it wouldn't have happened.

Posted by: Stuart Bruce at January 26, 2007 4:21 AM

Rob Weir shows us the page before the flap. It was anything but biased. Check http://www.robweir.com/blog/2007/01/crocodile-tears.html to see what I mean. If you then read Rick Jeliffe's article about it, you'll see that they had *him* convinced that it was one-sided and defective.

Posted by: W^L+ at January 26, 2007 10:54 AM

Bruce: You're joking, right?

Here's your homework: put Microsoft ethics PR into Google and search both the web and Google News.

Start here: http://www.kegel.com/corporate_ethics.html
BL

Posted by: B.L. Ochman at January 26, 2007 10:57 AM

Walt: The most telling thing in that post is the comment that says Rick Jelliffe should be insulted that Microsoft thought he could be bought in that way.

I love the "IBM made us do it" defense. It's even better than the Wal-mart, "a junior person did it without our permission" defense.

Posted by: B.L. Ochman at January 26, 2007 11:09 AM

no way to spin "we pay to change Wiki entry" into an worthy decision. Their a big outfit and need to expect being hit with a few tomatoes but I'm with you B.L. - Microsoft ought to concentrate on products that people rave about, can't live without.
Are you really Queen Elizabeth? :)

Posted by: Bob Glaza at January 26, 2007 5:33 PM

Did you get down into the comments enough to read Doug Mahue's defence. He's at least sticking up for his actions in asking Jelliffe to do the edits and trying to put his reasoning across.

Posted by: Rachel at January 28, 2007 6:04 PM

Actually, Wikipedia editors welcomed my involvement and I performed the (4 day) contract over the subsequent few months. Following Wikipedia's rules, I put all my suggested edits in the talk pages, and let editors and so on judge them. Almost all of them were accepted, by the way.

I wish people would bother to actually check up what happened before painting me with this mud. What MS did was pretty much exactly what you say they should have done...get a well-respected geek to present opinions, present them to Wikipedia, and publicize it.

As for me being bought, a large part of my job is writing and preparing seminars; there is a difference between being bought (i.e. changing your opinion) and being hired (i.e. trying to redress balance) to do what tens of thousands of other technical editors do: look through technical details and figure out what is correct.

You should be aware that there are many other open source advocates who see standardization as a big win for opponents of MS. In the same way as the decade-long network protocols trial that ended recently (i.e. the one where the SAMBA people were demanding that the secrets of MS' protocols would be revealed) would have been better handled by get standardized versions of them published, so it is better for us to have a published standard for OOXML (and remember, a standard is not a regulation: it doesn't mean we have to use it for anything, all it means is the information is out there and has been vetted for certain documentation-quality and consistency features.)

Posted by: Rick Jelliffe at December 3, 2007 10:20 AM

Rick - what makes you comment 12 months later on this post?

Posted by: B.L Ochman at December 3, 2007 11:12 AM

Post a comment




Remember Me?

(you may use HTML tags for style)






Email this story to a friend







TrackBacks

TrackBack URL for this entry:
http://www.whatsnextonline.com/mt/mt-tb.cgi/3624

Search


Join the What's Next Blog mailing list
Email:

Contact: BL (at) whatsnextonline (dot) com
212.369.8312



blog advertising


About BL Ochman
BL Ochman
Blogger, social media strategy consultant to Fortune 500 companies, and sought-after corporate speaker B.L. Ochman heads the creative team of whatsnextonline.com. She also publishes the Ethics Crisis blog for SRF Global Translations


Poll ID 0 does not exist.


top 25 marketing blog

B.L.'s flickr photos








    Categories
    Ad targeting
    Advertainment
    Advertisement
    Advertising Campaigns
    Alternative Marketing
    Awards
    B.L. Ochman
    Benny Bix
    Best Practices
    Blog Advertising
    Blog Bashing
    Blog ethics
    Blog Legal Issues
    Blog Post From Hell
    Blog Software
    Blogging and Moblogging
    Bloomberg for President
    Books
    Business Communications
    Business Ethics
    Buzz
    Case Studies
    Clueless ad agencies
    Commentary
    Conferences
    Corporate_Blogging
    Cross Media
    Customer Service Issues
    Dead Tree Journalism
    Design Train Manifesto
    Digital Journalism
    Don't Believe the Hype
    E-Commerce
    Email Marketing
    Entertainment
    Ethics Crisis
    Events
    Fatblogging
    Folksonomy
    Fun
    Global Business
    Heard on the street
    Hurricane Katrina
    Internet
    Internet PR
    Internet strategy
    Interviews
    Leaders
    Marketing Strategy
    Media Relations
    Memes
    Mike Bloomberg for President
    Multi-Media Advertising
    Must-Read Articles
    Needs a Blog
    New Products
    News
    Nikon D80 Blogger Program
    Nikon D80 Blogger Program
    Nonsense and Parodies
    Peer to peer
    Peer-to-peer
    People to Watch
    Pet Food News
    Podcasting
    Politics
    PR Cluelessness
    Press Release From Hell
    Product Placements
    Promotions
    Public Relations
    Publishing
    Reality Marketing
    Reports
    Resources
    RSS
    Satire
    Search Engine Marketing
    Second Life
    Shameless Self Promotion
    Social Media
    Social Media Marketing
    Studies
    Surveys
    Technology
    Thought Leaders
    Top Bloggers Essential Research Tools
    Trends
    Up and Comers
    Up Your Budget Treasure Hunt
    User Generated Content
    Venture Capital
    Video Contests
    Viral Marketing
    Virtual Marketing
    Vlogs
    Word of Mouth
    Worst Practices

    Powered by
    Movable Type 3.31