Blogging healthy athmosphere

an article added by: Artima at 05302007


In: Categories » Internet and online » Web services » Blogging healthy athmosphere

As you begin to blog and appreciate the complexities, benefits, and potential offshoots of blogging, you will undoubtedly begin to wonder how to get your employees to blog. The first step is to realize that it’s entirely likely that some of your employees are already blogging.

With millions of blogs in the world, assuming that none of your employees is blogging is about as naive as assuming that none of your employees has ever downloaded music online it could be true, but the odds definitely aren’t in your favor. Communicate with your employees about blogging. For some companies, this may mean a staff meeting about blogging; for others, it may be an e-mail asking for input. At a bare minimum, it should include a blogging policy and some information to managers about how to handle blogging-related issues. The goal of any blogging policy or guideline should be to communicate what is and isn’t acceptable. Some companies actually choose to make blogging a required part of an employee’s day. Creating a healthy blogging atmosphere goes beyond the policy you create, however. Having executives who blog and who encourage blogging is a great way to introduce blogging, though it isn’t a requirement. The key to a healthy blogging atmosphere is to have the company, leaders, and managers value blogging, bloggers, and blog feedback.

This is why having a corporate blog, product-specific blogs (if you make products such as cars or software), or market-specific blogs (if you create a wide variety of products) is important: it allows your customers to provide feedback in a variety of locations and therefore allows you to use that feedback in a variety of ways. Far too many companies who blog have only one official blog, which is so focused it seems like just another marketing vehicle. This approach is problematic, with the biggest problem being that it allows customers to communicate with you via only one blog venue instead of many. Building a culture that values blogs requires that you create foundational value statements such as these:

We value blogs.

We value bloggers.

We value blog-based input.

We value employees who blog.

We value customers who blog.

Each of these value statements is important. Valuing blogs means realizing that while a fair amount of noise is being made out there, finding and reading actual customer feedback can be more valuable than any other form of customer communication. Valuing bloggers involves more than just saying “yes, they’re out there”; it means reaching out to bloggers and customers for feedback on your company and your products. Creating passionate customers is effective, but reaching out to existing influencers and creating relationships with them will not only revolutionize your business, it will also pave the way for the third value statement: valuing blog-based input. The challenge with blog-based input isn’t getting feedback; it’s knowing what to do with both the positive and negative feedback, as well as having a place where you can respond to feedback in an open and timely manner.

THE VALUE OF CONVERSATION: THE iUPLOAD STORY

One company that values blog-based input is iUpload, which creates content management and blogging software for enterprises such as Adobe and CTV, one of Canada’s largest television networks. iUpload is a fairly small company, with about 20 employees, though the company is growing quickly. In early 2005, blogger Mark Vandermaas approached the company looking for information on services, pricing, and other features. During the conversation, wires were crossed and people got confused (as sometimes happens in real-world communication).

Mark posted information about his experiences with iUpload to his blog (at http://voiceoflondon.iuplog.com/default .asp?item=99350), which was, ironically, powered by iUpload: As of today, April 11th, nearly one month after my initial request, I still do not know the price of the Community Publisher software, and no one from iUpload has contacted me. My wife summed it up best when she asked, What’s the big secret? – Mark Vandermaas iUpload had dropped the ball and he, justifiably, wanted to know why!

Within days of Mark’s post, Robin Hopper, iUpload’s CEO, responded (http://hopper.iuplog.com/default.asp?item=85308). Hopper succinctly explained where and how things went wrong, apologized, and promised to make things better. He cleared up, in public, the question about pricing and promised to take a number of concrete steps to avoid this kind of confusion in the future. The net result was that Mark updated his post with the following: I have to admit that after notifying iUpload’s CEO, Robin Hopper of this post I was half-expecting that my blog’s switch would be flipped to the off position. Since my intent was to help rather than offend I offered to take the post down once he had a chance to review it. This is where it gets good: not only did he not want me to delete this post; Robin told me that he appreciated the feedback, and that he wanted to post something on his blog with a trackback to it! You can read his post by clicking on the link in his comment below. Today, I heard from iUpload. Turns out they weren’t trying to brush me off; I just got lost in the middle of a frenetic growth stage and misread their actions. We all make mistakes. If you’re good, you fix them. [emphasis mine]

If you’re really good you fix the mistakes and then fix the procedures that didn’t work. But if you’re destined for greatness, you have the guts to let someone like me tell the world what you learned from it. Well done, iUpload! – Mark Vandermaas

This story illustrates a number of core concepts for successful business blogging. First, Mark complained in public about what had happened. When you drop the ball, customers will complain. Second, iUpload wasn’t afraid to respond honestly to Mark’s commentary. Not only did iUpload leave his post on the site, but the CEO responded to Mark’s concerns in public on his own blog. The net result?

Hopper’s response and effort transformed Mark from a mistreated customer into a customer evangelist. And all it took was a little bit of blog love. Imagine the situation if Hopper hadn’t responded, or if he’d responded by dismissing Mark’s claims. It’s entirely likely that not only would Mark not have bought software from iUpload, but he would have told a fair number of people in his circle of influence about the experience. The lesson? Creating a blog-friendly culture requires moving past your fears. Fears paralyze us in everything from skydiving (in my case) to spiders (ditto) to responding effectively to customers. There is nothing wrong with being afraid of something new, but taking that first step and actually going skydiving or blogging is an incredible experience. Trust me!

legal notice

Our website is not responsible for the information contained by this article. Web-articles is a free articles resource.
Suggestion: If you need fresh, daily updated content for your website, feel free to use our service. Click here for more information.

Useful tools and features

Link to this article from your page    Send this article to you or to a friend
If you like this article (tutorial), please link to it from your web page using the information above.

related articles

1. The next few elements define options
In this example, the defaults for htdocs and its subdirectories are set to allow clients to view the contents of a directory (as a page with a list of files, or something prettier), enable support for content negotiation, and permit the use of Unix inter-directory links. The next subdirective, AllowOverride, makes provision for overriding .htaccess files in subdirectories. The options here allow you to specify that nothing be changed (as in the example with AllowOverride None), or that anything be changed (AllowOverride Any...

2. Slightly modified specification for a CS1 program
The manager of a fast food outlet requires a program to help track sales. The outlet only serves burgers with fries; a burger meal costs $5.95. Customers may order any number of burger meals. The program is to help calculate prices of orders, and is also to keep records of total orders and the largest single order. The program is to use a simple menu-select style loop with the options: (1) Place order (2) Print totals so far (3) Quit The order option should result in a prompt for the number of meals ...

3. Lists and arrays
A few more features of Perl must be covered before any more interesting programs can be written. First, we need Perl’s ‘lists’ (or ‘arrays’). A Perl list is like a dynamic array class in C++ or Java (e.g. java.util.Vector). Lists do not use Perl’s object syntax, but a list is basically an object that owns data and which has an associated group of functions. A Perl list: Owns a collection of data elements (usually scalar values, but you can build lists of lists and other more complex struct...

4. Each output line consists of a list of words
These lines have to be sorted using an alphabetic ordering that uses the sub-string starting at the keyword. The keyword starts after column 50, so we require a special sort helper routine that picks out these sub-strings. The sort routine is similar to the numeric_sort illustrated earlier. It relies on the convention that, before the routine is called, the global variables $a and $b will have been assigned the two data elements (in this case report lines) that must be compared. sub by_keystr { my $str1 = substr($a...

5. Finding what matched and other advanced features
Sometimes, all that you need is to know is whether input text matched a pattern. More commonly, you want to further process the specific data that were matched. For example, you hope that data from your web form contain a valid credit card number – a sequence of 13 to 16 digits. You would not simply want to verify the occurrence of this pattern; what you would want to do is to extract the digit sequence that was matched, so that you could apply further verification checks. Regular expressions allow you to define group...

6. Database example
This example illustrates basic use of Perl’s DBI module. The database contains records of people who wish to participate in an email-based ‘pen-pal’ service. Subscribers provide their email address, some limited personal information and a set of interests chosen from a predefined set of about 100 possible topics. Searches can be made for other subscribers who share some common interests, and satisfy other constraints. The database has just one table; the rows characterize subscribers to this ‘E-Pal&rsqu...