Feed on
Posts
Comments

I am just recently back from our user conference, the aQuatic user days – you may have seen Kirti Vashee’s blog on in already. We had around a hundred delegates from mainly West Coast customers, but there were lots of really interesting ideas floating around. The most interesting for me related to a thread that has been cropping up at all sorts of events I have attended recently: the importance of the community in customer engagement.

Francis Tsang, Senior Director of Globalization at Adobe started the ball rolling a three weeks ago, in a great presentation he gave at the CNGL meeting we were attending together as members of the CNGL Advisory Board. Instead of talking about technology he devoted the entire talk to the customer and how Adobe is working on customer engagement.

The big issue here is that the community is becoming the most important resource for customers interacting with, wanting to find out, or complain about, your products. And the catch is that right now there is almost nothing you can do about it; the content is created by people who don’t work for you. It is no longer one-way traffic – with companies creating content about their products for consumers – but rather it’s a relationship. The community creates valuable content, which companies want to make available to as many of their customers as possible. Also at the CNGL meeting was Greg Oxton from the Consortium for Service Innovation – and he was talking about pretty much the same thing.

What does this mean for Information Quality? Well, some people say that IQ doesn’t matter to the community. But they are wrong; majorly wrong. Let’s just think about product forums for a moment: you want your forum content to be available to the community, not just to the person or people following a particular thread. So you need to make threads findable and comprehensible:

  • Findable means that they can be indexed effectively for search (aka SEO), which ultimately comes down to tying your corporate terminology and taxonomy to the community jargon and folksonomy. Findable also means that you can find information in a language which is not your own.
  • Comprehensible means that once you have found some information you can understand it, even if you are reading it in a language which is not your own. You will also, as a company, want to know what your Chinese user community knows, and what they think of you. You might even be thinking, like most high-tech companies are, of translating forum content on demand with MT. IQ is the critical enabler for MT.

For all of these reasons, IQ is critical to the success of a strategy of “embracing your user community”. But obviously the idea of controlling the content is not going to work. The best we can hope for is to nurture good content. In much the same way as marketing departments are learning to get beyond the idea of controlling their company’s message; the after-sales experience also needs to embrace the uncontrollability of the community.

This post is too long, I will write more about how I think you can nurture community IQ another day…

The history of machine translation is a fairly turbulent story of boom and bust, broken promises and shattered dreams (and some spectacular successes). With the advent of Statistical Machine Translation (SMT), history has repeated itself with uncanny precision. I would say we are now between Phases 2 and 3 of the famous Gartner Hype Cycle (which, annoyingly, is not a cycle at all):

The Gartner Hype Cycle

For the last 10 years or so, researchers have been telling us that SMT represented a revolution in machine translation; that there would be no more linguistics, no more rules, just data. “Give me enough data,” went their motto, “and we can work miracles!’. Well Google has enough data, but they still have their limitations. I tried some things out:

  1. Ich will diesen Satz übersetzen
    Google says:  I want to translate this sentence

Perfect! If only we could always write like this…

  1. Ich will nur dass diser Satz richtig übersetzt wird
    Google says:  I just want that images this sentence is translated correctly.
    Should be:     I just want this sentence to be translated correctly

This is not so great. It just doesn’t make sense – where did “images” come from? So what went wrong?

Well I made two simple mistakes. There should be a comma after “nur” and “diser” should be “dieser”. Let’s fix those issues and try again:

  1. Ich will nur, dass dieser Satz richtig übersetzt wird.
    Google says: I only want that this sentence is translated correctly.

Much better, but sounds a bit funny to my (British) English ears. It’s not wrong, just a bit stilted.

Now let’s try something a bit more difficult (although by no means unusual):

  1. Ich möchte bitte den Satz übersetzen lassen
    Google says: I would like to translate the sentence

Now this translation sounds good (if you don’t know German), but it’s actually *wrong*. It should be “I would like to have this sentence translated”. A subtle, but quite possibly technically significant, difference.

Now I am not Google-Translate-bashing here; SMT is a great technology; but it’s not magic. Errors in the input to these systems will always lead to unreliable results – yes, you still have to care about the quality of your source content.

You also, by the way, also still need to care about branding, compliance, and liability in your source content – these issues won’t not look after themselves by magic either.

I have been very busy helping establish our new Japanese subsidiary.  On a recent trip to Tokyo, I got to thinking again about a favourite topic of mine: applying industrial production methods to information development. What would best practice in Japanese production methods look like if applied to creating product information? The Japanese are famous for having made a science out of observing American companies in the 50s; they developed a formal, repeatable model for ensuring that the production of anything from automobiles to zip fasteners was optimally efficient and reliable – without compromising quality. These methods enabled Toyota to become the biggest automotive company in the world (and YKK the biggest zip manufacturer). The quality challenges that Toyota are now facing are seen as a result of the company failing to live up to its own principles. There is no doubt that these deeply entrenched principles are still part of what makes Japan a technological powerhouse. So how do these principles apply to information development?

Buy-In

According to the principle of nemawashi (根回し) (“laying the groundwork, building consensus”), it’s critical to agree what your standards are. For product information this usually means discussing, agreeing, and then publishing writing standards for all to see. IBM and other major companies even sell theirs. A crucial part of any production project is the buhinhyou (部品表), the bill of materials: this equates with setting the technical terminology (basically, the naming of things). Agreeing your terminology is an indispensible part of setting information standards.

Deploy

Once you have set your standards you have to apply them. Quality management comes in two flavours: quality assurance and quality control. In the Japanese model, quality assurance is all about poka-yoke (ポカヨケ), meaning to avoid (yokeru) inadvertent errors (poka) and jidoka (自働化) (“automation with human intelligence”). Both of these concepts are about detecting errors and fixing them as they occur – not after the fact. In information quality terms this means giving feedback on issues as soon as information is created.

Control

In terms of quality control, the key issue is to have the process set up to prevent poor quality from getting through. The concept of andon (行灯) (“warning sign”) means giving a clear (unmissable) signal when quality issues arise. Defining quality gates for your information as goes through the production process is a crucial part of information quality (IQ) management. A second part of this is genchi genbutsu (現地現物) (“go and see for yourself”) means that management should go and look at issues for themselves rather than relying on second-hand accounts. In terms of an IQ strategy, this means that metrics and reporting have to offer not just numbers but the ability for management to drill down to the reasons for the numbers – in other words, to show the actual errors themselves.

Run and Optimize

The goal of all this is to achieve heijunka (平準化) (“production smoothing”) – to produce goods (or in our case, information) at a constant rate (avoiding mura (斑) and muri (無理) two kinds of waste).  A smooth production process means that processes become more predictable and subsequent processes, such as translation in the case of information development, can also be made more efficient and predictable.

All this leads to kaizen (改善) (“continuous improvement”), by which the organization learns to improve itself over time to constantly get better.

What can you expect if you apply these concepts to information development? Well, the same things that the Japanese expect from their production lines:
  • Buy-in from the whole organization; since everyone has had their say in setting [information] standards
  • Predictable, smooth processes for information development
  • Control of costs and resources in creating and disseminating product information
  • The ability to run and optimize processes to continue to achieve shorter time to market
Applied successfully we know that “the Japanese Way” provides a huge competitive advantage in  a fast-changing world where transparent, controllable processes are crucial.
I was looking at the program for the upcoming Content Strategy Forum in Paris in April. One of the presentation abstracts jumped out at me.
Joyce Hostyn from Open Text wrote the following:
“Customer experience is the sum of the experience a customer has with a business, across all channels and touchpoints. An experience always exists and always generates an impression, but seldom by design. No wonder only 8% of customers report their experience with a given company was superior.
What’s the problem? A product is designed in R&D then thrown ‘over the wall’ to marketing whose focus is on promotion rather than education, integration, and refinement. Product information is too often seen as a necessary evil rather than part of the larger experience. The services and sales organizations gear up to sell and service the customer, creating their own content along the way, and often in ways that are inconsistent with the R&D and marketing impressions that have already been created. Too often this silo’d approach results in fragmented experiences and dissatisfied customers.
What would happen if all these groups saw themselves as collaborators working to create a content strategy designed to deliver a superior, holistic, customer experience across all customer touchpoints and all stages of the customer lifecycle? How can we get to this ideal end state?”
I couldn’t have put it better myself!
A few weeks ago I was sitting with Hideo Yanagi and Daniel Kraft talking about how what we do fits into the big picture of enterprise information management. Hideo said “What we do is just the opposite of a spam filter”. What a brilliant intuition!

Most companies spend thousands (or even millions) on spam protection. And don’t get me started on the amounts spend on branding and content creation.

There is a healthy market for controlling incoming information (just ask Symantec, TrendMicro, McAfee and others) addressing the first market. There is also a huge (and bitterly contested) market for internal business information – the long list of combatants includes Autonomy, EMC, Google, IBM, Open Text, Oracle, SAP, etc.

But there is something missing. Who is looking after outbound information?

What are companies doing to ensure that outbound information is as safe as incoming information? Who is making sure that outbound information is as searchable and reusable as internal information? How are companies sure that branding is assured and your information is compliant with national or international regulations?

The answer is, surprisingly, almost no one.

There are some smart companies starting to connect the dots – for instance by trying to agree Information Quality standards across departments such as Marketing, Engineering and Support. But this is currently being driven almost exclusively bottom-up by practitioners, rather than in response to a strategic initiative.

Think about this just in terms of branding: according to about.com, branding is easy:
You [succeed in branding] by integrating your brand strategies through your company at every point of public contact.
Clearly “every point of contact” means more than just the website. It means all your customer communication.

It seems to me that CIOs and CMOs need to be developing an Information Quality Strategy – to work out how they want to communicate as a company with their customers. It might at the same time be a good idea to work out some tactics to make sure they can enforce company policy on information that will go to customers. This includes everything; from the website, advertising  and pre-sales materials before the deal is done, to technical support and after-care material for the rest of the customer’s time with the product.

What are the risks of not doing this? Well, I have seen time and again how disconnects between marketing, sales and support lead to products losing their key differentiation in the market. The costs of disconnected product information for global companies can be dramatic. If you are trying to deliver information to a global support organization in local languages, a successful Information Quality Strategy can reduce costs by up to 30%, or, as I prefer to think of it, you can be selling products in four markets for the price of three.