The first thing to understand about content strategy is that no two people understand it the same way. It’s a relatively new — and extremely broad — discipline with no single definitive definition. A highly informative Knol on content strategy defines it as follows:

“Content strategy is an emerging field of practice encompassing every aspect of content, including its design, development, analysis, presentation, measurement, evaluation, production, management, and governance.”

This definition is a great place to start. Although the discipline has clearly evolved, this breakdown of its scope makes perfect sense. The aspects of content strategy that matter most to Web designers in this definition are design (obviously!), development, presentation and production. In this article, we’ll concentrate on the relationship between content strategy and design in creating, organizing and displaying Web copy.

As a writer and content strategist myself, I’ve worked with designers in all of these areas and find the creative process highly enriching. I’ve been fortunate enough to work with designers who are quick to challenge ideas that are unclear or unsound, who are brilliant at creating striking visual representations of even the most complex concepts. A lively interplay between design and content is not only fun, but is how spectacular results are achieved. This is why content strategy should matter a great deal to designers.

What Is Content Strategy, And Why Should A Designer Care?

Content strategy is the glue that holds a project together. When content strategy is ambiguous or absent, don’t be surprised if you end up with the Internet equivalent of Ishtar. When content strategy is in place and in its proper place, we’re on our way to producing beautiful and effective results.

While wrapping one’s head around content strategy might be difficult, the thing that makes it work is very simple: good communication. Sometimes a project moves along like a sports car on a superhighway. Other times, the road is so full of bumps and potholes that it’s a wonder we ever reach our destination. As we explore the relationship between content strategy and design, I’ll detail how I keep the channels of communication open and go over the workflow processes that I’ve used to support that effort. I hope that sharing my experiences (both positive and negative) will help you contribute to and manage projects more effectively and deliver better products to clients.

How To Get Started: The First Step Is The Longest

Project manager: We need a landing page for client X.

Designer: I can’t start the design until I see some content.

Writer: I can’t start writing until I see a design.

You may find this dialogue amusing… until it happens to you! At our firm, we find that the best way to get past such a standoff is to write first. This is because content strategy, at a fundamental level, frames a project for the designer. As a content strategist, my job is to articulate the why, where, who, what and how of the content:

  • Why is it important to convey this message? This speaks to purpose.
  • Where on the website should the message appear? This speaks to context.
  • Who is the audience? This speaks to the precision of the message.
  • What are we trying to say? This speaks to clarity.
  • How do we convey and sequence the information for maximum impact? This speaks to persuasiveness.

Bringing it down to a more detailed level, let’s consider a landing page. A content strategist will determine such things as the following:

  • Audience
    Is the audience sophisticated? Down to earth? College-level? Predominately male? Female? Etc.
  • Word count
    Some pitches scream for long copy, while others must be stripped to the bare minimum. SEO might factor into the equation as well.
  • Messaging priorities
    What is the most important point to convey? The least important? What needs to be said first (the hook)? What needs to be said just leading up to the call to action?
  • Call to action
    What will the precise wording be? What emotional and intellectual factors will motivate the visitor to click through?

Clear direction on these points not only helps the writer write, but helps the designer with layout, color palettes and image selection. When we start with words, we produce designs that are more reflective of the product’s purpose.

Landing pages are a great place to try this workflow, because in terms of content strategy, they are less complex than many other types of Web pages. A product category page, on the other hand, might have a less obvious purpose or multiple purposes, considerably greater word counts, more (and more involved) messaging points, and a variety of SEO considerations, all of which would affect its design.

Quick Tips for Getting Started

  • Make sure someone is specifically responsible for content strategy. If strategic responsibility is vague, your final product will be, too.
  • Slow down! Everybody, me included, is eager to dive headfirst into a new project. But “ready-aim-fire” is not a winning content strategy. Make sure everyone is on the same page conceptually before cranking out work.
  • If content strategy falls on your shoulders as a designer, cultivate an understanding of the discipline. Resources are listed at the end of this article to help you.
  • Make sure designers and writers understand what their roles are — and are not. There’s no need for writers to tell designers how to design, or for designers to tell writers how to write.

Perfecting The Process: Break Up Those Bottlenecks

Project manager: How are things coming along?

Developer: I’m waiting on design.

Designer: I’m waiting on content.

Writer: I’m waiting on project management.

Web development projects in particular involve a lot of moving parts, with potential bottlenecks everywhere. The graphic below describes our Web development process, with an emphasis on the design and content components. Chances are, whether you are freelancing or at an agency, at least parts of this should look familiar:

The process is by no means perfect, but it is continually improving. In the next section, we’ll look at the many types of content-design difficulties you might experience.

To help our designers lay out text for wireframes and designs, we utilize content templates based on various word counts. These templates also incorporate best practices for typography and SEO. When the designer drops the template into a wireframe, it looks like this:

The use of content templates not only takes a lot of guesswork out of the designer’s job, but also speeds up client reviews. When clients are able to see what the content will roughly look like in the allotted space, they tend to be more comfortable with the word counts and the placement of text on the page.

Communication can be streamlined using project management software. We use Basecamp, which is a popular system, but many other good ones are available. If you’re a freelancer, getting clients to work on your preferred project management platform can be an uphill battle, to say the least. Still, I encourage you to try; my experience in managing projects via email has been dismal, and many freelance designers I know express the same frustration.

The big advantage of a project management system is that it provides a single place for team members to manage tasks and interact. Internal reviews of design templates is one good example. The project manager can collect feedback from everyone in one place, and each participant can see what others have said and respond to it. Consolidating this information prevents the gaps and miscommunication that can occur when projects are managed through multiple email exchanges. Designers can see all of the feedback in one place — and only one place. This is a big time-saver.

Companies often flush away millions upon millions on worthless, pointless, “fix it once and for all” website redesigns. All types of organizations are guilty: large government agencies, Fortune 500s, not-for-profits and (especially) institutions of higher education.

Worst of all, these offending organizations are prone to repeating the redesign process every few years like spendthrift amnesiacs. Remember what Einstein said about insanity? (It’s this, if you don’t know.) It’s as if they enjoy the sensation of failing spectacularly, publicly and expensively. Sadly, redesigns rarely solve actual problems faced by end users.

I’m frustrated because it really doesn’t have to be this way. Let’s look at why redesigns happen, and some straightforward and inexpensive ways we might avoid them.

The Diagnostic Void

Your users complain about your website’s confounding navigation, stale content, poor usability and other user experience failures. You bring up their gripes with the website’s owners. They listen and decide to take action. Their hearts are in the right place. But the wheels quickly come off.

Site owner

Most website owners don’t know how to diagnose the problems of a large complex website. It’s just not something they were ever taught to do. So, they’re put in the unfortunate, uncomfortable position of operating like country doctors who’ve suddenly been tasked to save their patients from a virulent new pandemic. It is their responsibility, but they’re simply unprepared.

Vendor

Sadly, many website owners fill this diagnostic void — or, more typically, allow it to be filled — with whatever solution sounds best. Naturally, many less-than-ethical vendors are glad to dress up their offerings as solutions to anyone with a problem — and a budget. The tools themselves (search engines, CMS’, social apps) are wonderful, but they’re still just tools — very expensive ones, at that — and not solutions to the very specific problems that an organization faces. Without proper diagnostics to guide the configuration of tools, any resulting improvements to the user experience will be almost accidental.

Design agency

Sometimes design agencies are brought in to fill the diagnostic void. And while not all agencies are evil, a great many follow a business model that depends on getting their teams to bill as many hours as they can and as soon as possible. Diagnostics can slow the work down (which is why clients rarely include a diagnostic phase in their RFPs). So, many agencies move to make a quick, tangible impression (and make their clients happy) by delivering redesigns that are mostly cosmetic.

A pretty face can last only a few years, but by then the agency is long gone. Invariably, the new owner wishes to make their mark by freshening or updating the website’s look. And another agency will be more than happy to oblige. Repeat ad nauseam, and then some.

Oh, and sometimes these redesigns can be pricey. Like $18 million pricey.

See why I’m so grouchy?

Forget the Long Tail: The Short Head Is Where It’s At

Whether you’re a designer, researcher or website owner, I’ve got some good news for you: diagnostics aren’t necessarily difficult or expensive. Better yet, you’ll often find that addressing the problems you’ve diagnosed isn’t that hard.

And the best news? Small simple fixes can accomplish far more than expensive redesigns. The reason? People just care about some stuff more than they care about other stuff. A lot more. Check this out and you’ll see:

Monster Graph

This hockey-stick-shaped curve is called a Zipf curve. (It comes from linguistics: Zipf was a linguist who liked to count words… but don’t worry about that.) Here it is in dragon form, displaying the frequency of search queries on a website. The most frequently searched queries (starting on the left) are very, very frequent. They make up the “short head.” As you move to the right (to the esoteric one-off queries in the “long tail”), query frequency drops off. A lot. And it’s a really long tail.

This is absolutely the most important thing in the universe. So, to make sure it’s absolutely clear, let’s make the same point using text:

Query’s rank Cumulative % Query’s frequency Query
1 1.40% 7,218 campus map
14 10.53% 2,464 housing
42 20.18% 1,351 web enroll
98 30.01% 650 computer center
221 40.05% 295 msu union
500 50.02% 124 hotels
7,877 80.00% 7 department of surgery

In this case, tens of thousands of unique queries are being searched for on this university website, but the first one accounts for 1.4% of all search traffic. That’s massive, considering that it’s just one query out of tens of thousands. How many short-head queries would it take to get to 10% of all search traffic? Only 14 — out of tens of thousands. The 42 most frequent queries cover over 20% of the website’s entire search traffic. About a hundred gets us to 30%. And so on.

It’s Zipf’s World; We Just Live in It

This is very good news.

Want to improve your website’s search performance? Don’t rip out the search engine and buy a new one! Start by testing and improving the performance of the 100 most frequent queries. Or, if you don’t have the time, just the top 50. Or 10. Or 1 — test out “campus map” by actually searching for it. Does something useful and relevant come up? No? Why not? Is the content missing or mistitled or mistagged or jargony or broken? Is there some other problem? That, folks, is diagnostics. And when you do that with your website’s short head, your diagnostic efforts will go a very long way.

The news gets better: Zipf is a rule. The search queries for all websites follow a Zipf distribution.

And the news gets even jump-up-and-down-and-scream-your-head-off better: Zipf is true not only for your website’s search queries. Your content works the same way! A small subset of your website’s content does the heavy lifting. Much of the rest has little or no practical value at all. (In fact, I’ve heard a rumor that 90% of Microsoft.com’s content has never, ever been accessed. Not once. But it’s a just a rumor. And you didn’t hear it here.) Bottom line: don’t redesign all of your content — focus on the stuff that people actually need.

You’ll also see a short head when it comes to your website’s features. People need just a few of them; the rest are gravy.

And there’s more. Of all the audience types that your website serves, one or two matter far more than the others. What tasks do those audience types wish to accomplish on your website? A few are short-head tasks; the rest just aren’t that important.

As you can see, the Zipf curve is everywhere. And fortunately, the phenomenon is helpful: you can use it to prioritize your efforts to tweak and tune your website’s content, functionality, searchability, navigation and overall performance.

Your Website Is Not A Democracy

When you examine the short head — of your documents, your users’ tasks, their search behavior and so forth — you’ll know where to find the most important problems to solve. In effect, you can stop boiling the ocean…

Sailing the ocean

… and start prioritizing your efforts to diagnose and truly solve your website’s problems.

Now, let’s put these short-head ideas together. Below is a report card for an academic website that starts with the short head of its audience:

Diagram

In other words, of all the audience types this university website has, the three most important are people who might pay money to the university (applicants,) people who are paying money now (students) and people who will hopefully pay money for the rest of their lives (alumni). How do we know they’re the most important audiences? We could go by user research; for example, the analytics might suggest that these audiences generate more traffic than anyone else. Or perhaps the university’s stakeholders believe that these are the most important ones in their influence and revenue. Or some combination of both. Whatever the case, these three audiences likely swamp all other segments in importance.

Then, we would want to know the short-head tasks and information needs of each audience type. We might interview stakeholders to see what they think (column 2). And we might perform research — user interviews and search analytics, for example — to find out what users say is most important to them (column 3).

Of course, as the good folks at xkcd demonstrate, stakeholders and users don’t always see things the same way:

Universal site

That’s why talking to both stakeholders and users is important. And once you’ve figured out the short head for each, you’ll need to earn your salary and, through some careful negotiation, combine your takes on each audience type’s needs. That’s what we’ve done in column 4.

Finally, in column 5, we’ve tested each task or need and evaluated how well it works. (Because it’s a university-related example, letter grades seemed appropriate.) You can do this evaluation in an expensive, statistically significant way; but really, enough research is out there to suggest that you don’t need to spend a lot of time and money on such testing. More importantly, these needs and tasks are often fairly narrow and, therefore, easy to test.

So, after testing, we can see what’s not going well. Finding information on “mentoring” is hard for applicants. And current students have a devil of a time when they “look up grades.”

Now we’re done diagnosing the problems and can begin making fixes. We can change the title of the “Paired Guidance Program” page to “Mentoring.” We can create a better landing page for the transcript application. The hard part, diagnostics, is out of the way, and we can now fix and tune our website’s performance as much as our resources allow.

From Project To Process To Payoff

These fixes are typically and wonderfully small and concrete, but because they live in the short head, they make a huge and lovely impact on the user experience — at a fraction of the cost of a typical redesign.

The tuning process itself is quite simple. It’s what we used to arrive at the report card below:

Chart

If you repeat this simple process on a regular basis — say, every month or quarter — then you can head off the entropy that causes fresh designs and fresher content to go rotten. Thus, the redesign that your organization has scheduled for two years from now can officially be canceled.

Your website’s owners ought to be happy about all this. And you should be, too: rather than tackling the project of getting your website “right” — which is impossible — you can now focus on tweaking and tuning it from here on out. So, forget redesigns, and start owning and benefiting from a process of continual improvement.

Special Thanks – Illustrations

Eva-Lotta is a UX Designer and Illustrator based in London, UK where she currently works as an interaction designer at Google. Besides her daytime mission of making the web a more understandable, usable and delightful place, she regularly takes sketchnotes at all sorts of talks and conferences and recently self-published her second book. Eva-Lotta also teaches sketching workshops and is interested in (something she calls) visual improvisation. Exploring the parallels between sketching and improvisation, she experiments with the principles from her theater improvisation practice to inspire visual work.

After several grueling days I had finally finished the proposal. I sent it off and waited for a response. Nothing. After a few weeks, I discovered that they were “just looking”. Despite the urgency and aggressive timeline for the RFP (Request For Proposal) plus the fact that we had done business with this organization before, the project was a no-go. My days of effort were wasted. Not entirely, though, because the pain of that loss was enough to drive me to decide that it wouldn’t happen again.

Why writing Project Proposals is a bad idea?

I work at a Web development company and we’ve experimented with proposal writing a lot over the years. We’ve seen the good and the bad, and we have found something better. In this article I will share the pains that we have experienced in the proposal writing process, the solution we adopted, and our process for carrying out that solution. I’ll also give you guidelines to help you know when this solution is and isn’t appropriate.

Proposal Writing Causes Pain

After several years of writing proposals, we began to notice that something wasn’t right. As we considered the problem we noticed varying levels of pain associated with the proposal writing process. We categorized those pains as follows:

The Rush
Getting a proposal done was usually about speed. We were racing against the clock and working hard to deliver the proposal as efficiently and as effectively as possible. However, sometimes corners would get cut. We’d reuse bits and pieces from older proposals, checking and double-checking for any references to the previous project. While the adrenaline helped, the rush gets old because you know that, deep down, it’s not your best work. Besides, you don’t even know if you’re going to close the deal, which leads to the next pain.

The Risk
Our proposal close ratio with clients that came directly to us was high. We’d work hard on the proposals and more often than not, we’d close the deal. The risk was still there, however, and I can think of several proposals that we had spent a lot of time and effort on for a deal that we didn’t get. Not getting the deal isn’t the problem — the problem is going in and investing time and energy in a thorough proposal without knowing if there is even the likelihood that you’re going to close the deal.

The Details
The difference between a project’s success and its failure is in the details. In proposal writing, the details are in the scope. What work is included, what is not, and how tight is the scope? Now, this is where the “rush” and the “risk” play their part. The rush typically causes us to spend less time on details and the “risk” says: “Why spell it all out and do the diligence when you might not even get the project?” A self-fulfilling prophecy, perhaps, but a legitimate concern nonetheless. Selling a project without making the details clear is asking for scope creep, and turns what started out as a great project into a learning experience that can last for years.

Now, writing is an important part of the project and I’m not about to say you shouldn’t write. Having a written document ensures that all parties involved are on the same page and completely clear on exactly what will be delivered and how it will be delivered. What I’m saying, though, is that you should stop writing proposals.

Write Evaluations, Not Proposals — And Charge For Them

Write Evaluations, Not Proposals — And Charge For Them

A few years back, we decided to try something new. A potential client approached us and rather than preparing another project proposal, we offered the client what we now call a “Project Evaluation.” We charged them a fixed price for which we promised to evaluate the project, in all of our areas of expertise, and give them our recommendations.

They agreed, paid the price, and we set out to deliver. We put a lot of effort into that evaluation. We were in new territory and we wanted to make sure that we delivered it well. So we finished the report and sent it to them. The client liked it, agreed with our recommendations, and started a contract with us to do the work.

That project became a game changer for us, starting an on-going relationship that opened doors into a new market. It was the process of the evaluation itself that brought the new market potential to our attention, and gave us the opportunity to develop this business model. It was a definite win, and one that a project proposal couldn’t have delivered.

What Is A Project Evaluation?

A “Project Evaluation”, as we’ve defined it, is a detailed plan for the work that is to be done on a project, and explains how we do it. We eliminate the guess work, and detail the project out at such a level that the document becomes a living part of the development process, being referred back to and acting as the guide towards the project’s successful completion.

The Benefits Of (Paid) Project Evaluations

As we put our proposal writing past behind us and embraced the evaluation process, we noticed a strong number of benefits. The most prominent of those benefits are the following.

Qualification

If a client is unwilling or unable to pay for a project evaluation, it can be an indicator that the project isn’t a match. Now, we may not always charge for evaluations (more on that later). We also recognize a deep responsibility on our part to make sure that we have intelligently and carefully explained the process and value of the evaluation. After all that is done, though, you may run into potential clients who just don’t want to pay what you’re charging, and it’s better to find this out right away then after writing a long proposal.

Attention to Details

Having the time available to do the research and carefully prepare the recommendations means that we are able to eliminate surprises. While the end result may be a rather large document, the details are well organized and thorough. Those details are valuable to both the client (in making sure they know exactly what they’re getting) and to the development team (in making sure that they know exactly what they’re delivering).

No Pricing Surprises

Figuring out all the details and ironing out a complete scope means that we’re able to give a fixed price, without surprises. This gives the client the assurance up front that the price we gave them is the price they’ll pay. In more than a few cases, the time we’ve spent working out the details has eliminated areas of concern and kept our margins focused on profit, not on covering us “just in case.”

Testing the Waters

When a potential client says “Yes” to an evaluation, they are making a relatively small commitment — a first step, if you will. Rather than a proposal that prompts them for the down payment to get started on the complete project, the evaluation process gives us time and opportunity to establish a working relationship. In most cases, the process involves a lot of communication which helps the client learn more about how we work, as we learn more about how they work. All this is able to take place without the pressure of a high-budget development project. And by the end of the evaluation, a relationship is formed that plays a major factor in the decision process to move forward.

Freedom to Dream

Occasionally, we spend more time on an evaluation than we had initially expected. But knowing how our time is valued has given us the freedom to explore options and make recommendations that we might not have made otherwise. In our experience, the extra time and energy that the context of a paid evaluation provides for a project has consistently brought added value to the project, and contributed to its ultimate success.

The Evaluation Writing Process

The Evaluation Writing Process

Over the years we have refined (and continue to refine) a process that works well for us. As you consider the process, look for the principles behind each step, and if you decide to bring this into your business, look for ways to adapt this process and make it your own.

#1 — Do the Research

The heart of the evaluation process is the research. If it’s a website redesign project, we read through each and every page on the website. We take notes and thoroughly absorb as much content as possible. Our objective is to get to the heart of the project and gain as much of the organization’s perspective as possible.

If it’s a custom programming project, we try to get inside the project’s concept, challenge it, look for flaws in the logic, research relevant technologies, and work to make recommendations that keep the goals of the project in mind.

We spend time with the client by phone, over Skype, via email, and sometimes even in person. As our research uncovers problems or finds solutions, we run them by the client and gather their feedback.

The research process allows us to go deep, and in our experience it has always paid off, giving us a thorough grasp of the project and providing a foundation to make intelligent, expertise-driven recommendations.

#2 — Offer Recommendations

Each project evaluation is different. Depending on the nature of the project we may make recommendations regarding technology, content organization, marketing strategies, or even business processes. The types of recommendations we make have varied greatly from project to project, and are always driven by the context and goals of the project.

When it comes to areas of uncertainty for the client, we work hard to achieve a balance between an absolute recommendation and other options. If the answer is clear to us, we’ll say so and make a single, authoritative recommendation. However, when an answer is less clear, we give the client options to consider (along with our thoughts) on why or why not an option might be a match.

We share our recommendations with the client throughout the evaluation process, and when the final report is given, there are rarely any surprises.

#3 — Prepare the Scope

After we’ve worked through our recommendations, we put together a technical scope. This is typically the longest part of the document. In the case of a Web design project, we go through each page of the website, explaining details for the corresponding elements of that page. The level of detail will vary based on the importance of a particular page.

The scope document is detailed in such a way that the client could take it in-house, or even to another developer, and be able to implement our recommendations.

As the project commences, the scope document will often be referred to, and can function as a checklist for how the project is progressing.

#4 — Prepare the Timeline & Estimate

With the scope complete, calculating the cost and preparing an estimate becomes a relatively straightforward process. While how one calculates the price may vary, all the information is now available to see the project through from start to finish, identifying the challenges, and determining the amount of resources required to meet the project’s objectives.

Note: Prior to the start of the evaluation process, we nearly always give the potential client a “ball park” estimate. So far, that estimate typically ends up being about ten times the cost of the evaluation.

We take the estimating process very seriously, both in the ball park stage and especially here within the context of an evaluation. Once we set a price down we don’t leave room for “oops!” and “gotchas!”, and that means we are extra careful to calculate as accurately as possible, both for our sake and for the sake of the client.

Now, because of the nature of the evaluation, we are often able to research and explore options above and beyond what the client originally brought to our attention. In the case of a Web application, this might be an added feature or a further enhancement added onto a requested feature. Within the scope of the evaluation we carefully research these extras, and when appropriate, present them as optional “add-ons” within the timeline and estimate.

They are truly optional, and while always recommended by us, we leave the decision up to the client (there’s no use wasting research energy on an add-on you wouldn’t fully recommend). In cases where the budget allows for them, they are nearly always accepted. In cases where a tighter budget is involved, the add-ons are typically set aside for future consideration.

When Evaluations Are Appropriate

A project evaluation functions like the blueprints for a new office building. Imagine that I own a successful construction company, and I have a number of world-class office construction projects to my credit. A new client comes to me after seeing some of my work and tells me “I want a building just like that!”. Assuming, of course, that I own the rights to the building, I can say “Sure!” and tell them how much it will cost. Why? The blueprints have already been drawn.

Now, there will be variable factors, such as where they choose to have the building built, and any customizations they may request matter. But in most cases no new blueprints will be needed, and I can proceed with construction without charging them for the plans.

Suppose another client comes to me after seeing one of my buildings and asks me to build an entirely new design for them. A new design calls for new blueprints all of their own, and these must be developed before the project begins. Can you imagine a large-scale construction project without any blueprints?

Web development is the same way. In our experience, evaluations are appropriate when a client comes to us and asks us to take on a project outside of our existing set of “blueprints”. Examples where we’ve found a project evaluation necessary include:

  • A redesign of an existing website.
  • Developing a new Web application.
  • Bringing new technology into an existing project.

Without an evaluation you’re either left to go ahead and do the research on your own (with the weight of the rush, and the risk on your shoulders) or you’re stuck making as educated a guess as possible for the scope of the project. This dangerous guessing in a situation where an evaluation is appropriate can leave you with an estimate that is too high (which can mean losing the project) or even worse, an estimate that is too low.

When Evaluations Are Not Appropriate

When a project is familiar, and doesn’t require an evaluation (or fits within the scope of an existing type of evaluation), we give an informal, direct estimate along with a scope of the work. Small to mid-sized Web design projects typically fall into this category. While the content and design are new, the process isn’t. The key here is the experience and confidence in your abilities (and the abilities of your team) that the work will get done within budget to the expected delight of all parties involved.

Conclusion

Project evaluations up until now haven’t been given much attention. I would suggest it is a simple concept that has been overlooked and passed by amidst the rush of a booming Web development industry. I invite you to implement the process, experience the benefits, and stop the pain of proposal writing.

We often hear companies, including Web agencies, boast about how they provide exceptional client service. But how do they define exceptional?

Consider this scenario. You are hired to design and develop a new website for a retail client. The client loves the design, and the pages you develop use the latest in HTML5, CSS3 and responsive design, resulting in a website that works wonderfully across browsers and devices. The e-commerce features of the new website help the client significantly increase their online sales, and the entire project is delivered on time and on budget. Now, is this “exceptional” client service? I don’t think it is.

When the client hired you, they expected that you would design and develop a great website. They also expected it would be done according to the timeline and budget set during the planning stages of the project. As successful as this project may have been for both you and the client, in the end, you did exactly what you were hired to do. You did your job.

Just Doing Your Job Vs. Delivering Exceptional Service

Nothing is wrong with “just doing your job.” In many cases, that alone is a tall order. So, while doing what you were hired to do is nothing to be ashamed of, it is also not exceptional — nor will it set you apart. There will always be other agencies or designers that will be able to do the work as well as you can — and there will certainly be someone willing to do it cheaper! The service you provide is how you can truly differentiate yourself.

Exceptional client service is about going beyond what is realistically expected of you. It is about surprising, and often delighting, customers, turning them into enthusiastic referral sources and lifelong clients who stick with you not only because you do great work at a fair price, but because the value you bring to them goes far beyond just your products.

In this article, I’ll detail a few of the ways that I have tried to take my own client service to the next level and deliver a better experience, starting with the most important aspect: the relationships that you establish with the clients who hire you.

superhero
There is a difference between doing what you were hired to do and delivering a superheroic level of service. (Image: JD Hancock)

Creating Real Relationships

Here’s a quick exercise. Write down your five most important clients (how you define “important” is up to you). Then, write down as many things you know about those clients that have nothing to do with their business or the work you have done for them. What are their hobbies or passions? How many kids do they have? How old are those kids, and what are their names? Where do they like to vacation? Things like that.

So, how long is your list? If you’re like most people I speak with, probably not very long at all. We learn everything we can about a client’s business, but we often fail to discover anything substantial about our clients as people. If we do not engage with our clients in a real, personal way, then we are just another vendor — and vendors are easily replaceable with better cheaper options. However, clients are much less likely to consider replacing people with whom they have real relationships.

So, how do you start learning more about your clients? Simple: ask them questions about themselves and their lives, not just about their business.

Asking Real Questions

When I give this advice to others, it is often met with some apprehension. Asking someone about their business goals is easy. Asking them about their life outside of the office is harder. We often avoid getting personal for fear of offending the person or saying the wrong thing; but by being overly cautious, we miss the chance to create a real relationship.

Whenever I get nervous about getting too personal with a client, I remind myself of a story. A few years ago, I had the privilege to work on the website for the Tori Lynn Andreozzi Foundation. This non-profit foundation was named after a young girl who, walking home from school one afternoon, was struck by a drunk driver. Tori survived but was forever changed. Today, she is in a minimally conscious state, unable to walk, speak or eat.

In one of my first meetings with this client, I sat down with the head of the foundation, Tori’s mother, Cathy. I began the conversation simply by asking her, “How is Tori doing today?”

Cathy smiled and answered that Tori was doing well. We had our meeting and discussed the website and the project. As we were wrapping up, Cathy thanked me for asking her about Tori. She explained that so many people avoid asking about her daughter, fearing the news would be bad or that Cathy would be upset by the question. The truth is that, even though Tori has bad days, Cathy always enjoys talking about her daughter and was very happy to be asked about her. By asking Cathy how her daughter was doing, I showed her that I cared about more than just the project.

tori-lynn-screenshot
The website for the Tori Lynn Andreozzi Foundation

Today, Cathy is one of my favorite people to speak with, and we begin every conversation by asking how each other’s children are doing. We have much more than a great client-vendor relationship, all because I asked a real question, honestly cared about the answer, and created a real, human connection in the process. Had I been too afraid to ask that question, I might never have been able to build the relationship that I have now.

Don’t be afraid to ask your clients real questions. If they don’t want to answer you, they won’t. But for those who do (and you will find that most, if not all, of your clients will be happy to have a real conversation that has nothing to do with business), you will be well on your way to building real relationships.

Participate In More Than Just Projects

Another way to build a relationship with a client that goes beyond the project is to participate in their events. If the client runs a non-profit organization, they might have fundraisers or similar events that offer you an opportunity to support their cause and nurture the relationship. Go to these events and participate. As a bonus, you will also be helping a worthwhile cause.

Not all of your clients will have fundraising events, but they might invite you to holiday parties and other gatherings. Take advantage of these opportunities to interact with your clients outside of a normal business setting. It will go a long way to reinforcing those real relationships that you are trying to create and show that you are more than just another vendor.

Similarly, consider inviting clients to some of your events to show that you view them as more than just a source of business. When they arrive, greet them warmly and enjoy their company, leaving business talk for another day.

Help Them With Services That You Do Not Provide

Clients may hire you to design and develop a Web presence for them, but in the course of the project you will often discover that they need other services that you do not provide. By listening to their needs, you might learn that they have issues with their payroll company or their accountants or some other aspect of their business.

Look to your own business and the vendors you use. There may be a service or company that you have had success with that you could recommend. Also look to your other clients to see whether they offer services that fit. If appropriate, set up a lunch meeting between you, the client with the need and the client that might be able to fill that need. Not only will you be taking two clients out for lunch, you will hopefully be helping them both by making a valuable connection between the two companies.

When a client can say, “I hired this company to design our website and they ended up helping us revamp our entire payroll system!” you position yourself as much more than just their “Web team” — you show that you are a valued business resource and a trusted advisor.

Pick Up The Phone

Good communication is key to any relationship. Still, judging from the number of clients I speak with who are unhappy with their current Web team — not because they do a poor job, but because they are unresponsive — quality communication is not always a given.

Regularly updating your clients by email is important, but also pick up the phone every now and then, so that you become more than just that distant person behind those electronic updates. By hearing your voice, clients will feel more connected to you and the project. It also shows them that you value them enough to take the time to make a personal call, and it gives you a chance to talk about something other than business.

Conversation
Regular phone calls allow you to have real conversations with clients, communicating at a personal level that email and other electronic updates do not allow for. (Image: opensourceway)

Face The Bad Times Head On

Have you ever had to share bad news with a client, but rather than pick up the phone to discuss the issue, you waited and sent an email at 5:15 pm on a Friday? By doing this, you may have bought yourself a few more days before having to face the client’s worried questions, but you also damage the relationship by hiding behind an email. It also means that the client will read the bad news first thing on Monday morning; definitely not a good start to their week, and definitely not the way to treat a valued relationship.

Here’s a secret: clients do not expect you to be perfect. They do, however, expect you to be honest. When something goes wrong, let them know quickly so that they are not blindsided by the issue later on. And never deliver bad news by email. Picking up the phone to discuss the news lets you reassure the client and answer any questions they may have. An after-hours email certainly won’t do that for them.

If the matter is handled correctly, the client will not remember that something went wrong. They will remember that you were honest and kept them apprised of the state of the project, even when it did not go according to plan.

Be Thankful And Show Appreciation

When was the last time you thanked a client for working with you? How did you do it? Did you send a basket of cookies or chocolate with a generic “thank you” message, or did you do something more personal?

Too often, we fail to even thank our clients for their business. We are so keen to finish a project and move on to the next one that we forget to properly show our appreciation.

While a basket of sweets and a generic message is better than nothing, consider sending a personal, handwritten thank-you note.

Handwritten letters have become all but extinct these days. With the rise of electronic communication such as email, social networks and text messaging, so few people take the time and effort to actually write a letter. The gesture of a personal letter will delight and surprise your client, not only because you have thanked them, but because the way you did so was personal, memorable and the perfect cap to a successful project.

Thank you!
A thankful, personal handwritten card is a great way to cap off a successful project. (Image: irrezolut)

Web design is a multidisciplinary craft. So why do so many of us try and do everything ourselves?

Maybe it’s because we can. Our nature as web designers tells us to build things. We have the capability to handle just about every role in a web design project. If we don’t already have the expertise in a certain skill, then at least we have the self-motivation to teach ourselves and learn on the job. That’s how must of us got to where we are. But is doing it all the right approach?

When you look at the bigger picture, maybe it’s not. For me, my over-arching goals are to build an impressive portfolio of work, land bigger and better clients, and grow my web design business. It’s simply not feasible to achieve these goals by doing everything myself. The only way is to build a web design all-star team to help me do it.

So here are some tips for building a well-rounded team for producing amazing web design work. These are things I’ve come to learn over the years as I transitioned from being a freelancer to owner of a distributed web design agency.

 

The “one thing” concept

What separates the high-end web design shop from the do-it-all freelancer? It’s the well-rounded quality of every piece in their portfolio. From wireframes to PSDs to code, copywriting, and strategy: Every role is executed by a specialist in that particular craft.

The key is to assign the right person to the right role. So how do you get this right?

I call it the “one thing” concept. The idea is to figure out what your subcontractor’s core competency is, that one skill that they’re a rockstar at. This can be harder than it seems. Most web designers, particularly those who primarily work alone, tend to claim they’re a “jack of all trades”. It’s your job to see past this and reveal that one thing that they’re most experienced with.

One of the first questions I ask potential subcontractors is “Do you consider yourself primarily a designer or a developer?”. Many of us can do both, but 99% of the time, we’re better at one than the other. I want to find out which one it is, and hire them to handle only that part of the project.

Creating a working Website with a team can be a challenge

Determine your own role first

Now hold on a minute. Before you can start outsourcing, you must first determine which role you will personally fill yourself. Start by figuring out your one thing that you’re best at. Maybe it’s front-end HTML/CSS coding.

Perhaps you’re a talented visual designer, capable of producing beautiful PSDs. Or maybe your strength is in the pre-design planning stage, producing wireframes and information architecture diagrams that provide a good road map for production. It should be difficult to choose just one thing.

Keep in mind that since this will become a team effort, your role will likely include project management duties: Finding and hiring teammates, communicating project specs, client communication, etc. Be sure to budget your time accordingly!

 

Build your network early and often

Many freelancers and web shops are going with the distributed agency model these days. That is, your teammates work remotely from their own offices across the street or across the globe. If this is your direction, then it’s never too early to start building your network of remote workers.

Here are some ways to do that:

  • Build relationships with designers and developers on Twitter.
  • Seek out and follow creators of amazing work on Dribbble.
  • Follow and comment with those you find interesting on Forrst.
  • Post targeted ads on job boards and filter the responses to separate the quality from the noise.
  • Meet designers and developers at local meetups and conferences.
  • See something great on the web and get in touch with the creator.

The last one is my favorite. There are so many amazing things being created on the web every day. In the space in which my company operates, which is WordPress web design, I often come across a really cool plugin, an interesting theme or a well-written article. I’ll immediately reach out to the author to see if they’d be up for brief Skype chat to talk informally about their work and strike up a new relationship.

Later on, when a new project comes in and you’re looking for talent, it’s better to start knocking on the doors of those you already know than to scramble and start looking for someone new at the last minute. Build and nurture your network today and leverage it for your projects tomorrow.

 

Identifying talent & fit

How do you identify who is worth considering for a spot in your network?

Before you reach out to people, you have to know what you’re looking for. Here are things I value before I speak to someone:

  • A great portfolio, but particularly an informative portfolio. The work should look great, but I want to know exactly what the person’s role was in the project. Case studies are great for this.
  • A well written blog. This shows they’re passionate about their craft, enough to take the extra (often unpaid) time to write about it. This is also a good indication of their written communication skills.
  • Their industry presence. High profile work, published articles, speaking engagements, books. These are all good signs of a talented and dedicated professional. But be careful, these credentials can sometimes be deceptive.

Next, we need to determine if we’re a good fit. You can’t get a full read on these things until you actually work together, but there are some things you can look for in your first few conversations:

  • Professionalism and reliability. Can they reliably schedule and show up for your call/meeting? You’d be surprised how many people fail at this simple act of professionalism.
  • Collaborative fit. Take note of the types of questions they ask (shows they really want to understand and collaborate). See if their “one thing” compliments yours and the others in your network/team.
  • Logistics. Ask about their working hours and availability for meetings and progress updates. I’m generally open to working with anybody, but I prefer a timezone that is within 3 hours from me (North America). Just makes collaboration easier.

Great people do great things… together

When it’s time to take your web design business to the next level, it’s time to start teaming up with great people.

That’s the key to thinking big and doing amazing things in this collaborative industry we call web design.

Hopefully these ideas will help you form the basis for your network, which you can look to when it comes time to assemble a web design all-star team.

Creativity vs. strategy: what do people really want?

It is super hard to find a job straight out of college — the places where you want to work aren’t hiring and many of the other jobs don’t seem right. After months of searching and waiting by the phone, you probably decide to take the plunge. I had done some freelancing throughout college times and later and one day decided I would trek back home and freelance full time.

I had a strategy and I had it all planned out. I really did. It didn’t matter, though.

The work I was doing in an attempt to get noticed (and paid) was getting absolutely no attention. I mean, I spent lot of time to create own website and got little to no views for long. I was trying my hardest, and I think on my best day I got maybe 150 views, and maybe 20 folks on my e-mail list.

My strategy just was not working.

The bright side, however, was that the work I was doing for fun got a lot more recognition than I thought it would and it eventually turned into some decent money. Who would’ve thought? I have noticed may times, that web site in that matter is not the issue, if you are good, people spread the word for you.

 

Why be strategic?

Creativity vs. strategy: what do people really want?

Having something organized and planned out works for some people. It’s what the experts tell us to do. I hate surprises so I liked the idea of having something to look forward to rather than feeling like I was taking a walk in the dark. Besides, it’s a lot easier to tell people you’re working on your web design business than it is to tell them you have no clue what you’re doing, but you hope it works.

Creating a strategy helps you to be prepared. You don’t want to just let yourself loose and hope something happens or catches on. Even when I was doing my primarily creative/fun stuff, I still planned it out. Think about it like this—how often can you open Photoshop (or the program of your choice) with no plan or idea of what to do and then end up creating something spectacular? I know I can’t. Web designers, print designers, architects, painters, and other creatives all have some sort of plan or some sort of sketch before they get into the development stage.

Strategy is what some people believe pays the bills. Now, I’ll say that’s up to personal interpretation, but if you have a plan and it makes sense, well then you’re far ahead of someone who has no clue what they are doing. Some folks come along and decide they want to create a blog packed with design inspiration and other creative articles or they want to create branded packages for small businesses. These are great ideas that have to have a strategy behind them…or do they?

 

Why be creative?

Creativity vs. strategy: what do people really want?

Sometimes I absolutely hate surprises. I had no idea how to create a good strategy. Mine were entirely too strict and didn’t give me a chance to totally be creative. If I look back at what I was doing, I was strategizing things down to the very bone — my goal wasn’t to get more Twitter followers, but it was to have 100 new followers a week.

My goal wasn’t to just create a website, but it was to create three types of freebies a week and get a certain amount of folks to download them. Thinking like that didn’t leave room for error, which I liked, but it also didn’t leave room for opportunity. If the results weren’t as I expected, then it was wrong.

Now if we recall, I said the things I did to have a bit of fun and be creative were getting noticed much more. I have two theories for that:

  1. While I still had a strategy, I was being creative. I strategized by saying, “Hey, I see people asking how to make this kind of effect in Photoshop, let me make a screencast video and put it online.” That was it. Nothing else, really. I didn’t even write a transcript (which I would do in the future). The idea here is that I gave my “product” time to sit and breathe and be itself. Perhaps with my other idea, I was too involved. Over-strategizing can be the death of any strategy. You’ve got to give your idea time to stretch out and grow and figure out what else it NEEDS to be. You can’t create something and immediately expect it to be something more. Especially when it was as generic as my over-strategized idea.There is an issue with trying to be too involved.
  2. People like creativity. Doing something new, or seemingly new, is smiled upon. I think there are a ton of psychological things we can explore here, but basically the idea is that folks are attracted to things that are new, that are different, that are unique. Think about the designers that stand out to you the most or the musicians and companies that are up and coming. Don’t they all have something new or unique to offer? Most times they do, and most times they start by serving a small niche, who were immediately attracted to it. Then as they got older, and got some more feedback, they figured out how to make it a monster—think of Macintosh back when they first started. Some of the greatest sites, products, musicians, etc. came about pretty much by accident (with little to no strategic backing).

The winner is…

I’m not saying that it’s bad to have a strategy but I am saying it is terrible to over-think some things. It’s also hard to put a strategy behind a purely creative idea. Strategies are extremely important to products or services that come about strictly to solve a problem.

Most app and program developers have found a problem and developed some app to try and help out. For example, with these high gas prices I was wondering (and hoping) there was an app out there that could tell me how close the cheapest gas was. I had a problem and needed a solution. Now that deserves a strategy for sure—how to get it in front of people who would use it and how much they might be willing to pay for something like that.

The thing to be careful of is trying to create a problem for our creativity to solve. For one, you’re probably boxing your creativity up. My bright idea straight out of college was to create affordable everything design for small businesses—I had ads up, I had made connections, but I was putting my creativity in one lane—small businesses. I was only following small businesses on Twitter and my portfolio only had stuff up for small businesses.

It sounded right, but I kind of made that strategic decision without letting my creativity find its own way. Secondly, being creative is a very sensitive thing—you can’t just push it on everyone and expect them to like it. Sometimes it’s best to just put your best foot forward and see what you get and go from there.

I know this is going against everything everyone else has taught you. Hell, it’s going against everything I was taught, but sometimes we’ve got to take risks and find out what ends up working for us. Take the feedback, cultivate it, and make something great.

In a highly competitive business environment, good communication is the engine of success.

With social media so ubiquitous, much can be achieved… and overlooked. When sharing interests and experiences online is so easy, people put less effort into maintaining their relationships, thus shortening the average life of an interpersonal connection.

A close look at the problem reveals that minimal effort can turn contacts into veritable relationships. Basic practices such as attentiveness, courtesy and friendliness can make each of your connections more meaningful and valuable. The advantages may be apparent or hidden, and they lead to client loyalty, referrals and a healthy public image.

Here you’ll learn how to enhance your communication strategy and make the most of every connection by keeping a few simple principles in mind.

Can’t Do the Job? Offer Advice

Saying no to a job offer is okay, but that doesn’t mean you have to reject the client. If offering your services is not possible, then offer some advice. Expert tips are valuable. At the very least, the company will appreciate your willingness to help, and that’s good for your reputation.

Let’s say that your quote is higher than a prospective client can afford, and you have to turn down the project. If it’s a matter of doing a couple of hours of extra work, think about taking it on anyway; most clients will appreciate the sacrifice. If you definitely can’t do it, perhaps you could include suggestions (based on what you know about the project) in your email declining the work.

A wide range of website-building services could be useful for low-budget projects, but less web-savvy clients might not know about them. Here are a few you could bring to their attention:

  • Site2You is an all-in-one solution for setting up and maintaining a business website. It includes a user-friendly website builder, e-commerce functionality (if enabled), hosting and domain-name services and professional support, all for quite an affordable price (plus a free trial).
  • is a user-friendly Flash website builder. Both free and paid accounts are available. It’s an attractive option for non-professionals.
  • WordPress is a decent website-building tool as well. You could even refer the client to a WordPress theme developer who you know, thus doing them two favors in a turn. Good karma!

Don’t leave the client helpless.

Always ask permission before dispensing advice; people will likely appreciate your input, but less so if it’s unsolicited.

Instead of wasting time reviewing projects that you’re not going to do and dwelling on lost job opportunities, communicate with these contacts. They will be grateful and will keep your name on their shortlist.

 

Recommend People To Work…

…with you: You probably know what’s happening in the design world and, because of social networking, can see who is doing interesting work.

Make contact and build relationships with other design experts and specialists so that when a project that requires it, you’ll be able to suggest competent copywriters, developers or illustrators. You’ll increase the chances of the project’s success and, thus, contribute to your own professional success.

…instead of you: Hard work won’t get you every great gig. If you receive an exciting job offer but your schedule is already full, don’t get upset; you will make another designer happy by sending the client their way-and helping others feels good. Yeah, you’ll lose a great project and a potentially regular client, but that would have happened anyway, right?

Get the most out of the situation by serving as a link. (And remember: refer clients only to professionals who you trust.) Whatever the project’s outcome, your gesture won’t be forgotten; the client will likely look for an opportunity to return the favor.

Never underestimate the value of word of mouth.

By the way, you might also like reading Web Designer’s Guide to Copywriting Profits.

Create a list of competent professionals who you could recommend to clients. You’ll show that you have a comprehensive grasp of the field, which they’ll appreciate.

 

Set Up a Friendly Email Policy

Your handling of email can make or break your communication strategy. We don’t have to look far for examples: just count the number of important connections you’ve established and maintained via email.

If email is your main communication medium, then put a suitable amount of effort into managing it. At the same time, put reasonable limits on the amount of time you spend on it.

Here are some simple techniques to manage email effectively. They might seem obvious-and they are easy to do-but they still get overlooked.

Auto-Reply

Using an answering machine is hardly a personalized approach, but it’s better than letting clients and others guess whether their emails have reached you.

Before going off the grid, write an automated reply to inform correspondents that you will contact them upon your return.

Automated replies are also useful for those who are lucky enough to attract a high volume of inquiries (not counting spam, of course). But do not promise to get back to someone ASAP if you’re not sure you can. Sure, saying so sounds better than something like, “Sorry, I can’t answer every message because of my high volume of email,” but it will put people off if you don’t follow through on your word.

Fast Response

Answer your emails promptly and clients will love you for it. Seriously, do it. Composing a message takes only a minute. You might not be able to solve their problems in that email, but a quick response is still appreciated.

Showing your concern will distinguish you from the client’s other contractors and partners.

Don’t keep people waiting.

Make a Good Impression

When approaching someone for the first time by email, make sure your message gives the right impression. Always check your spelling, and use a friendly but dignified tone of voice. Include a tasteful signature, but make sure the message, not the signature, is the focus.

When you want to inform your client base about important news or remind them that you exist, you’ll probably use an HTML newsletter. Before designing one, investigate which email service most of your recipients use so that you avoid problems with rendering and display.

Here are a few tools and resources to enhance your email communications:

 

Give Thank-You Gifts and Offer Freebies

A thank-you email might not feel like enough for a long-term client. What about cool office knickknacks or t-shirts? Never wait for the client to show their appreciation first; if you have enjoyed working with them, go ahead and show it! People will be twice as ready to help you out in future if they feel appreciated.

Don’t use gifts to suck up, though. If you have failed in a project, a fancy present won’t make the client ask you back again. Sincere gifts and gestures can only strengthen healthy relationships.

Another great way to tighten the ties in your network is to give stuff away. You could design and share freebies for your blog readers or social network pals. And don’t be afraid to re-gift; perhaps you have unused discount coupons, gift cards or other promotional items that you won in giveaways.

Luck is a funny thing; it often happens that we only get for free the things we don’t really need. But what you find useless, someone else might benefit from. Why not put it to use? Don’t let a coupon expire or a cool but ill-fitting t-shirt lie in your closet unpacked and collecting dust. Give it away. The simple act will get you kudos and a lot of attention. Swapping less for more: sounds like a great deal to me!

Announcing a give-away on Twitter or Facebook makes re-gifting a zero-risk enterprise.

Don’t Forget About Live Communication

Most of your work-especially if you’re a freelancer-takes place online. You might not notice that you’re gradually shifting into virtual-only mode, because your friends and clients (and everyone else for that matter) are just an email, tweet or Facebook message away.

Don’t be fooled by the unlimited pseudo-connectivity. Digital communication does not replace actual socializing. A photo gallery of your college reunion on Facebook won’t feel at all like the real thing, and watching recorded talks from a design event differs vastly from the experience you would have had if you were there in person.

More importantly, by limiting your communication to emails, IM, online social networking and Warcraft raids, you might lose some social skills and erode your ability to consult, negotiate and talk with actual people face to face. That still matters.

You might also enjoy reading “A Life Guide for the Antisocial Freelancer.”

What might happen if typing becomes your main way of communicating with others. (Image: The Oatmeal)

A ton of books and resources explore the principles of effective communication. The techniques won’t always come naturally, despite being “social” in nature.

Basic qualities like attentiveness, courtesy and willingness to listen can do wonders. Incorporate them into your communication habits and you’ll gain empathy, appreciation and referrals from clients, peers and friends.

Many e-commerce sites these days tend to be loaded down with too much information on their landing pages. The reasoning for cluttered e-commerce sites is simple: the more information you can cram on the page, the more the user will buy. Unfortunately, web buyers are a finicky bunch.

Jacob Nielsen reports that web users are becoming much more impatient while shopping and browsing online. Instead of spending their time going to a site’s homepage and finding the content by categories or other product recommendations, most shopping is done by quick Google searches. If the user can’t find what she’s looking for right away, she’s gone.

It’s crucial to have simple web designs to allow the user to quickly find the information they need, especially if you are selling a product. If the page is cluttered with useless text, widgets or unrelated products, the site becomes meaningless.

However, it’s become a common practice to do just the opposite. e-commerce sites have taken this “scatter shot” approach of trying to slap the potential buyer with as many options as possible. Instead of making the landing page solely about one product, sites usually clutter the page with unnecessary information, ads and related products.

Less Products Mean More Focus

Many web companies forget the cardinal rule of e-commerce: Web shoppers want as little hassle as possible. Instead of hopping in the car and driving to the store to buy a DVD, it’s much easier to go online and snag it from Amazon in a few clicks. The customer is even willing to wait longer and spend more money if the shopping experience is simple and fast.

Applecom in How Simple Web Design Helps Your Business

Apple has mastered the art of minimal homepage design. If you go to their homepage, they’ll only show you three things:

  • A simple header navigation
  • One product in the body of the page
  • A few informational links about the featured product with images below the fold

Aside from the standard footer navigation, the homepage consists only of three parts. Here’s what you see if you click on a product link (like the iPhone).

Iphone-homepage in How Simple Web Design Helps Your Business

Even on the product page, you immediately see what the page is about: the iPhone. The product itself dominates the bulk of the page, and the surrounding information are apps and features of the new iPhone. But more importantly, notice what’s not on the iPhone page:

  • Unrelated products
  • Unrelated sidebar ads
  • Lots of copy
  • Clutter

Apple has effectively shown just enough information in a very pleasing manner. There’s nothing wrong with showing lots of information, as long as it doesn’t feel like a lot of information. You’ll also notice that all of the information, links and pictures are all centered around the iPhone and what it offers. There are no distracting ads or unneeded information about other products.

There are a couple of tried-and-true methods that any designer or web developer can take to ensure that the site layout doesn’t drive customers away with clutter.

  1. Only what you need.
    The biggest aspect of simple web design is only showing what’s needed to make the sale, and nothing more. This doesn’t mean that you can’t give the user lots of information. Just make sure they want to see more information. Apple uses “Learn more” links throughout the page to accomplish this.
  2. Reduce clicks. The less clicks it takes for a customer to buy a product, the higher returns. Don’t make them jump through hoops to buy your product.
  3. The “Grandma” rule. If your grandma (or any elderly person) can figure out how to buy a product for your site, odds are it’s put together pretty well. Unneeded information will turn Grandma away quickly.
  4. Reduce the number of columns. Each time you add a column to a page, the content is pushed into a smaller and smaller space. This puts less emphasis on the main product, and more on extra stuff the buyer isn’t really looking for.
  5. Give less options. There is an added stress put on web shoppers to make decisions. Ultimately, the buyer wants to think as little as possible when making the purchase. Displaying products in a way that eliminates extra thinking and decisions will streamline the buying process and give the customer more peace of mind.
  6. Keep it clean. A clean design keeps visitors happy. By taking the time to ensure that the layout of the site is aesthetically pleasing keeps the customer returning to the site.

Intuitive web design means thinking like a potential customer. Would you shop at your site?

 

What now?

 

Every website is going to require a different type of layout, design and copy to sell products. But designers can strive to do more with less by:

  • weighing every word
  • removing unneeded elements
  • using tasteful colors and whitespace
  • and limiting the amount of overall information the shopper sees at one time

Remember, online shoppers are a fickle bunch. They don’t “window shop”. They use search engines to limit their searches to a very narrow field. If they don’t like what they see, they leave. Site owners only have a very small window of time to capture the attention of the prospective shopper. A tasteful, clutter-free design that places the focus on the product (and nowhere else) will allow the shopper to find what she wants faster.

When design teams focus on the Usage Lifecycle, they take an approach similar to what a great salesperson would do. When a salesperson approaches a customer, they first find out where the person is in the sales process and what their ultimate goal is. When you think about your application as something someone is using or purchasing, it’s very similar to a sales cycle.

At each stage of the Usage Lifecycle, users have very different needs and questions. Can you talk about these differences?

When most people first come to your application, they are unaware of what you have to offer them. It isn’t so much a stage, as a starting point. Most people are in this stage: completely unaware of your product.

Each of the stages are separated by hurdles. The hurdle between the “Unaware” stage and the “Interested” stage is “Awareness”. When people are in the Interested stage, they have a unique set of questions. For example, they ask: How does this product relate to what I’m currently using? Will this product or service fit my needs? How does it compare with other products and services on the market?

Most startups need to focus on solving the challenges in the Interested Stage. The problems they need to iron out are Awareness problems. Startups must help users learn about the application, gain confidence, and get users started most effectively. In this stage, I recommend that teams focus on messaging and emphasize the value proposition of the application.

Typically, once users start interacting with the application, most of these initial concerns disappear and now they are Users of the application. As Regular Users, their concerns are now completely different. They are using the product to accomplish a task and fulfill their end goals. When they use the application, they have a different mindset. At this stage, teams need to focus on helping users accomplish their goals and move beyond just making people aware of the product’s features and benefits.

For me, this level of distinction is incredibly valuable. I’m more and more convinced this is where to focus: where users are in their lifecycle and environment. If you can understand this about people, you can help users more effectively.

(Here’s a full summary I’ve written on the Usage Lifecycle.)

What are the best practices you recommend design teams use to first start getting users engaged in a product?

There are a lot of small and effective strategies design teams can use. If your team knows ahead of time when you’ll be launching, I recommend having a beta phase or set up an invitation list to tell people about what you’re doing.

For example, at Performable, we asked prospects to give us their email address to contact them when we launched. When we offered this option, thousands of people signed up. This is a simple thing, but a lot of startups don’t do it.

Another great tactic is message testing. With message testing, teams design two or more home pages (or landing pages) for their application and see what message resonates better with visitors. Once traffic starts arriving at the page, you can easily quickly see which message variations convert the best. Conversion can be different things depending on your business goals, such as users giving you email, signing up for a beta, or signing up for the product.

This technique helps companies find out whether their value proposition is being communicated effectively with visitors. In almost all cases it can be strengthened. In some cases the initial message is the wrong one, such as focusing on a benefit that just doesn’t resonate with the target audience. There is a lot of action in the testing space right now and I’m excited to be a part of it.

A common problem with many applications is that people sign up and then never consistently use it. How can designers combat this problem?

Yes, I see this happen all the time. I call this phenomenon the “Getting Started” problem. This is when people sign up or register for your application and then don’t know what to do next.

To solve this problem, I often recommend that clients pre-populate the initial application page with content. For example, if you have an application that allows people to make a widget, it’s very powerful tactic to pre-populate with a widget already made. People are far more engaged when they get to see how the application works instead of starting with a blank canvas.

With the Usage Lifecycle, most of the solutions are relatively small solutions, but taken together, it really adds to a positive experience if you’ve gotten each step right. With your application, you can’t just have one cool thing happen with your product. It’s the sum total of interactions that make up a successful user experience.

How can design teams create passionate fans of their product?

This is a question I often get from marketing teams. They will often try and add social features to create passionate users. They’ll say, “Let’s offer more sharing buttons or more opportunities to share.” However, while putting a social feature in the interface may result in users completing the interaction more frequently, that’s not the right way to create passionate users.

The best approach is to make users good at something. For example, imagine you are tasked with designing an email marketing software, such as Mail Chimp, Emma, Constant Contact, or Campaign Monitor. The best way to get users passionate about these types of applications is to make them better at their jobs as email marketers.

This really has to do with focusing on the experience users have when they interact with your product and working on getting users good at what the application does. The best design teams focus on a single activity set and ensure that the product successfully supports these activities and makes them simple to do. Once people are good at using the product, they’ll talk about it and share with others. This will also be more authentic. Campaign Monitor is a great example of a relatively small team doing great things by teaching their users how to be better email marketers.

So, the best teams move beyond just thinking about what social features to add to their product. In your writings, you’ve said it’s really more about the personal value of what people are doing. How did you first come to that realization?

Many years ago, I had a conversation with a designer who was building an application for runners. At the time, tagging and folksonomies were the trend and I was really excited about the topic.

The running application enabled users to enter their running time. I’m not much of a runner myself but I was really excited by the social opportunities around sharing running data and the competition it would engender. Knowing that many people thrive on competing with others, I thought there was huge potential there.

But the designer of the app was adamant that I was missing the forest for the trees. He wasn’t all that excited about the social possibilities. While the application would let users share their running time online with others, social influence isn’t the real motivation for serious runners. The people in that market valued their own improvement much more than seeing what others were up to. While sharing was a nice side effect, the most important thing to runners was to see if they were faster than the day before.

This was an eye opener for me, as I suddenly saw this same mistake applied over and over in social software projects. For users, personal value comes first, it precedes social value almost all the time. I call this the Del.icio.us Lesson, named after the popular bookmarking site. With Del.icio.us, people were tagging articles and sharing with groups and there was a tremendous focus on the social aspect of it all. But most people didn’t use Delicious to share stuff with others. They primarily used it for bookmarking stuff for themselves so they could read later.

There are two parts to every project…the Process and the Point.

The Process, which gets most of the attention, is the series of steps we go through to do the work. We obsess over the process…should we do wireframes, mockups, prototypes, or code right in HTML? What deliverables do we need to get buy-in? When do we do testing? What kind of testing do we do? Should we do user testing early? Late? When is the best time to get feedback?

We need the process to know what to do next. We need a framework to work with because it helps us get more efficient at what we do. When you’re user testing, for example, you’ll go much farther and get there faster if you have a repeatable process in place. You’ll want a quick way to get users for testing, a quick way to figure out what to test, what tasks to test, and what to do with the results.

While we should constantly tweak our own process, we also discuss it endlessly with others. Are you sure you’re doing user experience design correctly? Are you designing content first? Are you designing in the browser? Are you using lorem ipsum, for the love of Gods? Are you doing A/B testing? Using personas? I’m sure yours aren’t as robust as mine, natch.

And then there is the Point. The problem you’re trying to solve. The thing that isn’t part of a process but is the most important thing you need to focus on as a designer. The thing that, if you happen to solve it, makes the process almost irrelevant. Solve the problem and you’re successful no matter what process you’ve been using.

The point is often what’s different in your project…it’s the thing that you probably don’t have a process for yet (if you did it wouldn’t be a problem!). And you probably can’t talk about the point anyway because you don’t want other people to solve it before you (e.g. your competitors). So we instead talk about the process…

But we should remember not to confuse the two. The process is valuable…it’s a framework for deciding what to do next…and we need that…but it’s merely a means to an end. And whatever you do, don’t let process details distract you from solving your problem in any way possible.

The Process is important…but it’s not the Point.