SSW Rules/Communication/Rules to Better Blogging

 Rules to Better Blogging

​
What others have to say about us
See what people think about this product I've been putting together Development Guidelines for my employer and in the process have reviewed many published standards (in the .Net arena) from around the world. In each category, the suggestions at SSW are always among the best. See what people think about this product
- Leon Bambrick,
 
At SSW we encourage our employees to actively keep blogs about their achievements, discoveries, interests, and ideas. The biggest problem about putting up an article is that once it's up there its there for the world to see. Do you express yourself properly in blog posts?
This set of rules aims to help you efficiently write clear, effective blogging articles. In some cases you might be interested in seeing our Rules to Better Technical Documentation for comments on how best to express your techical problems.
Do you agree with them all? Are we missing some? Email me your tips, thoughts or arguments.  Let me know what you think.
Hold on a second! How would you like to view this content?
Just the title! | A brief blurb! | Gimme everything!

  1. Are you still UI aware?

    http://www.useit.com/alertbox/weblogs.html

  2. Do you know that 'Factual Content is King'

    It is easy to think that 'content is king', that is a well known quote. But Rupert Murdoch said it better "factual content is king" so:
    * Fix up your mistakes, and
    * Strike through content that is now been superseded and put a comment eg. "This is now not an issue as it was fixed up in TFS SP1"

  3. Do you post all useful internal emails to the Company Blog

    Most companies include intelligent people who make some relevant and useful points for the greater community or industry, while writing internal emails. Those emails should be published to the company blog for the following reasons:
    1. It will provide great content for Google to index
    2. Raise the profile of your company around the topics discussed
    3. Show the industry that you have intelligent and forward thinking staff
    Read more about Do you post all useful internal emails to the Company Blog

  4. Do you know to tip, don’t rant

    Probably the best reason to blog is when you have made a mistake, especially if you were pulled up for it by a peer. Post about the mistake you made, why you made it and how you are going to try and avoided it in the future.

    Turn a rant into a tip…

    SNAGHTML1b864a4
    Figure: Bad example – It is too easy to rant

    SNAGHTML1b94284Figure: Good example – What started out as a rant about Plaxo became a tip on how to get round it

    Read more about Do you know to tip, don’t rant

  5. Do you know to acknowledge people who feedback?

    If someone gives you feedback and you think it is worth incorporating into the content, you should always name them at the top of your blog post. This makes them feel good and gives your post more credibility.

    SNAGHTML1d4b746 
    Figure: Bad example, a static blog post. Does not look like it has been updated.

     

    SNAGHTML1d398ce
    Figure: Good example, dated and attributed updates give your posts credibility and make them seam alive.

    Make sure that the follow up and aggregate Twitter and Facebook users as well. Make all your readers feel included and you will create loyalty within your readership.

    Read more about Do you know to acknowledge people who feedback?

  6. Do you know how to invite replies?

    Wither you are converting an email to a blog post or writing it from scratch, always invite and instruct discussion.

     SNAGHTMLf1a9ab
    Figure: Bad example, there are no instructions here

    SNAGHTMLef6f69
    Figure: Good example – Asking some questions at the end will solicit more feedback

    Although people may not comply, it helps them adjust from the world of email only.

    Read more about Do you know how to invite replies?

  7. Do you know to make what you can make public?

    As long as there is nothing confidential or NDA in the content, any discussion point should be made public. Transparency is the name of the game. The more transparency you have between customers, management and your technical employees the better. This fosters trust and a closer working relationship.

     

    image

    Figure: Bad example, this is just an email and is hidden from all those outside of the recipients Any answer here would only be of use to those on the list. What if someone new to the company had the issue, or someone outside of the company?

    image 
    Figure: Good example, writing a blog shows both how you deal with mistakes encourages the wider community to contribute with discussion.

    So keep jewels from being left in your inbox. Remember that you are inviting reply’s, and that the gold in this process.

    Note: If the discussion is not worth a blog post, then tweet it and link to the rule.

    Read more about Do you know to make what you can make public?

  8. Do you know to allow employees to post to their personal blog?

    Technical people need a little bit of a free leash in order to be creative. This will benefit the company they work for by demonstrating how technical your staff are, by driving more traffic to your site, and making your staff happier.

     Figure: Bad example, employees must post to the corporate blog.

    Figure: Good example, Allowing employees to post to their personal blog is a win, win situation. But they should do the Gold Plating after hours
    See: Do you know to do the gold plating after hours?

    Tip: Get your employees to add an “SSW” category to their blog so you can aggregate their posts onto the corporate site.

    Read more about Do you know to allow employees to post to their personal blog?

  9. Do you know to do the gold plating after hours?

    There is always the need to Gold Plate a blog post. And this is good. But if you are posting to your blog during work hours you should avoid this. You can always open it up after hours to add this.

  10. Do you know how to document what you are doing?

    If you are recording a choice you should create a rule, if you are explaining how you did something, it should be a blog post.

    If you are writing a really long email, ask yourself if it would be better as a lining blog post rather than a one off email.

    Also see: Do you know to make what you can public?

     

    image
    Figure: This Rule describes the choice that was made: Do you know how to layout your solution?

    image

    Figure: This blog post documents the task or thought process: Solution: Do you know how to layout your solution? Hint: If you are really good you will end up with one or more rules, a blog post and a link in your email

    Read more about Do you know how to document what you are doing?
......