The Business Blogging Field Guide, Part 6: The Do-er

Whereas the Maven business blogs typically are written at a high level, cover a broad industry, and oftentimes do not overly associate the business blogger with the organization they are with, the “Do-er” blogs dive to a deeper level. In some ways, these types of business blogs could be thought of as a more narrowcast version of the Maven blog, concentrating on a particular area of expertise within a particular organization.

A number of large organizations – Sun, HP, and others – allow (or even encourage) developers to write about their area of expertise. Sun, in fact, has dozens, and maybe even hundreds, of bloggers writing about different detailed aspects of the organization. Although in Sun’s case, President Jonathan Schwartz has the largest number of hits on his blog (about 4,300 recent hits), the number of views by readers of the Sun Do-er blogs, in aggregate, outstrip his reach by at least 10:1. (And that’s just looking down the first 65 employee blogs at Sun…the actual number is probably much higher. Weren’t we just talking about this?) HP is testing out this strategy as well, but to date has taken a more cautious stance, with only a handful of Do-er blogs.

It is extremely important to note, however, that Do-er blogs in particular are not restricted to the high-tech industry. In fact, some of the most interesting stories and insight from down in the trenches comes from areas outside of high-tech. There are a number of medical professionals who are blogging about detailed topics, as well as individuals from midsize and even small companies in areas such as automotive repair and home improvement.

“Do-er” example #1


Blogger: Bryan Cantrill (middle)
Role: Solaris Kernel Development
Company: Sun Microsystems
Blog Location: http://blogs.sun.com/roller/page/bmc/20050125


“Do-er” example #2


Blogger: Archie Reed
Role: Secure Identity Management
Company: HP
Blog Location: http://devresource.hp.com/blogs/reed/


“Do-er” example #3


Blogger: Ivan Best
Role: Proprietor
Company: PickupSpecialties.com
Blog Location: http://pickupspecialties.blogspot.com/

Personalization, The Long Tail, And The Charge Against The Customer Monoculture

I’ve always believed the Long Tail is real (even before the concept had a trendy name and a piece in Wired). Maybe it’s some sort of subconscious iconoclasm on my part; perhaps it is the desire to not fit into any well-defined bucket.

I suppose marketers would call this a desire for “differentiation” in both my personal and professional personas.

Most of discussion so far around the long tail is tied to consumerism. That is, long tail economics seem to make sense when one is a consumer (in the strictest sense of the word) of “stuff.” Most of Chris Anderson’s additional writing on the subject centers around this idea as well. The long tail gets invoked when figuring out what is marketable, what is saleable, what is interesting, and to whom.

After further reflection, and at its core, I think the long tail discussion is about personalization, and the human need/desire/want/jones for experiences that uniquely resonate, emotionally, within an individual.

“But most of us want more than just hits. Everyone’s taste departs from the mainstream somewhere, and the more we explore alternatives, the more we’re drawn to them. Unfortunately, in recent decades such alternatives have been pushed to the fringes by pumped-up marketing vehicles built to order by industries that desperately need them.” – from the Wired article

This inherent tension between the “hits” and the long tail is not going to cause a mass jump to “only” long tail scenarios, however. There are still plenty (30%? 40%?) of things that will be hits. And 30% of “everything” is still “a lot.”

What we will see, I think, is a bifurcation. A split. A schism. This will occur not only in the way things are “marketed” to customers, but, moreso, in people themselves. One group, a fragmented set of loosely connected folk (“small pieces, loosely joined,” some might say) will be the “long-tailers,” actively seeking out and creating experiences for themselves that are unique and personalized to them. These folk, in aggregate, will be the majority. (But at the same time, they won’t. Each small community of like-minded folks will be teeny-tiny in comparison to the “mainstream.”) The other group will be those firmly rooted in the mainstream.

Of the long-tailers, there will be a particular set that completely eschews the mainstream. These are the ones who will rail against the monoculture that still, when compared to any particular long tail subgroup, is many times larger. And will continue to be.

Why is this? Why is it easier to be a consumer of the mainstream, rather than creating one’s own experience in the long tail? I think there are a few reasons.

Reason #1: It’s easier to be a customer of the monoculture. Search costs? Zero. Everything is marketed on the billboards, right to your front door, right to the TV, and blown into the most recent issue of People. Information about the mainstream is everywhere. If these are the products and companies you know about, they are the ones that are most familiar.

Reason #2: It may be cheaper, in monetary terms, to be a customer of the monoculture. For items that have signifcant fixed costs of production, spreading those fixed costs out over more units makes things cheaper to produce.

Reason #3: Depending on where one is a customer, the suppliers themselves may actively discourage long tail activity. Anderson’s article states that Wal-Mart, in particular, needs to sell at least 100,000 units of an item to make it worthwhile for them to carry it. It’s hard to be a customer in the long tail if you are never exposed to it.

Being a customer in the long tail takes work.

Now, traditional marketing tries to provide what matters to a buyers who are stuck in the monoculture that exists in a “hits-driven” marketplace. In the absence of local knowledge (e.g. a recommendation from a trusted source), one needs to draw one’s own conclusions. If the only information you have to go on is what is beaten into your head via thirty second spots, those are the products and relationships that you are going to engage with.

This is why technologies such as social networking are lowering the barriers of entry to the long tail. If you have visibility into the movies, the music, the people that other members of your community find worthwhile, you have not only awareness of things that were previously obscured in the long tail, but also an implicit recommendation. Your community has supplanted the traditional marketing machine.

Now, here’s the money shot. Organizations have been hung up on producing products that are “the hits.” We are now on the verge of getting hung up on a similar thing, but in the long tail…because everything that has been discussed about the long tail so far is about stuff. And the long tail really isn’t about stuff. It’s about relationships.

Being a customer in the long tail is not as much about acquiring the things that are unique to you. It’s about connections. It’s about doing business in the unique way you want to, on a day-to-day basis, with organizations who get it. (And, in this case, “get it” means that they offer you exactly what you want, in the way you want it, when and where it’s convenient to you.)

It’s also about building relationships within a community of like-minded folk. When you find out about the amazing Liz Phair B-side, you immediately want to share it with your friends. It’s not about you anymore. It’s about building a community. A community of individuals whose connections will span vocation and time and distance.

Listen up, vendors. If what you’re trying to do is serve only the mainstream, and everybody in it in exactly the same way, you’re about to miss the boat. Trying to build the exact same, cookie-cutter relationship with every one of your customers may work for your organization. But it’s only going to work if you have “the hit.” And people get bored with the hits after a while, and look for something that is different. So, it’s your choice. If you enjoy life on the treadmill, keep doing what you’re doing. Otherwise, you need to have the courage to change your game, and start building some bridges. And fast.

Update:

Ross Mayfield has complementary thoughts on this here and here.

The Ever-Shrinking, Ever-Growing Business Blogosphere

Yesterday, I had the absolute pleasure of sharing a malt-beverage or two with Neville Hobson and Shel Holtz, who were in the neighborhood for The New Communications Forum. (By the by, the Bombay Bomber IPA…delish.)

Neville and I had traded a few emails in the past few months, and I noticed on his blog that he was in from Amsterdam for a couple of days for the NCF conference. Shel and Neville have known each other for a decade. Two quick emails and 12 hours later, the three of us were shooting the breeze in person, without any of the typical awkwardness that comes when people meet for the first time. We already knew each other. It just so happened that, prior to yesterday, we’d never been on the same continent at the same time.

Reason #6537 why business folk should write, podcast, or otherwise communicate often, and in their own voice: your customers, vendors, and partners get to know you before they even meet you, so when you do get together, you already have shared context and can get things done 10x faster than you ever have in the past.

The Business Blogging Field Guide, Part 5: The Customer Advocate

Continuing our series on customer relationships and business blogging, we’re now to where the rubber meets the road. Today, we’ve a couple of particularly salient examples where business blogging engages directly with the customer in order to better drive the direction of the organization. Enter the “Customer Advocate” business blog.

Customer advocate blogs (or advocate-styled posts within a larger, more general blog) are those that expressly engage directly with the customer, solicit feedback, answer direct customer questions, and generally reach out and act as a bridge between customers, their concerns and suggestions, and the organization.

When done well, customer advocate blogs will communicate full-circle, and follow the following steps:

1) Engage the conversation – Ensure that customers have a mechanism for providing feedback, suggestions, needs, wants, and the like.

2) Distill and group the feedback – Many of the feedback items may be around similar topics. Group those together and handle them in aggregate.

3) Determine your own prioritization mechanism – All feedback items are not the same. How will your organization decide which ones to address, and by when?

4) Report back – Let the customers know what’s going on. The customers took the time to share their thoughts…what is being done with them? This is the step that is often overlooked.

5) Get to closure – When things are done, let customers know. Don’t let the feedback mechanism be a black hole. If enough suggestions are submitted that don’t seem to result in feedback or action, customers are going to stop participating the conversation.

“Customer Advocate” example #1


Blogger: John Dowdell
Role: Support
Company: Macromedia
Blog Location: http://www.markme.com/jd/archives/006722.cfm


“Customer Advocate” example #2


Blogger: Robert Scoble
Role: Technical Evangelist
Company: Microsoft
Blog Location: http://radio.weblogs.com/0001011/2005/01/06.html#a9118

(n.b. I’ve notes into both John and Robert, explicitly asking for followup on what their respective organizations are going to do with the feedback and suggestions they’ve received, per point (4) above…this post will be updated as responses arrive)

Update:

(31Jan2005) John has responded in the comments. Thanks for the quick response!

Another Baby Step Forward: A Zero Configuration, All-In-One Podcasting Device For About $25 That My Mom Could Use

Although I’m not an MacHead, the iPod shuffle did push a couple of buttons for me, especially around the use case of having a device that was intended to be transient in nature and only store a few songs (or podcasts) for a limited amount of time. The capability to sync a podcast to a flash-based device with the intention of listening to it on a commute seemed like something that would be useful to have. So, I was thinking about getting one of the shuffles.

Before doing so, and just for giggles, I did a quick search on Froogle for USB flash-based MP3 players. Although the shuffle has a killer cost/MB, I found a flash-based device for about 25 bucks that I thought it would be fun to try this out with. Less memory (128MB), but cheap. Definitely in the “good enough for concept hacking” category.

Looking at the specs, I noticed that it was a pretty nifty little bit of engineering for 25 bucks. Not only could you explicitly use it as a low-end MP3 player, but it was also designed to be used as a general-purpose thumb drive. Since I’m on the road a lot, I figured hey…why not? It’d be good for the quick-storage of documents that I might need to move between machines, etc…the usual use case for a thumb drive.

Then I started thinking about it and realized…holy crap…this is an MP3 player and a storage device. That means that the system will recognize it as a storage device.

One can put applications on storage devices.

Epiphany time…what if we took this one step further? What if…in addition to the downloaded podcasts…we put the podcatching client on the device itself and set it up to auto-run every time the device was plugged in?

The first step was to find a small footprint podcatching client. Doppler fit the bill. Fully installed, it only takes up about 1.2MB. So, I installed Doppler on the flash drive itself.

Podcastdopplerinstallflashdrive_1

The next step was to configure Doppler to write to the device itself. Piece of cake. Just specify the E: drive as where you want Doppler to store the podcasts.

Podcastdopplerinstallflashdrive2_1

Podcastdopplerinstallflashdrive3

Ok, cool. That seems to work so far. Let’s configure it with this feed. Fire it up and…holy crap…it works!

Podcastdopplerinstallflashdrive5

Let’s plug in the headphones. Yup. Works (note to self…since this cheapo device doesn’t have a volume control, ensure that all levels are normalized to 0db).

Podcastpix_003

Let’s try it in the car. I use the Belkin Tunecast (kinda like an iTrip, but device-neutral). This would also work with a cassette adapter. In this configuration, total weight has got to be less than two ounces. Cool.

Podcastpix_009

Next step. Set up Doppler to AutoRun. Everytime the thumb drive gets plugged into a machine, Doppler automatically starts and downloads the latest podcasts to the device itself. No setup for the user, no configuration, no nothing. Plug it in, it does it. Lights out. We now have a basic self-running, self updating, podcast listening device, that can be preconfigured and set up and handed to someone with no knowledge of podcasting, who can begin to listen to feeds. For a price point that’s low enough that even the most staid old company won’t even require an expense reciept.

Podcastdopplerinstallflashdrive4_1

Ok, this is pretty neat. So what?

So…here’s the business problem we can now solve. One of the things that my employer does is competitive intelligence. Up until now, we’ve always delivered this as an online document. But the actual end-users of this stuff (typically sales and marketing folks) don’t always have time to read the documents. They also can’t be sure that they are in possession of the latest update of the documents that we’ve delivered to them. However, as sales types, they are often in the car, or on a plane to see the client.

What we can now do:

  • Preconfigure these dirt-cheap devices, one per sales rep, with a preinstalled version of a podcatching client that is preconfigured to subscribe to a tailored competitive intelligence podcast feed. We can do one “post” per competitor. This allows easy navigation inside the device. We set up the device, subscribe it to the feeds, and hand it to our customer.
  • Prior to heading out to the client, the sales rep can plug the device into his or her machine, and within a couple of minutes the latest-and-greatest kill points will be automatically loaded to the device.
  • In the car, on the train, on the plane, the rep can listen to what’s going on in the competitive landscape. And always have the most up-to-date information available.

This is cool. This has been a good day.

Caveats:

  • AutoRun on WinXP is not natively enabled. Either it needs to be enabled on the destination machine, or the user may need to explicity run Doppler off the thumb drive when the device is plugged in.
  • Doppler is still twitchy. I’m running on the 2.0RC, and it occassionally crashes.

Update:

I did find that this does indeed have a volume control, it’s just less intuitive than it could be.

Update 2:

Steve’s right…put an extra five-spot in the budget to do the right thing for whichever podcatching client you use.

Equivalency (?) Between Ketchum And BzzAgent

(n.b. this is a continuation of this discussion)

Armstrong Williams and Ketchum (well commented on here). BzzAgent.

Any difference?

Both situations have an individual being compensated (or having the potential to be compensated) for talking about something. Both situations have a behind-the-scenes intermediary (Ketchum in the former, BzzAgent in the latter) that is itself compensated to have individuals start a conversation. These conversations take place in situations where the other parties in the conversation would typically feel that the commentator is speaking from the heart, and not as part of a part of a program (or under contract). In both cases, the others in the conversation feel duped afterwards, upon learning that an interaction that seemed genuine was actually staged and part of a program of payola.

Despite all the metrics and process, I still feel the BzzAgent model is broken. How to fix?

1) Explicity lose the incentives (per here). If only a small portion of the BzzAgents are redeeming them anyway, what’s the harm? Even if half the current participants drop out, there still are (if the claims are true) many tens of thousands of people who are participating.

2) Require disclosure. When BzzAgents are buzzing, anything less than stating (either verbally or in writing, if blogging, etc.) “By the way, I’m a volunteer part of an organization that’s getting compensated to promote this product, and I will be writing a report on it at some time in the future,” is disingenuous. Just say it. The Marqui people do. (I’m not thrilled with the Marqui model, but I do respect their upfrontedness about it.)

3) Aggressively change the meaning of the word “agent.” For this to work, “agent” needs to mean “agent, as in catalyst,” not “agent, as in shady operative.”

Communication is good. An increase in interpersonal interaction is good. Making money is good. But doing the first two as a means to the third without disclosing it is a good way to rile up a lot of hornets. And that’s not-so-good.

The Business Blogging Field Guide, Part 4: The Maven

“Maven” blogs (the maven moniker shamelessly stolen from the Malcolm Gladwell book The Tipping Point) are business blogs that highlight an individual’s expertise in a particular area.

Contrast these to the “Tour Guide” blogs mentioned earlier in this series. Where the tour guides are showing an inside view of the company, the mavens are putting their expertise out there for readers to discover. Want to know about the latest trends in PR? You’ll likely trip across Steve Rubel in short order. Want to know about wikis and collaboration? Ross Mayfield is your man.

The most interesting thing about the maven business bloggers is that, typically, the blogs are centered around a business area or concept, and are not focused on the blogger’s employer or associated organization. Instead of being directly tied to the corporation, the blog is tied to the individual. The assumption is, if you are an expert in your field and provide a reason for readers to frequent your blog, then you will be “top of mind” when a particular reader is looking for someone to help him or her with a particular business need in a related area at some time in the future. Most of the examples of mavens shown here are in “services”-oriented fields — PR, marketing, consulting, etc. — areas where the individual’s ability to contribute has a direct impact on the final result of an effort.

“Maven” example #1

Blogger: Steve Rubel
Area of Expertise: PR
Company: CooperKatz
Blog Location: http://www.micropersuasion.com


“Maven” example #2

Blogger: Johnnie Moore
Area of Expertise: Marketing & Branding
Company: The Clarity Partnership
Blog Location: http://www.johnniemoore.com


“Maven” example #3

Blogger: Carolyn Elefant
Area of Expertise: Solos and small law firms
Company: The Law Offices of Carolyn Elefant
Blog Location: http://www.myshingle.com


“Maven” example #4

Blogger: Russell Beattie
Area of Expertise: Mobile Technology
Company: Independent consultant
Blog Location: http://www.russellbeattie.com


“Maven” example #5

Blogger: Ross Mayfield
Area of Expertise: Wikis and collaborative technologies
Company: SocialText
Blog Location: http://ross.typepad.com

Minimizing Comment Spam: The Big Kumbaya

The big search engines have just announced that through the addition of “noFollow” tags in links in comments, they will no longer be weighting links that come from blog comments in their search results. This, in theory, will cause the incentive for comment spam to disappear. The big blog providers will be adding these tags to links in comments automagically.

Who’s on board:

(hat tip: ross)

Two Great Social Customer Examples From The Last 24 Hours

Got an email yesterday from Brian Dear, of brianstorms.com:

“Hi Chris…Big fan of your Social Customer Manifesto blog here…Just went through a delightfully awful customer experience with Intuit. Blogged the whole thing, thought you might find it amusing.”

Indeed! Brian blogged his whole convoluted experience trying to get his QuickBooks Pro 2005 “Slowbooks Amateur 2005” up and running, including a hysterical* exchange with a customer service rep who sounds like a cross between Jeff Spicoli and Patient Zero. The comments indicate that Intuit may have lost a potential customer or three based on Brian’s experience.

Then, not 10 minutes after reading Brian’s account, I’m listening to Adam Curry’s Daily Source Code for 18JAN2005. He not only talks about his ongoing hassles with British Telecom (BT) and EasyNet in getting the last 15m of wire put in place so he can get broadband, but records and podcasts the entire conversation with EasyNet customer service. (Click on the MP3 link; the EasyNet conversation starts at about the 4:50 mark in the recording.)

What does this mean? It means that the barrier to entry of publishing…be it via blogs, web pages, podcasts, what have you…has gotten so low that customers, at any time, can share exactly what their experiences are with the vendors with whom they are working. Not only that, but these experiences become persistent and searchable, sometimes to the point of being more visible than the contrivances the companies themselves are putting out.

Warms my heart, this does.

* – well, hysterical if you’re into schadenfreude, that is…