April 30, 2010
Feeling More Productive vs. Feeling Less UnproductiveQuestion: Would you rather spend 10 minutes drawing some cool graphics in Powerpoint, only to discover that there was a SmartArt that would have done it for you in a few seconds; or spend 5 minutes typing in bullet points and then have the program crash and lose what you typed?
I suspect that most people would mind the second one a lot less, even though technically the first one wasted more of your time. In the first case you still felt like you were doing something; in the second you felt like your time was wasted (in fact, Office these days has very good auto-save and the second scenario is unlikely, but it's just an example).
I mention this because when software designers think of productivity they seem to focus on the first kind of productivity--helping the user do something they already do, but faster--not the second--preventing the user from losing work they have done. What really annoys me about computers is when I spend time on something and then it is lost. When I worked at Softimage back in the mid-1990s, I discovered they their 3D editing product, and its competitors, were notorious for crashing a lot. But they also all had really good auto-save, so when they crashed you just restarted them, and you only lost a few seconds worth of work. This would horrify a typical Microsoft developer--just engineer it not to crash, and then you don't have to worry about auto-save! But very niche-y products like 3D tools tend to be designed by people who used to be the customer, so to them it can make perfect sense to crash and recover, because they understand that from a user's perspective, that is the behavior thet will make them feel like they lost the least amount of productivity.
In fact I realize that this is why Outlook's incessant "the attachment to this email has changed, would you like to save it" messages annoy me. A little bit of it is because I have to think, and make sure I closed the right email--the one that I just opened that Word decided to reformat on its own, not the one that I've spent 15 minutes typing. But it's mainly the attitude, that the designers of the software have chosen not to distinguish between work that the computer did for me, which is completely repeatable, and work I did myself, which I can only do by spending the same amount of time again.
April 12, 2010
Teaching a Horse to TalkMy father once told me a story that goes as follows:
A man is sentenced to die by the king. As the verdict is announced, the man says, "Wait! If you spare my life, I promise that in one year, I will teach your horse to talk. If I fail, you can kill me then." The king is intrigued, and figures he has nothing to lose, so he agrees. Afterwards, the man's friend says, "Are you crazy? You'll never teach the king's horse to talk." The man laughs and says, "Think of it this way. I have an extra year to live, and a lot can happen in a year. I might die. The king might die. And who knows, maybe the horse will learn to talk."
This is actually one of my favorite stories (see, Pop-Pop, I was listening). I like the bias to action and the "What do I have to lose?" attitude, but also the wisdom that if the worst thing that can happen isn't worse than what's going to happen anyway, why not give it a shot? I recall telling this story during my PowerShell days, possibly in regards to the alleged virus fiasco in 2005 (of course, what actually happened there was I got yelled at by the security team, and Lee won an award from our VP for customer engagement; not sure what the moral of THAT story is).
I was reminded of this story because I'm watching an internal presentation where somebody told this same story, except a) It took them 7 1/2 minutes, not the 20-30 seconds it would take to tell my version above, b) they told it badly, and c) they completely botched the moral, trying to turn it into something about "People like to convince themselves that the horse will learn to speak", which has absolutely nothing to do with the original story.
P.S. Oh gak, the presentation just ended with a little 45-second coda about "How the story turned out", which manages to confuse the moral even more. GREATEST. PRESENTATION. EVER!!!