Tag: Customer Service

  • Laser-like accuracy

    Word reaches me this morning of yet another incident of Bank Of Ireland double-dipping laser card transactions on or around a Bank Holiday.

    BOI will, doubtless, claim that this is a once off and hasn’t happened before. That’s what they said the last time (when it had actually happened before). Furthermore, I hope that BOI are more certain this time as to the root cause (last time out it was variously “retailer error” or “a software upgrade glitch”).

    And hopefully their process for catching “shadow transactions” which lead to the double-dipping will kick into play and actually refund the customers affected  (which if this glitch is on the scale of their 2009 one could be up to 200,000 card holders).

    For reference the relevant blog posts are:

    http://obriend.info/2009/09/09/bank-of-ireland-double-charging/

    http://obriend.info/2009/09/09/bank-of-ireland-double-charging-a-clarifying-post/

    http://obriend.info/2009/09/10/bank-of-ireland-overcharging-another-follow-up/

    http://obriend.info/2009/10/28/bank-of-ireland-again/

    The issue also featured over on IQTrainwrecks.com.

    My €0.02: This issue appears to manifest itself around Bank Holidays. This suggests a batch load process or some human triggered action doesn’t work correctly when there is a Bank Holiday. Having a process to detect the double-dipped transactions is not a fix, as if it doesn’t work (as seems might be the case here) then the incorrect data gets through.

    BOI might want to pay attention to Ferguson v British Gas, which while a UK case, could be arguable precedent for the view that Irish Courts won’t care how complex your IT systems are if a customer is impacted through a failure of your systems to process information correctly.

    BOI need to identify the precipitating root cause of this problem, based on the data they have available… I’d start with looking at the dates of incidents (BOI should have more data than newspaper headlines to go on) and seeking to confirm or disprove the ‘Bank Holiday hypothesis’.

    Relying on a ‘scrap and rework’ kludge that might itself fail is not a sustainable approach to ensuring information quality or quality of customer service.

  • Who then is my customer?

    Two weeks ago I had the privilege of taking part in the IAIDQ’s Ask the Expert Webinar for World Quality Day (or as it will now be know, World Information Quality Day).

    The general format of the event was that a few of the IAIDQ Directors shared stories from their personal experiences or professional insights and extrapolated out what the landscape might be like in 2014 (the 10th anniversary of the IAIDQ).

    A key factor in all of the stories that were shared was the need to focus on the needs of your information customer, and the fact that the information customer may not be the person who you think they are. More often than not, failing to consider the needs of your information customers can result in outcomes that are significantly below expectations.

    One of my favourite legal maxims is Lord Atkin’s definition of who your ‘neighbour’ is who you owe legal duties of care to. He describes your ‘neighbour’ as being anyone who you should reasonably have in your mind when undertaking any action, or deciding not to take any action. While this defines a ‘neighbour’ from the point of view of litigation, I think it is also a very good definition of your “customer” in any process.

    Recently I had the misfortune to witness first hand what happens when one part of an organisation institutes a change in a process without ensuring that the people who they should have reasonably had in their mind when instituting the change were aware that the change was coming.

    My wife had a surgical procedure and a drain was inserted for a few days. After about 2 days, the drain was full and needed to be changed. The nurses on the ward couldn’t figure out how to change my wife’s drain because the drain that had been inserted was a new type which the surgical teams had elected to go with but which the ward nurses had never seen before.

    For a further full day my wife suffered the indignity of various medical staff attempting to figure out how to change the drain.

    1. There was no replacement drain of that type available on the ward. The connections were incompatible with the standard drain that was readily available to staff on the ward and which they were familiar with.
    2. When a replacement drain was sourced and fitted, no-one could figure out how to actually activate the magic vacuum function of it that made it work. The instructions on the device itself were incomplete.

    When the mystery of the drain fitting was eventually solved, the puzzle of how to actually read the amount of fluid being drained presented itself, which was only of importance as the surgeon had left instructions that the drain was to be removed once the output had dropped below a certain amount. The device itself presented misleading information, appearing to be filled to one level but when emptied out in fact containing a lesser amount (an information presentation quality problem one might say).

    The impacts of all this were:

    • A distressed and disturbed patient increasingly worried about the quality of care she was receiving.
    • Wasted time and resources pulling medical staff from other duties to try and solve the mystery of the drain
    • A very peeved and increasingly irate quality management blogger growing more annoyed at the whole situation.
    • Medical staff feeling and looking incompetent in front of a patient (and the patient’s family)

    Eventually the issues were sorted out and the drain was removed, but the outcome was a decidedly sub-optimal one for all involved. And it could have been easily avoided had there been proper communication about the change to the ward nurses and the doctors in the department from the surgical teams when they changed their standard. Had the surgical teams asked the question of who should they have in their minds to communicate with when taking an action, surely the post-op nurses should have featured in there somewhere?

    I would be tempted to say “silly Health Service” if I hadn’t seen exactly this type of scenario play out in day to day operations and flagship IT projects during the course of my career. Whether it is changing the format of a spreadsheet report so it can’t be loaded into a database or filtered, changing a reporting standard, changing meta-data or reference data, or changing process steps, each of these can result in poor quality information outcomes and irate information customers.

    So, while information quality is defined from the perspective of your information customers, you should take the time to step back and ask yourself who those information customers actually are before making changes that impact on the downstream ability of those customers to meet the needs of their customers.

  • A game changer – Ferguson v British Gas

    Back in April I wrote an article for the IAIDQ’s Quarterly Member Newsletter picking up on my niche theme, Common Law liability for poor quality information – in other words, the likelihood that poor quality information and poor quality information management practices will result in your organisation (or you personally) being sued.

    I’ve written and presented on this theme many times over the past few years and it always struck me how people started off being in the “that’s too theoretical” camp but by the time I (and occasionally my speaking/writing partner on this stuff, Mr Fergal Crehan) had finished people were all but phoning their company lawyers to have a chat.

    To an extent, I have to admit that in the early days much of this was theoretical, taking precedents from other areas of law and trying to figure out how they fit together in an Information Quality context. However, in January 2009 a case was heard in the Court of Appeal in England and Wales which has significant implications for the Information Quality profession and which has had almost no coverage (other than coverage via the IAIDQ and myself). My legal colleagues describe it as “ground breaking” for the profession because of the simple legal principle it creates regarding complex and silo’d computing environments and the impact of disparate and plain crummy data. I see it as a clear rallying cry that makes it crystal clear that poor information quality will get you sued.

    Recent reports (here and here) and anecdotal evidence suggest that in the current economic climate, the risk to companies of litigation is increasing. Simply put, the issues that might have been brushed aside or resolved amicably in the past are now life and death issues, at least in the commercial sense. As a result there is now a trend to “lawyer up” at the first sign of trouble. This trend is likely to accelerate in the context of issues involving information, and I suspect, particularly in financial services.

    A recent article in the Commercial Litigation Journal (Frisby & Morrison, 2008) supports this supposition. In that article, the authors conclude:

    “History has shown that during previous downturns in market conditions, litigation has been a source of increased activity in law firms as businesses fight to hold onto what they have or utilise it as a cashflow tool to avoid paying money out.”

    The Case that (should have) shook the Information Quality world

    The case of Ferguson v British Gas was started by Ms. Ferguson, a former customer of British Gas who had transferred to a new supplier but to whom British Gas continued to send invoices and letters with threats to cut off her supply, start legal proceedings, and report her to credit rating agencies.

    Ms Ferguson complained and received assurances that this would stop but the correspondence continued. Ms Ferguson then sued British Gas for harassment.

    Among the defences put forward by British Gas were the arguments that:

    (a) correspondence generated by automated systems did not amount to harassment, and (b) for the conduct to amount to harassment, Ms Ferguson would have to show that the company had “actual knowledge” that its behaviour was harassment.

    The Court of Appeal dismissed both these arguments. Lord Justice Breen, one of the judges on the panel for this appeal, ruled that:

    “It is clear from this case that a corporation, large or small, can be responsible for harassment and can’t rely on the argument that there is no ‘controlling mind’ in the company and that the left hand didn’t know what the right hand was doing,” he said.

    Lord Justice Jacob, in delivering the ruling of the Court, dismissed the automated systems argument by saying:

    “[British Gas] also made the point that the correspondence was computer generated and so, for some reason which I do not really follow, Ms. Ferguson should not have taken it as seriously as if it had come from an individual. But real people are responsible for programming and entering material into the computer. It is British Gas’s system which, at the very least, allowed the impugned conduct to happen.”

    So what does this mean?

    In this ruling, the Court of Appeal for England and Wales has effectively indicated a judicial dismissal of a ‘silo’ view of the organization when a company is being sued. The courts attribute to the company the full knowledge it ought to have had if the left hand knew what the right hand was doing. Any future defence argument grounded on the silo nature of organizations will likely fail. If the company will not break down barriers to ensure that its conduct meets the reasonable expectations of its customers, the courts will do it for them.

    Secondly, the Court clearly had little time or patience for the argument that correspondence generated by a computer was any less weighty or worrisome than a letter written by a human being. Lord Justice Jacob’s statement places the emphasis on the people who program the computer and the people who enter the information. The faulty ‘system’ he refers to includes more than just the computer system; arguably, it also encompasses the human factors in the systemic management of the core processes of British Gas.

    Thirdly, the Court noted that perfectly good and inexpensive avenues to remedy in this type of case exist through the UK’s Trading Standards regulations. Thus from a risk management perspective, the probability of a company being prosecuted for this type of error will increase.

    British Gas settled with Ms Ferguson for an undisclosed amount and was ordered to pay her costs.

    What does it mean from an Information Quality perspective?

    From an Information Quality perspective, this case clearly shows the legal risks that arise from (a) disconnected and siloed systems, and (b) inconsistencies between the facts about real world entities that are contained in these systems.

    It would appear that the debt recovery systems in British Gas were not updated with correct customer account balances (amongst other potential issues).

    Ms. Ferguson was told repeatedly by one part of British Gas that the situation was resolved, while another part of British Gas rolled forward with threats of litigation. The root cause here would appear to be an incomplete or inaccurate record or a failure of British Gas’ systems. The Court’s judgment implies that that poor quality data isn’t a defence against litigation.

    The ruling’s emphasis on the importance of people in the management of information, in terms of programming computers (which can be interpreted to include the IT tasks involved in designing and developing systems) and inputting data (which can be interpreted as defining the data that the business uses, and managing the processes that create, maintain, and apply that data) is likewise significant.

    Clearly, an effective information quality strategy and culture, implemented through people and systems, could have avoided the customer service disaster and litigation that this case represents.  The court held the company accountable for not breaking down barriers between departments and systems so that the left-hand of the organization knows what the right-hand is doing.

    Furthermore, it is now more important than ever that companies ensure the accuracy of information about customers, their accounts, and their relationship with the company, as well as ensuring the consistency of that information between systems. The severity of impact of the risk is relatively high (reputational loss, cost of investigations, cost of refunds) and the likelihood of occurrence is also higher in today’s economic climate.

    Given the importance of information in modern businesses, and the likelihood of increased litigation during a recession, it is inevitable: poor quality information will get you sued.

  • Golden Databases – a slight return

    Last week I shared a cautionary note about companies relying on their under-touched and under-loved Customer databases to help drive their business as we hit the bottom of the recessionary curve. The elevator pitch synopsis… Caveat emptor – the data may not be what you think it is and you risk irritating your customers if they find errors about them in your data.

    Which brings me to Vodafone Ireland and the data they hold about me. I initially thought that the poor quality information they have about me existed only in the database being used to drive their “Mission Red” campaign. For those of you who aren’t aware, “Mission Red” is Vodafone Ireland’s high profile customer intimacy drive wher they are asking customers to vote for their preference of add-on packages. Unfortunately, what I want isn’t listed under their options.

    What I want is for Vodafone Ireland to undo the unrequested gender reassignment they’ve subjected me to. (more…)

  • The Customer perspective on Information Quality

    A short post today. I promise.

    Yesterday’s Dilbert made me laugh. As a telco guy I’m familiar with the lengths my industry will go to to create complicated contracts that can ‘obscure’ the total cost of a phone package. It was nice to see that getting a character all to itself in Dilbert.

    But what made me laugh most of all was the number of root causes of Information Quality problems which are mentioned in just two boxes of this strip:

    Dilbert.com
    Dilbert (c) Scott Adams, 19th April 2009
    1. Unlabelled strings of code – this is DATA, not INFORMATION because it lacks CONTEXT to make it ACTIONABLE
    2. Web forms or applications not designed to make sense with the information requested (fields too short for the code).
    3. Letters looking like numbers (and vice versa).

    If your customer can’t complete a rebate process due to any of the above issues (or similar), then your information quality focus is wrong (or non-existent) and your customers will go elsewhere eventually.

    Wooing price sensitive customers (and aren’t we all these days?) with rebates or discounts but then having processes which fail to successfully operate due to poor quality planning for quality information and quality outcomes means that any competitor who comes close to you on price but can make the customer experience easier and more transparent is likely to win business from you.

    Begin with the end in mind. Isn’t the end you want a happy customer who will buy again from your company (and maybe refer their friends to you)?

  • Final post and update on IBTS issues

    OK. This is (hopefully) my final post on the IBTS issues. I may post their response to my queries about why I received a letter and why my data was in New York. I may not. So here we go..

    First off, courtesy of a source who enquired about the investigation, the Data Protection Commissioner has finished their investigation and the IBTS seems to have done everything as correct as they could, in the eyes of the DPC with regard to managing risk and tending to the security of the data. The issue of why the data was not anonymised seems to be dealt with on the grounds that the fields with personal data could not be isolated in the log files. The DPC finding was that the data provided was not excessive in the circumstances.

    [Update: Here’s a link to the Data Protection Commissioner’s report. ]

    This suggests to me that the log files effectively amounted to long strings of text which would have needed to be parsed to extract given name/family name/telephone number/address details, or else the fields in the log tables are named strangely and unintuitively (not as uncommon as you might think) and the IBTS does not have a mapping of the fields to the data that they contain.

    In either case, parsing software is not that expensive (in the grand scheme of things) and a wide array of data quality tools provide very powerful parsing capabilities at moderate costs. I think of Informatica’s Data Quality Workbench (a product originally developed in Ireland), Trillium Software’s offerings or the nice tools from Datanomic.

    Many of these tools (or others from similar vendors) can also help identify the type of data in fields so that organisations can identify what information they have where in their systems. “Ah, field x_system_operator_label actually has names in it!… now what?”.

    If the log files effectively contained totally unintelligible data, one would need to ask what the value of it for testing would be, unless the project involved the parsing of this data in some way to make it ‘useable’? As such, one must assume that there was some inherent structure/pattern to the data that information quality tools would be able to interpret.

    Given that according to the DPC the NYBC were selected after a public tender process to provide a data extraction tool this would suggest that there was some structure to the data that could be interpreted. It also (for me) raises the question as to whether any data had been extracted in a structured format from the log files?

    Also the “the data is secure because we couldn’t figure out where it was in the file so no-one else will” defence is not the strongest plank to stand on. Using any of the tools described above (or similar ones that exist in the open source space, or can be assembled from tools such as Python or TCL/TK or put together in JAVA) it would be possible to parse out key data from a string of text without a lot of ‘technical’ expertise (Ok, if you are ‘home rolling’ a solution using TCL or Python you’d need to be up to speed on techie things, but not that much). Some context data might be needed (such as a list of possible firstnames and a list of lastnames, but that type of data is relatively easy to put together. Of course, it would need to be considered worth the effort and the laptop itself was probably worth more than irish data would be to a NYC criminal.

    The response from the DPC that I’ve seen doesn’t address the question of whether NYBC failed to act in a manner consistent with their duty of care by letting the data out of a controlled environment (it looks like there was a near blind reliance on the security of the encryption). However, that is more a fault of the NYBC than the IBTS… I suspect more attention will be paid to physical control of data issues in future. While the EU model contract arrangements regarding encryption are all well and good, sometimes it serves to exceed the minimum standards set.

    The other part of this post relates to the letter template that Fitz kindly offered to put together for visitors here. Fitz lives over at http://tugofwar.spaces.live.com if anyone is interested. I’ve gussied up the text he posted elsewhere on this site into a word doc for download ==> Template Letter.

    Fitz invites people to take this letter as a starting point and edit it as they see fit. My suggestion is to edit it to reflect an accurate statement of your situation. For example… if you haven’t received a letter from the IBTS then just jump to the end and request a copy of your personal data from the IBTS (it will cost you a few quid to get it), if you haven’t phoned their help-line don’t mention it in the letter etc…. keep it real to you rather than looking like a totally formulaic letter.

    On a lighter note, a friend of mine has received multiple letters from the Road Safety Authority telling him he’s missed his driving test and will now forfeit his fee. Thing is, he passed his test three years ago. Which begs the question (apart from the question of why they are sending him letters now)… why the RSA still has his application details given that data should only be retained for as long as it is required for the stated purpose for which it was collected? And why have the RSA failed to maintain the information accurately (it is wrong in at least one significant way).

  • Things that peeve me on the web

    A few things peeve me on the web. One of them is website form validators that do not recognise tlds other than .com, .org or a country tld. These validators seem oblivious to the fact that since 2000 ICANN has been rolling out ‘new’ tlds to take the ‘pressure’ off the .com and .org domains and .info has been active as a tld since 2001.

    I chose .info for my domain name partly because my old obriend.com domain was hijacked and partly because that problem manifested an opportunity for me to rebrand myself on-line with a domain name that related to me and my interests. Obriend.info is a website dedicated to information about OBrienD (me) and where OBrienD can discuss topics relating to Information Quality and Information Management (Info).

    However I find myself having to fall back on other email addresses such as my gmail or IAIDQ email address when filling out web forms as many validators (often on very reputable and high-profile sites) reject .info as part of an email address, in blissful ignorance of the fact that up to March 2007 there were 4 million .info domains registered with 1.6 million .info websites active (this being one of them).

    This is a small but significant information quality problem. The ‘master data’ that is being used to support the validation processes on these sites is incomplete, out of date and inaccurate. Web developers should take the time to verify if the snippets of code they are using to validate email addresses contain all valid TLDs and if not they should update their code. Not doing so results in lost traffic to your site, and in the case of registration forms for e-commerce sites it costs you a sale (or three).

    Another thing that peeves me is the use of (or not) of apostrophes in email addresses. Names like O’Donnell and the usual spelling of O’Brien have apostrophes. Some organisations allow them as part of their email addresses (joe.o’connor@thisisnotarealdomain.lie). For some reason however, many CMS platforms, website validators etc. don’t handle this construct particularly well. Indeed I’ve seen some chat forums where ‘experts’ advise people to leave out the apostrophe to avoid problems, even though the apostrophe is perfectly permissable under the relevant RFC standards.

    I’ve experienced the problem with Joomla and Community Builder on the IQ Network website which required me to manually work around the issue as I am not a good enough php developer to hack either application to fix the problem in a way that doesn’t cause other problems (such as the apostrophe being displayed back with an escaping backslash – ” \’ “.

    On the web you are in a global community. Just because your country/culture doesn’t use apostrophes or accenting characters doesn’t mean that they are not valid. Your code should be built to handle these occurences and to avoid corrupting data. Joe O’Connor’s name (to return to our fictional example) is not Joe O\’Connor. He should not see his name displayed as such on a form. Furthermore it should not be exported as such from a database into other processes.

    Likewise, if Joe.O’Connor@fictionaldomain.info decides he wants to register at your site you should make sure you can correctly identify his tld as valid and get his name right.

  • Dell Hell Ireland (and other flavours) on Google

    So for shits and giggles I decided to google Dell Hell and Ireland. (The wife is out for the night, I’m bored, it seemed like a good idea at the time).

    http://www.google.ie/search?sourceid=navclient&hl=en-GB&ie=UTF-8&rlz=1T4GGLF_en-GBIE226IE228&q=dell+hell+ireland

    To increase the sample size, I removed the reference to “Ireland” and instead googled for “Dell Hell Information Quality”… frack me, there I am again – the top 2 (tonight, 27 July 07).

    http://www.google.ie/search?sourceid=navclient&hl=en-GB&ie=UTF-8&rlz=1T4GGLF_en-GBIE226IE228&q=dell+hell+information+quality

    So to be fair to Dell I removed the reference to “hell” to see how the DoBlog might fare with the Great Search Algorithm in the sky. This was a ‘positive control’. Wasn’t I pleasantly surprised when I was again the top 2 listed links on this day…

    http://www.google.ie/search?sourceid=navclient&hl=en-GB&ie=UTF-8&rlz=1T4GGLF_en-GBIE226IE228&q=dell+information+quality

    Not yet in Damien Mulley/SkyHandling Partners/”the server cannae take it Captain, she’s goin’ te blow” territory one can always dream…

    I googled a few other combinations… for “Dell quality Information” I was results 3 and 4 out of 16,800,000. That was a very neutral query. Still other combinations were picked but I can’t be bothered typing them … the screenshots below will show you the story.

    What I learned is that I am missing a very important tag from these posts… “Dell Quality”. That will be fixed tonight.

    Also by googling for Dell Quality and Ireland I found this pdf of a Dell presentation. I was interested to read this quote from Michael Hammer (Business Process Re-engineering guru) towards the end of the slides… I’ve highlighted a few words that leapt out at me.

    “ The 21st Century Belongs to the
    Process Organization Centered on
    Customers
    and…Operates With
    High Quality
    , Enormous Flexibility,
    Low Cost, and Extraordinary Speed.”

    With regards to my broken keyboard Dell are hitting the marks on this one. Quickly dealt with, within the agreed time period – the failure of the delivery is down to me… (sorry Dell, I’ll sort it out as soon as I can).

    My Graphics card issue however is a result of a failed process (assembly) as a result of poor quality information (either the assembler didn’t know to put in a 256mb card or couldn’t tell a 128mb card from a 256mb card) which has dragged on now for five months (which is extraordinary speed, just not in a good way). The fact that the issue still isn’t resolved and I’ve got a second ‘Customer Advocate’ from Round Rock Texas on the case now is indicative of how wide of their goals Dell are.

    (A big shout out to Rick and John… hope you guys are reading this as you reached out and I believe you have done your best to help with my situation. Elizabeth in Dublin… if you are back in the office could you PLEASE respond to the last few emails I’ve sent you as they are quite important… the email address you gave for the person who was covering for you kept bouncing back.)

    Joseph Juran, the Quality Management guru put it very well:

    “They thought they could make the right speeches, establish broad goals, and leave everything else to subordinates… They didn’t realize that fixing quality meant fixing whole companies, a task that cannot be delegated.”

    Joseph M. Juran, “Made in the USA: A Renaissance in Quality”, Harvard Business Review, July 1, 1993

    Deming’s Point 10 tells us “Eliminate slogans, exhortations and numerical targets for the workforce since they are divisory. The difficulties belong to the whole system”.

    Firefighting does not improve quality, especially when the fire is let smoulder on for nearly half a year (and a whole new product launch).

    Dell Information Quality search results

    Dell quality Ireland

    Dell quality information

    Dell Hell Ireland

    I have others but I can’t be bothered to put them up… I think my point is made.

    Perhaps Dell should consider getting in contact with the knowledgable practitioners in the International Association for Information and Data Quality (www.iaidq.org) who might be able to share some pointers on how to address the root causes of this problem.

  • Dell Hell… but not mine, but perhaps a different circle of the same techno hell

    The other guy’s story

    Came across this on Tom Raftery’s blog. Looks like Tom’s guest writer Frank P had ‘issues’ with Dell when trying to buy some kit off them. A barrier had been created that prevented him from buying a machine from the UK Dell outlet store simply (it would seem) because the UK uses sterling and the Irish Republic uses the Euro.

    This does not seem to be a problem for Marks and Spencer, who will happily charge my credit card in Euros or Sterling when I am buying bits and bobs when on trips to London. Nor do the people in the UK I’ve bought stuff from (including a laptop and spares for my guitar) on ebay have any problems selling to the Republic of Ireland just because we use Euros… they let paypal sort the currency conversion for them and whammo the wifey has a new toy and I can get back to trying to hammer a few tunes out of my much abused fender strat.

    Quality is about meeting or exceeding customer expectations. Deming advises us in his 14 Points to ‘break down barriers between departments’. To meet FrankP’s request, Dell could have simply charged him a slightly higher fee to cover currency conversion costs and transport from the UK (chances are the machine is in a warehouse in Ireland though…). Bingo- one sale, one happy customer. The barrier might have more to do with internal accounting for products by the market they are sold to… but that is a supposition on my part.

    The economics of this ‘non-quality’

    If I’m right, that is just crazy and is an excellent example of how ‘stovepiped’ management of ‘battling business units’ is a fricking recipe for disaster in most businesses and how such artificial barriers to delivery of quality products or service should be torn down.

    It’s like having a football team with defenders who won’t pass the ball to their strikers who are in the box with a clear shot on goal and the keeper off his line just because the strikers are paid in Euros while the defenders get their cheques in sterling. (Jaysus, I think that was a football metaphor.. not sure what it means or if it makes sense but it reads well).

    If you have ‘seconds’ stock or ‘returns’ you have inventory on hand. That costs money to store and if not sold costs money to dispose of. The longer it is stock on hand (in a warehouse gathering dust) the faster the resale price is dropping (due to obsolescence and the entry of newer/better products into the market at the original price point) and the less likely you are to recoup the cost of production, cost of storage and other related costs. Eventually the inventory becomes ‘below-zero’ in that it will have cost you more than you’ll make by selling it… resulting in declining profit margins.

    In order to reduce the costs to your business you should really be trying to sell that fecker to anyone (within the bounds of the law) who comes knocking/calling/writing as soon as possible without putting seemingly petty administrative barriers in the way. Doing so results in a business process that does not meet the expectation of the customer and as such is not a process that delivers ‘quality’. Furthermore it creates a risk of negative profit margins in the business.

    Instead Dell got a blog post on a highly trafficked blog (Tom Raferty’s)written by a respected professional pundit on the IT industry and Web2.0 trends (not an amateur by any stretch) where through various comments the customer service issue is discussed at length. And then that post is in turn linked to by me, with my particular perpsective on the issue.

    And for all we know the laptop still sits unsold in its cold warehouse shelf, unloved and spurned by the new Vostros and Inspirons that swank by with their swish coloured lids and ‘more bang for your buck’ specifications. Stick a red nose on that laptop and call it Rudolph. It won’t be let join in any laptop games I can tell you.

    My saga continues

    I have had and continue to have my issues with Dell. Currently I’ve been dealing with John, one of their Customer Advocates, Elizabeth (a Dell Ireland person) and half a dozen others over the past 5 months. At this rate I’ll probably have spoken to more Dell employees than Michael Dell himself by the end of the year.

    To cap things off (no pun intended), the ‘Q’ key on my keyboard broke off on Tuesday (too much angry typing of ‘Quality’ I fear and the end of my career as a ghost-writer for James Bond novels unless I do some business re-organisation of MI6 or cut back on the gadgets).

    HAPPY NEWS

    I contacted Dell support and was dealt with promptly. I was informed I’d have the keyboard today. I arranged to work from home to be available to take delivery here. Unfortunately I missed the call from the courier and will need to try to rearrange delivery (hopefully I can get it tomorrow rather than having to work from home Monday as well).

    Crappy News

    This is the GOOD NEWS. The BAD news is that some strange things happened to my information as it bounced around Dell Customer Support. For one, they changed my name.

    Here is the email I received yesterday informing me of delivery:

    Dear Mr. Brien,

    Thank you for your reply.

    Your call has been logged, and your reference number is [edited out by me]. Keyboard will be with you on next business day, between 09.00 and 17.30 (or other local working hours). If you are office based then please advises your reception of the expected Courier visit. You will be contacted in the event of any unforeseen delays.

    Thank you for giving me the opportunity to assist you. Your case number for this interaction is [edited out by me].

    Thank you again for contacting Dell Hardware E-Support.

    BRIEN” That’s not my name. That annoys me. That’s not good information quality. Why not?

    Well, Dell’s on-line Tech Support form looks like this (once you key in the asset tag that identifies your machine)

    Dell’s Support Site

    I’ve blocked out the asset tag for my machine (for privacy) and you’ll need to click on the thumnail to see the full image but you’ll need to for the rest of this to make sense…
    Note the first two mandatory fields:

    • First Name
    • Last Name

    I won’t go into why this is a bad labelling convention that is Anglo-centric (Given Name/Family Name are better)… for now it is enought that Dell’s form has distinct fields for my Firstname (given name): DARAGH and my Lastname (Family Name): O Brien. That’s what got typed in there. So why/how did Dell decide that the “O” in my name was surplus to requirements?

    Attention to the little details (like getting my name right or ensuring that my laptop ships with the correct graphics card installed) are evidence of a coherent and congruent quality culture. Soundbites, slogans and self-contratulatory marketing materials don’t build such a culture. The IAIDQ is a professional organisation that exists to support the development of ‘Information/Data Quality’ as a management discipline. Their website is www.iaidq.org and Dell employees (or anyone for that matter) will find some useful information there about the root causes and real impacts of these types of problems

    But back to the happy path

    That said… the tech support guy Guaran was great in sorting out the replacement keyboard and I am kicking myself I missed the couriers call when it came bang on schedule.. when you’re good you’re good.

  • Some good quality experiences

    I recently bought a case for my PDA from the lovely people at Proporta. Unfortunately, a few days after getting the case the belt clip disintegrated with the hinge part simply snapping off. I was dismayed.

    By co-incidence that day I received an email from one of Proporta’s customer service people following up on my order. I responded to the email and explained the situation. By return of email I was assured that some replacement belt clips were on the way and I am expecting them soon.

    Proporta have asked me if they can quote my feedback to them in their testimonials… and I say definitely they can as their process seems to be very customer focussed with a quick turn around on issues. I can’t help contrasting that with my experiences with Dell.

    The cost to Proporta of replacing the belt-clip is probably a lot less than the likely referrals or follow on sales that they will get as a result of the positive feedback (and link from this blog). I am likely to buy from them again myself.

    Good quality, be it in products or service, promotes growth and profitability. Well done Proporta.