Retention? Nope.

by Kevin

Ilium Software is really happy to have customers, but not so happy to have them that we would do anything to keep them. On the surface, doing anything seems like ‘bending over backwards’ to satisfy the customer. That’s not a horrible idea - we really try to make people happy within reasonable limits and company policy.

When I say ‘do anything’, I include threatening, badgering, obsfucating, hard-selling, and otherwise retaining.  The first - and quasi-official - thing that I want to get across is that we don’t have a retention policy or a manual. Ilium Software does not have a document that says how to retain customers when they say, “I don’t like [product], I want a refund.”

For more examples and some ranting, keep reading.

Example: The Consumerist [Warning: links in this paragraph may lead to articles containing profanity] is a blog that collects good and bad stories of customer service. A while back, they cracked a story about AOL’s customer retention policy with a stunning recording that a customer made while on the phone with a CSR (customer service representative) to cancel his account. The customer, Vincent, even appeared on national TV with his story. More recently, The Consumerist received a supposed copy of AOL’s retention manual and published it online.

Ilium Software has a ’no questions asked’ return policy. This means that we don’t try to hassle you, give you tons of surveys to fill out, make you jump through flaming hoops, etc.

If you ask for a refund, you may actually be asked a question, but that’s usually if you indicate in the request that you had a specific problem with the software - an error message, failure, etc. When I get a request to refund a purchase that seems motivated by a problem that I know we have a solution for, I offer the solution first. If you don’t want eWallet because it won’t install onto your PDA, but I happen to know how to make it install since you are running into a common problem, I want you to be happy with what you purchased and get it working. If it isn’t going to work, or if you just don’t want to spend the time, that’s fine too. I don’t consider this ‘retention’, more like the original refund request is really a technical support issue and the refund portion is just out of frustration.

In other words, I’ll offer you help if I can, and if you don’t want it, I stop there - I’ll process your refund as soon as I have all the necessary information.

So, to conclude the mostly-official-Kevin-interpretation-of-company-policy statement, we don’t do what AOL and other companies apparently do. If you want a refund, we’re happy to refund you if we can.

If you want to read my personal opinion on this whole ‘retention’ issue, read on. Otherwise, stop. Put down your pencils and do not keep writing.

Warning: personal exclamations of incredulity that may or may not be shared by other people who work for Ilium Software ahead.

I have one question for you, companies that have policies in place to sell a customer on something they don’t want: WHY? I almost feel like the startled, angry use of a profane word or two would be relevant. When I found the stories about AOL on The Consumerist, I was mad.

I try to help customers who have problems leading to a refund request because I want them to be happy with our software, and if the reason they aren’t happy is fixable without a refund, then why not offer it? The exchange is usually pretty short.

Customer: “[Program] won’t install, I get this error, I tried it ten times and it still gave me the error, I want a refund.”

Me: “It looks like you’re having this well-known problem. You can fix it by doing [sequence of steps to fix problem.] If that doesn’t work, let me know and I’ll be happy to refund your purchase.”

You: “Yay, it worked!” Or, sometimes, “I don’t care, refund me,” or, “It didn’t work, refund me.” In which case, I refund you.

I really hope this doesn’t make me into a hypocrite, saying that we don’t try to retain customers, while there I am trying to retain them. If I bought something at a store and angrily stormed up to the service desk demanding to return it because it didn’t do X, and the desk rep said, “oh, did you try this?” and educated me on how to make it work, I don’t think I’d still want to return it. I might feel a little dumb, but I wanted the product in the first place and I can assume I’d still want it if it worked right in the end. I assume this is why most consumer electronics now come with a large graphic on the inside box flap, reading, “STOP! Having problems? Don’t take this back to the store! Call this phone number instead!”

But a manual detailing the process to convince a user they’re wrong? People hired by a company specifically to sell you something you don’t want any more? People whose job future depends on how many people they successfully “win back”? People whose job is to make the customer defend their own reasoning repeatedly in order to ‘satisfy’ them? Give me a break.

Aren’t customers important? Wouldn’t trying to sell someone on something they truly didn’t want just alienate them? Doesn’t it effectively prey on their own confusion, lack of knowledge, or fear of confrontation to get them to do what the company wants? That’s ethically awful in my eyes. I will certainly never, ever refer someone to AOL since I’ve heard about this mess. I don’t feel afraid saying that publically - why would I want anyone I know to have to potentially deal with customer support reps who won’t let them go? Why would anyone want that?

It makes me wonder if whoever made this business decision ever ends up on the other side, like with spam (Do spammers hate spam too?) I try to imagine an executive putting in motion a system to retain customers, then having to discontinue his cell phone and having to say, “pretty please with sugar on top” to the CSR.

I have had one exactly one experience with a retention department. I cancelled my mobile phone service with T-Mobile to switch to Cingular for various reasons, mostly because I wanted a phone T-Mobile didn’t have. The exchange went something like this:

Them: “Is there a particular reason you wish to cancel service?”

Me: [Lists reasons]

Them: “Is there anything else we could do to make you wish to stay with T-Mobile?”

Me: “Well, not really. You actualy have really good service, I just want to do something that you don’t offer.”

Them: “Okay. Your account will be terminated, you’ll receive a final bill for X amount on date Y, blah blah blah.”

That’s about as far as I want to see ‘retention’ ever go.

Is the bottom line so important, the minimization of ‘churn’ so vital, that a company is willing to do whatever it takes?

I hope that someone who reads this has a different opinion than I do. I  want to see the other side to this, to see what it’s like to be in a position where the decision to forcefully retain customers is one that you or your company feels is necessary. I promise not to create some sort of argument if anyone posts a comment like that, and you can certainly post comments anonymously with our blog system.

Share this article:


Form & Function: A Developer's Perspective

by Marc

How important is appearance? Is it a vital part of any application design? Or just a nice thing to add if you have time for it?

There have been a couple of great posts about this subject today. One of them is at Just Another Mobile Monday and another at Treonauts. Both of these address the subject from the point of view of a user. I thought I’d take a second to discuss it from the developer end.

Creating a great looking app is actually something every developer (well, every developer I know anyhow) wants to do. Actually doing that, though, is something else altogether. There are plenty of roadblocks to making this happen.

Resources This is an obvious one and it affects a lot of small software houses. Designing a really good looking interface takes time and money. If you don’t have the skill in-house, you need to out source and that requires a serious investment. …

Screen Real Estate This is something both of the articles I mentioned talked about. Mobile software needs to take full advantage of the limited screen space mobile devices offer. The challenge here is that a good looking interface takes up space. While it can make the use of space more effective in some cases, more often it uses up screen space that cannot then be used to display data/content/etc..

Making it Work Pretty is one thing. Pretty and functional is another. It is a serious challenge to come up with an interface that not only looks good, but also does its job! (Anyone remember the old IBM commercial where the guys were showing off the animated flaming logo on the website but the site couldn’t handle customer orders?)

“Microsoft Says…” Or “Palm says…” or “HP says…” There have been many times when we’ve wanted to do something a certain way, but in order to achieve that all important approval from the powers above us we had to do it in what we thought was a less effective way. (Ever wonder why so many Windows Mobile apps don’t have an Exit/Quit function?)

Planning for the Future And last of all, when you put a beautiful interface like that onto a product, you’ve just set in virtual-stone how that product will work. Need to add a button for a new feature? Time to redesign the entire interface! Discover that the field isn’t big enough? Gotta order a whole new skin!

OK, so it’s hard to do and there is lots standing in the way. You probably get that by now. The question of course is how much should developers care?

In my opinion, a lot. A plain text data feed has its place but for those programs we use while we’re on the move, over and over throughout the course of our day, it has to be a product that treats us like human beings….not data processors.

For Ilium Software, this is something we are always looking at and as we move toward the future, it’s something that is becoming increasingly important in the evolving mobile software marketplace. It costs money. It costs time. But hopefully in the long run it will pay off.

Share this article:


Common sense is neither common nor sensical. Discuss!

by Kevin

One of my little Google Homepage widgets is for a blog by one James Bach, who knows more about testing than me. A lot more. He recently blogged about his dislike for the words ‘intuition’ and ‘common sense’ being used as explanations in arguments.

Bach has a very good point when it comes to using those two concepts as ways to explain away a problem.

The article also made me think about how often I run into issues of common sense or intuition while providing tech support. Keep reading for some examples, and a little discussion on how I think the common sense and intuition pitfalls can be avoided.

Common Sense

Dictionary.com says: “Sound judgment not based on specialized knowledge; native good judgment.” [ link] This is a good definition, since the idea of common sense is that it’s common, or rather not uncommon. Take crossing the road. You look both ways, right? That’s common sense - if you don’t look, you get hit by a car. This is common because most people are taught it when they’re a child.

The problem is when you, me, or anyone else thinks that something is common sense, but isn’t. “ It’s common sense that to make a new file, you go to File -> New File, right?” No. One key part of tech support is instructing users on how to accomplish tasks. If the user doesn’t know how to do something, then thinking, “But that’s common sense!” is pointless. It’s only common to you.

 A related problem concept is ‘obviousness’. I think the only way something can be truly obvious is if it is simply in plain sight and clearly delineated. If you say something is obvious and it’s not staring you in the face saying, “I’m obvious!”, it’s not.

My favorite example is the picture below:

Microsoft ActiveSync: Spot the Device Name!

This is the Microsoft ActiveSync connection window, with a Pocket PC 2002 PDA connected. I’m not trying to pick on ActiveSync, but this happens to be a very common scenario that I have to deal with, and it’s a subtle one.

If you are familiar with Pocket PCs, forget that you’ve ever used one before. If you aren’t familiar with them, stay that way for the next 30 seconds.

Now, pretend that you’re on the phone with me getting help:

Me: “Okay, now I need to know the partnership name of your Pocket PC.”

You: “How do I find that?”

Me: “Open your ActiveSync window on your PC and you’ll see the name listed.”

You (more often than not): “Uh, where’s the name?”

Where is the name?  Something is connected, and probably synchronized. Do you know where the name is?

The name is “Pocket_PC” - that’s the name assigned to your Pocket PC by ActiveSync, for use in identifying it in other software. That’s the piece of information I needed. Do I blame you for not knowing how to get it? Not at all. That piece of information is not obvious.

My solution for this obvious problem would be to place the following in front of the actual name text, so it reads Device Name: Pocket_PC . That way, if I ask you for the name of your Pocket PC, there’s a much higher chance you could look at the ActiveSync window and say, “Oh, it’s Pocket underscore PC.”

Obvious things are a kind of discoverable common sense. To learn not to walk blindly into the street, your parents had to tell you not to do it - you can’t really discover ’look both ways’ unless you want to get hit by a car. To learn how to save an article as a draft and keep writing it in WordPress, you hopefully just look down below where you’re typing and see the large button labeled “Save and Continue Editing” - in other words, you discover the obvious button.

From a tech support perspective, everything should be obvious - this helps maximize a user’s happiness with software and minimizes tech support for things that aren’t actually broken. Obviousness helps people develop their own common sense and helps them explore the software on their own.

Intuition

If common sense is something everyone is supposed to know, intuition is something no one knows. “The act or faculty of knowing or sensing without the use of rational processes; immediate cognition.” [ link] James Bach argues that intuition is really, “I don’t know how I did it,” and I agree with that definition.

Sometimes it’s easiest to throw out a counter example - here’s the file menu I see when I’m right-clicking a file in my FTP client to rename it to a backup copy:

Two Options You Don’t Want Next To Each Other

What’s wrong with this picture? Let’s say that wasn’t SurvivorGuide.clf, but instead ThisFileIsSoImportantYouWillDieIfYouDeleteIt.ext . Let’s say you sneeze right before clicking ‘Rename’. What other option might you click? DELETE.

You could argue that this is not an intuitive thing to do - it’s counter-intuitive. But what’s the reason? Well, because. Maybe it’s a bad idea to put delete next to a very innocuous thing such as Rename. It just feels funny, at least to me.

Part of tech support involves fielding feature requests. A user decides that it’d be easier to use OurProduct if the Widgets are configurable by right-clicking on them, and so they send something along which gets to me. But why is it any better to have right-click on Widgets? Sometimes the user gives a really good explanation, but other times, it’s just, “I like it better that way.” It’s like explaining why you like pistachio ice cream - you just do. I could implement my GTD organizational system using Microsoft Outlook, but I don’t like the way Outlook works, and for the most part I don’t know why. Other options just feel better.

When users can’t use our software, I want to know why. It’s in my best interest to figure out what the problem is, since I’ll be helping people with it when it becomes a problem.  Are we assuming users know something that they really don’t know (“it’s common sense!”)? Are we ignoring an easy way to make things ‘feel’ right for users (“it’s not intuitive unless the category tree’s on the right!”)?

It’s all very linked together. Users come to technical support with problems, technical support goes to the developers with common problems, developers fix the problems and refine the software, users take the refined software and find more problems.

Share this article:


What is RSS? Here's a short answer.

by Kevin

One thing I’ve noticed in terms of support is that people usually come to us wanting to make lists (ListPro), keep track of passwords and such (eWallet), keep track of financial transactions (Keep Track), but when it comes to NewsBreak, it’s a bit up in the air. It lets you… read news! Specifically, it’s an RSS feed aggregator, and if you know what RSS is, you understand the concept immediately.

If you don’t know what RSS is, wrapping your head around just what NewsBreak is good for, can do, can’t do, etc. can be a little tricky. If you don’t know what RSS is, this article will probably help: A non-technical explanation of RSS.

Share this article:


A Good Name is Hard to Find!

by Marc

With the recent announcement of the Microsoft Zune I just felt a need to talk about naming products. I’ll give Microsoft a little credit. It’s really hard to name a product these days. Most of the good names are already taken by something. That leaves new products stuck with either made up names or names that squish two words together and pretend that it is one word (yes…we’ve done this too…I know).

Now, some of the made up names end up being quirky cool, like WOOT! and Google. Unfortunately, it seems that this has led big corporations to think that a wacky new word for their product name is the smart way to go.

Take the now infamous decision by Nintendo to rename their REVOLUTION! game system “wii”. (“wheeeee!”) I mean, seriously. Revolution was something I could get excited about. “Join the Nintendo Revolution!” “Become part of the gaming Revolution!”

But wii? I’m almost embarrassed to walk into a store and ask about this system.

“Hi, do you know when you’ll be getting the wee’s?”

It would be so much cooler to walk in and ask:

“Can you tell me when you’ll have THE REVOLUTION!?”

Back to the Zune. apparently Microsoft hired the same ad agency to name their Argo media device. The name “Argo” had power. It filled my head with images of going on adventures, of legendary journeys, and excitement. But Zune? I guess it’s a little like “Zoom” and that’s sort of cool. I don’t know. All I can think is that the big corps have a room full of suits trying to figure this stuff out:

Suit 1: “OK…what’s happening on the web and how can we tap it!” Suit 2: “Crazy product names!” Suit 1: “Good one Bob…now think crazy…what’ve you got?” Suit 3: “Um…zerbert?” Suit 1: “No no…crazier!” Suit 4: “Zuh…zuh…zune?” Suit 1: “YES Johnson! Now that’s crazy!”

And of coure there is the Origami. While the name “UMPC” isn’t a terrible name, it doesn’t evoke the same cool image of flexibility and zen comfort as Origami does.

I guess what I’d really like to know is what they are thinking. Is it really the scenario I described above? Or maybe some market research company in India calling thousands of people in the U.S. and asking them how the word Zune makes them feel? As I said, I know that it is hard to pick names for new products. Still, these guys seem to pick great names and then toss them out at the last minute.

Well, enough of the naming rant. I’ll close with what I thought was a pretty funny quote about the Zune from James Kendrick’s Blog, JKOnTheRun . It’s the very quote that got us on the subject of product names over here at Ilium Software.

" I don’t know if I like the name Zune or not, but I thought Microsoft would come up with something like Ultra Mobile Audio Media Adapter (UMAMA)."

Share this article:


You got "Getting Things Done" in my ListPro!

by Kevin

Ten points to whoever recognizes the advertising throwback in the title. “Getting Things Done” is a methodology developed by one David Allen to help create a ’trusted system’ for tracking what you need to.. get done.

GTD focuses on helping you dump your brain into this trusted system, so you don’t leave obligations looming in the black uncertainty raincloud over your head. If you don’t have time to read his book, you can probably get a good sense of how the core of GTD works by looking at this flowchart [PDF file, 30KB].

GTD is pretty popular with geeks, probably because it takes quite a bit of fiddling to get it done (geeks love to fiddle with things, in my experience), and because it’s a “Life Hack”, a way of optimizing your life to make things work better.

GTD is also something that is basically a bunch of lists. We make a product called ListPro that is very good at making bunches of lists. So inevitably, the two will collide. For the collision, keep reading after the cut thingy below.

Disclaimer: I am not the master of GTD. I am still ’trying it out’, so to speak, figuring out what the best way to implement it is. That’s one of the downsides of GTD - there’s no 100% right answer for how to make it work. The important parts of GTD are:

  • Making a trusted system, that you can rely on 100% without thinking
  • Making a trusted system, that you can rely on 100% without thinking (is there an echo?)

If you can’t rely on your GTD system, then you’re no better off than before you tried implementing it. This is one on of the downsides of a lot of organization tips and tricks - you have to do it, and you have to stick to it. One way to help you stay stuck is to find a system that’s comfortable for you. I’m still looking - so far, I’ve tried LifeBalance, the eerily-similar MyLife Organized, our very own ListPro, and am about to tack a program called Ultra Recall. If you want a good smattering of GTD aids in one spot, check out this blog post on 52Reviews.com .

Disclaimer 2: I don’t think I’m going to use ListPro for GTD. This doesn’t mean you should stop reading. If you like ListPro, and want to do GTD, give it a shot. You can certainly do it, and it may work perfect for you. I just feel like I need to say this so I’m not purely saying ListPro is the best thing since sliced bread. It’s like how I drive a Toyota - I don’t hate other car companies, I’m just familiar with them and found my car to suit my needs. ListPro works great for testing checklists, daily process lists, call logging, my groceries… just not my GTD.

Anyway, enough yap. I present to you the ListPro GTD template. [Warning: 122KB .CLF download, requires ListPro!]

Just download that file, stick it wherever you want, and peruse it. You’ll find helpful hints written by me.

Is this the only way to use ListPro for GTD? Probably not. Is it the best GTD implementation there is? Probably not. Is there a best GTD implementation? For you, yes. For everyone, no.

So go get some things done. [Kevin now checks off the ‘push publish button in Wordpress’ Next Action…]

Here are some tips:

  • On a Pocket PC, to sync your GTD list, make sure you have Files turned on in your ActiveSync settings, then just drop the GTD template into your Pocket PC’s synchronized My Documents folder.
  • On a Palm, you’ll want to open your regular ListPro list file on your desktop and go to Tools -> Import Lists…, then point to the GTD file.
  • Get familiar with the shortcuts for copy and paste (Ctrl-C or Ctrl-X if you want to cut, Ctrl-V for paste), since you can’t drag items between lists.
  • If you want to change your columns, you may need to re-build the entire template. This just is a limitation to how ListPro works - each List has its own format, and you may not be able to copy items between lists of different formats.
  • If you really want to stick with ListPro for GTD, make a shortcut for your actual GTD file and place it in your Start Menu’s Startup folder. This will launch the file whenever you boot up or log into Windows. Then, right-click on the shortcut and pick Properties, and assign a keyboard shortcut. Whenever you want to add something to your list, just press that shortcut and ListPro will open right up - it should open up to displaying your Inbox, but it may change to whatever list you had been working in last.

If you make modifications to the template or have any feedback, feel free to either send a message to Ilium Software or leave a comment below! I’ll be glad to post different templates or update it based on user requests.

If you have any problems getting this to work in your ListPro, or have any other problems with our software, just contact Ilium Software directly and someone will help you. I’d like to put my email here, but I haven’t figured out how to effectively spam-proof it in Wordpress yet.

Share this article:


Search

Archives

Categories

RSS Feed

News