User Experience Designers- Hot Commodities

Marshall Kirkpatrick writes on Read/Write Web that User Experience Designers and Information Designers are going to be very important due to the increase in information overload. Gone are the days of trying to keep up with MTV. Its a Twitter Nation now and we have to design better interfaces. I still see the need when working with clients as they try to handle the onslaught of data from their datawarehouse and external sources such as RSS feeds.

It's not just corporations who are trying to deal with this over abundance of information- it's now the regular Joe user at home working with family pictures, videos, word processing documents, spreadsheets for the personal finances, etc.

The question is... are you ready to handle it?

The Relevance of User Experience

Mean What You Say- SmugMug and Privacy

The popular site SmugMug is getting some not so friendly commentary today due to a perceived security hole. Essentially, users have the ability to set their photo galleries to be "private" and/or "password protected." Users that selected ONLY private can still have their photos viewed by the general public by easily playing around with the sequential naming convention of the URL addresses. It seems that SmugMug didn't see this as a problem.

Based upon their response you can assume that they see nothing wrong with their distinction between private and password protection. This is a semantic problem. The developers have to realize that private means just that. It infers that ONLY the person who created the gallery should be able to view the photos- no one else. This is why user advocate roles on development teams make a positive difference. Now how much is the problem going to cost the company that maintains SmugMug? It's more than a financial issue- it's a confidence problem that can put a big mark against the brand.

For more details review: The GoogleBlogScoped.

The Relevance of User Experience

So I finally took a moment to record my thoughts about the profession and why it is going to be a sought after skill in the coming future. As the craft matures so will the adoption by mainstream Fortune 500 firms. Read more here.

Usability on 60 Minutes

8:15 PM EST- 12/30- Don Norman is commenting on the ill-usable products out in the market. He commented on the universal remote. Try finding the volume buttons. The 60 Minutes reporter spoke about why products need to be more user friendly. Is usability now mainstream? I blogged earlier this year about the Wall Street Journal article about usability and now 60 Minutes. Watch out world- things are going to be getting easier.

Getting Ready for Web 2.0

So you’ve heard all about it. You’ve been waiting a year or so to see if it’s a passing fad. And now you see it is not and you’re not sure how to get started.

Well, Web two dot “o” is more than blogging and reviewing products. It’s larger than large typefaces and pastel colored interfaces. It’s all about you and your relationship with your customer. For some of you, your customer is your “end user” but let’s think of this person as one in the same.

Building a brand is about creating a culture. It’s also plugging into an existing culture with what you have to offer. Think about how Apple has a loyal following just like Volkswagen. What’s even more interesting is that many Apple lovers also drive VWs but that’s a different topic all together. So what does branding have to do with Web 2? It’s all about the relationship.

Web 2 provides you with functionality that creates and can strengthen the bond between the company and the customer. Blogging shows that you are willing to hear what your customers have to say- even if it’s not all good. It’s about letting your users share their experiences with your product by rating you. Ultimately, it reveals your open door policy. Hopefully you have one.

When does Web 2.0 not work? It doesn’t work when you’re trying to create an experience that is not genuine. You have to believe in the notion that you want to hear what your customers have to say about you. Fakes are easy to spot. Remember, the under 25 crowd is skeptical first, logical next, more experience with the Web than ever before and yes they do know about Enron and big corporate bad behavior.

If you are going to make the move to Web 2.0 take the time to create your roadmap. You must map the relationships between your customers and your products. You have to see what Web properties are ripe for the new functionality and which ones may need a reface. Once you get your plan in order execute in phases and test. Make incremental improvements and test with the user community. You’ll find that listening to your customer is the best method for building and strengthening your brand. Make Web two dot “o” part of your plan for 2008.

Two Ears and One Mouth

I'm amazed by the number of clients who say their IT or Web resources don't listen to them. Often listening will reveal the root issues of clients' problems. Let's say hypothetically that the you are picking up keywords from your conversation around getting people to use the site, getting people to find the site, and generating income.
Sure you can make the site pretty or pretty useful but the client needs the site to generate traffic as that seems to be their goal. So address the search engine optimization strategy and the look and usability will fall into place as secondary items.

Take the time to listen. Providing solutions too quickly will net you zero. By the way, this is good life advice ;)

Explaining Trends- a free PowerPoint presentation

I'm discovering that many corporations are a year or more behind solid trends in the Web. I have created several presentations along the lines of usable innovations that apply to every day web design and construction. I've attached the presentation to my corporate site. Feel free to use it when the time comes to shed some light on AJAX, SEO, and Web standard coding.

Download the presentation here.

BTW: I give credit to some of my favorite interfaces: Flickr, Odeo, Kayak, Gmail. Other interfaces mentioned are Kodak's EasyShare, Travelocity, Yahoo! Mail, and MapQuest.

Usable Interfaces Becoming Mainstream?

While taking a moment to read through The Wall Street Journal yesterday, June 21st, I noticed an article that stated SAP is going through a series of design courses to better the interface execution of their enterprise software. Wow! It's about time that a large organization realizes that functionality has everything to do with the front end AND the back end. When your software moves to the web it has to compete with conventions that ease use in a way that a multi-million dollar application has to contend with or face loss of revenue due to sales.

Viva la usability!

User's Say One Thing and Do Something Different

Last week I had the opportunity to facilitate a usability evaluation. Users were observed while they were asked to perform certain tasks utilizing a hi-fi prototype. Afterwards, they were given a post evaluation questionnaire. Only the participant was in the room this time, no evaluators, no note takers, just them. And man, their responses were totally different then their comments during the task analysis. Users voiced they had trouble determing the state of an entity within the app. This was a key piece of functionality. Then in the evaluation they say the application was easy to use!

Which IA is Right for Your Project?

All IAs are not the same. Some are focused on content heavy sites. Some are focused on transactional sites. But which one is right for your project?

With more than a decade of experience building web sites, applications, and web-based interfaces, I have encountered all types of designers, developers, and IAs. I have found that most designers have a certain style and some developers may have a particular liking to one platform over another. Much the same IAs typically have a slant to a specific type of project.

But which type of IA is right for your project? At a high level you should at least know if you are building a site or an application (client vs. web). If you are working on an application make sure you find an IA with application experience!

Not all IAs have worked with systems. When interviewing, ask them what applications they have architected. You don't want a non-technical IA who does not understand general programming principals and how systems typically respond to user's input.

Ask them what the development environment was like. Ask them for specific sample deliverables like workflow diagrams and functional requirements. Look at their wireframes and see if they built in controls for all the use cases (ex. what does the screen look like if the system becomes unavailable to the user). And most importantly, make sure you ask them how they worked with the development team. This is critical. Communication between the two groups will determine the success or failure of your app. Take a look at The Information Architect's Field Manual for more on this topic.

Creating Bridge Documents- A UX Tool of the Trade

Bridge documents help inform other documents by providing the concept, research, and thought work behind the destination document. For example, when delivering a site architecture to a stakeholder you should be prepared to justify the placement of content and nomenclature utilized. A bridge document can outline your user segments, their needs, and the type of language that they are most comfortable using. This document will provide the justification for the site architecture thus informing the stakeholder on your premise for the destination document (site architecture).

Use What You Have

Time and time again I see companies trying to reinvent their eCommerce site transaction flow without the right data. From the usability test team to the Information Architect... "Wait didn't we do that last year?" "What were the results?" "Revenue is up, revenue is down."

Look, your customers tell you how they want to buy your products. If not explicitly through direct feedback, implicityly through site traffic and abandonment rate. Research, research, research and then act. It will not take as long as you think if you just take the time to see how your customers are reacting to the page flows that you created.

Maybe another screen will help. Maybe it won't. Sell them on that high dollar product later through email or mail. Give them what products they want WHEN they want them. I'm convinced that most companies sell good products. They just don't sell them well.

Stay tuned for more commerce related commentary. Have a commerce problem now? Looking for a consultant? Contact Daimon at http://www.modalinc.com.

Short Order IA

I gotta tell you I can't take credit for that title. My co-worker came up with that one. It's adapted from SUAC (shut up and color) but applied to Information Architecture. Let me explain: you get handed a 100 page requirements document that contains tab names, page flows, and everything you need to build a wireframe. You've got 5 days to create the entire set of wireframes including alternative views. What do you do? Burn through Visio like nobody's business!

I guess in some cases that is just fine. I like gettin' my hands dirty though. Give me a blank requirements doc and I'll have at it. But "Hey" that's just me. All Short Order IAs put your hands in the air and wave 'em like you just don't caaarreee! :)

2006 Projections- musings of an IA

The Industry
2005 was all about Web 2.0- big buttons, cool AJAX interaction, and web services. This will continue into 2006. Interface "style" will mature and big fonts and buttons will remain. Designers and IAs will work closer with their development counterparts. They're going to have to do this in order to create the interactions they envision.

The Company
What about Modal? We will begin to consolidate most of our web sites into one umbrella brand. What other sites? Don't go runnin' a Whois quite yet... I've got the hosting site, my resume site, and two community sites. It's all about bringing our presence and the User experience community together.

Take a Developer to Lunch Day

After working as a Senior IA and Experience Designer at many large corporations (Fortune 500 or 1000) I have benefitted greatly by directly interacting with the development team (programmers). My products typically launch on time and on budget. There is little back and forth between coding and requirements clarification. Rarely will I hear a developer say..."Our systems can't do that."

So how does a primarily user-focused, front end guy launch enterprise-level web apps without losing his hair? I do believe that this is due to my willingness to work with my counterparts throughout the lifecycle of concept, design, implementation, and testing. Throwing business requirements (func. specs) over the wall to the dev team does not make for on time, on budget projects. Someone has to bridge the gap. We all know that we don't speak the same language (arrays, session management, and EJBs) but we should all have the common goal of building a great product.

I've realized that even if no one else on the business side wants to become more "technical" or attempt to communicate with developers- I need to in order to get my job done efficiently. Here's my suggestion to my fellow IAs, Analysts, and Designers... take a developer to lunch one day- Heck make it a weekly thing to do!

You'll find that you are not as in the dark about those "black boxes" that make the site do this or that. You will also start to create a common vocabulary that will help you better communicate the business needs to the other side of the house. No one likes to just "shut up and color/code" they all need to be a part of the success of the project.

Modular IA

As I work more closely with developers I have learned their model of concepting and implementing code. They think very much about flexibility and the next request the business is going to have regarding future functionality. Working with developers I believe has made me a better Information Architect and Experience Designer. Why? We're starting to establish a common vocabulary and concept path. I too now create my functionality is a modular fashion. I think about the extensibility of my component and where it can be placed next regardless of the limitations of other screen assets. For something as simple as a login box, I can think about containing it in such a way that I can move it to a messaging unit or within the body of a page. I'll be talking more about Modular IA as the weeks develop.

Remembering why...

For those of you who have been working on the web since the early 90s let me know if you're still working in the medium. I've had some co-workers burn out recently and I hear the same thing..."I'm tired!"
The Web is getting it's second breath. Folksonomies, AJAX, and social networking are spawning a new found vigor... I'm excited about this new wave. It wasn't enough to keep some of the "old schoolers" but we all haven't forgotten those exciting times of innovation!

From Static to Dynamic

I've been working with IAs who have most of their experience in non-transactional sites. I'd like to hear from other IAs who have made a shift from non-trans to transactional sites. I ask as it seems like a bit of a chasm to adjust. Process flow diagrams and use cases seem to be a challenge as now they must think like a webserver (request/response) as opposed to wireframing and sitemapping.

A Bit Disturbing...

Hop on over to 37 Signal's blog post on the definition of information architecture. There are many posts stemming from IAs that "do" site maps to IAs that arrange information to those that don't have a clue. Is the discipline in trouble? I posted my definition which you'll find there but I find it all a bit disturbing...

What type of IA are you?

Information Architecture is still a relatively new discipline. I encounter designers who also do site maps, writers who also do site maps, and then those that create web apps. They all call themselves IAs.

There are some IAs that are technical (not developers but understand data modeling and OOP concepts and principals) and others create site maps. Sure this is a generalization, but it seems that I've encountered IAs that are either technical or not technical. If you're not technical your focus is on site mapping and local navigation strategies. If you're technical you write use cases, process flow diagrams, and activity maps.

Much like my comments about designers who say they are not programmers does the IAs lack of technical knowledge hinder their ability to deliver best of breed solutions?

What should the criteria be for an Information Architect? What's the job description?

In Response to Mena Trott's Defensive of Big

Mena, it's not very professional to take stabs at 37Signals. :) Sorry but "big" is out and "small and smart" is in. You're points are interesting but purely subjective. I've been on both sides of big (15) teams and small (3) teams and I can tell you there are pros and cons to both. The bottom line is that the success of your company/product is not based upon the size of your company but the quality of your people and the skills they bring to the table.

Just my 2,
Daimon


Here's a link to the article: http://www.sixapart.com/about/corner/2005/09/in_defense_of_b.html

I'm a Designer not a Coder!

So I'm sitting in on a conference call with a designer on a web project. It's a pretty straightforward marketing page with some minor css stuff- background image inside a div. So I ask the designer..."How are your HTML skills these days?" Her reply, "I'm a designer not a coder!" Ok, her response gave me pause... You're working on the web, you 're designing screens and you don't know simple CSS?

Am I asking for too much? The problem with this is that she's not the only designer I've heard this from. Print designers/wanna be web- wake up HTML is not coding! Know the medium you're working with not just Photoshop and Veer. Give me a break!

Do you really need it?

A Reflection of Needs and Wants
By Daimon Caulk

Let me first say that in the literal wake of hurricane Katrina many of us have witnessed the removal of peoples’ possessions and the effects of desperation due to loss. After all we are attached to our things. In the midst of that situation you think about the bare necessities and a plan of action. You ask yourself... Who is in charge? What happened to the levies? When is help coming? Where are my loved ones?

During the hurricane aftermath many reporters interviewed frustrated evacuees, local, and federal officials. They were all saying pretty much the same thing. They had questions, and there was no clear path to the answers. It is ironic that in the Age of Information we still have trouble with the basics: who, what, when, and where.

So how does this relate to the Web? Well, the Web is changing. Consumers are tired of too many applications that do a lot of things but not one of them well. They can’t create a simple document or perform a simple operation. Take me back to the basics!

Eighty percent of New Orleans is under water. Streets are unidentifiable. How can the Web help rescue workers find people- Google Maps. Utilizing their satellite imagery and “hybrid” street overlay view, workers are able to see the city again.

Now, Google Maps is not complicated, type in an address and view it on the map. It’s not overburdened by trying to be all things to all people much like Yahoo! Maps. I don’t see Yahoo! Maps saving lives.

An interactive product company, 37 Signals, has fueled a movement to get back to the basics. For example, imagine creating a web-based product that manages projects. That’s it. That’s all it does. It doesn’t manage budgets, it doesn’t create Gantt charts that aren’t printable anyway, and it doesn’t create invoices (get Blinksale for that).

Take a look at Basecamp, it’s the web location for 37 Signal’s project management software. It is a web service that assists mainly creative studios with their projects and clients. The interface is clean and simple. No over the top graphics and consensus driven menu options. There aren’t any complicated Boolean searches or (if, then, else) statements that make a straight forward application complicated and expensive.

The company’s design process is rapid in nature and somewhat cut throat. When someone recommends additional functionality they come up with every reason why they should NOT do it. It speaks to their desire to create a straight forward, smart product that solves the problems of a group of people.

We know that change is constant and many times those changes are cyclical. But there is meaning that comes from creating something that is pure and smart. We have to learn to let go of things and focus on the necessities. The app should not be full of things it “could do” but it’s simply smart in the execution of what it is.

Google Maps helped get people off of roof tops. A simple application saved lives. When you are championing your next project consider these things: what is the real problem, what is best and simplest way to solve the problem, and how can I create a clear path to the answers the user is asking.

As always, let me know if these suggestions worked for you. Remember, just my opinions, I'd like to hear what you think.

Itchin' for an App

Ok, I'm itchin' for a new app to build. This time it's Web 2.0 style with open standards and extreme ease of use. I want my Grandmother to be able to use this thing... With so much going on in the world- news, busy schedules, information management we need an app that can do most of those things well. And it should be a service- no installation.

Let me know if you are a developer into 2.0 stuff and are interested in some weekend construction. I'll get a box, bandwidth, and you bring your creativity. Email me.

Online Services

Ok, I'm getting addicted to the latest swarm of online services. I moved all my project management to Basecamp in combo with StrongSpace, moved from Ofoto to Flickr, and hopped on the 37 Signals wagon with BackPack. It's been good so far. I've had to create a dashboard so I can access all the services in one web window but it's been a marvel to work with. Now I just hope no one of these services decides to shut it's door or all my goodies are gone!

IA Celebs

Ok, don't steal my word but WebWood is the new online Hollywood. Let me demonstrate...while attending the UX Week happy hours I noticed that JJG, Spool, and Veen are truly IA celebs. They had groupies for goodness sake! Look, I'm not even referencing them by their full names and I bet you know who I'm talkin' about.

I will say that this is good for our discipline. Maybe we'll get noticed even more as more poorly designed interfaces get released to the general public :)

Join me in congratulating JJG, Spool, and Veen in elevating IA to the new "hotness!"

UX Week 2005 Day One- Synopsis

Ok, you know how you go to these conferences and get sold immediately about how great their company or product is and how you've just paid all this money to have them sell to you... Well, guess what? It didn't happen here!

Here's my synopsis of what did happen...

Janice Fraser, CEO of Adaptive Path (AP), opened up with the discussion around Web 2.0 apps. Lots of this is Web 1.0 and this is Web 2.0. For example: Ofoto is Web 1.0 vs. Flick'r which is Web 2.0. What's the take away... "things are changing people!"

Jesse James Garrett (AKA JJG)- known for coining the name AJAX, spoke about...AJAX! He gave a good overview of the technology, how it can be implemented as well as the challenges associated with it such as the infamous Back button and maintaining state. He did bring up a really good point about looking at the page as a container (Janice resonated this as well) for elements. Each element, utilizing some sort of AJAX functionality will make web apps more rich vs. being burdeoned by multiple calls to the database and page refreshes.

Eric Costello- Flick'r DHTML front-end guru, spoke about Flick'r and it's development lifecycle. They iterate by pushing new code out to the production site every day... interesting. Oh and for those of you who did not know... Flick'r came from the developers desire to create an online game called the "Never Ending Game." Very cool mix of Flash and DHTML.

Jeffrey Veen of AP talked about letting go. We must see the user as a peer- give them the ability to create their own product utilizing the framework we provide them. Those with obsessive compulsive disorder should not subscribe to this mass amateurization.

Janice came back and had a round-table with the presenters and a couple of others to talk about the reality of Web 2.0 in a somewhat Web 1.0 corporate culture. An audience member voiced the fact that this conference was great but I can't take this back to my office and sell it. Lane, one of the AP co-founders, articulated it well when he said something to the fact that it will take time to sell the value of this to some but keep winning small battles. I tend to agree :)

The day ended with Jeff V's presentation on measuremap- a site metric tool that is simple to use and designed for blogs. The interface is very cool! It's still in beta but should be out soon.

The night ended with a happy hour. There were about 20-25 people in and out. I will say that all the AP folks were very approachable and up for good, sometimes deep conversations regarding the state of user experience.

I give it a THUMBS UP!

For those who did attend... what do you think?

-d

Wayfinding: Off the Web

I was walking around two different malls in the Northern Virginia area and realized that they were all centered around the goal of keeping the would be customer in the mall. One mall had "gentle" curves designed to provide you with gentle surprise around the corner. In contrast the other mall was obvious in its goal to entrap the customer by putting all stairs, elevators, and escalators at the far ends of the floors.

It an interesting activity. Look at the "global" navigation- floor to floor. And check out the "local" navigation in the stores themselves.

Its a good offline activity to keep you fresh and rid yourself of a few dollars in the process :) Any other offline suggestions for wayfinding and IA?

Wireframes

I've found that wireframes mean different things at different places. Generally, wireframes are the representation of functionality on a barebones screen. It does not reflect branding or exact dimensions. It's a skeleton.

However, I've noticed a trend toward more polished wireframes. Let's define polished. Grayscale color blocks to branded color blocks depicting functional areas of the screen to full on Illustrator produced screens with the company logo.

What's the deal? Are we still conveying the same information within the same context? Are you going to start getting feedback on the "design" of your wireframe? Stick to the facts. It's all about the functionality and the visual hierarchy of information.

What do your wireframes look like these days?