Brain Traffic Blog » User Experience

Top 10 infographic resources

Christine Benson — Fri, 07 May 2010 17:21:44 +0000

We're infographic junkies here at Brain Traffic, and it's not hard to figure out why: Successful infographics are the marriage of great design and useful information. In other words, infographics are visually appealing content.

Converting your information to an infographic benefits your users by communicating your message in a visually compelling form. Whether they show up in internal deliverables or online, infographics seem to get everyone excited. Whenever I'm ready to create a new graphic, I use these resources for ideas and inspiration.

Great Lists from other sites
1. Smashing Magazine They've done several infographic round-up posts, but this is the one I keep going back to.
2. Six Revisions There's a strong consumption theme running through this collection. I've sent the coffee and beer graphics around to family and friends on more than one occasion.
3. Blog of Francesco Mugnai 50 great infographics. Nothing else.

Sites dedicated to Infographics
4. Flowing Data Great graphics and advice about how to create them. Props to Nathan Yau .
5. Chart Porn There's a humor category. (swoon)
6. Cool Infographics Lots of resources for creating graphics as well as examples. Check out the tips for designing infographics
7. We love Datavis The browsing on this one is not my favorite (the thumbnails are tough to decipher without clicking), but the graphics they pick are really strong.
8. How Toons Cartoons are not infographics in the traditional sense, but these are so entertaining I had to include this example.

Print Infographics
9. Feltron Annual Report Nicholas Felton does a report every year. It’s pretty amazing.
10. Good Magazine You know about Good, right? No? Just go there. Go there NOW.

Bonus – Interactive graphics!
I know I've already named 10, but I have to end with my all-time favorite interactive infographic. It's the New York Times Olympic Medal count – there's one for the Summer and Winter. They’re both so amazing, I love to go back to them even when it's not an Olympic year.

Don’t put content in your users’ blind spot

Angie King — Fri, 23 Apr 2010 16:38:30 +0000

So, you’ve done your research. You know what content is important to your users. You put that information on your website and pat yourself on the back for providing useful, useable content.

But wait. Don’t congratulate yourself just yet. Because simply putting content on a page doesn't guarantee users will find it. It could be hidden in a "content blind spot."

What’s a content blind spot?
Content blind spots occur when the information is there, but users can’t see it. In general, users scan and skip content, looking for clues before committing to read. But if the clues are missing, users won’t find the content.

Problems that prevent users from finding content include:

Information is not where users expect to find it, based on past experiences on that website or the web in general
Links do not look like links (e.g., link text not underlined or not blue)
Copy is “hidden” inside a graphic element or photograph
Page titles and links do not use relevant keywords or common user terms

Just like those little Smart Cars that hide in your Prius’s blind spot on the freeway, content stays unseen until someone changes their position. While driving, that means you or the Smart Car needs to speed up, slow down, or change lanes. Likewise, content stays hidden in a blind spot until either the user changes their approach to accessing the information, or you change the way it’s displayed.

What it’s like to experience the content blind spot
While doing our taxes, my husband asked me how much interest I paid on my student loan in 2009. I went to WellsFargo.com to find out.

I get all my bank-related documents electronically, so I knew right where to find that sort of information—or so I thought. I logged in to my student loan and went to the Statements & Documents tab. Once there, I saw a link called “Available Tax Documents.” Bingo.

“Hey! I’m looking for information to help me file taxes. The 'Available Tax Documents’ link will give me what I need.” (Click image to enlarge.)

Wrong. I went from feeling triumphant to confused within seconds—or however long it took a “Tax document not available online” error message to load.

After a few more failed attempts, I called customer service. A friendly representative walked me through the exact same process I had just gone through. I got the same error message. She was confused. I was confused. She transferred me to another department. The call was disconnected mid-Muzak stream. I was fuming.

I gave up. But my husband was convinced the information had to be online. I handed him my laptop, and wished him luck.

He found the information in two seconds.

“Oh. The information I was looking for was there along. Now I’m mad at Wells Fargo for making me feel stupid.” (Click image to enlarge.)

How the content snuck into my blind spot
I totally missed seeing my 2009 tax info because I had expected to find it in the Statements & Documents tab. Then, the tab rewarded my incorrect assumption by providing an “Available Tax Documents” link.

I didn’t even look for the information on the Account Activity page. Why? Because I was used to looking at a similar page for my checking account, and there is no “interest paid” information there. It’s just a summary of my balance. So why would I look on that page for interest information on my student loan account?

How to avoid the content blind spot
My experience is just one example of how content can “hide” from your user. To avoid this type of content blind spot:

Be consistent in where you put similar pieces of content throughout the site
Use relevant keywords and user terminology—especially when labeling links and navigation
Don’t mislead users with links that don’t deliver what they promise

If you put content in your users’ blind spot, they’ll leave your website feeling angry, confused, and frustrated. And without the information they needed. Not everyone has a husband with eagle eyes, you know?

Clients say the darnedest things: How to deal with bad feedback

Elizabeth Saloka — Thu, 18 Mar 2010 16:35:19 +0000

You spend weeks writing your client’s site. And it pays off. Your messaging is dead on. Your copy is fresh, clear, and active. Deliriously tired but satisfied, you email the document to your client.

Two days later you get the document back. You open it.

MAMA SAY WHAAAATTTTT?!

She. Butchered. Your. Document. Butchered it! Using track changes, she reformatted your beautiful bulleted lists into gigantic paragraphs filled with run-on sentence after run-on sentence. She added “dynamic” and “synergism” to the home page intro. As an overall comment, she requested you please “change all the links to ‘click here’, so people know to click.”

This feedback is bad. Very bad. But she’s the client. What do you do?

First, let’s clarify something.

This article is about dealing with bad feedback. Not dealing with negative feedback. Bad feedback and negative feedback are two different things.

Negative refers to how the client perceives your work.

Bad refers to how the client expresses their perception (negative or positive) of your work.

For my fellow visual learners, a chart:

Now let’s talk about types of bad feedback—and how to deal with them.

Below, a profile of four popular types of bad feedback accompanied by coping tips:

1. Jargon-y feedback.
Your client: “I’d like the copy to be more delightful.”

You: “Sure! No problem! I’ll make it more delightful!”

Wrong move, buddy.

When a client uses subjective, vague terms in feedback, you MUST call her on it. Right away. Even if you know stopping to dissect and analyze her feedback is going to take extra time and effort. Even if you have to revise schedules.

In the long run, you will save time, the content will be better, and your client will be happier. Promise.

If you can, help your client see the flaw in her logic. If she wants the intro to be more “robust,” respond with an open-ended question such as, “What does ‘robust’ mean to you, exactly?”

Also, make sure you get examples—ask the client to email you “robust” copy samples. That way you have something tangible to work with.

2. Vague feedback.

She says, “Looks great!!!” And that’s, like, it.

Your client read all 87 pages of your copy deck and had no changes? Riiiiiggghhht.

I’d bet my bellybutton this is what’s really going on: your client didn’tactually read your whole content doc. Or at least not thoroughly. She’s so busy worrying about the site’s design/other projects/her newborn octoplets she didn’t have time to read it.

So she’s cool with it. For now. That is, until her site is four hours from launch and she calls you for a boatload of last-minute revisions.

Do yourself and your client a big favor and make it very clear she needs to provide feedback now (remember, do so nicely!) or forever hold her peace.

Say something like, “I’m so tickled pink you went through ALL the content and you don’t haveANYrevisions. I’ll go ahead and send you the invoice and close out your project. It was great working with you!”

If she responds with, “Wait! Wait! I might still have some revisions!” you can firmly (but nicely!) remind her of the feedback process you agreed to when the project kicked off.

Tip: Include one or two questions using the comments feature in your document when you send it to the client. That way, if she gives you the ‘ol, “Looks great!” you can respond by asking if she had any further thoughts about your questions.

If she has no idea what you’re talking about, or if she responds with, “Oh, right. We’re going to have to change that,” you know she didn’t look it over thoroughly. Proceed with caution!

3. Contradictory feedback.

She says, “We only call ourselves ‘managers’ internally. Please don’t use that term in the copy.’”

You say, “Okay.”

What’s so contradictory about that, you ask? You’re right: It’s perfectly straightforward direction. Until you get your document back from your client and see she added ‘managers’ to the company tagline, home page headline, global navigation, footer, and image ALT tags.

Clearly, you need to clarify what your client wants.

But, for the sake of your working relationship, you also need to be careful not to put her on the defensive or make her feel foolish. There are many ways to proceed. For instance, you could say …

“Earlier you said I shouldn’t call you ‘managers.’ But throughout the document you inserted the word ‘managers.’ What exactly would you like me to do?”

There’s nothing wrong with that approach. I guess. But doesn’t this just seem friendlier …

“Hey! Thanks for the feedback. I had one quick question regarding the word ‘managers.’ I see you’ve added it in a few places—is it okay to use that term now? Thanks!”

See? Nicer. Generally, clients like it when you’re nice to them.

4. Nonsensical feedback.
Maybe she’s high on coffee. Or she prefers expressing thoughts verbally. Or maybe she’s been up all night watching Lethal Weapon and its sequels. Whatever the reason, sometimes your client will give feedback that, well, makes absolutely no sense.

“Could you please add another future verb to this entire beginning of copy paragraph? Thanks!”

Huh?

“I talked to Janice and she said Tom’s player copy doesn’t need any more action-oriented dropdowns (except maybe for twice?). Thanks!!”

Whazza who?

“Legal review. Stakeholders. Danny Glover. Thanks!!!”

Mmm.

If you have no clue in sweet heaven what she’s talking about (it does happen), schedule an in-person interview with her—over the phone works, too—so you can walk through her, um, “points.”

Start by reading a couple of her comments back to her. Hopefully, she’ll stop you after a couple minutes and say, “Geez. I wasn’t making any sense! I meant to say blah, blah, blah.” Or whatever. If she doesn’t, hopefully you’ll be able to glean some insight into her state of mind through verbal cues.

Finally, a request.

It’s easy to roll your eyes when a client gives you slick, vague, contradictory, nonsensical feedback. But you know what? She’s likely juggling a billion things, from wireframes to babies to Lethal Weapon DVDs. Your copy is just one of them. Cut her some slack. And remember, she’s not a writer. If she were, she wouldn’t need you.

If you’re willing to have patience and put forth a little extra effort, you can help your client. You can educate her about content best practices. You can show her examples of successful websites with great content. You can take time to really understand where she’s coming from, so you can put her feedback in context.

In the end, your content will be better. And your client will be grateful. So, what do you say, ‘ol chum?

Personal pronouns: It’s okay to own your web copy

Angie King — Thu, 11 Mar 2010 17:29:31 +0000

Using personal pronouns may sound like a simple, common-sense web writing best practice. Speaking directly to users with the word “you” is something most companies get on board with easily enough. But those same clients often ask us to avoid self-referential pronouns like “we,” “our,” and “us” in their web copy.

Granted, sometimes there are legitimate legal considerations that keep companies from getting personal with their web copy. (I’ll get into these legalities later.) Other times, it’s simply a matter of being overly cautious or old-fashioned.

Why use personal pronouns in web copy?

In my experience, many larger corporations have trouble breaking free from the formal business communications style they’ve been using for years. But guidelines that limit the use of personal pronouns should be reconsidered now that we’re in the digital age. These days, content needs to speak to users clearly and directly. It needs to compete for their attention.

A simple way to grab your users’ attention is by using personal pronouns in your web copy. Why? Personal pronouns reflect the way real people write and speak.

For example, most of us don’t refer to ourselves in the third person. We use first-person (me, we, our, us) and second-person (you, your) pronouns in our email exchanges, Facebook statuses, and Twitter feeds—channels that compete for your users’ attention every day.

Using these first- and second-person pronouns on your corporate website will:

Help users connect with the content
Help users understand the content
Identify who owns the content
Make writing the content easier

What happens if you DON’T use personal pronouns in web copy?

Not using personal pronouns forces you to repeat your company’s name throughout your website. This approach creates awkward sentences that are tedious to read and to write. The repetition can also set off keyword stuffing alarms. At the very least, your website ends up sounding unnecessarily formal and stuffy.

Worse yet, the bland third-person pronoun “it” may creep into your web copy and force you into using awkward sentence constructions. For example, something simple like “Content strategy is all we do. And we do it well” becomes “Brain Traffic believes its focus on content strategy is an advantage.” Blech.

Coupled with company name repetition, “it” creates confusion around who is speaking. It’s hard to tell who owns the content when it’s written so generically. (Right?) And if you want your users to feel connected to your brand, it’s important they know you stand behind your content.

When legal reasons prevent personal pronouns

Of course, sometimes there are legitimate legal grounds for not using personal pronouns. For example, we work with a few clients who sell cobranded products. Their legal departments strictly forbid the use of personal pronouns in order to avoid making sweeping statements about the collective “we.”

To illustrate what I mean, let’s say White Castle partnered with Holiday station stores on a special line of slider-scented gasoline. (Ok. That’s gross. But it’s the first thing I came up with from a quick glance out the office window.)

Anyway, if White Castle/Holiday created a website dedicated to this cobranded product, legal teams may advise against using “we/our/us” in the content. Value statements and “about us” sections get a bit more complex when cobranding. Maybe Holiday wouldn’t like being lumped together with White Castle on general statements about what “we” as a company believe in. Or, vice versa.

Large corporations with many divisions may also have legal concerns about using personal pronouns. Insurance companies are a good example. While Division A offers products similar to those of Division B, the products may have completely different rules and regulations restricting their features and use.

Let’s say Acme Insurance Company uses personal pronouns on their website when describing their products. If a Division B customer purchases a plan based on benefits they saw on a Division A product page, the customer may have grounds for a legal complaint. But by avoiding personal pronouns and only using the specific division name in product descriptions, Acme reduces their chances of getting sued.

So, to be safe, it’s better not to make broad “we/our/us” statements when there’s this type of product overlap.

How to prevent legal issues with personal pronouns

To avoid finding out the hard way, ask your client for any legal restrictions surrounding the use of personal pronouns at the start of the project. Because I can tell you from experience, going back and rewriting copy decks to eliminate all “we/our/us” statements is not fun.

When to use personal pronouns on your website

Unless legal guidelines prevent you from using personal pronouns, go ahead and get personal with your web copy. Using this type of plain language will make your web writing process easier. Even better, your users will more quickly connect and engage with your web content.

Personally, I think it’s a great style choice.

Thanksgiving is over, turkey: When to kill your darlings

Angie Halama — Wed, 20 Jan 2010 16:56:31 +0000

My suburban neighborhood is pretty typical, with the exception of the 200-acre wooded park in the middle of it. I live right on the edge of the park, which means deer, ducks, pheasants, and turkeys roam near my house. And I enjoy that.

But a certain turkey has really started getting in my way. Literally.

He often hangs out on the corner of a four-way stop. At first it was funny, like he was waiting for the bus.

Then, this weekend as I approached the stop, the turkey was in the middle of the intersection. I waited for him to cross the road (I see the joke here), but he had other ideas. He headed right for my car and proceeded to block me every time I tried to swerve around him. He was so close I couldn’t even see him until his blue head popped up over the hood and he "gobble-gobbled" at me.

It was ridiculous. And maddening. I had no idea what to do. I wasn’t about to get out of the car—turkeys are surprisingly large. And this one clearly had no fear.

I finally escaped, and then I called Animal Control, who said, and I quote, "We’re aware of the turkey."

Apparently, even the local news had heard about this traffic-stopping bird. Police hadn’t been able to catch him. They even hired a professional trapper. And guess what? His trap was stolen.

Why? Because the neighbors like the turkey. They’ve been feeding him. They think of him as their mascot. They’ve even called city hall to protest his capture. They love this turkey so much that they are willing to put up with the hazards and annoyance this turkey imposes on, well, me.

So. Do you have any turkeys on your website? Let’s discuss.

A navigation "concept"
Website navigation helps users find the information they’re looking for. Sometimes.

The Flash-powered navigation on thomasedison.org includes an impressively long list of Edison’s inventions. But it literally spirals and moves as you use it, and the font is so small it’s illegible. I want to know more about Edison, but the design is getting in my way.

Here’s another example: The tiny gray boxes at the top of the site for fashion designer Alexandre Herchcovitch may look sleek, but as unlabeled navigation they tell you absolutely nothing about the content—unless you click each one. (P.S. Incredibly loud intro music and no off button? Isn’t that against the law?)

Give me what I’m looking for
If you give me a text link, make sure that when I click I get whatever the text tells me I will.

If a "Read more" link on a "Project Management Courses" page goes to a video, that video should give information on course content. It shouldn’t just show course participants saying "hi." This is only interesting to the people in the video.

And the video ending, showing a participant in his underwear and covered with Post-It notes, helped me decide to never sign up for these classes.

Show, don’t tell
Don’t fall victim to the "blah blah blah." Just give me the goods.

Ladder Golf site visitors are likely interested in ordering this new game or learning how it’s played. So the homepage doesn’t need all kinds of content telling them why the product is so great. Instead, move that animated banner demonstrating the game from way at the bottom of the page to the top, and give visitors what they want.

Too much fun
If you’re looking for product information on the Beggin’ Strips dog snacks site, you’re in for some unexpected fun. Play games! Put a picture of yourself and your dog in a music video! Lots of fun—and no actual product info anywhere. Hmm. Bacon-flavored turkey?

Why did the turkey cross the road?
I don’t care. Because it’s not funny.

Do you have turkeys on your website? No matter how fun, cute, or beautifully designed a turkey is, if it keeps users from getting to the information they want, then it’s causing an annoying, even aggravating, experience.

Think of it this way: Does anyone want a turkey getting in their way? No, they don’t. Trust me.

Members vs. guests: how to label users on authenticated sites

Angie King — Tue, 12 Jan 2010 19:31:34 +0000

Recently, Brain Traffic Twitter friend Taj Moore (@tajmo) asked us for some advice about copy for authenticated websites, or websites that require registration in order to log in for firewalled content and/or functions.

Taj wanted to know our thoughts on what to call members vs. non-members, and logged in members vs. non-logged in members.

Taj’s question inspired quite the philosophical discussion around here. And by “philosophical discussion,” I mean: “really long email chain.”

We like Amazon’s approach to labeling members.

In short, we side with Amazon’s way of doing things. But, as it is with anything of value, it was the ride that mattered. Here’s how we came to our conclusion.

@tajmo to @braintraffic

Are there terms to diff. bw member logged in and member not logged in? "Guest" not useful bc conflates w/ non-member.

…Or another tack: how about a word for guest/visitor who is not a member?

…b.c. I am leaning toward "logged-in," "logged-out," & "non-member" but thought you might have better insight.

Kristina: Let’s discuss. Who wants to go first?

Katie D.: Just call everyone Earthlings. We’re all just people, after all.

Christine A.: Is he asking about a user-facing label? I’d question whether there is any value in showing those terms to users.

I like Amazon’s approach. They use a cookie to identify users who have accounts, and ask them to log in only when they do something significant like go to their shopping cart.

Amazon doesn’t tell people they’re logged in, logged out, non-member, etc. They just put the person’s name up there if the cookie is in place, or show a generic login link if it isn’t. They don’t need users to keep track of their own status.

If he’s asking about what the developers/UX people/etc should call it, it doesn’t much matter as long as they’re consistent and the labels identify clearly defined roles.

Elizabeth (her email passing Christine’s on the information superhighway from NYC):

I’d say, the first question is, how are these terms going to be used? Are they internal or user facing?

If they’re meant to be user-facing, they don’t really seem necessary. If the user is logged in to the site, you’d address them by name. If they’re not logged in, you’d probably call them a guest. If they’re a member who isn’t logged in, you can’t really know that. Not sure why it’d be necessary to label each separately, unless he’s talking about terms to be used internally …

Angie K.: Whoa. It’s like Elizabeth and Christine A. had a cross-country mind meld.

Elizabeth: We’re Vulcans!

Twitter says…

@braintraffic to @tajmo

Address logged in members by name. Everyone else, guest. Internally, use whatever labels you like. Just be consistent, please!

Yeah, we heart Amazon. But nobody’s perfect.

When not logged in, Amazon covers all of the bases—member, non-member, logged in, or not logged in. Check it out:

Hello—greets the user, whether a member or not.
Sign in—invites members to log on.
Start here—gives non-members the opportunity to create an account.

When you’re logged in, Amazon greets you by name and gives you the option to log off. Nice.

However, when I used our company’s login to do some office supply shopping the other day, “Not Brain?” had me giggling for hours.

Behold, the mighty hive

Kristina Halvorson — Fri, 08 Jan 2010 15:56:11 +0000

Happy New Year!

(My New Year’s resolution was not to resolve anything this year. So far, I’m doing great.)

Say, I’ve gotten several requests for the "hive" diagram I use in presentations. It’s a simple, visual example of how web project team roles interact with one another.

This is it:

(click to see full-sized image)

I found the diagram on Skillset.org back in ’08, but apparently they’ve pulled it down since then. So, as my gift to you, here it is. Wield it within your organizations at will.

“Hand-Crafted Content” vs. the Machine: Betting on the People

Kristina Halvorson — Mon, 14 Dec 2009 20:33:35 +0000

I just finished reading Michael Arrington’s "The End of Hand-Crafted Content " (also published elsewhere as "AOL’s New Fast-Food-Content Strategy Means the End of Journalism You Actually Enjoy").

How. Depressing.

Since reading Wired‘s apocalyptic article, "The Answer Factory: Demand Media and the Fast, Disposable, and Profitable as Hell Media Model," I’ve certainly spent plenty of time bitching about the lowering of our already low standards for web content.

Here’s a summary of how mass-produced content works:

Pieces [(content to be created)] aren’t dreamed up by trained editors nor commissioned based on submitted questions. Instead they are assigned by an algorithm, which mines nearly a terabyte of search data, Internet traffic patterns, and keyword rates to determine what users want to know and how much advertisers will pay to appear next to the answers.

Then, the assignment is posted to a ginormous database; it’s accepted by a freelancer somewhere, who then throws something together as quickly as possible because he’s only getting paid, like, four dollars to create it. (Want to know what the best vodka in the world is? A random bartender from a random bar in Florida KNOWS THE ANSWER!) (Uh, you’ll have to sit through the ad first.)

So, in one fell swoop, Demand Media—and now AOL—are both flooding the search engines with awful, terrible content and gleefully commodifying the work of writers, videographers, editors, and other media professionals around the world.

I hate them. Oooooo, how I hate them.

But, you know what?

McDonald’s didn’t put La Belle Vie out of business.

Does McDonald’s make more money than La Belle Vie? Of course they do. They’re freakin’ McDonalds. But La Belle Vie is running a very fine, profitable business, thank you very much, turning out exquisite French food that makes me want to weep with joy. (Even their cocktail menu is extraordinary.) (No, I do NOT say that about every cocktail menu.)

You don’t have to eat at La Belle Vie to appreciate the metaphor. Not everybody wants McDonald’s, and nobody wants McDonald’s all the time. People go out of their way to find what will satisfy, even delight, their appetites.

AOL and Demand Media (and dozens more competitors, I’m sure) are anathema to pretty much anyone who wants an even slightly obscure question answered online. But in the long run, I’m betting on people, not algorithms. Just because I clicked on your stupid video doesn’t mean I can’t use my back button.

p.s. Google, get on this.

Ask yourself

Christine Benson — Wed, 09 Dec 2009 15:25:48 +0000

Do you really need that?

As an Information Architect and HUGE Martha Stewart fan, I have unrealistic expectations about how organized my house should be. I periodically take on projects to get sections of my house in order. I approach them similar to my work projects, with audit and analysis, followed by designing a solution and implementing the structure.

Early attempts at these projects would always stall in audit and analysis. I would come across the random things that just didn’t seem to go anywhere. Unable to find a home or at least some friends for said item would paralyze me into inaction.

But I’ve since found a solution that’s made my projects finish without fail… I get rid of it.

This doesn’t always work, but approaching a large organizational task by assuming that I will be getting rid of anything that is redundant or without a home clarifies the usefulness of the item and my emotions about it.

If I truly cannot part with it, then it needs a home. Usually that home is a highly prominent location that allows for organization based off of frequent use, like a utility drawer.

I’ve since transferred this process to wrangling source content. When I’m left with the stragglers that aren’t like anything else, I consider a series of questions:

"What will this information add to the experience?"

"What would be lost if this information went away?"

"Who would be affected if they look for this and can’t find it?

"By including this information, will it get in the way of more important information?"

If any or all of the answers to the above mean I need to keep it and there’s still no obvious home, perhaps I need to reconsider how I’ve organized things.

If I don’t need to keep it, then it’s simple. It just goes away.

Useful, usable website content is not about providing every single piece of information that anyone could ever think of, but instead focusing the information that people are most likely to want and use.

Getting rid of extra stuff clarifies your message and makes it easier for the majority of people to learn what they came there for.

So when you’re faced with leftover pieces of content start with "what if we got rid of it?" If you can answer that, the rest is much easier.

A little label love goes a long way

Christine Benson — Wed, 02 Dec 2009 16:07:38 +0000

I’m currently seven months pregnant. Rather than developing nesting tendencies and actually cleaning my home, I have developed an addiction to reading craft blogs.

On many of these blogs, I’ve noticed the trend of labeling the comments section with something more customized than the standard "comments."

Here are a couple of examples:

via UK lass in US:

via V and Co:

It’s a great combination of being human and still being useful. This small change demonstrates an individual’s voice, but also clearly communicates the goal of the section.

I also thought it was a great example of how content (rather than design) can show brand and personality. These are blogs that are built on standard templates, but with this one little change, I suddenly felt a connection to a human on the other end.

Added bonus? People seemed to comment on these blogs more than the ones simply labeled "comments" or "leave a reply".

Many companies are locked into template designs that they feel constrained by, resulting in lamentations about being unable to add a lifestyle image or change a font. These projects are often time-consuming and expensive. Neither of those terms are popular, especially in the current economic climate.

So, when half of the room is screaming for a redesign while the other half is screaming back about time and budget, consider focusing on how the content can improve your site.