PR meets the WWW / Constantin Basturea’s weblog

I just uploaded a bunch of links to notes and audio recordings from Les Blogs on Loic Le Meur’s wiki. Enjoy :)

{tag: lesblogs}

Steve Rubel is asking some important questions:

So far this year, the mainstream media has cited Wikipedia as an authoritative body of knowledge nearly 100 times. [...] What should someone in PR do if he/she finds inaccurate information?

As Wikipedia is relied upon as a credible source by the press, will these and other companies begin to edit articles? What guidelines should we follow? My initial feeling is, if you can prove the article false, challenge it. If it’s true, leave it. You’ll only make matters worse. Besides, inaccurate information on Wikipedia doesn’t stay that way for long. What’s your take?

(Coming next week in Part II: what should you do if your client/brand is not listed in Wikipedia? Is it ethical or proper to create an article?)

The best source for starting to explore this issue is Wikipedia itself; more exactly, a page included in Wikipedia’s Problems FAQ and titled Autobiography (formerly known as Don’t create articles about yourself). Here’s an excerpt relevant to this discussion:

Some of us feel that even editing an article about yourself is best avoided [...]. If you do so, please only add verifiable information and be especially careful to respect the neutral point of view. Noting objections or corrections on the talk page may be appropriate.

Similar principles apply to articles about works that you are primarily responsible for - the company you run, the website you started, the book you wrote. Use common sense.

Now, it’s important to note that this is not (yet) a Wikipedia policy page, it’s a semi-policy:

Semi-policy pages are an attempt to codify and write down long-standing unwritten rules that have widespread support. They should be treated as guidelines, not as strict rules.

In the Talk area for this page there’s an interesting exchange between Wikipedians, including a person — username: Pfwebadmin — who’s working for a "US-based non-profit that does reproductive health work in Asia, Africa & Latin America." Pfwebadmin wanted to see an article about his organization on Wikipedia, but was reluctant to start one, and asked what’s the proper way to handle this.

Someone responded that this kind of things have been anticipated, but didn’t happened. What’s crucial is that the article, if started, should conform to the "non-negotiable" policy of maintaining a Neutral Point of View (NPOV); for that, the authors should stick "as much as possible, to facts that can be verified using third-party sources."

(I’ll skip a juicy bit about how Pfwebadmin has offered money to any experienced Wikipedian to start and expand an article about his employer, and that the article has been created, although the money was refused.)

There are a couple of things that Pfwebadmin did right - and they can serve as a start in responding to Steve’s question:

• he joined the community, by starting a user page
• was upfront about the relationship with his employer
• was aware of Wikipedia’s policies (especially the NPOV) and rules (Don’t start a page about yourself), and respected them
• asked for guidance
• made clear that he’ll try to stay out of the editing process, and that he will disclose any edits
• asked fellow employees to contact him before trying to edit the page, especially if they’re not familiar with Wikipedia
• asked people to discuss the issue of an employee starting/changing the page of a company ("Enable me and my organization to do right by Wikipedia.")

His care for respecting Wikipedia’s ethos was noticed and appreciated. Here’s what another wikipedian — user name: Lotsofissues — wrote:

Thank you for your careful consideration of POV on this site. It’s refreshing to see after discovering/deleting so much vanity/marketing daily.

It’s a "success story" - at least for now. The page on Pfwebadmin’s employee is very short, and it didn’t experience any editing war so far. But this could change, since the organization focuses on reproduction and AIDS/HIV prevention issues, which are sensitive topics.

There are a couple of things that you might want to consider before jumping to start or edit a Wikipedia page about your employer:

• I think it’s unlikely that most journalists –and their editors– are taking the information provided by Wikipedia as facts, without checking them for accuracy, especially if the subject matter is controversial. Steve points to a page showing that Wikipedia has been cited by mainstream media nearly 100 times so far this year. But the number itself doesn’t tell much (and, by the way, most citations are from English-speaking media, and at least two of them are from WebProNews reposts of blog postings). Sometime Wikipedia is indicated just as a resource for more information. Also, look at the terms for which Wikipedia is used as a source: definitions of podcasting, phishing, anime, weblog, webcasting, folksonomy, spamming, spyware, warez... — and Sauerkraut. So, let’s see these numbers in perspective.
• Is your company important enough to have a page in Wikipedia? Would you expect to find an entry in Encyclopaedia Britannica about your employer? No? Then why do you want a page in Wikipedia? Aren’t there better ways of making people aware of your company and engaging in a relationship with them than starting a page on Wikipedia?
• How much of what people know about your company is likely to be influenced by what they read in Wikipedia about it?
• You will have to invest time in maintaining the accuracy of your page. You’ll have to be prepared to do research, to find third-party endorsements for things that you take for granted. You’ll have to go through editing wars, and to explain why you’re adding to, or deleting, or modifying the page. Are you ready for this type of work and involvement?
• Finally, if you are a PR professional, ask yourself: would you have considered editing the page about a company if the company was not your client? And, more important: what impact a (perceived) "flack attack" is likely to have on Wikipedia as a community and as a resource?

On the other hand, it would be unrealistic to think that companies (and PR professionals) will shy from involvement in influencing what Wikipedia says about them. That’s why it’s better to start now a process of establishing the rules of engagement. Wait, Pfwebadmin already thought about this (emphasis added):

I’m wondering if there is room for a project of some sorts to help facilitate people and entities that will have to walk these Autobiography issues choosing to walk them correctly. I’m basically trying to create, on my company’s discussion page and on my login’s discussion page, a blueprint for how to act with respect to this sort of stuff. I wish there were a few options in somewhat a cousin vein to a license of sort that I could use there instead of having to try to create the wheel and also figure out which and how many spokes should go in it. Maybe even something that I could then get my president to sign off on being our company’s official policy towards its employees’ interaction with Wikipedia? Does that make sense? Strikes me that as Wikipedia and Wikipedia’s relevance grow, these sorts of issues will be ever-present and increasingly important to address.

There’s no such project right now, but we should start one soon. Does anyone have Jimmy Wales’s phone number on Rolodex? Scratch that. Now we’ll have do discuss it with the whole community. Heh.

April 25, 2005 - Les Blogs: Blogs and Social Software:

• Program
• List of participants
• Chat room
• Coverage (blogs & MSM) (on Loic Le Meur’s wiki)
• Follow the event on the blogosphere:
  • Feedster (RSS feed)
  • Technorati tag: lesblogs
  • del.icio.us tag: lesblogs (RSS feed)
  • Flickr photostream (RSS feed)
• PR/Comm bloggers participating at the event:
  • Neville Hobson
  • Fredrik WackÃ¥
  • Daren Barefoot
  • David Tebbutt
  • Bjoern Ognibeni
  • Adriana Cronin-Lukas and Perry de Havilland (Big Blog Company)
  • Guillaume du Gardier.

(Updated April 23, 2005)

Yahoo’s blogging platform — cleverly named Yahoo! 360° — has launched a product blog. I really hope that the person responsible for setting it up will be interviewed and kindly asked to spell out, in print, on radio and TV, the weblog’s memorable, easy-to-remember, URL:

http://blog.360.yahoo.com/blog-1qCkw2Ehaak.hdNZkEAzDrpa4Q–

Update:

Commenting on Steve Rubel’s blog, an anonymous "360 Team Member" is taking him to task for using the ugly URL "when the link on every single page is http://blog.360.yahoo.com/product_360 and it works just fine," and explains that "the persistent (scrambled) links are for people who want to protect their Yahoo! ID."

That’s great, but the problem is that most of the people will land on Yahoo! 360°’s product blog without being logged into their Yahoo! accounts. The permalinks for the blog are carrying the same ugly sequence, and if you want to go to the blog’s home, you’ll click in the left side menu on Blog or on Top Page, which –surprise– has the same 1qCkw2E…. in its URL. There’s nowhere on the blog an indication on what’s the blog’s friendly URL (in this case, blog.360.yahoo.com/product_360), so I don’t understand what the "team member" means by "the link [is] on every single page."

By the way, I stumbled upon Yahoo! 360’s blog by following a link from b-spirit.com’s blog, who read about it on The Blog Herald. I guess we’ll have to be excused for not logging into our Yahoo! accounts first :)

Now, it’s great that Yahoo! 360 thought about protecting the Yahoo ID of those who are using their services, but maybe it could reconsider how this feature was implemented. For example, how about allowing users to write the URL of their blog in (a more) natural way, a la Blogspot?

Here’s another example, that maybe it will illustrate better the problem on using human-unfriendly URLs. If the person commenting on Steve’s blog is actually a Yahoo! 36o team member (which I doubt), then the name of Jeff Weiner should ring a bell. Mr. Weiner is Senior VP of Search and Marketplace at Yahoo! — and he has a blog. Let’s say I don’t know the URL of his blog, so I’ll go to Google (I know, I’m mean) and search for "Jeff Weiner blog". Guess what I found? Exactly:

http://blog.360.yahoo.com/blog-zuC3Zp07bKNSlo73LN4rX7c-

I doubt that Mr. Weiner will print this URL on his business card. There’s no indication on the blog’s homepage of what its friendly URL must be, or if it has one; and I’m not sure that the author will be willing to share his Yahoo! ID with the rest of the world. So, what’s to be done?

John Gruber — Translation From PR-Speak to English of Selected Portions of Adobe’s ‘FAQ’ Regarding Their Acquisition of Macromedia:

Said FAQ is available in convenient PDF format here.

What is the mission of the combined company?

Adobe’s mission remains the same — to help people and businesses communicate better. With the acquisition of Macromedia, Adobe strengthens its mission through the combination of leading-edge development, authoring and collaboration tools — and the complementary functionality of PDF and Flash.

Where by “complementary� we mean “the two leading technologies that irritate people when they’re used in lieu of regular web pages.� Note that we’re using PDF to serve this very FAQ — in our synergistic future, perhaps we’ll serve our FAQs in a hybrid PDF/Flash format. One can dream.

Via Tim Bray’s ongoing.

The team credited for creating Sun Microsystem’s blogging community, blogs.sun.com, has received the company’s Chairman Award. The title of the award is "blogs.sun.com: Humanizing Sun, Changing Perceptions and Re-Enlisting Champions".

Will Snow:

It’s kind of hard to believe that it all started with a discussion in a big conference room where we convinced our COO that blogging was a good thing. Almost a year later (geez, has it been that long?) and we’ve been recognized by executive management as top innovators.

This is, probably, the "secret" ingredient of Sun’s success in opening blogging to its employees: the fact that an initiative coming from grassroots has been totally embraced by the senior management team. If you didn’t get this feeling from Jonathan Schwartz’s postings or from Tim Bray’s weblog, maybe these snippets from a 2004 interview with the Sun’s (then) vice-president of of global communications Andy Lark will convince you:

• "Many companies think they can introduce blogs. They can’t. Employees introduce blogs. Customers blog. Shareholders blog. Even executives blog. All we did was turn the web into a printing press so more employees can engage."
• Isn’t Lark a little worried about what might emerge in this uncensored forum? “Why hide your voice? Our employees are smart and will ultimately do the right thing. And some of them write really well. Blogs improve communication – inside and out. Employees understand how responsible they are for our reputation.â€?
• But Sun’s blogs do have a downside. “They really freak the lawyers out. And some of the grammar is shocking. Both are meaningless in terms of the benefits – although the lawyers might disagree … It’s just entertaining to see some of the stuff our employees have an opinion on.â€?
• Lark’s final word: don’t try to fight the blog. Your staff are going to chatter anyway, so it’s best to try to be a friendly facilitator rather than network dictator. “Unleash them. Give employees the printing press. It’s going to be much easier to manage if it’s your press. Organisations with septic cultures are going to have a real hard time not changing. Employees will lay them bare.â€?

Sounds like a Cluetrainish fairy tale in Corporate Blogland, right?

Other resources on blogs at Sun:

• Sun policy on public discourse
• Making Sun policy - Tim Bray, Technology Director at Sun Microsystems, May 2, 2004
• Sun blogs directory

(Update - April 29, 2005: added the award’s title, found on Doc’s blog.)

Lenn Pryor - Goodbye Microsoft, Hello Skype:

I recently accepted a new job and have resigned my post as Director, Platform Evangelism at Microsoft after almost 8 years with the company. I am joining Skype and the family and I will be moving to the UK. I have taken a position on the product and services team at Skype. I have decided that Microsoft and I need to go our separate ways and it is time to move to new pastures.