ui design lessons
I was recently examining some interesting articles on Engadget and noticed how the web site has been experimenting with different visual representations of data. As many know, Engadget is a high traffic tech blog. While it has not been special outside of the tech domain of knowledge. My eye caught something that was neat when trying to find popular articles and a little bit different. Next thing I knew I was no longer looking at the articles and instead was focusing on the interface design.
When I travel to conferences and speak with people about their agile UX experiences I come across a lot of repeat questions. Most of these pleas for help are about time management, rapid design sketching, traditional usability approaches, group design mentality, lack of support for UI development, and let’s not forget meeting burnout.
Even today UI designers hear the word AGILE and there mind is flooded with demon visualizations straight out of Dante’s Inferno. Why has this methodology caused so many headaches to UI Designers world wide? Why are they terrified? Can we beat them, or should we join them?
So I am bringing back the UI design challenge and wanted to try this a bit different. I want this to be an interactive experience. If you listen to my audio blog posts: http://boo.fm/b29310. I talked about recent research I was conducting to locate a new house.
I read a lot of books and in this field it’s good to both refresh and improve your skills. The latest book I finished (just this morning) is Neuro Web Design: What Makes Them Click? by Susan M. Weinschenk.
There are some applications I never used or expected to use for more then a few days. And in any given week I try out about 10 – 15 new applications. I do this because I love analyzing and predicting new trends, design patterns, and visualizing work-flows. Usually, I end up with using 0 of these applications after a few months.
If I had a million dollars for every time a client asked me to add more features, or more appropriately stuff and jam more features into an already bulging application, I would have published a book, bought a mansion, and maybe a small island somewhere in the South Pacific.
Let’s talk about proper widget usage. It’s imperative to know when to use the right tool for the right job. I wouldn’t use a sledge hammer to hang a painting (unless it was a very large painting.) I wouldn’t use a socket wrench as a pliers. I could use a butter knife to screw something in, but is that the best solution? It’s all about using the right application piece at the right time.