Gentlemen - Start Your Engines - or not

 I got this offer to view videos of business software. All I had to do was sign up. 

So I went to the create account section and there was this nice red text and button inviting me to get started. 

Only problem - it was inactive - clicking did nothing. And, right below this area of the page was a form for signing up.

So I'm wondering

1. Since the form is right there why do they need this kind of prompt?
2. If they feel they need it - why did they make it look like an actionable element? No action is required (yes I know - other than fill out the form)
3. I know it's a call to action but the text would have been sufficient. Like I said, the form was about half an inch below. 

Why do I have a problem with this? Because people have preconceived notions about what certain things on a web page represent. The downward arrow looks like it should be clicked to get started.  Some users might interpret this as a necessary action even though the form was close by. 

So, choose icons carefully. Use graphical elements that clearly do one of two things

1. Prompt the user to click to take the next step  OR
2. Direct the user to continue on without having to click on anything

How to make friends even if you don't want to

Social networking tools are really cool. They help us to find old friends, make new ones, locate companies, see who's doing what etc.

One of the more popular ones has this interface. It opens if you click on a name connected to one of your linked "friends" and offers you the opportunity to connect with this friend of a friend, in this example Glenn B..

My question is, why would I need to go through the process of connecting with Glenn when I don't know anything about him except he knows my other friend.

But these folks seem to think I need to connect with Glenn in order to read his profile, see who we both know, and consider sharing details with him before I'm sure if I want to be connected with him at all -I haven't seen his profile, only know of one friend who knows him and haven't shared any details with him yet. 

Gotta go - I have to hook up my horse to my cart, or is it my cart to my horse or...

If you build it they will come

I got into the whole software design/usability world by accident. Never thought about doing it before and sure didn’t know I had a talent for it. 

Starting my new job as Manager of Telecom Planning 9 years ago was supposed to be the crowning achievement of my career of more than 20 years in telecommunications. Too bad that the other department already doing that work didn’t feel like giving it up. So after an 18 month dance my group lost out and my beloved position was dissolved. 

Now what? Turns out that the audit department had developed quite a hate for some of the documentation practices of one of my colleagues. So, without further adieu ladies and gentlemen, I was given the task of fixing it up – a decision based more on my availability than on any identified capability. 

Pretty soon it became apparent that some kind of tool was going to be necessary to manage all of the documents in the fashion the audit guys cherished. We didn’t have one and none of the senior executives saw any reason to help us buy one. But, through a stroke of good fortune, I met an independent developer and we convinced my management team to give us a small fund to start building something. 

Based on an existing web-based CMS application written by my new colleague we began the process of creating an electronic document management system. Up to that point I had never seen or used one so I had absolutely no idea how they worked. And that my friends is the moment at which I began my incredible journey into designing software. 

We did the most extraordinary thing – we asked our user community what they needed – sounds like USER CENTERED DESIGN (I’d never heard of it!). We didn’t even look at any existing DMS systems for ideas. We just built on the basic methods the users already had and added in the things that they needed. 

We asked, they told  us, we designed a working model, they kicked the tires, we added/subtracted/changed things then asked them again. “Better this time!” they said – sounds like AGILE DEVELOPMENT (something else I had never heard of!) 

This went on every day/week/month for about 2 years – from day one the system provided value and with each new iteration it got better and better. At the end we had a highly functional system which rivaled many commercial offerings. It cost us $63,000 to build and it stayed in production for 3 years until one of the senior executives got the bright idea (not from us) to buy from one of the industry giants. 

I actually helped implement the new system, kind of a sad time. But, it was most satisfying to hear many of our users say “I like the old one better!” 

So out of the ashes the Phoenix rises. One failure led to an incredible new beginning. I moved into a field that required the kind of instincts I had about technologies and humans. Build it for them and they will come! 

I went on to design other things, again using the same customer focus and got similar results. And, I’m still at it today- helping to build useful, usable tools. Just what the Dr., and the customer ordered!