Archive for October, 2007

What will derail your website strategy?

I just read Scott Glatstein’s article in the American Chronicle about Business Strategy Execution: 4 Reasons Why Your Company’s Strategy Isn’t Working. (A nod to Erica Olsen who posted about this on her blog, Strategically Speaking, and got me thinking.)

Scott Glatsteins’ four points of a failing strategy were:

  1. The strategy fails to recognize the limitations of the existing organization.
  2. Employees don’t know how the strategy applies to their daily work.
  3. The organization’s business systems or processes can’t support the strategy.
  4. Performance metrics and rewards are not aligned with the strategy.

The same four things that can cause a business strategy to fail can cause your website’s performance to derail or be greatly diminished. I always tell clients that small changes to their website can demand large changes to their business. I think of it as the mind|body disconnect of the web. The client often thinks that the mind (the business) is disconnected from the body (in this case the website.) Mr. Glatsteins’ four points outline where this disconnect can be. Let’s look at an example:

ABC widget wants an email contact form for their website as an alternate method for customers to contact them. The form will store the customer’s information and message in a database and send a notification email to info@abcwidget.com. They hire a web development firm and get the form built. Right before launch (or worse yet – after launch) someone within the company asks a simple question: “Who is info@abcwidget.com?”

There is stunned slience as no one has considered before where the email notification goes. This question then gives birth to more questions (hopefully):

  • What is the schedule for checking the email address? (business process)
  • Does the person who checks the email need to reply? Is there a generic script? (business process)
  • Where do requests get routed to? (business process)
  • How are requests tracked? (metrics)
  • What is the expected turnaround time for a customer request? (metrics)

All this for a simple form! Every interactive piece of a website (where you are requesting a customer to communicate with you) requires a business process and responsiblity chart. It seems overkill, but when Janice in accounts recievable leaves the company and stops checking the generic email account – will anyone know what to do? Will they even realize what Janice had been doing for years?
If these questions haven’t been addressed beforehand, a customer may email a request and either never get an answer, or fail to get a timely answer, or possibly not get the answer the company’s strategy really calls for — as someone in the IT department ends up getting the email and doing the best they can to route it.

This example illustrates how a customer relationship can suffer if the details behind a simple contact form aren’t planned for and outlined. I would rephrase Mr. Glatsteins’ four points for the web:

  1. The website processes fail to recognize the limitations of the existing organization. Often website applications require a human component that you don’t plan on. You have a great new publishing platform (a blog) but who writes for the blog?
  2. Employees don’t know how the website can apply to their daily work. Websites can make the lives of employees easier with sales automation, information for customers, etc. but if there isn’t an internal campaign to educate your employees about your new website, then the right hand will truly not know what the left hand is doing.
  3. The organization’s business systems or processes can’t support the strategy. Can your website work with your customer relationship management system? Can your sales team go electronic?
  4. Website metrics are not aligned with your strategy. If you have a blog that is separate from your website, is it being tracked? Are you still pouring over raw server logs for information? How do you even measure website performance, and who is responsible for that?

These may seem simple questions for you to answer and simple problems for you to solve, and they are — if you’ve taken the time to do your homework. When you think about your website, think about it as an extension of your business and your business strategy.  Like with any business effort, good planning and a little bit of forethought can make (or break) the enterprise.

A tale of two restaurants

I went and got take out this weekend at a brand new restaurant. We have a lot of new restaurants opening up near where I live. I love the expanding selection, and am eager to support local businesses, too. I also have two small children, so take out is often the best option for my family. My decision about which new restaurant to patronize first was based on one thing: a website.

There were two restaurants to choose between. Restaurant A had a website. Retaurant B didn’t have a website at all. Both had opened at roughly the same time. The type of cuisine Restaurant B offers sounded really good to me. But, since I needed to order ahead and pick up the food (I was going to be running multiple errands with a 4 year old in tow!) I had to go with Restaurant A, who had their information available to me.

Restaurant A’s website was no great shakes. It was clean and professional. Built by a national company that grinds out templated websites. But regardless of the site design, architecture or individuality, it was highly effective. Even I have never actually chosen a restaurant based on the quality of their website – but I have made the call based on the information given by their website.

Restaurant B will be losing out on my family’s business until I get their information. If I ever have time to swing in and pick up a menu, I’ll call them – but chances are that won’t be for a while. Restaurant A will continue getting my business. How many more people in my situation (busy, technologically savvy, caring for kids too young to sit for table service) are living in this market? How much business is Restaurant B missing out on?

If you have a selection of services or goods people can order over the phone – get yourself a website. It doesn’t have to be slick or pretty – just easy to use and up to date. Then you can have my business — and that of many more customers with little time and a decent internet connection.

Is your web site accessible?

Last Tuesday October 2nd, a federal judge ordered Target to stand trial on charges that its website is not sufficiently accessible to visually-impaired shoppers. For more details on the ruling read this article in e-week.

What does this mean?

It means that marketeers and online retailers need to pay as much attention to the form and structure of thier code as they do to the look of their website.

I am not a fan of ugly websites. I understand designers who want to push the limits of website design – but websites can be unique, beautiful, functional — and ADA compliant.

The web was created to help people share information. At its most basic, the web is a series of interconnected documents. The basis of all good information is logical organization (to arrange the data), good roadmaps (to efficiently find the data), clear labels (quickly understand the data) and clear text or writing (data easily divided into parts for digestion). ADA compliancy is no different.

I am not an alarmist. Do I think that the precedent of Target being sued for ADA compliancy means that every mom and pop website needs to be worried about a lawsuit? No. Do I think a lot of other large businesses and government websites could be sued? Maybe. I do think that this ruling highlights the need for business to be aware of all audiences.

I think that ADA compliancy on the web comes almost naturally by being courteous toward your users. Why not make your information easy for everyone to use?  You’re not talking about added physical infastructure (ramps to your door, for instance), you’re talking about being smart when you architect your site and choose your solutions for images and text — the basics.

I recently got a brief glimspe of how frustrating it is navigate a visual medium with only aural narration ( not unlike blind users with a browser that reads to them). A non-technical friend of mine needed guidance through the steps of burning some digital pictures to a CD. I couldn’t see what they were seeing, I and could only rely on what he told me over the phone. This lead to some significant frustration. But my little experience would probably seem the tip of the iceberg for someone who only has that method available to buy something or look information up on the web.

There are lots of good guides for ADA compliancy on the web. A couple resources I like:

ADA Best Practices Tool Kit for State and Local Governments

Section 508

WebAIM Checklist

Is your website going to be perfect? No. Information labeling and organization is a process – so is website development. Keep the standards in mind when considering changes and remember to be as polite as you can to all your audiences.