I love discussions about Service Management! So, you can probably understand that I quickly opened an e-mail from eSeminars (
http://www.eseminarslive.com) with the subject line of "The race for Business Service Management".
I did not find what I was expecting, but the again I did not have my IT hat on. While this seminar was on IT tools, I was looking for something, on a strategic level, on managing the relationship between customers and an organization.
It shows though, the value of a good subject line. No wonder direct marketing copywriters spend plenty of time on those few words on the outside of an envelope.
But back to service management, the kind I grew up with back in Europe (long story... maybe another time). In the early/mid 80's Richard Normann published his book on Service Management. [ Comment: While I have since seen lots of comments suggesting this is not the best book on this subject ("Meaningless" "...not always consistent or complete") it was still the book of choice in my circles back then.] And while the concept may not have originated with Normann, the term "Moment of Truth" forever got imprinted on my mind.
To me, the Moment of Truth, where customer and organization meets - is something we need to pay particular attention to. It is in this "Moment" that our Brands, Quality etc become real to the customers, and they use their experience from these Moments as a basis for future decision making. Think about it! Have you ever paid a higher price "somewhere else" because service was poor where you initially went?
An the "Moment" is everywhere - in staff blogs, on the phone, via e-mail, web, through Word-Of-Mouth" etc etc. How our company and products/services are perceived, depends on how the "customers" reacts to/remembers these moments.
Two examples I've seen over the last year comes to mind ....
- a software developer with lots of dead links on their otherwise nice web site. Would you trust the code of a developer that can't even get the links right on a 5 page static web site? Not me. But this company obviously didn't mind. Actually, one of their senior managers later "blasted me" for even suggesting to his staff theat the site should be updated to take care of these - relatively few - errors.
- another software developer - an ASP based service ... promising their distribution network a certification & training program. A few days before launch I had still not seen even an outline of how this would take place. I hope they have it fixed by now, I know they made some major changes, but again ... would you trust a supplier that promises you one thing but never delivers? Not me, at least not if this lack of care for me is consistent over a series of issues.
Time to go, I have an interesting seminar to go to ... on early stage financing ...
By the way ... if you've read my last posting a couple of weeks ago ... you probably have been thinking that I did not follow my own advice on keeping things up to date. Both yes and no! YES - my earlier blogs were more frequent. NO - every two weeks might be fine if that is what the audience expects. That being said ... more often is likely better. I saw somewhere, today or in the last couple of days, that they recommend smaller paragraphs a couple of times a day instead of a long blurb now and then.
Feedback appreciated.