1. Citizen Marketer on “Citizen Marketers: When People Are the Message”

    Sunday, 29 Jul 2007 No Comments Posted by:

    When People are the MessageMy book pile has grown faster than I can deplete it.  I’ve done what I rarely do…started reading multiple books at the same time.  Some people can do that, it’s not for me.

    While traveling this week, I finish Citizen Marketers by Ben McConnell and Jackie Huba of Church of the Customer.

    It’s one of the better books on the changing face of marketing and influence in the post read/write web world and I certainly recommend adding it to your pile.  If you are already in a web 2.0 role, Citizen Marketers is a warm blank of reassurance and if you are just considering the implications, it’s an excellent primer for pulling together your business case.

    Here’s what I liked:

    • Good story telling – it’s just a good, entertaining, well written book – notable in that so many business audience books simply are not.
    • Examples galore – I wouldn’t necessarily call them best practices, but a range of examples that span industries and company sizes.  Selling the benefits of community in a company is in part good story telling with examples.
    • Approachability – If you are "web 2.0 literate" already, this is one of the books to drop on the desk of your boss. 
    • Structures:
      • Personas: The Four F’s:  Filters, Fanatics, Facilitators, and Firecrackers
      • Programs: Contests, Co-creation, and Communities

    Enjoy the book…next up, finishing The Influentials.

    Sean

  2. “To Blog or not to Blog” Part II

    Friday, 27 Jul 2007 6 Comments Posted by:

    A few months ago I blogged about Blog policy in "Does your company support employee blogging" – for some reason that post struck a cord and was picked up quite a bit by others.  As one of 3-4K Microsoft employee bloggers, I’m often asked about our blog policy and the road we’ve been on to transparency.  How’d we get management support?  How did we get employee interest?  How would I do it if I was trying to repeat the success in other companies?  This last question got me thinking, how would I implement a blog strategy in a company that didn’t have one in place already?

    First off, let me say that individual blogs are GREAT and should be broadly supported for anyone who wants to go down that path – I’m an example and advocate for that as core to a blog policy/strategy.  Frankly, I think not embracing employee blogging in today’s world would make you an unattractive employer for anyone entering the workforce from Gen Y.

    Having said that, what I haven’t seen as widely spread is a formal commitment to group blogs.  Individual blogs are often challenged by loss of interest by the blogger, change in role at a company, change of place of employment.  These churn issues clearly create risk in continuity.  There are plenty of group blog examples out there, but let me take this one level deeper.  What I’d really LOVE to see is group blogs where the bloggers crossed functional roles in their companies – someone from product, from marketing, from support, from sales, from professional services… This is the type of blog I’d like to read as a user.  Southwest Airlines does this where you see posts from a wide range of contributors in very different jobs at Southwest (Communications, Captains, Executives, flight attendants and mechanics).  It makes for a much more interesting read and as a non-tech company, creates a much easier model for participation for employees.  This approach mitigates the risks associated with churn, drives internal cross group communication and collaboration and better represents your customers end to end experience.

    Of course, I still say it is critical to keep continuity in a few of your core bloggers on the site and allow their personalities to come through very clearly – this, after all, is part of what actually makes it a blog!

    Am I the only one who loves this idea?  What do you think?

    Sean

  3. What’s the most important web 2.0 feature to implement next?

    Wednesday, 25 Jul 2007 1 Comment Posted by:

    Feeling overwhelmed?

    Unless social computing is your full time day job (and night job too) it’s virtually impossible to keep up with (and make sense of) all the new developments around web 2.0.  I regularly get links to interesting implementations that other companies have done as ideas we should consider … or more directly questioning when we are going to do that!  On a recent best practices sharing tour to large companies implementing web 2.0 services I ended the day getting this question:  "What is the most important web 2.0 feature we should be implementing next?"

    What a great question.  It got me thinking about all the people I had talked to in recent months and the common challenges, regardless of industry, that I heard at conferences, in peer discussions and within my own company.  I’ll follow up this post soon with some summary points on what the biggest pain points seem to be, but my answer to this question will give you a pretty good idea.

    So, what’s the answer?  Simple (simple to say, not do).  The answer is none of the above.  The most important feature to implement in your web 2.0 strategy is integration with existing systems and processes.  Sad, this isn’t the funnest answer.  It’s not roll out a blogging strategy or a product wiki or an influencer program or a feedback management system or forums or …

    It turns out that Web 2.0 projects are really not that hard to implement – getting to market quickly with a new service isn’t all that difficult and in many organizations there is a premium placed on shipping things that are very visible.  What I’ve seen is that the premium on speed and visibility drives most companies to leverage vendor / outsourced solutions for deployment.  It’s faster and easier than working with IT.  There’s also a budget issue here, vendor dollars are easier in most places than incremental IT expense.  This means you quickly end up with multiple suppliers and multiple platforms for your web 2.0 projects – all of which are sitting both organizationally and operationally outside your existing systems, processes and infrastructure.  This is a problem in user experience, in driving organizational culture change, and in measuring business impact.  Community works because you get critical mass, it’s easy to use and there is social proof or evidence of shared value in participation.  Do you have multiple points of authentication as your users move across your communities?  Does your reputation/recognition model transfer across properties?  Do you capture differing depth of profile data?  Is it evident why?  Is the user experience jarring from one venue to the next?  Is there a clear workflow for how the various touch points integrate? How discoverable are the assets?  How obvious is your org chart based on your online experience (this would be a bad sign, not good)?  On and on.

    Now, let’s say you have all the web experiences integrated.  If you have, send me the url!!! I’d love to see the best practice at scale – please don’t send me threadless.  I love them, they are doing cool stuff, but let’s see a fortune 1000 company example – who should be the envy of the market?  If you have the web experiences integrated, I’m impressed and I’d love to come visit!  The next question is have you integrated these systems with traditional systems and processes (Call management, market research, product quality systems, customer service, CRM, brand monitoring, etc.)?  If you’ve done this, I’m not impressed, I’m blown away! 

    Earlier I blogged about ROI and Web 2.0 as Business transformation.  I’m more convinced than ever that these are the critical issues to be addressed.  I’m curious what you think and hungry for great examples.

    Reality check.  Utilizing 3rd party solutions, despite none of them having the full solution is still the right way to go.  Addressing process and systems integration issues is easier once you have data flowing – so I’d still advocate some deployment first (if you haven’t yet).  But, choose your vendors carefully.  Best in class silo solutions may not be as good as pretty good breadth of functionality solutions.  Professional services capacity is critical.

    Love to know what you think.

    Sean