« Googlebuse | Main | From the mind of Philippe Starck »

Intel Corporate Blogging Guidelines

Intel is famous for being paranoid so it is probably no surprise that there has been no external sign of corporate blogging. Certainly the fact that there is internal blogging has been reported in places like the San Jose Mercury News which talked about CEO Paul Otellini's internal blog.

But things are changing a bit and a bunch of people are working on how to break a small hole in the corporate wall. I've even argued that some portions of the wall should be kept. But I think it is nearly impossible to avoid getting on the bandwagon. With that in mind, here is what I've proposed as guidelines for Intel's corporate blogging guidelines:

  1. Be PASSIONATE!!! (uh, well only if you want to... It is OK to be boring... if you like)* Write about what you know, and what you're excited about.
  2. Respect your audience. Write clearly and well. With only your text to go by, many people will make assumptions about your intelligence so good writing (including correct grammar and spelling) does matter. Respect their opinions and don't insult them.
  3. Respect the truth. If you are posting code, take a minute to confirm it is not buggy. If you are posting product data, make sure it is up to date. If you are repeating information you have heard elsewhere, take a moment to fact check with another source.
  4. Respect privacy. If you are writing about co-workers or posting pictures which may show them, please make sure you have talked to them first. When in doubt, don't do it. Treat unreleased products as your closest friends and make sure you have permission before you write about them too.
  5. Respect the law. Understand and obey copyright law and fair use (link to EFF site -http://www.eff.org/bloggers/lg/faq-ip.php). Understand and obey Intel's trademark guidelines (link to trademark guidelines).
    Respect your limits.
  6. Call for help if you need it. Trolls, stalkers, journalists and other strange creatures live on the internet. If you are feeling like you are getting in deeper than you can handle contact the blogging Ombudsman and they will help you.

It will be interesting to see where this leads. Certainly legal and corporate marketing people will chomp on whatever is proposed. I'll try and do a comparison between this proposal and the "real" guidelines if/when they are released. What do you think about this proposal?

*(note: the exhortation and triple exclamation points in the first item were lifted from someone else's version. The italics and permission to bore are all mine)

[Update: I was reminded that I'm required to add this: The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel’s position on the issue, nor am I authorized to speak on behalf of Intel on this matter. ...etcetera, etcetera, etcetera.]

[Update 2: don't forget to check out Josh Bancroft's ideas on this too]


Comments (5)

Looks like people are noticing this topic:


My public post on the matter:


Niall Cook:

Great initiative, and the very best of luck. I hope you can convince your senior management that this is something they need to do, and do well. More importantly, that it isn't just a legal/HR problem, but a communications and marketing one.

Give me a shout if you need any help - we created quite a few internal presentations and proposals in the process of getting our own approved.


jim wilde:

I've been pitching an open source enterprise blogging sys to businesses for almost a year with moderate success. Your suggestion are a great start for external blogging but do not address the biggest internal problems: employees are afraid to speak up, management does not trust employees, people do not want to share what they know. Besides, big orgs are about killing passion and emotion in most cases.

From open source perspective, most of the posted code is posted because it is buggy and needs to be fixed.

Jim Wilde



I agree, it would take more than blogging to completely address the biggest internal problems. However, from my experience, those who are blogging are generally not so afraid to speak up and are quite willing to share what they know. So, providing a simple way for them to do this DOES addresses in a small way the issues you have cited.

As for code, My experience in reading blogs is that most of what I see are fixes posted. Questions and big chunks of open source code are more common on forums and the like. You are right though, there is no reason that a request for help should be debugged, but it should be complete enough that it can be debugged.

I have loved your site for its useful and funny content and simple design.

Post a comment

(Comments are moderated to fight SPAM and will be published after I have a chance to approve them. Thanks for waiting.)


The previous article is Googlebuse.

The next article is From the mind of Philippe Starck.

Current articles are in the main index page and you can find a complete list of articles in the archives.

Creative Commons License
This weblog is licensed under a Creative Commons License.
Powered by
Movable Type 3.34