Comments on: Why not have the interface teach?

By: sara girlscantell

sara girlscantell — Thu, 24 Jul 2008 20:52:19 +0000

ps. geoff, i just noticed you had a calendar called “path to domination”?

By: sara girlscantell

sara girlscantell — Thu, 24 Jul 2008 20:51:20 +0000

i agree, there could/ should have been a little more “hey, this has changed!” but this one didn’t bother me, probably since i think i had a couple of my calendars already unchecked, so it was really pretty easy / intuitive to spot the difference right away when i saw it.
i think i like it because it’s just less stuff on the page, and google calendar is one page i could definitely use less stuff on.

By: Dan Mal

Dan Mal — Fri, 11 Jul 2008 15:26:06 +0000

I like the idea of the interface teaching, but I do have a problem with allowing someone to use an interface element “one last time” before it’s revised. It seems a bit like taunting.

For the record, I actually liked the checkbox version better. To me, a checkbox is an immediate read for an on/off toggle. The presence—or absence—of a background color is just style.

When they first changed this, I had a calendar off, and couldn’t figure out for the life of me how to turn it on. It took a good 15 to minutes for it to occur to me to just click on the link.

I like to take advantage of conventions when designing interfaces. Clicking a link typically takes a user to a different page, or at least a different portion of the same page. It breaks general expectation for the functionality to be different. It’s the difference between expected, inherent, and learned behaviors.

By: roz

roz — Thu, 10 Jul 2008 15:27:46 +0000

I have noticed that Google tends to release small iterations on their products frequently, without really letting you know, other than noticing one day that something is different. I have found that, for the most part, they are better changes, but I agree that it would be nice to have a little more information.

I think we’re used to the 37s model where they have an announcement across the top of the Basecamp screen to introduce a new feature. I really like this method because I take a moment to test out the feature and become familiar with it.

By: Geoff

Geoff — Wed, 02 Jul 2008 22:12:43 +0000

I was thinking about the time issue and I do agree with you, as a general rule.

However, it occurred to me that if you are the type of company (like Google) that spends time on documentation, you could save time there.

Since we develop web applications, we certainly feel that time pain, but I was interested in opening the conversation.

By: Colin Devroe

Colin Devroe — Wed, 02 Jul 2008 22:03:18 +0000

I only see one potential problem with your idea. Oh, and for the record I love the idea.

The problem is time. Google is probably a bad example of this because they have a lot of resources at their disposal, but coming from the perspective of someone who is trying to run a company that develops software – there is only so much time in a day, week, month, etc. The amount that we can get done as a team is limited by our resources (number of people, generally). So we have to squeeze in only important things when we make changes, fix bugs, etc.

The idea that you’re asking for here would, essentially, take more time than simply making the change and letting the users just figure it out on their own (like you have).

If there was a way to have the interface teach, it’d be all in the usability. And I think Google struck the balance here.