Developing Web Tools with a Good User Interface

For the past few months I’ve been developing three different web-based tools.  All three are things that I started as tools for me, and it was after talking to other folks that I learned they might ultimately be useful for them, too. When my user base shifted from just me to a whole lot of other folks, I made a small list of rules to help me make my web tools user-friendly instead of Frank-friendly.   As one of those tools nears completion, I figured I’d share my lil’ list of rules for making good web tools.
Read More

Clever CSS3 Tricks: Using the em in text-shadow and box-shadow

Any of my web development buddies have learned that I’m a huge fan of the em. Huge fan. We’d be Facebook friends, we’d go on vacation together, yadda yadda yadda. When you look at my online resume you’ll be hard-up to find too many px written into my stylesheet. In fact, almost every property with a px is a shadow of some kind. But that won’t be the case too much longer, because I’ve got a nifty trick for creating kind-of global shadows by using the em instead of pixels in your shadows. Read More

CSS Tip: An em isn’t an “m”, but an ex is an “x”

I’m in a CSS mailing list and this morning, Vince over at Ghodmode Development shared a fun little experiment showing that an em isn’t an “m” in CSS. I, along with others, more or less responded with “d’uh”. We’ve seen this phenomenon for years and didn’t totally understand the purpose. In fact, I attempted to devise an experiment that would prove when an em is an “m”, and I couldn’t. Turns out, I don’t know anything about font sizing. Who knew?

 
Read More

Why I use a Mac for building websites and Android for making phone calls

I hated Mac for years. Approximately 27 of them, if I recall. Then my wife twisted my arm and we bought an iMac. Then, two work-issued Macbooks later and I’ll admit that I like designing and developing with Apple’s OSX interface. But I’m not a fan of the iP/hone/ad/od.  Why? Usability isn’t user experience, and  Apple’s mobile devices are a win for the former and an epic failure for the later (I eagerly await your refutations ;).
Read More

Layering the feedback with CSS

Feedback Matters

Long gone are the days where all we did was stare at a website and absorb content. We fill out contact forms, buy stuff, hold chat sessions, Tweet this and unlike that. These website interactions become more complex as they slowly get better at mirroring real-world interactions. One of the steps in mirroring real-world interactions is providing natural, progressive and intuitive feedback.

Ask any pianist or drummer why they don’t like the cheap electronic equivalents and they’ll tell you, “It doesn’t feel real.” That bounce of the key, the way the sound gets louder as you hit it harder; the feedback is either missing, or just wrong. Contrarily, video gamers can’t imagine a day that their controllers didn’t vibrate because it gave them a sense of the game they weren’t getting with graphics.
Read More

The layers of Design

Ogres and onions have layers…

And so do websites. Depending on who you’re talking to and how they’re slicing it, you’ll get different names that essentially represent the same thing: content, design, and functionality. While the end user looks at a site and sees seamless pages linking to one another, the content authors, designers, and developers see the website as a collection of layers that interact with each other.  As content strategies become more complex, we see content being sliced into more distinct layers for content management systems while the design gets treated as a flat, layer-less component of the site.
Read More

Are New Pop-Ups the Old Flash Intros?

After a project was laid on me in the eleventh hour which had to be delivered in the twelfth, I found myself madly trying to educate myself on a foreign subject. The project and the subject doesn’t really matter. What mattered to me was collecting enough data for me to deliver it on time.  Google performed beautifully; but a lot of the sites failed. Why? Pop-ups.
Read More

The CMS Diaries: What’s your first step

I’m beginning the first in a series of posts call the CMS diaries. I’m a contractor for a very large and reputable organization which is launching a new website very soon. I was brought in specifically to serve as the business analyst for the web content management system. As exciting as that might sound, it isn’t.  In the wonderful, wide, world of the web – the CMS is the dullest part. The guy who does your CMS is the accountant for Greenday†. There’s no chance of being hip, cool, or creative. At best, he can say that he’s the reason American Idiot was 99 cents a song on iTunes. Regardless, I will sexify the incredibly boring and forgotten part of your web redesign: The Web Content Management System.

Hold on. What’s really wrong with your web site?

Design. That’s usually what people will tell you, because no one likes a design from last season. And that’s usually what lead to the redesign. And truthfully, design alone is an awful reason to redesign your site. Read through anything that Steve Krug and Jakob Nielsen have written and they’ll tell you it isn’t design, it’s usability. Page one of Ginny Reddish’s book, Letting Go of the Words, says that, “people come to web sites for the content that they think (or hope) is going to be there.” If design is what’s wrong, spend an afternoon with a designer and a CSS developer and fix it*.

Now, if brand and design isn’t the issue, then what I hope is that you’ve gotten user insights that have forced you to focus on usability. And to go back to my previous quote; that makes content top priority. So take your beret-wearing Über-Genius of a web designer out to the park and leave him there to draw pictures of auras. It’s time to bring in the accountant.

Numbers aren’t just your friend, they’re your FaceBook Friend

It’s called web analytics. Analytics is so boring and unsexy, right? Right. But you need someone to actually figure out the user behaviors. Unless you’re planning on doing formal user experience and usability testing, web analytics are your best bet. Google Analytics is free. Throw a few lines of Javascript on your web pages and you’re set. Get in your accountant, or other available nerds to study the numbers and tell you what’s wrong. Getting a committee to tell you what colors are hip won’t fix this. You need objectivity – which numbers can offer.

You want to figure out what people are really getting out of your site. So drop the emotions about how many hours your poured into that venn diagram in the shape of hearts to describe your HR department’s org chart*. No one saw it in two years. But if you’ve got 4,000 searches in the last month for your phone number, the problem is with how someone can find content. It’s time to rearrange your website. That is called Information Architecture.

What does Information Architecture have to do with a web content management system?

What does a stock broker have to do with Green Day’s next album? If it’s going to make a lot of money, you want to know what to do with the money. If you’ve realized that the way your content is arranged on the site is the reason users can’t use it – then your first step is to figure out how to architect your content.

How should the user be finding content?  Look at your numbers and figure out what isn’t getting activity. What is, but isn’t easy to find on the site right now? It isn’t time for a Content Management System yet. It isn’t even time for a design. It’s time to reconstruct your entire website, so that users can find what they want. There’s your first step in the CMS Diaries.

†A quote from a contractor, after I described my job to him. He described me as, “the accountant of the web”
*Unless your existing CMS or infrastructure actually prevents the ability to update stylesheets in a timely manner. If that’s the problem, you need a new CMS.
**Not a joke. I encountered a venn diagram in the shape of Balloons which was actually an org chart. It took three months for the marketing department to create it and despite that no one had seen it in two years, politics kept it coming over.

Seven Rules for Web Design My Mother Would Understand

Not too long ago I had a conversation with a graphic designer who was tasked with designing a website. Web Design is out of her area of immediate expertise, and she asked me if I had any pointers that I could share with her. After I sent her my email, I realized that I’ve said this before — and I’ll probably say it again. So, in case my mother, or anyone else, asks my thoughts on how to design a website,  here are seven rules that I’ll mouth off.

F is for F-shape

The eye moves in an F-shape on the web page. The hottest spot on the page is the upper left, the coldest spot is the middle right.  The last place the eye lands is the bottom right. This is why all navigations, regardless of whether the language reads right-to-left, are left-to-right horizontal, or left side top-to-bottom. Don’t break that rule. The trend today is centered horizontal navigations. When it’s a small website, it’s the best way to go. It leaves you with more room for work. Everything in the website design should support this physiological fact. The F-shape is how you show the user importance, take disgusting advantage of this principle. Design websites to follow the F-shape. http://www.useit.com/alertbox/reading_pattern.html

A Good Looking Header on Your Shoulders

Your header is at the top, and it tells the user where they are. The header is the first thing the eye sees. Get it right or they’ll leave.  Logo at the top, above navigation.  Center the logo, or put it in the upper left corner. If you have other universal elements, like a search box or an “Español” link, put those in the upper right, opposite of the left-side logo. Users have come to expect that, even Wikipedia got on board; follow the trends.

Don’t get cute with navigation.  Absolutely no Mystery meat navigation. Some people would say that’s a key qualifier for a web page that sucks: It should be obvious where your navigation is and where it takes you. Keep your headers simple and easy to read.

Rainbows are for Unicorns, not Web Pages.

One color for links, one color for paragraph text. Link color should not match the color of any other text on the page.  Ever. Ever. That’s how users get confused. It is okay for navigation to share color with something else on the page, so long as it’s obvious  that it’s navigation.

The old, “yellow on white background” is somewhat obvious, but how about blue on a black background? Ever try a orange with red? Don’t throw colors together. Built a palette first. Be very intentional with how you match colors. I rely heavily on kuler.adobe.com for helping me build color palettes, as this is a weakness of mine.

Be mindful of the cultural implications of color. Be careful with red — and avoid using it in plain text. Red is an attention grabber. Often with software, red means warning. If your website is themed red, that’s fine, but make sure you’ve accounted for how you’ll be able to grab attention if you need it. Color on the web page tells me if it was done by a pro or an amateur.

Isn’t that red annoying?

F is for Fitt’s Law

The bigger something is – a button or navigation, the easier it is to click and the faster they can click on it. Make buttons big. Woot.com is a perfect example. The bigger the navigation or the bigger your call-to-action button is, the faster someone is getting to where they want to be.

Call to Action Like You Call Your Mother

Consistent and frequent Calls-to-Action are good, but don’t ask someone to do 7 things on a page. On every page, every user should be told to do something with a Call-to-Action at least once: Order Now, Register, Learn More, Call us. If someone landed on a page, they should know what they’re supposed to do now that they’ve gotten there. That’s bounce-rate vs. exit rate. They bounce to another page, but they exit when they’re finished. If someone gets on a page, and doesn’t know why they’re there, they’ll leave.

Please, absolutely no more than three CTA’s per page —and they shouldn’t be the same size. The most important CTA should be the largest. The CTA should be like a link; different and distinct in color and shape from everything else. When the user gets to the web page, within 1/4 second she should know what to do, now that she’s there.

Read some techniques for Calls-to-Action

F isn’t For Fold

The fold is the point on the page where the user needs to scroll to see more content.  You’ll hear some folks say “don’t put anything important below the fold, users don’t see it”. That’s not true. So long as you indicate there’s stuff below the fold, you’re fine. Look at http://www.ilchiro.org/. I did some usability consulting for them. Ultimately, they broke my rule, so when you visit, you don’t catch there’s anything below the fold. My initial design lined up Current Publications and previous headlines. My intent was that the picture on the right get cut off – forcing the user to want to scroll down.
A vertical fold on a web page is fine. A horizontal fold isn’t.

Don’t Build a SteakHouse for a Vegetarian Chef

Don’t design something if you don’t know what you’re putting in it. Content before design. Content before Design. I swear that most website designs and redesigns go in the wrong order; design it, then write the content. That’s not a good idea. Architects don’t do it, web designers shouldn’t, either.  Know your content first. Design the site to support the content you already have. If it’s a new site, and they don’t have any of their own content, write it yourself.