I have 7 red, half-gallon gas cans sitting in my garage right now.


Why? Let me tell you why. Pride.

It was about 7:30pm on a Friday evening in Dallas, Texas when my wife and I were heading to a concert with some friends. We were cruising down 635 in our black 1995 Jeep Grand Cherokee and life was good. Gonna get away, enjoy the night when an ever so familiar sound came from the dash of our Jeep.

Bing. Low fuel.

I look at my wife and she looks at me – and the ever so familiar conversation takes place.

“Honey, we need gas,” I said.

“No, we can make it….we’re gonna be late, and you know the Jeep really let’s you go way further than our other car.”

So we push it.

And the inevitable happens. A few miles down the road….*putter*, *ppput*…we coast to the side of the road. I get out the Jeep, look around, and start my trek down the road.

2 and a half MILES down the road, I find a 7-eleven when I walk straight in and know the spare gas cans are 3rd isle and on the right. It looks like this will make 7 in my gas can collection.

Why am I telling you this? Time and time again in speaking with customers, they don’t realize the need for good user experience in their development projects until it is WAY too late. Users are stranded. Confused. And stuck on the side of the road wondering why the “system” is so confusing and hard to use. We wait way too long to fill up and continue to say to ourselves “We shouldn’t care about the user experience.”….”That’s just overhead”…and time and time again we end up on the side of the road stuck, out of gas, and reluctant to have to add yet another gas can to our already large collection.

User experience really does matter. And let me tell you why.

I recently finished up working on a project with a government customer who was looking to update a legacy mapping system. The system was old. Dated. And needed some serious help in making the app more usable and productive. In fact, since the UI was so difficult to use, often times the high ranking government officials would prefer passing on using the system rather and go with straight up paper for mapping out the scenarios they needed.

Why should you care to wireframe or storyboard when you’re dying to diving into whatever project you are in?

Two reasons. Time. And Money.

Stop waiting your efforts in trying to fix a broken app that has zero usability. Start thinking “How can I make sure this app really does make sense from the user’s view?”

Enough of my rant….I know you get it and want to know how…..so that’s why I’m working to push out more video posts and less reading. I’m just like you when it comes to “show me” style of learning.

Stay tuned.