189. How to keep up with web innovations

On this week’s show: Paul looks at keeping up with web innovations, Marcus shares how we make the podcast and Nora Brown reviews building findable websites.

Play

Download this show.

Launch our podcast player

News

Web design match making

Finding a web designer can be tough. Equally, if you are a web designer (especially if you are just starting out) finding clients can be hard. Much like in love, finding the perfect partnership is difficult.

37 Signals feel they have the answer. To accompany their already successful jobs board, they have now launched Haystack.

Haystack, allows web designers to upload a brief description of their agency for free or a more detailed portfolio for $99 per month.

Clients can then browse this directory in attempt to find the perfect agency.

And there in lies the problem. Although Haystack is beautifully designed it is actually incredibly limited from a clients perspective. They are only given three choices.

  • Search through hundreds of listings manually
  • Filter by city
  • Filter by budget

These filters are both extremely limited and are not enough for narrowing down such a large number of designers.

Haystack.com

Filter by city allows you to select from a handful of US cities, while dumping all other locations into a catch all of ‘other cities.’ This might possibly be acceptable if there was an option to search by country, region or city. Unfortunately there is not.

Filter by budget is equally flawed. As a web designer you have to select a price range that you normally work within. This effectively excludes you from smaller or larger projects. In reality things are rarely that black and white.

Finally I would argue that there are many other characteristics clients look for in an agency. There are no options to filter by technology, skill set or sector experience. The tools available are simply too blunt for making an effective decision.

My guess is that 37 Signals have been caught off guard by the instant popularity of the app. The current application has been built with a small number of agencies in mind. In such circumstances it would be perfectly adequate.

I am sure that they are already working on upgrades to the app which will handle the large number of agencies much more elegantly. These guys do good work and there is no doubt that an app like this is much needed.

Client relations

There seems to be a lot of posts around this week looking at the working relationship between clients and web designers.

There is a sitepoint post that focuses on fine tuning your persuasive techniques, a smashing magazine post on dealing with difficult characters and A List Apart post on when to walk away. There is even an article teaching us how to deal with things like scope creep and unhelpful design feedback.

Although it is good to see posts tackling client management, I do fear they all have a negative tone.

Last friday I ran a workshop on client relationships and although we discussed dealing with problematic relationships, I tried to make the overall theme a positive one.

Too many web designers go into new projects seeing the client as either the enemy or as a hinderance to the projects success. Articles like those I have mentioned are in danger of reinforcing this viewpoint.

It is important to remember that our clients are extremely knowledgeable in their own fields and that both designer and client wants the same thing – a successful website.

I also worry that too many web designers are perceived as negative. Instead we need to be positive and stop saying no to our clients.

Myths of usability testing

Two posts have been published recently that challenge some of our preconceptions about usability testing.

The first is a post by A List Apart entitled “The Myth of Usability Testing” and is a response to some fairly shocking research.

The research monitored a number of usability tests run by different agencies on the same site. The result was that although all of the agencies found many problems, only 30% of those problems were common to more than one agency. In other words the agencies could not agree on where the problems lay.

The article goes on to examine the discrepancy focusing in particular on the questions asked and the people tested. It also explains that context is vital to the interpretation of results.

The second post is one that challenges the role of eye tracking. The post looks at the pros and cons of the approach and in my opinion is a balanced assessment.

The post ends with the following conclusions:

Some have concluded that the benefits of eyetracking are not worth the high cost, effort, and complexity it adds to usability testing. On the other hand, some eyetracking vendors and consultants have promoted the idea that you cannot conduct usability testing effectively without eyetracking.

The truth lies somewhere between these extremes. If you know how to use eyetracking effectively, it can provide additional insights to usability testing that can help you find problems and answer questions about user behavior. Eyetracking is not essential to usability testing, but if you can afford it and have the time to learn how to use it effectively, it is definitely worth it.

Personally, we have never recommended eye tracking to our clients and this post has done nothing to persuade me to start. For the type of clients we work for the expenditure is hard to justify.

jQuery for designers

I am a huge fan of jQuery. I have said this more than once in the past. The thing I love most about jQuery is that it is aimed squarely at designers. If you can understand HTML and CSS, then you can wrap your head around jQuery. What is more, it lets you do some really cool things very easily.

Imagine my delight when this week I discovered jQuery For Designers. Apparently the site has been around for a while but I seem to have missed it entirely. In case you have missed it too I thought I would give it a quick mention.

The site contains dozens of screencasts and examples of various cool functionality that can be built with jQuery. Just some of the tutorials include:

  • Tabs
  • Slider galleries
  • Carousels
  • iPhone sliding headings
  • Fixing floating elements

Best of all, you can subscribe to these screencasts on itunes enabling you to view them as a podcast.


This is just one of the many excellent tutorials on jQuery for Designers.

Back to top

Feature: 10 secrets to staying informed about web design

Keeping up in the world of web design is tough. Things move fast and its hard to stay informed. In this post I share 10 ways that RSS can come to the rescue.

Read 10 secrets to staying informed about web design

Back to top

Ad: Win a Macbook Pro or iPod Touch

Webvanta are running a superb contest that I wanted to quickly mention.

There is an opportunity to win a Macbook Pro or one of three iPod Touch.

To be in with a chance of winning, you need to build a great looking, effective website on the Webvanta CMS.

Don’t worry if you are not an existing Webvanta user. They are going to give you a Webvanta premium account for the duration of the contest.

The panel of judges (that includes our own Ryan Taylor) will pick a winner on the 1st February so get designing.

For more details on how to enter visit Webvanta.com/Contest.

Back to top

Listeners feedback:

Recording the podcast

I had the following tweet from @david_o_connell:

@marcus67 could you guys do a spot on the tech setup for recording the podcast please (didn’t ask Paul as he muffs the audio :) )

Thinking about this I realised that I have never covered this riveting subject so after nearly 200 shows it was probably about time!

It’s worth noting that we are set up to record and edit things as quickly as possible. We have recorded a weekly show for years so we have to get it down and get it out the door. I’m sure there are other ways of doing things and I expect my history of working in expensive recording studios potentially means that I overcomplicate things… but, this is how I do it.

Hardware

Ok, this is a list of all the stuff we use:

  • AKG C 2000B microphone (x3) – these are ‘mid’ quality mics that need phantom powering. ‘Decent’ quality mics are a must otherwise you will end up with a thin and probably noisy result. Built-in laptop mics are a total no-no!
  • Angled mic stand (x2) – these are recent addition that mean we can comfortably use our laptops while recording the show.
  • Straight mic stand – we use this for any guests we have on the show.
    Pop shield (x3) – again, a recent addition to the setup. Vital in avoiding pops and bangs on words that begin with ‘p’ or ‘b’.
  • XLR to XLR (balanced) mic leads (x3)
  • Behringer mixing desk – our mixing desk has 4 ‘proper’ mic channels and 4 stereo channels, 2 sub groups and phantom powering to power the mics. On a standard show, I take a feed from sub the group outputs to the input on the Mac. When we’re recording a live show things are little more complex as we need to get the audio to two places at the same time (my Mac recording the show and Paul’s that is broadcasting live). I also need to hear the audio from the intro videos so we’re taking an out from Paul’s Mac for the videos and a feed from the desk master outs to his line input… you need to see it really!
  • Technics closed-ear headphones – these are my ‘old faithfuls’ that I have used for years. It is imperative that one person monitors voice levels throughout the recording. I plug them into the headphone input on my Mac. Closed ear are best because they do not ‘spill’ into the mic.

I don’t use any external compressors or limiters. That gets taken care of in the software.

Software

In my current setup I use Logic Pro to record all of the audio. This is a bit over the top for podcast recording but I also use it to record music and it does both jobs beautifully.
For the voice tracks I use the setting Voice > Speech > Male Radio that adds a compressor, de-esser (to stop sibilance) and EQ.

However, if you’ve got a Mac then Garageband will do the job admirably. It even has ‘podcast’ settings that you can assign prior to recording.

Back in my PC days I used to use Sony Soundforge to record the audio tracks which I would then edit together using Propaganda. I still use Soundforge to bounce down to MP3 (Logic is unreliable at this).

Recording tips

Here’s a bunch of tips to :

  • As I’ve already mentioned, use headphones while recording the show to avoid anyone going ‘off mic’. Usually, pointing at them, then their mic gets the message home!
  • When recording 2 people pan the input channels hard left and hard right. This means that if you have to boost any part of a recording it’s easy to locate the specific part. The absolute ideal here would be to have some sort of multi-input box into the computer thereby allowing multitrack recording i.e. I am recorded onto one track while Paul is recorded on to another simultaneously. Thinking about it, I could probably do this right now (for max 2 channels) by separating the inputs and recording 2 mono channels instead of one stereo. But, to be honest, it’s really not worth doing as, mentioned earlier, time is of the essence.
  • Record a quick levels test prior to any recording (because you really don’t want to have to go back in and fiddle with the levels afterwards unless you absolutely have to).
  • Record each section of the podcast on a separate track. Don’t do one long recording as this is much harder to edit later and add in music and audio dividers. If you record each section separately then you should only have to top and tail it which takes no time at all.
  • Once all the voice recording is done, I will add in the intro and outro music, the section dividers and any interviews or questions that are part of the show.
  • Once I’m happy with result, I bounce to Wav format which I then open in Soundforge and save out as 64Kbps 44.1 kHz mono MP3 format which is tagged and FTP’d to our hosts.

Here’s a screenshot of a final ‘mix’ in Logic before the bounce down (v zoomed out).

Screenshot of a final ‘mix’ in Logic before the bounce down

Building Findable Websites

My name is Nora Brown; I’m a freelance web designer in Boston.

I’d like to give you and Boagworld listeners a recommendation for a book I recently read, called “Building Findable Websites”, by Aarron Walter. Though I finished reading it a month or so ago, I find I’ve been referring back to it constantly ever since.

Building Findable Websites: Web Standards, SEO, and Beyond

In this book, Aarron Walter views SEO as just one aspect of, and in some ways almost a side effect of, improving a website’s “findability” — which is defined on page 2 as:

“The quality of being located or navigated, the degree to which an object or piece of data can be located, and the degree to which a system supports navigation and retrieval.”

The goals of findability are listed as:

  1. Help people find your website.
  2. Help people find what they are looking for once they arrive at your site.
  3. Bring your audience back to your website.

Notice there is no mention of Google or any other search engine, because obviously the ultimate goal is to help *people* find and use your website, not search bots.

To that end, Walter provides straightforward advice for improving findability at all levels of site development:

  • Front-end markup strategies
  • Server-side strategies
  • Content generation

Though not every technique will be right for every site, as someone who builds small business and portfolio websites, I found the majority of the recommendations to be practical and implementable. Furthermore, nothing in the book represents SEO for SEO’s sake — all the techniques have other benefits, primarily improving the user experience.

Aarron Walter manages to fit an amazing amount of useful, actionable information into this slim volume, but if it’s not enough, there are even five bonus chapters which you can download for free at buildingfindablewebsites.com.

I hope you and your listeners take a look at this excellent book.

I also think the author Aarron Wlater would make a great candidate for a Boagworld interview.

Thanks and keep up the wonderful podcast.

Back to top

How moodboards can save time, money and your sanity!

Mood boards are a traditional design tool. However, few web designers use them. This post looks at how they can transform your process, increase profitability and reduce the stress associated with design sign off.

Headscape has been using mood boards as part of our design methodology for some time. We believe they are an invaluable tool that helps both the client and the designer.

However, before you can understand the benefits of mood boards, it is important to acknowledge where the traditional design process falls down.

Where the traditional web design process fails

Obviously everybody approaches the design process slightly differently so it is unfair to refer to a traditional approach. However it would appear that many agencies and freelancers follow roughly this process:

  • Ask the client a bit about what they want from the design
  • Ask the client to identify some websites they like.
  • Produce 3 design comps in Fireworks or Photoshop.
  • Ask the client to choose a design from the comps presented.
  • Iterate until the client is happy.

This was certainly the approach we used until we realised it was not working.

We identified the following problems:

  • When asked what they wanted from their design, most clients focused on personal preference rather than business or user needs.
  • Clients often referred to sites that were either inappropriate for their audience or were selected based on content rather than design.
  • Producing multiple design concepts was time consuming for the designer and expensive for the client.
  • Multiple concepts led to frankenstein design, where the client would try to combine the ‘best bits’ from each comp.
  • The designs went through a lot of iterations because the designer did not have a full understanding of the clients requirements.

We utilised several approaches to overcome these problems. However, the most successful component was mood boards.

What is a mood board?

A mood board is basically a collection of graphical elements that set the tone for your design. Typically these include examples of:

  • Typography
  • Imagery
  • Colour
  • Layout
  • Style

Often these elements are lifted from other sites or even from sources such as magazines.

An example mood board

They are not meant to represent the final design, but rather provide an indication of how the site may feel.

When you first start producing mood boards it is difficult. You may have a strong sense of how the site should look, and so it can be hard producing alternative approaches.

Increasingly we produce four mood boards:

  • One that is our initial gut reaction.
  • One that is a more conservative version of the initial board.
  • One that is more extreme.
  • One completely ‘out there’ approach that is probably inappropriate.

Admittedly you could get away with the first three, but the fourth enables the designer to be more creative and potentially discover a completely different approach.

How mood boards can help

The reason mood boards made such a difference to our process was three fold:

  • They put us in control - Previously it was the client who was making design suggestions and selecting inspirational sites. By using mood boards we were the ones setting the tone and suggesting the direction. After all that is what the client is paying us for!
  • They are quick and easy to create – Developing design comps is time consuming and expensive, especially for something that may ultimately be discarded. Mood boards can be produced relatively easily, which means they are viewed as disposable. As a result the designer is not overly committed to a particular path and the client can see multiple revisions.
  • The client focuses on design, not content – We found that when clients looked at a design comp they were more concerned with the content than the design. Because mood boards do not contain real content, this problem is avoided and the client can focus on typography, imagery and colour.

The introduction of mood boards made an enormous difference to the running of our design projects. However, over time we have made some mistakes that have reduced the effectiveness of mood boards.

Mistakes when designing with mood boards

If used correctly mood boards are an extremely powerful tool. However, it is also easy to fallback into old habits. If you are going to use mood boards, be careful to avoid the following mistakes:

Designing a website and not a mood board

One problem we encountered was that we were so conditioned to build websites that it was hard not to. Every time we produced a mood board it ended up looking like an actual site.

A mood board that looks like a final site

The solution

The way we are resolving this issue is by changing the format. Instead of designing on a 1024 by 768 canvas, we have switched to creating A4 mood boards. In fact we also try to minimise web elements such as navigation or search boxes.

Making them too finished

An associated problem was that clients were getting confused. The mood boards were looking so polished that they were no longer sure what they were looking at. Was this a mood board or a design comp? What were they supposed to be providing feedback on?

The solution

We are still battling this problem. However, one approach I have adopted is setting constraints on the designer. Typically this involves limiting what Photoshop tools they can use.

When all the designer can do is copy and paste elements they have found elsewhere, the mood boards cannot become overly designed. The emphasis shifts from designing detail to looking for inspiration and setting the mood.

Spending too long on a mood board

Of course, the final problem relating to overworked mood boards is time. As our mood boards started to become more and more like design comps, they took longer to produce.

This had two consequences. Firstly it cut into our profit margins. Secondly, the designer became increasingly attached to the mood boards and find it hard when the client don’t like them.

The solution

The solution to this one is simple. We are beginning to set time limits on mood board production. We are now asking designers to spend no more than one hour on a single mood board. Most of that time is spent sourcing elements rather than doing design work.

By taking this approach we can afford to produce multiple iterations of mood boards and experiment with many different directions.

Conclusions

I am aware that we are in a minority by using mood boards. However, I would suggest that every designer should consider them as a tool.

If you design multiple comps then this could be a real cost saver.

If you pursue a single approach, this will enable you to explore other avenues with minimal effort.

So, what do you think? Do you use mood boards already, or do you think it is an outdated tool that has no place on the web? Whatever your thoughts I would love to hear them in the comments below.

187. Jedi Mind Tricks

On this week’s show: Paul looks at how to better communicate and we ask whether you should mask your email address to avoid spam.

Play

Download this show.

Launch our podcast player

Housekeeping

Although we promised you ClearLeft on this week’s show we have had to postpone it until next week. However, that gives you a whole extra week to submit questions via the comments on our blog.

Back to top

News

A web designers time is precious

We are all too busy, period. However, life can be particularly intense if you work as a web designer or developer. The pace of change is so fast it can be hard to find the time to keep up.

Fortunately there are some great articles around that provide time savings tips. Take for example Sitepont’s post this week “How to take control of your time.” It provides some excellent advice including the importance of prioritising, the need to leave adequate time and learning to say no.

Smashing Magazine has a post of their own entitled “20 time saving tips to improve designers workflow.” This includes ways to customise your work environment and better work with tools like Photoshop.

Speaking of Photoshop there is a great cheatsheet that contains all of the keyboard shortcuts you need to speed up your workflow in Photoshop. When combined with the IE6 cheatsheet for solving common IE6 bugs you will find yourself saving considerable time.

The answer to overload is not to work longer hours. It is to work smarter and that is what these posts enable you to do.

15 common ecommerce mistakes

I love working on ecommerce sites. They are by far my favourite. The reason – you get to see an obvious return on your work, because they have an obvious call to action. Conversion either increases or decreases. Profits either rise or fall. You are in no doubt as to whether you have made a difference or not.

However, the other reason I love working on ecommerce sites is because so many of them are terrible. Often when you start working on an ecommerce site there are loads of quick wins that make an instant difference to revenue.

People make the same mistakes again and again. In fact these mistakes are often so predictable that you could write a top 10 list of them… and guess what… that is exactly what Smashing Magazine has done: “15 common mistakes in ecommerce design and how to avoid them“.

Some of my personal favourite mistakes include:

  • Hiding contact information
  • Long winded checkout
  • Poor customer service
  • Not highlighting related products or otherwise upselling
  • Hiding the cost of delivery

If you are designing or running an ecommerce site then you really should check this post out. You will be surprised just how many of these mistakes you make.

The benefits of inline form validation

I have said it before and I will say it again: “forms are the most important feature on most websites.” Most often a sites call to action requires the completion of a form. Get the form wrong and you frustrate users potentially driving them away.

Nobody likes filling in forms. Whether it is a contact form, site registration or just a simple login form. It is therefore vital that we make the process as painless as possible.

There is a post on a List Apart which I have only just gotten around to reading. “Inline Validation in Web Forms” does not sound like the most exciting read but it does provide some invaluable best practice for dealing with forms. However, it doesn’t just provide somebodies opinion on best practice, instead it backs those views up with valuable testing.

The post takes a typical signup form and trials different forms of inline validation with real users. They didn’t just monitor success/failure rates. They also looked at errors made, satisfaction rates and completion time. They even did some eye tracking.

Although the results are not surprising, it is nice to have some numbers to put against what we have known to be true. For example, it was obvious that inline validation makes an enormous difference to both actual success and perceived success. Just validating a form on the client side increased success rates by 22% and satisfaction by 31%. Those numbers went even higher when the user is given feedback as they completed each field.

A valuable post, worth reading.

Innocent smoothies: A case study into corporate communication

When you speak at as many conferences as I do, you often find yourself referring to the same examples of good or bad practice. Whether it is comparing Google and Yahoo or fawning over Apple’s great UX design, the same names keep coming up.

One of the names I often reference is Innocent Smoothies. I love them. They just ‘get the web’. Actually, that is a lie. They get people. They know how to communicate and they know themselves. They have a distinctive voice that makes people warm to them and that is carried through to their website.

This week Anna Debenham has written an excellent case study on Innocent Smoothies looking in detail at what makes them successful online. In particular she looks at their blog and mailing list.

As Anna says at the start of her post:

A lot of the clients I work with who have just set up a web presence for their company think it’s a good idea to start a mailing list and a blog. Everyone else is doing it, so why shouldn’t they? The problem is, so few companies get it right and very few people will bother to read them.

So what makes Innocent different? Anna gives 6 reasons:

  • They show you the real people behind the business
  • They make their copy fun
  • They don’t just talk about their products
  • They are generous
  • They provide useful information
  • They make good use of imagery

Anna’s post is packed full of examples, so be sure to check it out. There is a lot most corporate bloggers could learn from Innocent.

Back to top

Feature: How to persuade your users, boss or client

Whether you are trying to get signoff for a site’s design or persuade a user to complete a call to action. We all need to know how to be convincing. This week, we look at how to present our message

Read Jedi Mind Tricks: How To Persuade Your Users, Boss, Or Clients

Back to top

Listeners feedback:

Email masking

One of the more popular suggestions for topics was how to mask your email address so it doesn’t get harvested by spammers.

This is something that everybody worries about from designers to website owners. However, unfortunately there is no good solution. In my opinion you need to just put your email out there and deal with the spam.

Sure there are a number of possible solutions but none of them are acceptable. They either require the user to be running Javascript (which creates accessibility problems) or they place extra burden on the user. Giving users the ability to contact you is a fundamental part of almost all websites and, so you do not want to make it hard.

There are however two ways of minimising the impact.

First, you could choose not to publish your email address, but instead offer a contact form. Although spammers can spam these too, it is harder and there are ways of minimising spam without putting an added burden on users. However if you do use a contact form, send a copy to the user so they have a record.

Second, you can fall back on good spam filters. Use a site specific email address and make sure it is guarded by a good quality filter. I personally find Google Mails spam filter particularly good, so you might want to consider routing enquiries via that.

However, at the end of the day if a spammer is determined to spam you there is very little you can do to stop them. Unfortunately, this the price of being online.

Back to top

Jedi mind tricks: How to persuade your users, boss, or clients

Whether you are trying to get signoff for a site’s design or persuade a user to complete a call to action. We all need to know how to be convincing.

Like many in the web design industry I have a strange job. I am part sales man, part consultant and part user experience designer. One day I could be pitching a new idea to a board of directors, the next I might be designing an ecommerce purchase process.

There is however a common theme – I spend most of my time trying to persuade people.

As web designers we often have to nudge people in the direction we want them to go. It is a vital skills that we all have to learn.

I am not talking about manipulation. I don’t believe in using underhand techniques and I certainly do not believe in lying. However, there are ways of presenting yourself and your argument in such a way that people are more receptive.

The first and probably most important way is to empathise.

Empathise

The worse thing you can do is go into a meeting or begin designing a user interface with a personal agenda.

If your goal is to push the other party into agreeing with you, they will resist. However, if you seek to understand their needs and respond to these, you will find them more cooperative.

Start by listening

To achieve this you must really listen. It is not enough to pay to pay lip service to the idea of listening. You need to hear what they have to say and look for ‘points of pain’ where your ideas might actually help them.

Tailor the way you communicate your agenda

The idea is to tailor the presentation of your ideas so that it can be seen to benefit the other party, rather than forcing them to reluctantly agree. This involves some creative thinking but is possible if you really understand their needs.

Show the other party what benefits you can offer them

Remember it is not enough to explain how your ideas will help you or even others. You have to demonstrate how it helps the person you are speaking to.

For example do not say to your client:

Users are going to love this new feature.

Instead say:

This new feature will keep users coming back and that will dramatically improve the number of leads you receive.

Once you understand the other party and are thinking about their needs, the next step to form a relationship with them.

Be personable

If you have a good relationship with your users, boss or client they are more likely to follow your suggestions.

Obviously the kind of relationship you build is dependant on who the other party is. Your relationship with website users is different from your relationship with the boss. However, there are certain approaches you should always consider:

Get them nodding

It’s a silly little thing but when I go to pitches I try and get people nodding. If they start nodding it is a good sign. However, more than that it put them in a positive mood.

I normally achieve this by repeating back to them (in different language) a point they themselves have already made. This is obviously something they can agree with, but also demonstrates that I was listening and that we are on the same wavelength.

The same approach can be used online. For example if I am writing a post aimed at web designers, I know that berating IE6 will start them nodding in agreement. I have succeeded in making a connection.

Be enthusiastic

Enthusiasm is such an important tool. Clients want to know you care about their project. Bosses want to know that you are motivated to work and users want to know you care about the service you provide.

However, so many people lack enthusiasm when communicating their message. They either come across as defeated before they start or as overly aggressive.

A better approach is to go in with overwhelming enthusiasm. People get caught up in enthusiasm. It is infectious. However, most importantly it is hard to say no to somebody who is exuding enthusiasm and excitement from ever pore. It would be like kicking a puppy :-)

Mirror them

You have all heard how mirroring somebodies body language helps establish a positive connection. Whatever you do, do not do it! If it is done as a conscious action it just comes across as creepy! It will happen naturally, so do not worry about it.

That said it is a useful indication of whether a face to face meeting is going well. If the other party is mirroring your body language, then the chances are they like you.

What is more interesting is that you can mirror people’s language.

Try and use the same terminology as the other party. If your boss or client talks about return on investment or success criteria, ensure you do too. Equally if your user is not familiar with certain language, make sure you avoid it.

The way we speak associates us with a certain ‘tribe’. If we share the same language we are more likely to build a rapport.

Make them smile

A final trick I use for building relationship is to inject some humour into proceedings. If you can make the other party smile, you are a long way to breaking down any barriers that may exist.

Of course, this has to be used with some care. Overdo it and you look like the fool. However, even the most miserable looking board of directors are human beings and like to smile.

Although all of these approaches are great for building relationship there is one that trumps them all – openness.

Be open

You maybe reading this thinking “this guy is mad, what if his clients read this stuff. Won’t they feel manipulated?” My answer is no. I am being open and honest about what I do. I would be entirely happy for any one of my clients to read this because there is nothing manipulative or hidden here. People hate being deceived and so if anything the honesty in this article will build my relationships, not undermine it.

I believe there are two key components in building open relationships that lead to a receptive audience.

Disarming honesty

Many times the best approach is to diffuse potential conflict with disarming honesty. For example I regularly acknowledge in sales situations that I am there to sell and that they should take anything I say with a pitch of salt.

The client would obviously know this already. However, admittedly it verbally is the kind of honesty people rarely encounter.

When designing a website it is important to be upfront with users too. For example if you are asking for somebodies telephone number on the website, do them the courtesy of admitting that it is because you want to contact them.

A willingness to show weakness

We can sometimes be so desperate to make our point that we become unwilling to admit even the slightest weakness in our argument. However, ultimately we come across as pig headed and inflexible.

People respond well when you admit that you are wrong or if you are unsure of an answer. Be willing to say I do not know or I have messed up if appropriate. People will respect you for it.

One of the best examples of this is Flickr’s blog post “Sometimes We Suck” in which they apologised for performance problems. By taking this approach they demonstrated their integrity and completely defused the anger of those complaining.

Of course, being willing to show weakness takes a lot of confidence and that is a trait desperately needed if you are going to convince others.

Be confident

As humans we are drawn to confident leaders. We follow those who have a clear vision and who walk that path with confidence.

It is therefore important to communicate your message with confidence. Establish yourself as an expert and talk with authority. People will respond to this.

However, confidence is not the same thing as arrogance.

Confidence not arrogance

Being confident also involves having the confidence to admit when you are wrong. A truly confident leader does not claim to have all of the answers all of the time. Conceding points and being willing to allow others to express their views is a key component of confidence. Only those who lack confidence fear an opposing view being expressed.

You do not need to always win

Pick your battles. It is okay to concede some points to achieve your greater aim. It does not undermine your position to give ground. Sometimes you need to play a submissive role to get people on board.

Don’t allow your ego to get in the way. If it makes somebody feel good that they have won an argument then they are more likely to be consolatory when you suggest an alternative.

Some degree of compromise is okay. It is certainly better than being negative and constantly rejecting counter proposals.

Be positive

Whether dealing with your boss, a difficult client or your users, you need to impress them with your attitude and service.

You should always remain helpful and keen to leave a positive impression. Sometimes that involves going the extra mile in customer service. Other times it means finding some positive aspect in your bosses latest mad scheme.

Whatever the situation, the worse thing that can happen is you get a reputation as somebody who is unhelpful and negative.

Conclusions

You will probably have gathered by now that my title is somewhat misleading. There are no Jedi mind tricks here. At the end of the day the secret to persuading others is to show them respect, listen to their opinions and seek ways of presenting your vision in language that they can understand and benefits them.

How to Win Pitches, Charm Clients and Get Signoff

Being a great designer or developer is only half the battle. You also need to be able to promote and sell your services, unfortunately there is little advice online about how to do this effectively.

The most common questions I get asked focuses on selling web design services and getting client approval. In short many web designers and freelancers struggle to engage with clients.

The problem appears to be so big and I get so many questions on the subject that I have teamed up with the guys at Carsonified to create a full days workshop on the subject.

Where and when

The workshop will take place on Friday 23rd October from 9AM to 5PM at the RIBA London.

We have limited the workshop to only 20 places so there will be lots of opportunities to discuss your particular challenges.

I will also be hanging around afterwards so there will be opportunity to go out and socialise too!

Who should attend?

This workshop is aimed at web freelancers, web design and development agencies and anyone involved in generating new business and maintaining and developing existing client relationships.

What Will You Learn?

Here is the agenda for the day. Hopefully that will give you an idea of what we will cover…

Shameless self promotions
  • What does not work?
  • The benefits of specialising
  • How to specialise
  • Selecting your target audience
  • Reaching your target audience
  • Demonstrating your expertise
  • How to make the most of social sites
The perfect proposal
  • How to price a project
  • What to include in a proposal
  • Should you provide speculative design?
  • When to walk away
The pitch
  • Who should attend?
  • What makes a client want to hire you?
  • How to generate confidence
  • Engaging with clients?
  • Learning how to engage
  • Making the most of your time slot
  • Dealing with difficult characters
Sales through relationships
  • Why repeat business matters
  • How to foster repeat business
Dealing with difficult people
  • The techie
  • The hard man MD
  • The price negotiator
The importance of establishing a good working relationship
  • Where it goes wrong
  • The benefits of getting it right
Changing the client/designer relationship
  • How to become the expert
  • The importance of positivity
How to communicate better
  • Speaking the clients language
  • How much does the client need to know?
  • Methods of keeping the client informed
Running the perfect kick-off meeting
  • Controlling the agenda
  • Educating the client
  • Defining roles
  • Explaining the process
Doing your research
  • Business objectives and success criteria
  • Target audiences and personas
  • Competitive analysis
Dealing with design
  • The importance of a design methodology
  • The tools of design development
  • Understanding the clients perspectives
  • Developing a site persona
Presenting work
  • When to present
  • Methods of presenting
  • Who to present to
  • Techniques for presenting
Managing feedback
  • Dealing with politics
  • Tackling committees
Dealing with difficult people
  • The existing client
  • The no clue client
  • The micro manager
  • The marketeer

How much?

So if you are interested in attending? If so don’t pay the full price :-)

The first 10 places are only £375, but you can also get a discount if you use the code: CWPB_09. This will give you 15% off that price.

If you decide to book drop me an email as I would love to chat beforehand!

Book Your Place Now!

183. Inspired

On this week’s show: Paul shares 3 ways to make your site stand out from the crowd. Matt Curry introduces us to Google website optimiser and Lyle Barras reviews Dropbox.

Play

Download this show.

Launch our podcast player

Housekeeping

A couple of random pieces of housekeeping this week.

Sponsor SXSW

First, we are looking for some Micro sponsors for this year’s Great British Boozeup. In case you don’t know the Great British Boozeup is a party that Headscape and Clearleft have thrown for the last few years at SXSW.

This year we are looking for some additional sponsors. So if you are a company interested in reaching out to the web design community and have £500 to spend, drop us an email and will look at making you a sponsor.

We want to showcase your work

Second, I really want to start showcasing upcoming members of the web design community on Boagworld. Therefore, if you have written a great blog post that you think Boagworld readers would like, drop me a line with a link to the post and we will look at reprinting it on Boagworld. Obviously we will link back to your own blog and publish a little bio about yourself.

Back to top

News

6 Steps to Creating a Unique Selling Proposition

One of the first questions we ask new clients before beginning a site redesign is “what are your unique selling points?” Of course in reality it is extremely rare to find an organisation that have truly unique selling points. However, every organisation should have a clear idea of what their distinguishing features are. What are the things that makes them stand out from the crowd.

What surprises is how few clients know what their USPs are. This is fundamental stuff and yet many organisations fail to address them. Whether online or off an organisation needs to be able to clearly articulate what sets them apart.

There is an excellent post on Sitepoint this week entitled “6 Steps to Creating a Unique Selling Proposition” that kinds the reader through the process of establishing their USPs. The six steps include:

  • Describing your target audience
  • Explaining the problem you solve
  • Listing the biggest distinctive benefits
  • Defining your promise
  • Combining and reworking your promises
  • Cutting the whole thing down into a single statement

It is a great post and definitely worth a read if you are a website owner trying to communicate what your organisation is about online.

Building a blog with HTML 5

Last week I was at the Future of Web Design Tour in Bristol and was fortunate enough to hear Bruce Lawson talk about building a blog with HTML 5. It was a real eye opener.

Many of us have the perception that HTML 5 is a technology we will work with in the dim and distant future, when all the major browsers fully support it. However, that is not the case. Browser manufacturers already support many of the elements in HTML 5 and handle gracefully many of those they do not. The result is that we can start building sites using HTML 5 now.

In Bruce’s talk he built a basic blog live on stage demonstrating many of the new characteristics of HTML. It was an amazing demonstration that significantly improved my understanding of how this new specification would work in practice.

Unfortunately the talk is not online yet. However in the meantime Bruce has released an article on HTML 5 Doctor which covers exactly the same subject.

This is a ‘must read’ if you code HTML. There really is nothing stopping you using HTML 5 right now. However, if you are still to be convinced listen to next week’s show where we plan to interview Jeremy Keith on exactly this subject.

Colour communicates meaning

Colour is one of the most powerful tools in a designers arsenal. Colour can have a profound impact on how we respond to design and significantly influences our behaviour.

However, it is often an area that is underestimated by website owners. They view colour as a personal preference not as something that we respond to collectively. That is why I was so pleased to see Rob Mills post “How Colour Communicates Meaning.”

The post is a great introduction into colour theory and the meanings that are communicated through your choice of colour. The post looks at:

  • How colour affects our mood
  • How different colour communicates different messages
  • The cultural significance of colour
  • How colour is inspired by our surroundings
  • The political and religious associations of colour

It is a great post that introduces the reader to the world of colour theory.

With all of that in mind it is unsurprising that picking a colour palette can be tricky. One approach used by designers is to use a key image or photograph as the basis for a colour palette. Another post we came across this week shows you how to use Kuler as a tool for doing exactly this. So next time you are struggling to select a colour palette checkout this Sitepoint post on how to use Kuler to pick a palette from an image.

The Seven Deadly Sins of Web Project Management

TheSamBarnes.com is a great blog about web project management. We have mentioned it before on the show and it is certainly one of my regular pit stops.

Web project management is not the most exciting of subjects, but one that to some extent we all have to deal with. Whether you are freelancer running your own projects or a website owner dealing with politics and external suppliers, there is no avoiding project management.

A new series on the blog particularly caught my eye. It features the seven deadly sins of web project management. At the time of writing there were only two posts dealing with four ‘sins’. Nevertheless it is shaping up to be a great series.

If you ever find yourself managing projects this is a series you will want to read.

Back to top

Make your website stand out from the crowd

This week we discuss how too many websites look the same as their competition. If you want users to remember your site it needs to stand out from the crowd.

Read 3 Ways To Make Your Website Stand Out From The Crowd

Back to top

Listeners feedback:

A/B Testing

Joshua writes: I recently read an interesting post over on the 37signals blog about how they use Google Website Optimizer to test different versions of their landing page to see which converts the best. Do you guys have any experience using tools like this? Any tips or thoughts on the subject?

I’m Matt Curry, Head of New Media for apetito, and for my sins I’m one of Paul’s clients. We’ve worked with Headscape for around 5 years now, predominantly on WilthsireFarmFoods.com, an ecommerce site with a unique elderly customer base, which if you subscribe to the podcast, you’ll know a fair bit about by now.  As at WiltshireFarmFoods.com we have a healthy obsession with conversion rate and website optimization, so Paul’s asked me to respond to a reader question this week. How exciting.

Joshua writes: I recently read an interesting post over on the 37signals blog about how they use Google Website Optimizer to test different versions of their landing page to see which converts the best. Do you guys have any experience using tools like this? Any tips or thoughts on the subject?

Google Website Optimiser is a tool used, unsurprisingly, to optimize the conversion rate of your site. Now every site ultimately wants a user to do something, be it buy a product, subscribe to service, make a donation or something simply forwarding the article to a friend – if your site has a clear goal, Google Website Optimiser allows you to perform 2 types of tests on your website content, A/B Split tests and Multivariate Tests.

In the case of 37 Signals, they were seeing if Website Optimiser could help them increase the conversion rate of their paid plan signup page – they were testing different variations of copy for the Heading and subheading of the page, to see which combination worked the most effectively.

This is of course nothing new, and indeed, some platforms such as Demandware have content testing built in, alternative analytics packages such as Omniture or Coremetrics also do this, and looking at email content, many ESP’s such as Pure allow you to test multiple subject lines and broadcast times. At Wiltshire Farm Foods, being as obsessed with conversion rate as we are, we’ve performed numerous tests, such any rate changes a new design brings, testing changes to Average Order Value during a price led promotion, and checkout abandonment rates given different variations of microcopy.

Whilst simple A/B testing can be performed in easier ways – remember a simple landing page conversion test can be done by varying destination address in your Google Adwords, Google Website Optimizers power comes from it’s multivariate testing suite. This allows you to perform tests on variations of your content, as in the example from 37SIgnals, to see which combination works better at driving your visitors to action.

However, if you have a particularly complex site, as we have, Google Website Optimiser can be frustratingly limited. For example testing a new product detail page layout across the site – when you have friendly URLs in place, which we do via an isapi rewrite,  can be rather difficult. Google Website Optimiser is very strict on the criteria needed to complete a test, and if you most of your content is dynamically generated, be prepared to write considerable additional code to ensure you’re calling the correct tracking script for each experiment.

If all this sounds too much for you, remember many such tests can be done using User Defined Variables in your Google Analytics. I dearly love the Advanced Segments part of Analytics, and despite “still” not being able to overlay segments, it can tell you a great deal about your site. So, for example, for an A/B test based on a redesign of dynamic content such as a Product Details page, you could set the variable to “New Design” or “Old Design”, and track goal conversion from there.  Just remember to drop a cookie to ensure a consistent experience. Being able to set visitor variables like this in code, rather than having to rely on the strict requirements of Google Website Optimiser, means your open to test a great deal more.

Remember, that if you’re testing a radical change to your website, you should expect an initial drop in conversion – users tend not to like change! You may wish to only test the new design with only a small percentage of your traffic, and increase the percentage as you become more confident. When we launched the new Wiltshire farm foods website mid February, we started with only 1 in 20 visitors seeing the new design, and gradually (or not!) increased it as we saw the positive effect on conversion rate it had.

And of course, nothing even got to this stage without User Testing – but that’s a topic for later!

Personally, I’m surprised by the significant increases in conversion that 37Signals had – how many of us even read the headings of such pages – you normally can’t expect vast jumps in conversion rate unless you are radically changing content.

The most successful variant 37Signals tested was the one that communicated no commitment, a minimal time cost – signup takes less than 60 seconds, and a delayed monetary cost with a 30 day free trial – yet giving immediate utility to the user.  I’m not exactly shocked it won! If you haven’t read Richard Thalers Nudge, which deals with incentives & choice architecture, then I heartily recommend it.

Of course, any good website copywriter would be able to tell you this, without copious testing.  There’s certainly a danger, especially when you are looking at testing and changing copy that each page may end up with a different tone of voice, and your site could easily come across as schizophrenic. If you’re serious about conversion, employing someone to develop an audience-appropriate tone of voice is very important.

I’d be interested if 37Signals play around with the words “Free Trial” – since with nowadays promotionally savvy audience, these words can have negative connotations.

Finally, I would say, as a caveat, don’t get wrapped up in statistics, it sounds corny, but analysis paralysis can happen, getting so wrapped up in each little percentage point increase that you forget the bigger picture. We’re all clever people, we hopefully know our audience, what works and what doesn’t, and we should trust our gut instincts more.

A review of Dropbox

Lyle Barras has been kind enough to send us an audio review of Dropbox:

Hi Paul and Marcus, my name is Lyle and I’m a hobbyist web developer. I’d like to give a quick review of an online tool called dropbox and a little about the way I use it.

Dropbox is an online storage device. You simply sign up for an account at www.getdropbox.com; the free accounts give you 2GB of storage, and then download the little application.

You can download as many copies of the application as you want so that you can sync up as many computers as you want and the really great news is that it’s Mac, Windows and Linux compatible. I have tried it on all three and it works seamlessly. There is also a pretty cool web interface if you happen to be on a machine that doesn’t have the app installed.

As soon as you place a file or folder into the dropbox then it sync’s to the other machines you have set up and the file is there almost immediately.

If 2GB isn’t quite enough you can upgrade to one of the two paid accounts. Pro 50 gives you 50GB for $9.99/month and Pro 100 gives you 100GB for $19.99/month. I think the Pro 50 is pretty good value if your storage need is big enough.

At any time you can refer the tool to your mates. If they then sign up, even for a free account and download the app then you get another 250MB of free storage and so do they. To date I have referred two of my mates and got 500MB free.

I have found one problem with dropbox. When I upgraded my iMac and MacBook I found dropbox to be a bit glitchy and crashy. I did a bit of Googling and found that dropbox had already released a new fixed version of the app.

To pinch a bit of the advertising guff from the site

Dropbox replaces:

  • Emailing file attachments to yourself and other people
  • Using USB drives to move files between computers
  • Renaming files to keep a history of previous versions
  • Complicated backup software
  • FTP servers, system-specific sharing methods, Network Attached Storage (NAS)

As I said at the beginning I’m a hobbyist web developer. I had been using a memory stick to carry round my work as I can really justify one of these posh versioning tools. I was sick of thinking “Right I’ll do a little bit” and find that I have left the drive at home or in the office.

Dropbox replaces all that. I just use it as my memory stick and it’s always there I don’t even need to be connected to the net as long as I have sync’d the machine recently.

I’m utterly sold and couldn’t imagine not having my dropbox now.

Thanks for your time guys, keep up the good work and keep up the dodgy jokes Marcus.

Back to top

177. Back in business

On this week’s show: Paul and Marcus talk to Brett Welch about the business of web design, and Paul chats with Ryan Taylor about creating a buzz.

Play

Download this show.

Launch our podcast player

Twitter post: Decided I like the boagworld podcast much more when @stanton and @ryanhavoc host it. Odd.

Oh right, I see! I’ll get my coat!

Back to top

News

The web font showdown

There has been a lot of exciting developments in the world of embeddable web fonts. It doesn’t look like it will be long before having custom fonts on our websites will be a reality.

We already have the likes of Cufon, which appears to be a huge improvement over the flash based sIFR technique. We also have Jeff Veen’s Typekit coming soon. This promises to give us access to a large number of fonts using nothing more than CSS font-face and some Javascript.

However, this week has also seen clearleft’s announcement of Font Deck, a direct competitor to Typekit. The rumour is that it will differ from Typekit because it will not rely on Javascript. Exactly how this will work is currently unclear. There is also a possibility it will use the same kind of caching approach Google Code offer for Javascript libraries. If it does this will significantly improve the perceived download speeds of fonts.

Although Font Deck is arriving a little late to the party, ultimately it will come down to who has the best selection of fonts. Until we know that there will be no clear winner.

That said, judging by an article on Think Vitamin, Typekit looks pretty impressive. The article demonstrates how Typekit will work and I have to say it looks very straightforward. Unsurprisingly for an application developed by Jeff Veen, it is incredibly well designed. However, it is not perfect. The demo page associated with the post shows a significant delay as custom fonts are loaded. Until that is complete the user sees a web safe font. Unless they seriously ramp up their server capability this delay could get even bigger as the popularity of their service increases. This might possibly be the opportunity that Font Deck needs to leapfrog their competition.

Moving design forward

Web design has come a long way from the grey backgrounds and blue and purple links of just a few short years ago. But where do we go from here? That is the topic tackled by Jennifer Farley in “Art Direction: Taking Web Design To The Next Level.”

As you will guess from the title, Jennifer’s answer is Art Direction. Art Direction is (among other things) the process of bringing together design and content. This is something sadly lacking in modern web design. Most websites are designed with little understanding of what content they will finally contain. Design is built around a series of templates integrated into a content management system. There is little customisation of the design to work with the content of each page.

Jennifer shares some examples of sites that endeavour to move beyond the template mentality and introduce real art direction. They are definitely worth looking at as they will inspire you to move beyond template design.

Jennifer’s article is not the only post that encourages a change in our approach to design. The other is a post from 37 Signals entitled “Stop following directions and start designing.” This post encourages designers to view feedback from the client as suggestions rather than solutions. The author writes…

When you’re getting direction from a client, manager, art director, etc., it is easy to fall into the mode of just following instructions. You get so caught up in getting it right that you forget to keep thinking about the problem.

Of course it is totally understandable to take the ideas of those that pay our bills as gospel. But we should also be reminded that those same people hired us for our expertise.

That is easy to say when you work for a company that does not have clients! That said, it is good advice and worth taking on board.

Being persuasive

My favourite post of the week is “50 Scientifically Proven Ways to Be Persuasive.” Although not strictly to do with web design it provides a lot of advice that can be applied when trying to nudge users in a certain direction.

For example one of the techniques suggests personalising the herd effect. The herd effect is used regularly on websites as a way of nudging users to complete a particular call to action. For example it is not uncommon to see ‘popular products’ on ecommerce sites or ‘average donation values’ on charity sites. This is because we tend to be led by the crowd. If somebody else did something then we will too.

However, the post suggests taking this step one step further  by personalising the message. It cites an example from a hotel change…

The hotel sign in the bathroom informed the guests that many prior guests chose to be environmentally friendly by recycling their towels. However, when the message mentioned that majority of the guests who stayed in this specific room chose to be more environmentally conscious and reused their towels, towel recycling jumped 33%, even though the message was largely the same.

So instead of refering to popular products you would say “other users who bought this product also bought this”. This is a approach also used regularly by ecommerce sites like Amazon.

This is just one example from a massive list included in this post. It really has a wealth of knowledge that is applicable to almost all aspects of web design from information architecture to copywriting.

Continued confusion over HTML 5 and XHTML 2

The last few weeks have been full of discussion about HTML 5 and the demise of XHML 2. There seems to be a lot of division and confusion over what designers and developers should be doing. Should we be abandoning XHTML 1.0. and moving to HTML 4? Should we try and adopt HTML 5 even though it is in draft? Its all very confusing and I have to admit I’ve felt unsure myself.

Fortunately there are some very clever chappies giving out excellent advice. Jeremy Keith has written an excellent post on the subject, as has Bruce Lawson. Drew McLellan has also contributed some interesting points to the discussion.

The problem is that it is all pretty turgid stuff and a bit of pain to wade through. The good news is that you don’t have to. Brad Colbow has saved us from this pain by turning the whole discussion into a very easy to follow (and bueatifully designed) comic strip.

Extract from the comic strip

SO, if you want to know whether you should be closing your tags and whether you can start supporting HTML 5 now, then pop over to smashing magazine and take a look.

I won’t ruin the end, but I will say you won’t need to change the way you code.

Back to top

Interview: Brett Welch on the business of web desgin

Paul Boag: So joining me on the show is Brett Welch. Good to have you on the show.

Brett Welch: It`s good to be here.

Paul: Thank you for agreeing to do this on very short notice. Because I didn`t notice your talk. We`re still at Future of Web Design. I`m still interviewing people here. You’re going to get bored of me saying that cause I’m doing loads of them. I didn’t notice your talk on the line up so I almost missed you entirely and I didn’t hear you either. So I haven’t heard what you said. But I’ve had lots of people come up to me saying you are interviewing Brett right? He’s really good. So you obviously went down very well. Which is a good thing.

Brett: That’s a good thing yeah.

Paul: Because I missed it what did you talk about?

Brett: Okay. I talked about how designers can go beyond pushing pixels and start to create more effective website for their clients. So I talked about the business end of web design. Which you know a lot of the time gets ignored at conferences like this.

Paul: Sure does.

Brett: And I think it’s really important. Cause that’s where the money flows into their pockets. So when it comes to actually getting the client on board and that process. That’s a really important part that I thought needed talking about. I talked about how designers can do that and I used and acronym called BUSTA and I put a bit picture of Busta Rhymes up there because if you’re into rap and hip hop you’ll know the guy. Not that he’s had any hits recently. As far as I know. BUSTA stands for talk Business. Understand why they want to go online. Talk stragety. Talk business targets and set an Action plan.

Paul: Okay.

Brett: So there’s the B-U-S-T-A. Or in one sentence you can say. Businesses Understand Strategy Tactics and Action. So all together it sorta works as sort of a nice little coat hanger for your thinking. And the idea really is to start off by talking about a clients business. What do you do? How long have you been doing it? How do you sell what you sell? Sort of getting into the business owner’s mind a bit. I think that’s something that you need to do to set the tone of what you are going to talk about. It’s not about a pretty website. It’s about having something that actually is effective for the business owner. The next thing is really understanding what they are trying to achieve. That’s important because you may need to dial up their expectations or dial down their expectations.

Paul: Okay.

Brett: Sometimes people if they’ve read a few blogs. They’re thinking that they’re an expert. They’re thinking that they can take it to the next level really easily. Sometimes you need to slow that down a bit and say hold on. You’re not going to be Amazon overnight. You need to take it slow. Other guys are going to be a bit timid. I don’t really know much about bespoke stuff. That’s where you need to hold their hand a bit. Guide them to understanding how exicted they should be. So the next part is strategy. I made a big point about the fact that strategy is not dirty word. It’s really just about connecting the dots between their website and their business. It’s about understanding how you can achieve the goals you want to achieve. Through their website. The main thing about stragety is really helping them understand what they can achieve. and showing them how they can achieve it with concrete targets. That’s what where T comes in. T is your targets. There I think you need to set 3 to 5 concrete targets business targets that actually relate to things like revenues and customer leads. Things like, not traffic. I actually made a point of saying not traffic. Traffice doesn’t mean anything until you understand what your conversions are like. It’s great to say 1000 people came to my website. If you’re not actually getting leads out of that. That are captured in some sort of database or if you’re not making money out of the sales. It’s an empty number. Then finally was action. So you need to set some short, medium and long term goals. A plan. The tools. The what and the how really. How are you going to get there? I think that was a rough overview of what sort of B-U-S-T-A is all about.

Paul: Okay. So what are the benefits of using this kind of approach. As a freelancer say. Why do I need to worry about this kind of stuff?

Brett: I think that even the process, if you look at it from the other point of view, from the business owner’s point of view, it’s still an important one to go through. A lot of people don’t realize that you probably need a marketing plan for your website. Because how else are you going to get people to view it? It’s just like opening a bit store. You need to put in the same amount of effort and ongoing effort to get a result. So I think the why is really more effective websites. If you think about what you’re doing in a business oriented way what’s going to come out the other end is going to be a much more refined and polished representation of what you want to achieve. It’s going to work better for you. I think you get from a freelance point of view you get less arguements from clients. They say I don’t like that blue and you can say well that blue will get you better conversions.

Paul: Right so you’re going back to the stuff you established.

Brett: Exactly. You established already so you can link it back. Obviously you need to have a valid point. You can’t just make things up.

Paul: Well you can try.

Brett: You can try. The real key thing is you can close arguements off by, the silly ones anyway, saying ‘hey look this is better for these reasons.’ Trust me.

Paul: The way we often talk about it is it moves aways from personal opinion of like I don’t like this colour to well this colour comes out of this set of things that we agreed up front.

Brett: Exactly. It’s drawn from this business goal. Then the other ones are you get repeat business because you’ve set that action plan. You’ve got long term and medium term goals that they’re going to link back to you. So once your first sections done and they sort of say ‘This is working well.’ Then they go who’s the next person to talk to? Obviously the same person cause you’ve had them actually plan.

Paul: It’s interesting we went up to a pitch on Tuesday and it was for a small little job, a design job, and we went through this pitch and we outlined what we do. We got to a point in the pitch where we said ‘But if this is as far as you’re going to go don’t hire us.’ If you’re only looking in short term views of this immediate project then we’re not the right people for you. But here’s where we think you should be going over the long term. And I think ultimately that’s really beneficial. It means that your going to get that long term business that you’re talking about.

Brett: Absolutely. People want to know what’s next. I think being able to answer that question ‘What’s next?’ is really a key to making them come back to you when it’s time to implement what’s next.

Paul: How far do you think you can go on that line? We do a lot of work with public sector clients I remembe sitting in one meeting when they wanted to establish a 5 year plan for the website. Which to me seemed unrealistically far ahead. How far do you go with things like that?

Brett: If you can imagine 5 years ahead I think congratulations. I think that’s great. The main thing is not so much how far you can think ahead. I think it’s really the exercise of thinking ahead that is most valuable. Whether it’s a 6 month or 12 month or a 2 year or a 5 year plan. However far you can get that’s great cause you probably have a fantastic imagination. Right now Twitter is big in 5 years who knows what it’s going to be?

Paul: Exactly.

Brett: You can work those into your plan. It’s great to sort of skecth something rough out for as far as you can think ahead. I think it’s the exercise that makes the, it’s the process that makes it more effective and more polished. The outcome just becomes more effective in the wash.

Paul: What you don’t cover in that B-U-S-T-A analogy is, you don’t talk about user testing and user feedback as a tool to convince clients to do a particular thing. I’m guessing that’s part of your process as well.

Brett: Well I think that’s really important. It’s not specifically part of B-U-S-T-A cause usability…

Paul: Yeah it would ruin the whole…

Brett: I think that when you talk about two things Targets well three things Strategy Targets and Action. Those last two, if you’re going to achieve the targets you want to achieve then that’s where you need to, and the action plan, doing that testing and doing that side of things is a really important part of making sure you can achieve those goals. I’m a big fan of usability testing and I read your article on ThinkVitamin. What was it?

Paul: I don’t remember. I write so many of them I get confused.

Brett: It was like cheap usability…

Paul: Oh yes I remember that.

Brett: That was like fantastic and I like tweeted it. It’s the sort of thing that I’ve definitely fit in and the actions and the targets. Because targets are about conversions and actions are about how are you going to get those conversions. I think usability is really a big part in working out those conversions. It’s like supermarkets. They have the aisles and they put the products in the right places because they want the kid to scream about the cholocate at the last minute. It’s all well thought out and on a different level it is usability. It’s arranging things in a way so the client behaves in a way, or the customer behaves the way you want them to behave. So I think it’s an essential part of the process. I didn’t fit in talking about it.

Paul: You can only fit so much in.

Brett: That’s for sure.

Paul: It was very impressive that you did it in only 10 minutes. Obviously there are real benefits to using this approach in regards to convincing clients of stuff as we’ve already said. You know you can say well we’ve gone with this colour because of these reasons etcetra. Do you think there is also a value from a sales point of view in terms of up selling yourself and giving yourself more credibility and value?

Brett: Absolutely. That was final point that I didn’t manage to get to about why you’d follow a process like this. It’s simply higher profits. What I’m saying is nothing particularly new or ground breaking. It’s really just a simple process that helps you get your head around these things. So that you’re able to more effectively how valuable what you do is and basically end up with a more effective result which sort of is a feedback. If you do something, if you sound like you do something well you do something well. Then it sort of feeds back and they’ll tell their friends and it’s sort of a marketing for yourself. So I think that having that process really is just about being able to up sell and justify. The problem that we’ve got right now and I talked about this briefly in the talk as well, is that design is becoming a comodity. People view design as a comodity. That’s a real shame. It is about up selling. It’s about selling yourself, the value you have and effectively communicating what you do. In a way that puts you in the right light so that people are willing to pay the money for it.

Marcus: It also makes you seem like more of the expert.

Brett: That’s exactly it.

Marcus: We actually tell people who say we’re not doing this obviously we feel this is the right thing for your business to take this kind of consultative approach but it benefits us as well. We tell people upfront it’s a benefit to us as well. And they’re like oh okay I see this is helping everybody.

Brett: Yeah that’s right. I think there is two things, one of the key questions we have right now that every freelancer has to ask themselves is are you worth it? Are you worth your cost? I think the two things that are worth it are strategy. Being strategic and being an expert because experts know things that you don’t. If you can get both of those things into your pitch then whatever you do you’ve already put yourself on a different platter. I think that’s where you really, and we tell this to our designers, we have a large community of resellers for GoodBarry and we tell them all the time, we have training sessions, we always talk about making sure you really lay out what they want to do, how they want to do it, and link it back to their business so that they can really put themselves at that expert level and justify the price.

Paul: I think there is also an issue here of the fact that clients like to be reassured. That when you’re buying from somebody you want to be reassured that this person knows what they are doing.

Brett: It’s about trust.

Paul: Having a methodology and an approach that you work through and has all of the different things that you just outlined. I think gives you, it gives clients that reassuring feeling that these guys know what they are doing. They’ve got an approach and they always use this approach and are comfortable with that.

Brett: I think that it’s not just about the followig the process by wrote necissarily. It’s about, or each design or freelance person or agency has their own specialties. I think at a broad level you can follow it. But there are some parts where you may dig deeaper because that’s your real expertise area. These processes are meant to be used and bent. Adapted to whatever your situation is.

Paul: So where do you think the time is to start talking about these processes? Is it once the client as signed on the dotted line? You take them through or do you encourage people to be talking about this even at the pitch stage.

Brett: I think at the pitch stage. When you’re pitching you need to demonstrate, not necissarily tell them the name of your process what your following, the methodology. But start to go through the process and say look I want to talk about your business so lets do that. Then I want to understand why your going online. Then I want to talk with you about strategies we can use, and targets that work for you. Then we’re going to talk about how we’re going to achieve this. Just by setting out that roadmap I think you’re already putting yourself miles ahead of everybody else who’s gone right to what sort of colours do you like? I think right in the pitch stage. You don’t want to go into too much detail. I think you have to strike a balance between showing them that you know this stuff really well and that you can really help them achieve these things but also leaving enough behind the fence so that there is something they’re actually going to pay for. That’s the trick is that balance. I would always fall more on the side of making friends with the client and sort of making them understand the process and how great they can be. How effective they can be. Rather than holding too much back.

Paul: I think the other benefit talking about this, I don’t know what your attitude is towards this but, it’s actually quite a good arguement agains speculative design work as well. If you’re in a position where your talking to a client and they’re asking for speculative design you can almost say well in a way this isn’t the time to do it because I haven’t understood your business. We haven’t set targets. We haven’t got a strategy here. So you can take them through the logic of why it’s too early for me to start putting designs in front of you. Is that something you’d agree with?

Brett: Totally. I’m not sure what our official company stance would be. I don’t think we’ve really talked about it. On principle I definitely agree. In our reseller training we teach stuff like that. I would have to say that I, yeah I use 99designs as an example.

Paul: Oh that’s where Ryan’s comment. I heard Ryan’s comment right at the end.

Brett: I said designers if you want to see we broke it down we had millions of designs and millions of dollars put in there and you crunch the numbers and it works out that every design that is gone and done is worth $2.80. That’s lower than minimum wage. You can go work at McDonald’s and do better than that. I think that, yeah I’m not a fan personally of speculative design. I would generally say and what we teach our resellers as part of our training is saying don’t go with that. We want to go in and understand the business. Make sure that you get your head around what they want to do because your work needs to reflect that.

Paul: I realize I haven’t asked you about GoodBarry at all. What do you guys do? I haven’t come across you before.

Brett: We have a platform for running online businesses. When you’re going online these days business owners want to be able to run their website. Email marketing is more and more important. Selling products and hooking into Paypal and things like that is harder than it needs to be. Behind all that, having a CRM database that you can track your customers and save them in a central place when they sumbit a webform or interact with your site however they interact. We’ve got a platform that does all of that.

Paul: Wow!

Brett: Our system does everything that’s in sort of that realm. It’s great for web designers because they’re able to actually create any design and put it on the system. Use all of that functionality without doing any programming. So that’s sort of what we sell. We have a reseller program. That’s why we’re here. We get designers on board to become resellers of our product. Basically they use the product they get comissions. They get a whole bunch of training from us about how to make more money and how to, pratical training. How to be a reseller. We not only take you one as a resller we want you to be able to add value to your clients. And give you some ideas about how you can do that.

Paul: Interesting business model. Well thank you so much for coming on the show. That was really useful.

Brett: That was really fun.

Paul: It’s nice to hear some other people saying the things we rant on about week in and week out.

Marcus: That’s what we rant on about all the time.

Brett: Yeah I saw your talk at FOWD in New York.

Paul: Educating Clients to Say Yes.

Brett: It really struck a chord. It’s like this is what I am talking about. I think we’re definitly on the same page.

Paul: Excellent.

Thanks goes to Curtis McHale for transcribing this interview.

Back to top

Listeners feedback: Creating a buzz

Paul: So we’re going to do something a little bit different for the listener feedback section today and it’s come about because I was chatting with Ryan Taylor via IM and he asked a particular question and I nearly turned round to him and said “Ah, you can pay for one of my consultancy clinics for an answer to that question” but then I thought that might be a bit tight of me of me, so instead I thought, lets talk about that on the show because it’s a really good issue to discuss and its a different way of doing the listener feedback and I think we’ll probably do it with some other people in the future as well. So I have Ryan on the show, hello Ryan.

Ryan: Hello Paul.

Paul: Oh I’m so honoured to meet you, your the guy that does that podcast aren’t you?

Ryan: I am, I’m the one who makes sure it doesn’t sink like a lead weight.

Paul: It’s so exciting, I feel quite in owe of this amazing super start that I have on the show.

Ryan: *laughs*

Paul: Can I have your autograph?

Ryan: Of course, you’ll have to come up here though, I’m not coming down there.

Paul: That’s a bloody long way to go isn’t it? Can’t be bothered with that.

Ryan: Aye, you have us come down there often enough.

Paul: Yes this is true.

Ryan: *laughs*

Paul: But you live up north, it’s dangerous there.

Ryan: It’s not.

Paul: There’s wild animals and thugs and things.

Ryan: It’s all rumour and hearsay.

Paul: I see it on the news all the time.

Ryan: If you weren’t such southern softies you’d be alright.

Paul: And also isn’t there loads of pollution from the factories chucking out toxic gases and stuff.

Ryan: Yeah well you see though, if the ice caps melt and we flood, your going to go first because we’re higher up than you.

Paul: That is true. Yeah but whenever I think about the north I always have this image of a post apocalyptic barren waste land anyway so it’s all swings and roundabouts.

Ryan: That’s Scotland, you’re going too far north.

Paul: *laughs*

Ryan: *laughs*

Paul: Anyway, it’s really good to have you on the show. I actually listened to last weeks show which was sold waffle but very entertaining none the less.

Ryan: Well we try our best.

Paul: *laughs* It was good, I really enjoyed it. I particularly enjoyed the horrendous swearing after the outro music.

Ryan: Oh, Anna’s just so good at all the editing she does, it was constant throughout, I really feel sorry for her.

Paul: She worked hard on that one.

Ryan: I had to ring her up an apologies personally for that one.

Paul: *laughs*

Ryan: *laughs*

Paul: Yen, we were chatting on IM and you asked a question do you want to share what you asked? Or what the issue was?

Ryan: well, erm, as you know I’ve been recording my own series of video interviews called please start from the beginning and you were the first person I interviews.

Paul: ah, it was very boring. Have you started editing them down yet? Or have other people been more concise?

Ryan: they are getting long

Paul: oh shit really.

Ryan: I think Dan Rubin holds the record at 50 minutes

Paul: flip me!

Ryan: well has also been the most interesting interview, has also received the most hits and the most traffic.

Paul: really?

Ryan: yep, everybody likes to hear Mr. Rubin waffle

Paul: I Marcus should be pretty good when you get to do him because of his whole pop-star career.

Ryan: he keeps putting me off you know…everybody I can get hold of his the hardest one to nail down. I’ve been asking him since the weekend in June and I’ve done 10 interviews now and I just can’t nail him down.

Paul: So the basic principal of the show is that you ask people about their past and ask them how they got where they got.

Ryan: Yeh, its nothing technical it’s something a little different in that I want to know what people do now, what their job title is is the first question I ask, Because I think it’s interesting to hear about what peoples different job titles are because there are so many different bearings of the same thing in the industry. So I ask that first and discuss what they do now, and then ask them to go back to the beginning as per the title of the series and take me through their career path. All the experiences they had all the lucky breaks they had, achievements and so far it’s working out really well.

Paul: Cool

Ryan: Yeh, people seem to like talking about themselves.

Paul: yeh, it’s funny that. So as we were chatting, do you want to say what your question was, what was it you were getting at, what was it you wanted from me?

Ryan: the question was how can I kind of advertise the series a bit better, how can I get more people watching it. The uptake so far has been really good, I’ve had some really good feedback and people are kind of linking to it and spreading the word a little on twitter. But for a lonely guy like me with less than 400 followers it’s hard when I tweet and you’ve only got potentially 400 people that will see it. You know the number of people coming to the site is good it’s better than I’ve ever had, but I’d like more people seeing the videos and commenting and just spreading the word. Someone like yourself with 9000 followers it’s very easy for you to spread the word about thing and I was wondering how you built your way up with Boagworld? If I do something similar, starting from the beginning.

Paul: yeh, I think this is a problem most people have they’ve got some particular website or application or service that they are offering and wanting to build up a bit of a buzz. I’m not that high up the food chain if you compare me with Mr Carson or some of the guys over in America who seem to find it very easy to create buzz and excitement about products. But I guess I’ve picked up a few things that have worked for me. I think the first one is struck me is patience, you know you haven’t been doing it that long have you?

Ryan: Well no, not too long. So far we’ve released the 8th video and it’s been steady. The kind of traffic interest has been steady level, it’s not like a huge, it not going up every week. You know we release Monday and obviously get a surge of traffic on a Monday as everyone comes to visit. That tails of towards the end of the week and then the next Monday we get another surge of traffic and I suppose there is going to be more traffic with more interest of people who are more in the public eye. Like Ryan Carson for example. There will be a spike in traffic I would have thought. But everybody just seems to like everybody which is quite interesting. So it seems to be the same every Monday, there seems to be the same amount of traffic coming to watch that video. Despite whom the person is.

Paul: well that to some degree might be down to be how much the person interview is actually pimping what you have done. You’ve got a good model in the sense you’ve got a situation where your interview well known individuals which works really well as a technique because if they do mention it and push it themselves then it’s going to drive traffic to your site and hopefully get people hooked on the other ones. Erm, but ye hi mean that’s only kind of part of the equation actually. To be honest it was a long time before I actually saw much traffic on Boagworld at all. I mean I reckon it was over a year before I got much over the 400 / 600 subscriber numbers. So it was a long long time before anything really happened, you just really need to keep plugging away and releasing regularly and often. You’re on ITunes now aren’t you?

Ryan: yes, I finally got the series on ITunes and the uptake of that has been pretty good as well, you know people jumped on that straight away and that’s slowly increasing which is nice. Yeh searchable on iTunes and please start from the beginning.

Paul: this is sounding like a massive big plug for free start from the beginning; on the other hand it is also useful stuff for other people because other people are on the same kind of position. We’ve given one tip which is produce content which has got expert whom has a big following, because they are going to talk about it which is a good thing. I mean the other thing that I think a big part of it is, is your own reputation aswel. That (erm) it’s easier for me, if I launch something new … I don’t know let me say I started a new podcast or website it will be relatively easy for me to create some buzz around that because I’ve already got 9000 followers on twitter, because I already know other people and friendly with names that will actually promote it themselves, If I ask them too. So your own reputation matters quite a lot as well and your building up quite a good network of people you know, and don’t be afraid to ask those people to pimp it a little bit. This is where your really going to see the pay off from all the conferences and meeting and chatting with people. Because you’ve become a name that people are aware of, so there’s another tip. Take the time to build up your own personal brand and reputation and attend conferences, because people will take more of an interest in you. Take this week clear left have realised font-deck, now because it’s clea

Ryan: left that’s done it they’ve had far more publicity than some other web app that has just been launched, does that kind of make sense?

Ryan: yeh, yeh, absolutely. Erm I suppose it’s a bit like anything, your reputation again takes time doesn’t it. (

Paul: yeh) I have this slight fear of ramming it down some people throats, I want people to come visit the videos and participate without really feeling harassed into doing so. (

Paul: mmmm) So I don’t want to be tweeting all the time about it and things like that. I’ve been looking at some people who retweet and nearly everybody i’ve interviewed tweeted to say there is an interview there. So if and when people see that tweet they tend to click through, it’s for people who maybe miss that tweet. It seems to be that twitter is the main thing that is driving traffic to my site for my series, and I was wondering if there was anything else I could be doing to advertise it and get people to find it naturally?

Paul: That’s the trouble isn’t it with twitter, something will get missed because you’ve just got this stream of stuff. I think there are a few things to say on that before we move on to other things you could do. Erm, I will actually tweet about something multiple times but I will subtly different ways ok. So for example I will initially (say in your case this video) then later in the day I will I maybe quote some of the comments have been made on the video. I will refer back to it a couple of days later, you know i’ve been pleased with the level of traffic or whatever. Just in order to bring it up a few times so that’s one thing that I do. The other thing is pick your times for actually tweeting about it, and that’s where something like using bit.ly like where you can track traffic is really worthwhile. Erm, because that enables you to kind of monitor the different links that your tweeting out, and notice which time of day gets the best level of traffic for you. So for example in my case I know that if I tweet around about between 5 and 8 in the evening UK I will get the most click through on whatever I do. And the reason for that is the people in UK have just finished work and are at home having their T and are checking twitter whilst they are there. They’ve got time to look at stuff, but yet in America that are following me are just waking up and are around now and their traffic is added to it in addition. So thinking about when you twitter is quite important as well.

Ryan: well that’s interesting because i’ve been releasing the episodes around about 11.30 just before lunch so people could watch over lunch if they wanted to.

Paul: yeh but that doesn’t particularly support the American audience and that is a big audience. I mean you’ve been interviewing people in America as well so I think it’s more important for you (

Ryan: mmm). The other thing you might want to do is, the people that speak that you’ve got coming on the show I presume you write to them and email them when their show goes live…or at least you should do (

Ryan: yes I do). Right include in that the embed code, in case they want to put the video on their site, because that then enable them to have some content, it’s easy and quick to put up on their site and will give you more exposure. And it’s on their blog so it’s permanent, rather than twitter which disappear in time, so that maybe a good way of doing it. (How else can I do build buzz) I mean the other part of it is building the community as well. That is at the moment you’ve just got the early days, and you’ve got visitors (

Ryan: yeh) rather than actually a community. For example I now have people that come back to my site whatever I post. So I mean you want to look at building up that community in the comments and the stuff like that. You want to give people the opportunity and making people feel involved in it. So you do that by saying “hey who should I interview?”, or “what questions should I ask them?” erm, encourage people to put comments on the video maybe ask them questions in order to encourage that commenting. That’s always a good thing you can do. And then of course in addition that as well maybe run a competition where you get people to write in and suggest themselves, why you should interview them not just interview web celebs. Interview some ordinary designers as well, people that have been in the industry from the beginning but aren’t necessarily well-known names. So anything to kind of draw the community together, because once people feel like they are involved in you know Boagworld or from the beginning, once they feel like they’ve got an ownership in then they will start to promote it themselves and that’s where word-of-mouth recommendation really comes in because people are really enthusiastic about it.

Ryan: ok that’s a good idea; I have been trying to contact and target people not necessarily big. I know the majority of people i’ve been interviewing are web celebs i’ve been trying to get all different kinds of people and different kinds of profession in the industry. So I’m trying to get a copywriter and a journalist for industry, and all the different people and their takes on the industry and how they ended up getting involved in it. To try and get as much of a diverse catalogue of people as possible. So ye hi like that idea of getting people, because as you say people don’t have to be a web celeb or a big speaker or a speaker or an a-list person to have an interesting story of what they have been doing. So yeh I like that.

Paul: The other aspect to this is looking for influencer’s o those are individuals that have a big network and a lot of influence. Going back to say twitter for example a lot of people go on about you’ve got 9000 follower or 12000 followers or whatever. But actually the number of followers is less important than erm who is following you. And if you can kind of get at and influence (no wrong word) if you can get certain key influencers to mention your product or service or website then they will reach a much bigger audiences o for example you take someone like Jeremy Keith as a good example of this. His number of followers is actually less than mine yet the people that do follow him are in turn big influencers themselves, so he’s as much of a big influencer if that makes sense?

Ryan: yeh, it’s kind of quality over quantity

Paul: yeh, exactly, totally. Erm, what else? (Mumbling) could you do? … I mean the main thing is just a time thing it has to be said, you just have to keep plugging away being regular posting, not giving up on the project because a lot of people do that you know, especially with blogs. They do it for a while and they give up because they aren’t getting the returns they want out of it. And you know maybe try writing for things like smashing magazine or sitepoint or the webdesigners depot and write about career paths that are relevant to that what it is your doing. The guys at smashing magazine are always looking for new articles because they have this beast that needs feeding on a daily basis. I know you’ve tried to write some stuff for .net mag but I have to .net mag isn’t the best place to start because they are monthly publication which means they can be a lot more picky about what they have in. Also they are very reliant on big names, while you don’t care about the name it’s about this particular product. And actually have got less of a reach (fewer subscribers) than something like smashing magazine or webdesigners depot so I would try and go to write for some of them.

Ryan: mmm that’s another interesting idea, the whole idea from this series stemmed from the fog around job titles and you know how people just kind of pick a name for themselves, like yourself web strategist (

Paul: chuckles, yeh) you know it’s so ambiguous all the time and that’s where people starting out in the industry. That’s what it started off as; people don’t know what they want to be because there is no kind of defined roles.

Paul: that’s what we spoke about on last week’s show.

Ryan: absolutely that’s really where this started and that why I started putting this series together so the series is great that it’s self promotion of myself. But it started off from an interest and it still is, and I’m enjoying doing it because it interests me knowing about other people’s career paths and that’s why I like it. I want to interview interesting people that don’t necessarily have to be hugely popular people. So ye hi like that idea about writing about them, I think that will be the natural progression when i’ve got a few more interviews and bit more raw data to work with. An article about career paths will be something in the pipeline.

Paul: I mean the back log of material really important as well (

Ryan: yeah) , because I mean i’ve got people that start from show one that are still working their way through, and obviously that increased the number of hits and visitors, because people are going back episode after episode. The other thing you’ve got to think about which is the big problem that I had which is the one of getting it transcribed so that its good from a search engine point of view as well as an accessibility point of view. But you know that’s a big old challenge doing that until you’ve got a community like I’m fortunate enough to have that are helping out and supporting it, it’s really difficult to do that.

Ryan: absolutely.

Paul: but anyway I think at that point we ought to wrap it up else this will be the longest show ever recorded, but hopefully there was some useful stuff in there for you and other people. Giving you a little hint at how the consultancy clinics work.
I think I may like to do this again so if you have a web project or you want some advice on something whatever it is then write in to [email protected] and once in a while we’ll pick one and do an interview like this. What do you think good idea Ryan?

Ryan: yeh really good idea I think people will find it useful.

Thanks goes to Andy Kinsey for transcript this listeners question.

Back to top

Case Study: Wiltshire Farm Foods

One of the biggest challenges of running a successful website is balancing the needs of users with those of the business. This is especially true when an existing business model conflicts with user needs.

Although not always the case, one situation where this conflict can arise is with franchise based businesses. For the last few years I have been working with a franchise business called Wiltshire Farm Foods. Although, their business model has been phenomenally successful it caused significant problems for their online customers.

When business models and user needs conflict

When hired to redevelop the Wiltshire Farm Foods website I saw an opportunity for a quick win. Before a user could enter the website, they were required to provide a postcode. This was a massive barrier to entry as users do not like handing over personal information (such as a postcode) without being given a reason. From looking at the website statistics it was obvious many users were abandoning the site because of this requirement. I couldn’t understand why the company had created such a huge usability hurdle.

The Old WFF homepage

The answer was simple – Wiltshire Farm Foods had chosen to give their franchisees control over pricing. Without knowing where the user was located it was impossible to provide a price.

The decision to give franchisee variable pricing was a good one in the pre e-commerce era. However, as the importance of the web grew, it created a significant problem when competing against large supermarket chains with a national distribution network and standardised prices.

Although this was a problem for online users, the model worked for the business as a whole. Wiltshire Farm Foods had an incredibly successful relationship with its franchisees. Some had been with the company since day one. The business was driven by the entrepreneurial spirit of its franchisees and independent pricing was a key component of that success.

Working within constraints

With the variable pricing constraint remaining unmovable it became a case of managing the impact. Our first step was to move the point at which users were asked for a postcode. Instead of requesting it up front, we only asked for it when users asked for a price. This allowed users to view products and clearly linked the request for a postcode with pricing. We also explained why this step was necessary to reassure users this was not a ploy to send them unsolicited mail. However, ultimately we could not get around the extra step required to see prices.

It would have been counter productive to dig our heels in and refuse to compromise the user experience. Instead we took a pragmatic approach and worked within the business constraints. Ultimately this worked in our favour. When Wiltshire Farm Foods saw the increase in sales that came from moving where users entered their postcode, it encouraged them to consider changes in their business model.

Users now get a web price for each product when they arrive on the site for the first time. This price is then ‘adjusted’ once they login or provide a postcode. The user is notified of the change and because the price normally decreases they are generally happy. It is not ideal but it is a dramatic improvement that has greatly increased sales.

Turning a negative into a positive

Although the introduction of web prices is significant, it has not been the biggest change in the site. The real change has happened in my own thinking. In the beginning I saw the franchise model as a hurdle to overcome. However, I have since come to realise the benefit it has to the overall user experience, especially for the site’s target audience.

The Wiltshire Farm Foods audience is elderly with the average purchaser being in their eighties. Not only does this audience have certain accessibility requirements, they also have a number of concerns that need addressing.

One of their biggest concerns is security, both when purchasing online but also when meals are delivered. They are nervous about letting strangers in their house and yet need help unpacking and storing their meals.

The Wiltshire Farm Foods franchise system accommodates this perfectly. Customers always get the same driver and feel they are dealing with a local supplier rather than a national brand. They can even pay with cash on delivery and place new orders directly with the driver.

The problem was that the website did not reflect this local caring service. I was so preoccupied with the negatives of the franchise system, that I failed to identify it as a major selling point.

Franchises can offer personal service

Fortunately as I grew to understand the business model, I was able to grasp what Wiltshire Farm Foods had known since the beginning – that service was what set them apart. Wiltshire Farm Foods did not need to be overly concerned about universal pricing because they offered things no national supermarket could. They offered a friendly, caring service from police checked uniformed drivers. These drivers would even unpack meals and take next orders. However, most importantly they were a local supplier who customers came to know personally.

Once I understood this important selling point it fundamentally altered my approach to the site. The homepage shifted away from merely showing products to promoting the service that was supplied alongside the meals.

WFF homepage

The homepage now focuses on promoting these ‘value added’ services through the use of animation. However, more importantly we made a feature of postcode entry. Entering your postcode no longer just revealed your region specific pricing, it introduced you to your local franchisee. Gone was the faceless national brand and instead you were given the names and phone number of your local supplier. Soon you will even see a photograph of your local franchisee and details about their delivery schedules.

Screenshot of the local outlet information

All of this helps to reassure the user and personalise the experience. Computers are seen by many (especially the elderly) as impersonal and cold. Techniques like this humanise the experience and connect with users.

Lessons learnt

There is a lot that can be learned from the development of the Wiltshire Farm Foods website. We can learn about the importance of understanding your target audience and their motivations. We can learn how a perceived limitation in a business model can be turned into a strength. However, what excites me most is the opportunities provided by the Franchise model to engage with users in a more personal way that is lacking in many websites. With the growth of online social interaction there is the potential for an unprecedented level of customer care.

Bamboo Juice

I was fortunate enough to speak at the first everBamboo Juice conference on the subject of selling web design services. If you were there or are just curious, this page will allow you to access my slides.

My talkwas entitled ‘Winning business in tough times‘ and covered the following…

As the economy slowly collapses like a giant soufflé, where does that leave us as web designers? How do we ensure the work keeps rolling in? Paul shares his experiences of winning new business in the tough times while still nurturing existing clients. He explains how business development is everybody’s concern, not just the sales team.

You can eitherdownload a PDF of my slides(31.1mb – includes speaker notes) or watch here thanks to Slideshare.

160. Education, Education, Education

On this week’s show: We speak to Aarron Walter about teaching web standards. Ryan Carson starts a series on web applications and Paul talks about remote user testing.

Play

Download this show.

Launch our podcast player

Housekeeping

A couple of quick pieces of housekeeping to kick off with…

  • Huge thanks to Ryan Taylor, Paul Stanton and Sarah Parmenter who did a stellar job standing in for myself and Marcus on last week’s show. They were actually far too good and I have already started receiving requests that they become the permanent hosts! Anyway, if you didn’t hear last week’s show then make a point of downloading it.
  • My second piece of housekeeping is a quick plug for Bamboo Juice, a grass roots conference taking place in Cornwall on the 24th April. Myself and Jeremy Keith are just two of the speakers in what will be a packed day. It’s so good to see smaller conferences like this springing up outside of London and so I would encourage as many of you as possible to attend. Best of all its only £99 (£79 for Boagworld listeners!)

News

To be honest, what with SXSW and my week’s holiday I am feeling completely out of touch with the web design world. Fortunately, Mr Stanton is continually updating our twitter feed with juicy stories. I have therefore picked 4 that caught my eye.

How to create a great web design CV

Poor old Smashing Magazine. People do like to tease them (myself included), but they write some damn useful articles. A recent example that caught my eye was ‘How To Create A Great Web Design CV and Resume?‘.

This post is essentially two articles in one. It starts by asking 10 designers to design a hypothetical CV for a fictional individual. Each designer writes a short paragraph about their chosen approach and you get to look at some nice examples.

The second part of the post provides 10 useful tips for creating a great CV. Suggestions include…

  • Make it printable
  • Have a summary
  • Link to online projects
  • Show your personality
  • Keep it simple and understandable

For the complete list of tips read the whole post.

Its a good post, but I am not sure whether producing a ‘designed CV’ is entirely necessary for web designers. If I was hiring a print designer then I would expect a CV to look impressive. However, if I am recruiting a web designer I think I would be just as happy receiving a cleanly designed CV that links to a stunning portfolio website.

There are a lot of differences between designing for the web and print. It is possible to be good at one and not the other. Therefore, a printed CV doesn’t tell me much about a persons capability as a web designer. That said, a well designed CV isn’t going to hurt your cause!

Design: Make it Memorable

One tip that could have gone in the Smashing Magazine article, is to make your CV ‘memorable’ and not just ‘flashy’. This picks up on the theme of a post over at 37 Signals entitled Designers: Make it Memorable.

The post talks about the difference between making something visually appealing and actually memorable. Too many sites are impressive but fail to leave a lasting impression. At one point in the post the author writes…

I started to recall those amazing Flash Sites of the Day. You know those sites that get passed around via IM in your office on a slow day? Simply amazing design and programming. Problem is: I can’t for the life of me remember what those URLs were much less the company/product that was being featured! Isn’t that the point with those sites? That the impact should be profound so that you remember Product or Company X?

This is a lesson that all those involved in the web design process need to learn. Whether we are designers or website owners, we have a tendency towards thing that provide the wow factor. However, often it is the thing that makes us go wow we remember rather than the message being communicated.

Statistics and website owners

Our next article of the week is an ‘all too brief’ post on web stats entitled How to Sell Statistics to Clients.

The post focuses on a common problem – most website owners know they should be tracking website statistics, but don’t really know what they are looking for. In fact the author writes…

In my experience, the loudness or frequency of a person’s request for web statistics is inversely proportional to their understanding of them.

That has often been my experience too.

He goes on to identify three ways that we as web designers can help rectify this problem. These are:

  • Providing cheat sheets that help the client understand terms like ‘hits’ ‘page views’ and ‘unique users’.
  • Add web metrics training into the budget of your projects.
  • Provide summaries and reports for the client on key metrics such as conversion rates or sales.

To be honest this is a much bigger problem than can be covered in a short blog post. Too many website owners think that having Google Analytics will solve their statistics needs. However, having the data is not the same as understanding it. If this information is misread it can lead to bad decisions about the future development of a site.

Specialist vs. Generalist: Who Wins?

The final post this week is of interest to pretty much everybody who listens to this show. It asks which is better – the Specialist or the Generalist.

This is an important questions for both web designers and website owners. As web designers we need to know whether we should be specialising in a specific area of web design. It is important for our careers and our businesses.

As website owners we want to know whether the pain of dealing with multiple specialist suppliers is worth the increased expertise you would receive over a generalist.

It has to be said the article is written mainly from the web designers perspective. However, I think there are lessons to be learnt for all sides.

The post outlines the pros and cons of both approaches, but ultimately comes down on the fence when it says…

There are advantages to being in both groups, but I think the only way to be truly successful is by being a little of both. You can be a specialist, but in order to be able to develop a profitable business, you may need to be able to supplement your specialty services with some add-on services that may not be exactly in line with your focus.

Personally, I think it depends on how you define specialist. The type and level of specialisation can vary massively and the way you position yourself will define your success. For example, you may specialise in a certain discipline (e.g. Ruby on Rails development) or in a specific market (Higher Education).

Ultimately, whether you are a website owner seeking an agency or a web designer forging a career, it is all about balance.

As a web designer, if you specialise too much you will not find work. If you generalise you cannot differentiate yourself.

As a website owner you want a web designer who is enough of an expert to deliver an outstanding solution, but you do not want so many specialists that your project turns into a nightmare.

Back to top

Interview: Aarron Walter on Interact

Paul: Hello, and so joining me today is Aarron Walter. Good to have you on the show, Aarron.

Aarron: Thanks for having me.

Paul: And the reason we have Aarron on the show is because he is going to talk about a new initiative.. is ‘initiative’ the right word, Aarron?

Aarron: Yeah, yeah.

Paul: Let’s go with that. A new initiative from the web standards project, called Interact. Now, let’s kick off, Aarron, by maybe you telling our listeners a little bit about what Interact is.

Aarron: So, whilst Interact is an open curriculum framework, basically we’ve been recognising that the Web Standards Project has been around for a long time and we’ve done a lot of things to try to get standards into industry. And to a certain degree we’ve made some big triumphs in that respect, but there are still a lot of websites out there that aren’t following standards and people that are sort of behind. And we saw the Achilles heal as to why that’s not happening, as really, education. So, you know, our medium’s really young and it hasn’t really found it’s bearings with how we’re going to marry industry and education, so whilst Interact is a curriculum that has a series of courses that teach not only web standards, but best practices.

So there’s of course the stuff that you would expect from WaSP which is the front-end development courses that teach progressive enhancement and semantic markup and that sort of thing. But we have six learning tracks that include foundations; there’s a course in there that’s like an intro to internet concepts and how people can use the internet to teach themselves and use RSS, that sort of thing.

So there’s front end development, there’s a design track, there’s server side development, there’s user science and then there’s also professional practice. So what we’re trying to do is create a collection of courses that are very modular, to try to get these into schools. And we recognise that not every school is just going to take the entire curriculum and integrate that into their program. You know, if you’re a Computer Science program maybe you’ll take a course or two, if you’re a design program you’ll take a course or two, or even just grab the assignments or look at our competencies.

Each course is based on competencies, which are the things a student has to master before they can pass a course. And then the evaluation methods: So each course has assignments, it has exam questions, it has readings that come from Operas own web standards curriculum – we’ve been collaborating with them. It has textbooks, it has pretty much everything that an educator could need to teach a particular topic.

Paul: Okay, so is this something that is then aimed entirely at educators, or if somebody wanted to get into web design and they were trying to learn it in their spare time, could they just go to this and use it in isolation by themselves?

Aarron: To some degree, I guess they could, but Operas web standards curriculum is really learner-centric, so if you’re trying to teach yourself, that’s probably the place to go. But ours is very much focused on educators, because we feel like there’s a lot of great resources out there on the web if someone wants to teach themselves, but there’s not a lot of great stuff for educators to get stuff into their courses.

Paul: So, when you say ‘educators’, I mean what kind of level are we looking at here? Earlier you mentioned schools. Are we talking about school age, or are we talking about higher education? What are we covering here?

Aarron: I’d say our primary target is higher education, colleges, universities, even training programs to some degree. But we are also seeing some of our content in high schools as well and we’d like to see that more. Especially foundations courses like the web design one course or the internet fundamentals course. If students could go into college with a solid foundation, then they can start to focus more on "What can I do with these techniques?" than theory and concept.

Paul: So is this design to be fairly international or is it quite U.S centric in the way that it’s written.

Aarron: We want it to be very international and the people that have worked together on this are from lots of different places. We’ve got some folks in Europe, Canada and of course some folks in the U.S, so it is in an international group that’s coming together and we’re actually working with WaSPs ILG group – that’s the International Liaison Group. And we’re working on, this year one of our big goals is to try to get a lot of our content translated to different languages.

Paul: Okay, so there will be multiple language versions of all of this as well at some point?

Aarron: That’s the direction we’re heading, yes.

Paul: So, I mean, how did this come about in the sense of, you know, well, how did you get involved in it for a start and what was the motivation behind it?

Aarron: So, I’ve been teaching for the past ten years in different schools in the U.S and colleges and universities, but I’ve also been working in the industry as well. And I got on WaSPs mailing list, I just joined the mailing list and started to talk to some folks and then they invited me to join – it was a year ago, I guess it was at the very beginning of 2008 – and so I joined the education task force who created the Interact project. And basically there were ideas about the curriculum and I’d heard lots of people say "Yeah, what we really need is, you know, education’s way behind" and they’re happy to point fingers and "We need a curriculum", but it just never was really transpiring from anyone coming from the industry and so we kind of just decided we need to do this. And I’ve helped create curricula before as a faculty member at the Art Institute of Atlanta and so I had some ideas and we had a really great group of folks that are in the education task force – people that are educators and people that are experts from the industries. So, yeah.. actually South by South West was where this all started, which is pretty amazing, of course there are lots of great people there. So Glenda Sims, who’s one of the heads of WaSP these days introduced me to Chris Mills from Opera who was working on his project and we kind of had some drinks at the Geeks Club bowling event and we just kind of went crazy talking about these ideas. And Steph Troeth then Leslie Jensen-Inman and we all had these ideas, and then we just set a goal for ourselves in 2008 at South by South West and we said "In a years time, we’re gonna be back and we’re gonna have a curriculum." and that’s what we did. This year we launched our curriculum at South By.

Paul: That’s quite an impressive turnaround for the amount of information that’s in there. How did you draw everything together? Where did it all come from?

Aarron: Well, we met every week online and we talked and we established a course template, which really helped us. The stuff that we really needed to put in these foundation courses, we all know what needs to go in there. It’s just a matter of getting around the pedagogy or the educational part of it. So we developed a template for assignments, a template for a course and a template for learning modules which are basically like, you know, a teacher could teach a concept like let’s say, HTML forms in a weeks time. So we developed those templates and then from there we just assigned courses to different people and we used a wiki and we just met regularly and.. I gotta say, you don’t have to have a huge group to develop a curriculum.You just have to have a few people who really have their heart in it and.. we have some amazing folks, so..

Paul: So, what kind of response are you getting so far from H.E institutions? Are they interested in adopting it? If they are, how are they going to go about that, because, I mean, my impression is that it always takes forever to get a curriculum approved at a university or whatever. So I’m just interested in how that process is going.

Aarron: Yeah, education is.. one of it’s benefits is that it’s slow to move, so once it gets a solid foundation it keeps that solid, but you know, one of it’s drawbacks is that it’s slow to move. And so we’ve got some schools that are really excited about it and generally the folks that.. you know, it’s only been a couple of weeks that this has been live, we’ve got some folks that are really excited about it and those are folks that were kind of headed in the same direction themselves. So we’ve gotten some responses from schools in Europe and some schools in the United States that are interested in pulling some stuff in. And we have a school that’s looking at using a lot of our content right now. So we’re in the early stages of trying to get this out there. I think the easiest part is building the curriculum, because we know what needs to go in there. The hardest part is getting it into schools. So one of our strategies is to get the endorsements of folks in the industry, so we’ve gotten endorsements from Google, from Yahoo, from Adobe, from W3C, from Opera, from Mozilla – they’re all just super excited about what we’re doing and that sort of brand recognition can help us get our foot in the door with schools. And of course going out to conferences, we’ve got folks at the European Accessibility conference right now, talking about it, so we’re just trying to get out there and let people know.

Paul: Excellent. That sounds brilliant. I mean, I know that a lot of people that listen to the Boagworld podcast – there’s a large number of students that we’ve got listening and I often get complaints about this, that what they’re being taught at university bears no resemblance to what they’re hearing on this podcast. And I’m hoping that that’s because the podcast is right and the university is wrong and not the other way around. So if they’re listening to this and they’re getting really excited about it and, you know, they’ve gone to your website and they’re seeing the curriculum – I’ve got it on front of me now and it does look really exciting – how do they make this happen in their institution? What would you encourage them to do?

Aarron: So, this is the interesting thing – that so many of us have complained about a problem, but there aren’t a lot of people that will take that complaint and turn it into action. So if you’re a student or if you’re an educator what we need you to do is, there’s a page that’s called Advocate Standards (http://interact.webstandards.org/advocate/) – you can get to it from the homepage of http://interact.webstandards.org. It kind of just describes what standards are, why they’re relevant to you and we need people to share that information with their teachers, we need people to share just this website with their colleagues and show them the testimonials of the people who believe in this and want students to come out of schools with these skills. So we need people to act in a bottom-up sort of way, you know, grass roots. Take this to your classroom, take this to your teacher, take this department chair and just let him know. That’s the most powerful thing that people can do right now.

Paul: I mean, what I’m quite excited about from looking at this curriculum is that it contains a lot more than "Here’s how you code in X language" or whatever and even has got more in it than just design and user experience stuff. All this stuff about professional practices is very exciting too. Could you perhaps tell us a little bit about that?

Aarron: Yeah, so professional practice, we want people to not only get the concrete skills of "I can code a standard compliant page" or "I can construct a usable website", but we want people to be able to present their about their work and you know, be able to survive in a real career in the web. And so professional practices is going to have a series of courses to do that. We’ve got some pretty exciting ones that are coming up. There’s ‘writing for the web’ – it’s going to be a really cool one, that Alan Hussain from a List Apart is going to be creating. And we have a presentation course that’s coming down the line. So, we’ve got a number of those coming up.

Paul: That’s quite interesting, you just said something that I hadn’t grasped which is that there’s more to come here. That this isn’t the end of the line. It sounds like you’ve got lots more that you’re still developing. Is that right?

Aarron: Yeah. We call it a living curriculum, because you never write a curriculum and then you’re done. Especially in our industry, things change so fast. is what of course we’re going to be working on this year. Our design track is light right now and we want to try and address that ASAP, so we’ve got Dan Rubin and Ethan Marcott, are working together to create a foundation design course, that is specific to what web designers need to understand. And we also have Dan Mall is going to be helping us with a Flash course and Aral Balkan is also going to help us with some flash stuff too. We have a lot of stuff going on this year for new courses, so we hope next year at South By when we see everybody that we’ll have a brand new stack to add to Interact.

Paul: Excellent, so do you kind of envisage, from an institutional point of view that, like we were saying, it takes a long time for a curriculum to get approved and that part of the problem has always been that, by the time it’s approved it’s out of date, when it comes to the web. So is the idea that you’re going to get institutions to buy into the Interact curriculum in its evolving nature so that they always get the most up to date version of it. Is that the kind of plan? They’re not grasping one moment in time from it, if that makes sense?

Aarron: Yeah, exactly and we want to take some of the hard work out of being a teacher. I speak from experience, there’s so many things you have to keep track of and trying to keep pace with a lot of changing technologies and concepts, that’s hard on top of the umpteen other plates you’re spinning. So that’s exactly what’s going to happen, is that our courses, they’re not chiseled in stone, they’re published on the web, they’re in an expression engine and we’ll change those as they need to be changed. But that said, we need to strike a balance, because we can’t be chasing every new technology all the time, we have to evaluate and there has to be foundational concepts that remain steady. Separation of presentation and content, that’s steady foundation concept. But new technologies or techniques, they might change.

Paul: Okay, I mean, the whole area of education and web design is massively exciting and there’s so much going on at the moment in so many different fields. I mean, from your perspective, what else out there is really exciting you at the moment that you’re seeing.

Aarron: There’s so much, I just feel like last year that I just saw so many companies, organisations, individuals that, it seems that everyone just was pissed and they just walked out their house and they were headed in one direction until it was like everyone sort of meets up in one big mob. And so, what Opera’s doing, what Chris Mills has done with the 55 articles that he’s brought together and edited for Opera Web Standards Curriculum, that’s huge. Those are all rolled into WaSP Interact as our recommended reading, so that was fantastic. Yahoos Juku project, if you’ve heard of this it’s quite amazing. Nick Fogler, who’s the running Juku – Yahoo actually has a training program, where they bring students that are not employees, they’re not hiring them. They bring them in and they train them to be front end engineers over the course of a few months. And they’re doing it because they’re trying to solve this problem on their own. So, we’re talking with them about how they’re solving problems and looking to collaborate and discuss what we can learn from them. John Allsopp who runs Web Directions (the conference series), he brought myself and Chris Mills and Steph Troeth together with a number of other experts and we did Ed Directions, which was a day long workshop that taught teachers how to teach these concepts in their classroom. So there’s just so much stuff that’s happening right now and that’s just the tip of the iceberg.

Paul: Exciting stuff. It sounds like it’s a really good time and it’s great to have you on the show. How you manage to fit all of this in alongside earning a living too is quite beyond me, but it’s really good that so many people are volunteering and pitching in. That’s great. Okay, let’s get you back on the show, I guess in a years time and sees what’s changed. But thank you very much for coming in now and I will talk to you again soon. Thanks.

Aarron: Thanks for having me.

Thanks goes to Andrew Marquis for transcribing this interview.

Back to top

Listeners feedback:

We have two emails this week dealing with two totally unrelated subjects.

Remote user testing

Our first email is from Steve. He writes…

Catching up on past podcasts, I listened to the episode on User Testing (#150). A method I’ve used that I haven’t heard tossed around much is remote user testing using a screen sharing program like GoToMeeting.

I used this for usability testing of our Intranet and it has several advantages:

  • No need for people to come to central testing facility, or you to go to them.
  • The user is at their own computer, so more comfortable.
  • Ability to record the entire session (screen and audio) so others can look at it later.
  • Tester can conduct testing while in his underwear only (I didn’t do this, but you could.)

What do you think of this method?

Sounds interesting although it would not be my preferred approach.

It’s easy to become a snob when it comes to usability testing and so let me make it entirely clear – any usability testing is better than none.

If you have no budget for user testing, test on friends and family. If time is tight, test on a colleague sitting nearby.

In the same way, if you are having trouble arranging sessions then use Steve’s approach. Something is always better than nothing.

That said, I do have some concerns with remote testing. These include…

  • It sets a minimum bar of technical competency. A user has to be able to connect to the system in order to participate. I know this would have been beyond the capabilities of some test subjects I have worked with.
  • It is less personal. Face to face usability testing puts users much more at their ease and allows you to build a relationship that facilitates honest feedback.
  • It does not allow you to read non-visual signals. Users will often pull a face or shift their positions when they are frustrated. As a facilitator you need to be able to see these signals and ask what they mean.
  • You are not seeing exactly what the user is seeing. You can only see their screen. You cannot see other distractions such as TV in the background. You cannot see the position of their keyboard and mouse. You have a limited field of view.

My preferred approach is to test in people’s homes. Not only are the users more relaxed, you also get a unique glimpse into their world. You see where they access the web, you learn about their home environment and even gain a better understanding of their character.

However, we do not always live in a perfect world and so would definitely use remote testing if better options were not available.

Finding a job

Our second email is a rather despondent one from Andrew…

I have one question, In the past you’ve talked about hiring new for staff, but as far as I can tell you’ve never discussed how to look for a job. I’m currently looking for a career in the industry, but I can’t get a resume to any company or even talk to someone of said company. Almost all the businesses I’ve approached (or at least tried to) either work from home, are no longer at that address, or no longer in business, and actually are just freelancers. And when I find a job posting online its for someone far more experienced then I am. I’m completely demoralized.

You have my sympathy Andrew and I have to say its a tough time to to break into any new sector including web design.

I am also probably not the best person to answer this question. I have been completely unemployable for some time now due to my ill defined skillset and opinionated character :)

So, I am going to try something different with this question. If you have some advice for Andrew, post a comment below. That way we can get the Boagworld community helping each other.

In the meantime here are a few random ideas from me…

  • Give up on the cold calling technique. Randomly contacting agencies is largely a waste of time. You have to get amazingly lucky to contact an agency who happens to be currently recruiting.
  • Try for an internship. Admittedly you will not get paid, but it is a foot in the door. You get a chance to improve your skills and also get to know the people in the industry within your area.
  • Be willing to move. There are jobs out there but they are often further a field.
  • Put yourself in a neat little box. Potential employers need to know what you do. Are you a designer, a coder or a server side developer? Companies don’t know what to do with people who know a bit about everything.
  • Start networking. The best place to find job opportunities is by attending conferences and meetups. Even if you cannot afford the conference itself, turn up at the parties and stand in the halls. Just get yourself out there.
  • Register with recruitment agencies. As an employer I hate recruitment agencies because they cost me money. However, we do still sometimes use them and it doesn’t cost you anything to be listed with them.
  • Ensure your website is perfect. The first thing I do when I look at a potential employee is check out their website. Their site has to be outstanding. It needs to look amazing, be well coded and rich with great content that demonstrates a passion for the web.

Hopefully that helps Andrew and keep an eye on the comments for more advice.

Back to top

Series: Building A Better Web Application by Ryan Carson

Ryan Carson: Hi I am founder of Carsonified a small web company in Bath, England. I am an American as you can probably tell, as for living in England I have been here about nine years. So a little bit of history about us real quick so you know who I am. I have a computer science degree and I have been involved in building four web apps and we are building a fifth truvay.com which will be released later in 2009, and we have sold two of our webapps dropsend.com and heyamigo.net. So the stuff that I am going to share with you today are lessons I have learnt the hard way basically as we have built web apps.

So the first thing I want to talk about is the Admin area that you will build for your web app. What a lot of people don’t know is that the Admin area is really the key to good customer service. If you haven’t enabled really easy customer service then it makes it hard to actually please your customers when they have problems so the first one to make sure you build into your admin for your web app are one click refunds so if someone calls and complains and says hey I am having trouble this month I am really frustrated please help you want to be able to just go into the admin do a search for their email address, their name or their company or anything and bam one click and refund their last invoice and what this does is it gives you, it gives you the ability to just make them happy right away. With a lot of web apps these days on recurring billing you will probably be charging people 5,10,15, $20 a month so losing that amount of revenue in return for really making a customer happy is super important. So make that easy for yourself to refund that money.

The second thing I would make it easy to do is have one click password reset that automatically sends out email with the new password, so with Dropsend it was really hard to reset people’s passwords and that was the number one request people had problems with, they couldn’t remember their password. So if I was to do it again what I would do is I would actually build the admin so I could forward an email from somebody presuming they had sent it from the email address of the account, forward it into Dropsend or the admin and it would automatically know that what it needed to do is reset the password for that email and then it sends out a new one so literally you do not even have to visit the admin area to reset someone’s password you just forward an email that would be amazing, so that’s the way I would do it next time.

The next thing I would do is also doing a one-click resend invoice. So a lot of people they don’t understand they can go into their "My Account" area of a web app to see their past invoices and what they will do is they will just email you and say hey you know I need last month’s invoice. If it is hard for you to find that or send that it is going to make you less likely to help that person so I would do a search on the email address show a list of invoices bam one click and it emails them a pdf version of the invoice. That’s another, that leads me onto another area that I would like to talk about that is invoicing. If you are doing recurring billing sort of every month billing your customers make sure that you are not re-inventing the wheel I would recommend a web app called Spreedly.com and what it is basically it is a web service for recurring billing they have done all the hard work, written all the code, the code for the Dropsend recurring billing was at least I think 1200 lines of PHP and it was good solid code but it was really hard and painful to write. So I would recommend don’t re-invent the wheel use a service like Spreedly because it is making calls to an API if later you decide you don’t want to use a service like Spreedly any more that layer has been abstracted out so you could replace it with your own billing system or another one and it won’t kill you, but I would say hands down don’t rebuild reoccurring billing it is a real pain in the ass.

The last tip I would say about your admin area is make sure that it is easy to give your customers credits. you want to be able to login search for an email address and just give them, hey I want to give them five bucks towards next month, ten bucks just to make them happy and you will have lots of happy customers. So that is my five minutes of tips, thanks Paul for letting me be a part of this. Take care Bye.

Back to top

Sneak Geek

Marcus shares some thoughts about our upcoming trip to SXSW.

I’ve really been looking forward to SXSW this year. I think it has something to do with familiarity with the whole event and also that Paul and I will be doing a little more than sitting in the audience (and bars).

So, it’s my third year. Does that mean I can say ‘southby’ now instead of the interminable south-by-south-west? I hope so.

Does it mean I can call myself a geek? No chance.

Other than making me feel old (which I honestly don’t care about), being at SXSW does give me a sense that I’m out of place.

In some ways I am a geek, but none of them to do with webs and internets. Following my career as a musician, and the advent of ‘proper’ jobs, I have, and let’s make no bones about it, been a salesman. Salesman is such a dirty word. It’s the complete opposite of ‘cool’ and in no way geeky at all.

I’m not suggesting I don’t have a role within the agency I work for, far from it. I like to think of myself as the person that interfaces (oh god, did I say ‘interface’) with people who are even less web-savvy than I am. This undoubtedly works. I have been blessed with enough intelligence to listen to people like Mr Boag and relay his words of wisdom, often making recommendations based on business objectives, in ways that potential (and existing) clients understand.

I’m likely to get shot down here but, usability is largely common sense and I’ve got bags of that too. But can I do design? No. Can I do any coding of any kind? No. Therefore, I am not a geek.

Ah yes, but geeks aren’t cool. Not like musicians are cool.

So, the SXSW music conference has got to be the real place to be right? I never attended it during my pop days, but, way back in early 90s I did go to MIDEM in Cannes which is the European equivalent. This event was frequented mostly by music business tossers (apologies) who were about as far away from ‘cool’ as you can get and I have a sneaking suspicion that the SXSW music conference is similar.

Conclusion: geeks are cool. Rock stars? No, probably not but the vast majority of the geeks I have met are conscientious, innovative people that really want to make some kind of difference. And, for the most part, very entertaining speakers.
Like I said, I’m really looking forward to southby this year.

10 criteria for selecting a CMS

Choosing a content management system can be tricky. Without a clearly defined set of requirements you will be seduced by fancy functionality that you will never use. What then should you look for in a CMS?

I have written about content management systems before. I have highlighted the hidden costs of a CMS, explained the differentiators behind the feature list and even provided advice for CMS users. However, I have never asked what features you should be looking for in a content management systems. That is what I want to address here.

Illustration of a sales man selling a CMS the client does not need.

When I left home for University my mother taught me a valuable lesson. If you want to save money, never go grocery shopping when you are hungry and always write a list. If you don’t you will be tempted to buy things you do not need.

The same principle is true when it comes to selecting a content management system. Without a clearly defined set of requirements you will be seduced by fancy functionality that you will never use. Before you know it you will be buying an enterprise level system for tens of thousands of dollars when a free blogging tool would have done.

How then do you establish your list of requirements? Although your circumstances will vary there are ten areas that are particularly important.

1. Core functionality

When most people think of content management, they are thinking of the creation, deletion, editing and organizing of pages. They assume all content management systems do this and so take the functionality for granted. However that is not necessarily the case. There is also no guarantee that it is done in an intuitive fashion.

Not all blogging platforms for example allow the owner to manage and organize pages into a tree hierarchy. Instead the individual ‘posts’ are automatically organized by criteria such as date or category. In some situations this is perfectly adequate. In fact this limitation in functionality keeps the interface simple and easy to understand. However, in other circumstances the absence of this functionality can be frustrating.

Blogger Homepage

Consider carefully the basic functionality you need. Even if you do not require the ability to structure and organize pages now, you may in the future. Be wary of any system that does not allow you to complete these core activities.

Also ask yourself how easy it is to complete these tasks. There are literally thousands of content management systems on the market, the majority of which offer the core functionality. However they vary hugely in usability. Alway look to test a system for usability before making a purchase.

The editor is one core feature worth particular attention.

2. The editor

The majority of content management systems have a WYSIWYG editor. Strangely this editor is often ill considered, despite the fact that it is the most used feature within the system.

The editor is the interface through which content is added and amended. Traditionally, it has also allowed the content provider to apply basic formatting such as the selection of fonts and colour. However more recently there has been a move away from this type of editor to something that reflects the principles of best practice.

The danger of traditional WYSIWYG editors is two fold. First, they give the content provider too much design control. They are able to customize the appearance of a page to such an extent that it could undermine the consistence of design and branding. Second, in order to achieve this level of design control the cms mixes design and content.

The new generation of editors take a different approach. The content provider uses the editor to markup headings, lists, links and other elements without dictating how they should appear.

Wordpress WYSIWYG

Ensure your list of requirements include an editor that uses this approach and does not give content providers control over appearance. At the very least look for content management systems that allow the editor to be replaced with a more appropriate solution.

The editor should also be able to handle external assets including images and downloads. That brings us on to the management of these assets.

3. Managing assets

Managing images and files are badly handled by some cms packages. Issues of accessibility and ease of use can cause frustration with badly designed systems. Images in particular can cause problems. Ensure that the content management system you select forces content provider to add alt attributes to imagery. You may also want a cms that provides basic image editing tools such as crop, resize and rotate. However, finding such a cms can be a challenge.

Also consider how the content management system deals with uploading and attaching PDFs, Word documents and other similar files. How are they then displayed to users? What descriptions can be attached to the files and is the search capable of indexing them.

4. Search

Search is an important aspect of any site. Approximately half of users will start with search when looking for content. However, often the search functionality available in content management systems is inadequate.

Here are a few things to look for when assessing search functionality:

  • Freshness – How often does the search engine index your site? This is especially important if your site changes regularly.
  • Completeness – Does it index the entire content of each page? What about attached files such as PDFs, Word documents, Excel and Powerpoint?
  • Speed – Some search engines can take an age to return results. This is especially common on large sites.
  • Scope – Can you limit the scope of search to a particular section of the site or refine search results once returned?
  • Ranking – How does the search engine determine the ranking of results? Can this be customized either by the website owner or by the user?
  • Customization – Can you control how results are returned and customize the design?

The issue of customization is one that goes far beyond search.

5. Customization

I have been unfortunate enough to work with content management systems that are completely inflexible in their presentation.

Illustration demonstrating the inflexibility of some CMS

The presentation of your content should not be dictated by technology. It is simply not necessary now that we have techniques for separating design and content. Unfortunately like web designers, many content management providers have failed to adopt best practice and their systems produce horrendous code. This places unreasonable constraints on design and seriously impacts accessibility.

You need a content management system that allows flexibility in the way content is returned and presented. For example can you return news stories in reverse chronological order? Can you display events on a calendar? Is it possible to extract the latest user comments and display them on the homepage? It is flexibility that makes a cms stand out.

Talking of user comments, it is worth mentioning all forms of user interactions.

6. User interaction

If you intend to gather user feedback, your cms must provide that functionality or allow third party plugins to do so. Equally, if you want a community on your site then you will require functionality such as chat, forums, comments and ratings.

As a minimum you will require the ability to post forms and collect the responses. How easy does the cms make this process? Can you customize the fields or does that require technical expertise? What about the results? Can you specify who they are emailed to? Can they be written to a database or outputted as an excel document? Consider the type of functionality that you will require and look for a cms that supports that.

Also ask what tools exist for communicating with your customers. Can you send email newsletters? Can recipients be organized into groups who are mailed individually? What about news feeds and RSS?

Finally consider how you want users to be managed. Do you need to reset passwords or set permissions? Do you need to be able to export user information into other systems?

But it is not just user permissions that may need managing. You also have to consider permissions for those editing the site.

7. Roles and permissions

As the number of content providers increase, you will want more control over who can edit what. For example, personnel should be able to post job advertisements but not add content to the homepage. This requires a content management system that supports permissions. Although implementation can vary, permissions normally allow you to specify whether users to edit specific pages or even entire sections of the site.

Illustration showing the consequences of not having a permissions system

As the number of contributors grows still further you may require one individual to review the content being posted to ensure accuracy and consistent tone. Alternatively content might be inputed by a junior member of staff who requires the approval of somebody more senior before making that content live.

In both cases this requires a cms that supports multiple roles. This can be as simple as editors and approver, or complex allowing customized roles with different permissions.

Finally, enterprise level content management systems support entire workflows where a page update has to go through a series of checkpoints before being allowed to go live. These complex scenarios require the ability to roll back pages to a pervious version.

8. Versioning

Being able to revert to a previous version of a page allows you to quickly recover if something is posted by accident.

Some content management systems have complex versioning that allow you to rollback to a specific date. However, in most cases this is overkill. The most common use of versioning is simply to return to the last saved state.

Although this sounds like an indispensable feature, in my experience it is rarely used expect in complex workflow situations. That said, although versioning was once a enterprise level tool it is increasingly becoming available in most content management systems. This is also true of multi-site support.

9. Multiple site support

With more content management systems allowing you to run multiple websites from the same installation, I would recommend that this is a must-have feature.

Although you may not currently need to manage more than a single site, that could change. You may decide to launch a new site targeting a different audience.

Alternatively with the growth of the mobile web, you may create a separate site designed for mobile devices. Whatever the reason, having the flexibility to run multiple websites is important.

Movable Type admin system

Another feature that you may not require immediately but could need in the future, is multilingual support.

10. Multilingual support

It is easy to dismiss the need to support multiple languages. Your site may be targeted specifically at the domestic market or you may sell a language specific product. However think twice before dismissing this requirement.

Even if your product is language specific, that could change. It is important that your cms can grow with your business and changing requirements.

Also just because you are targeting the domestic market does not mean you can ignore language. We live in a multicultural society where numerous languages are spoken. Being able to accommodate these differences provides a significant edge on your competition.

That said, do think through the ramifications of this requirement. Just because you have the ability to add multiple languages doesn’t mean you have the content. Too many of my clients have insisted on multilingual support and yet have never used it. They have failed to consider where they are going to get the content translated and how they intend to pay for it.

Conclusions

Features are an important part of the CMS selection process, but they are not everything. It is also important to consider issues like licensing, support, accessibility, security, training and much more.

I leave you with a word of warning – Don’t let your list of requirements become a wish list. Keep your requirements to a minimum, but at the same time keep an eye on the future. Its a fine line to walk. On one hand you don’t want to pay for functionality you never use. On the other, you do not want to be stuck with a content management system that no longer meets your needs.

This has been an extract from the Website Owners Manual - now available as an ebook and for preorder in print.

Three secrets to simplicity

Many website owners damage their sites by continually adding features and content when they should be simplifying. In this post I reveal why that happens and how to simplify your website.

In my post ‘5 options when website budgets get slashed‘ I explained that many organisations waste money adding ever more functionality and content to their sites when they should be simplifying. Unfortunately it is much easier to add content than take it away. But why is that?

The 3 lures of complexity

In ‘10 harsh truths about corporate websites‘ I outlined 3 reasons why website owners shy away from removing content…

  • A fear of missing something – By putting everything online website owners believe they are giving users easy access to everything they need to know. Unfortunately, with so much available, it is hard to find anything.
  • A fear users will not understand – Whether it is a lack of confidence in their site or their audience, many website managers feel the need to provide endless instructions to users. Unfortunately, users never read this copy.
  • A desperate desire to convince – Many website managers are desperate to sell their product or communicate their message. Text becomes bloated with sales copy that actually conveys little valuable information.

However, I think there is more to it than that. First, there is a general laziness. It is easy to leave content online. It takes effort to remove it. Second (and more importantly) there is a desire to please users. If a user asks for a feature or piece of content, we feel obliged to provide it.

3 questions that encourage simplicity

Adding functionality requested by users is not always a good idea. You need to ask 3 questions…

  • How many people are asking for it? – If only a few people request a piece of functionality, there may not be the demand to justify the time and money.
  • Who is asking for it? – If it is not being requested by your primary audience then you should probably not be building it.
  • How will it affect others? – With new functionality comes complexity. Will that functionality confuse some users? Will it distract from your main call to action?

What then do you do if your site has become overly complex? How do you achieve simplicity?

3 steps to achieving simplicity

According to ‘The Laws of Simplicity‘ there are three practical ways you can simplify anything, including your site. These are:

  • Remove elements
  • Hide elements
  • Shrink elements

Let’s look at how these steps work in practice.

1. Remove

Headscape Website

The first step to simplifying your site is removing unnecessary content. This is by far the hardest step for the reasons I have outlined above. However, it is necessary as Steve Krug explains in his book ‘Don’t Make Me Think.’ He identifies two benefits of removing content…

  • It reduces the noise level of your site
  • It makes the useful content more prominent

Removing content really does make a difference. We applied these principles to our own website at headscape.co.uk and saw a significant increase in conversions (those visitors who request a quotation for our web design services) and some amazingly positive feedback on the site itself.

In fact we took the principle so much to heart that we went from a 40+ page site down to a single page! Of course, that kind of radical approach is not for every site. However, even removing some content can make a huge difference.

2. Hide

Unfortunately, it is not always possible to remove as much as you wish. Sometimes you need to keep content to serve secondary audiences. That is where hiding content comes in.

It is important to cater for secondary users, but you do not want their content to distract or confuse your main target audience. Instead of removing their content, you can hide it deeper within your site or within the interface itself.

Menu on the Wiltshire Farm Foods website

An example of this is a recent homepage redesign we completed for Wiltshire Farm Foods. Most of their sales come from 6 categories of meals. However, they also offer a number of other categories. On their old homepage the 6 main categories were lost among the other categories. Users felt overwhelmed by choice and sales were lost.

One option would have been to reduce the number of categories to focus on the 6 big sellers. However, this would upset a sizeable secondary audience. So instead, we hid some of the categories under a show more link. This meant that their secondary users could still be served, without overwhelming the primary audience.

3. Shrink

Finally, there are occasions when content can be neither removed or hidden. This is often because the content is of critical importance to a secondary audience and needs to accessed quickly. In such cases the content can be shrunk.

Take for example University websites. Their primary audience is almost always prospective students. However, they also cater for staff and existing students. These people need quick access to intranet tools such as the institutions address book. The solution is to add a small inconspicuous link on the homepage that takes them quickly to this content. By keeping the link small (shrunk) the site serves their needs without distracting or confusing the primary audience.

A similar approach was used on the Wiltshire Farm Foods new homepage. However in this case the content was actually shrunk.

Because of the elderly demographic it was important that we provided lots of help to new users. We therefore wanted to dedicate a substantial amount of homepage real estate to meet their needs as they arrived. Our solution was this…

WFF get started guide

Unfortunately this became distracting once the users were familiar with the site. It became a usability hurdle. One solution was to remove it. However, this would make it impossible for users to refer back to if they became stuck. The next option was to hide the content elsewhere (for example in the help section). However, previous usability studies of this demographic showed they develop ‘habits’ in the way they navigate. If we moved these links that they relied upon, it could prove confusing.

Our final solution was to shrink the content. So instead of moving or removing it we simply collapsed it…

WFF get started guide, collapsed

This meant the content continued to be accessible but did not become a distraction or take up too much real estate.

Conclusion

Although the ideal scenario is to remove content, it is also possible to simplify in other ways.

This should not be mistaken as an excuse to avoid removing content. However, you could use hiding and shrinking as the first step towards removing. If these techniques do not alienate your users, then it maybe appropriate to remove that content entirely.

Whatever the case, we should all be looking for ways to improve our sites by simplifying rather than adding more and more content.

7 Harsh Truths about running online communities

In ‘10 harsh truths about corporate websites‘ I highlighted some of the problems I perceive in how companies run their websites. However, many organisations are not content to simply run a website, they want to run an online community too.

Don’t get me wrong, I am excited to see organisations embracing the idea of community. I have been involved in running virtuals communities since 1996 and in 2004 I wrote about the business benefits of community. To this day I encourage Headscape’s clients to build relationships with their users.

A well run community can…

  • Drive traffic to your site
  • Generate a passionate, evangelistic users
  • Encourage repeat traffic
  • Help develop your products and services
  • Save you money

This is not a ‘rant’ against community, or even corporations running communities. It is an argument against the way they sometimes choose to do so. I continually see the same mistakes being made by organisations. It is time that they faced the harsh realities of running an online community.

1. Technology does not create community

When clients ask for help to build a community, they almost always talk in terms of technology. “We want to add a forum to our site” or “can you create a profile system”.

In ‘10 harsh truths about corporate websites‘ I write about how a CMS will not solve your content problems. In the same way a forum will not create a community.

Vanilla Website

Community is about people and relationships, not technology. The technology is the easy part. You can have a forum like Vanilla up and running in minutes, but it will take months of hard work to build a vibrant community.

If you implement the technology and just sit back then your community will fail. The technology merely allows you to engage with your community in the same way as a telephone lets you talk to your friends. It is a tool and nothing more.

2. Show some commitment

I have already said that building a community takes time, but it also takes commitment.

Too many website owners start communities only to give up when they do not see fast results. A community can take months to get off the ground and years before it shows real returns.

It also takes ongoing input. To make your community successful it must be nurtured on a daily basis. When a user posts, you need to replying promptly. Until your community is well established it will need monitoring multiple times a day.

You also need to demonstrate commitment to the individuals that make up your community. You need to take on board their input, address their concerns and encourage their contributions. You need to show you care.

3. Learn how to lead

As well as caring for your users, you also need to know how to lead them.

This is not leadership in the ‘managerial’ sense. These people are not obligated to listen to you or do what you say. You need to inspire, excite and encourage them.

Running a community requires you to be more like a politician or preacher than a manager. You need to mobilise people around a common cause and stamp your personality on the community.

Unfortunately there are few course that teach these kinds of skills. However, I would encourage you to look at great leaders like Gandhi, Martin Luther King and even Barak Obama for inspiration. These men can teach you a lot about engaging with people and encourage others to follow your direction.

Photograph of Barak Obama

4. An antisocial community is your fault

As the leader of your community, your personality sets the tone. As a result if the community behaves in ways you do not want, then you only have yourself to blame.

I have seen many bloggers write about the negative comments they get on their posts. In most cases this is due to the tone they themselves strike in their writing. Although there are exceptions I believe that users will respond in the same voice you yourself set. If you are irreverent, then so will your users be. If you are rude, expect rude responses.

A good example of this is the social news website digg.com. Digg has developed a reputation for its ‘harsh and juvenile’ comments. I believe this comes from the leadership of founder Kevin Rose in his associated podcast Diggnation. This irreverent, comically and highly entertaining podcast has set a tone that has been carried across by users into the comments.

Diggnation Homepage

This is not a criticism of diggnation. Digg.com has become very successful because of their passionate community. It is merely an observation that you reap what you sow.

5. You need to swallow your pride

Another aspect to leading a community is the need to learn humility. No matter how well you run your community, you will mess up. When you do, how you respond is of crucial importance.

Because of the ‘distance’ that the web affords, people are often more critical than they would be face to face. Feelings are overstated and there is an inability to read the non-verbal signals we normally rely upon. This can often lead to confrontation and disagreement.

I have seen communities fail because the organisation alienated its community by responding badly to criticism.

If you want to run a successful community you must swallow your pride and never respond defensively to criticism. Instead acknowledge the comments and thank people for their honesty. Ask others what they think and hopefully they will come to your defence. If not, then you must seriously consider whether the criticism is valid. If it is then you need to admit your mistake and correct it.

By admitting you are wrong, it is possible to heal a relationship with your community and actually leave them even more enthusiastic about your brand than before.

flickr blog post - Sometimes we suck

6. Stop trying to control the message

If you work in marketing some of these points may make you feel uncomfortable. It feels messy and you do not have control over your message. Unfortunately that is the reality of community.

Community is not marketing in the traditional sense. It is not a broadcast medium, it is a dialogue with your users. Failing to grasp that will rip the heart from your community and force it underground.

I have seen unsuspecting companies experience a terrible backlash from a community simply fed up with being sold at rather than listened to. Users do not want a sales pitch or a feature list. They want the opportunity to feedback and a chance to help shape the future of the product or service they use.

Another tactic for controlling the message is to moderate. In extreme cases I have seen organisations moderate every single user contribution that appears on their site. However, I have also seen companies quietly remove negative comments made about their products and services. This is enormously counter productive because people feel censored and will go elsewhere to express their feelings.

That is the trouble with community, you simply cannot control it. If you do not allow it to flourish on your site and engage with it there, then it will pop up elsewhere where you have no control over what is written.

Adobe complaints on Get Satisfaction

7. Nobody likes to be alone

The final harsh truth I want to raise is that “users don’t want to be alone”. Too many organisations launch a forum with a plethora of topics and discussion areas only to have it lay dormant and unused. The reason – it appears empty, so what is the point of posting.

Before you can even consider adding community features to your site you need a critical mass of users that want to get involved. A lot of companies add community features not because users are asking for them but because management wants it. Communities like that rarely succeed.

Also there is a tendency to go straight for a forum. However, a forum requires a substantial number of users to work. Contributions can often become buried in some thread or topic and remain unanswered because it is never seen. If your community is small you may be better starting with comments, reviews or a mailing list. User contributions are much more likely to be noticed using these tools.

Finally, make sure you are seeding the discussion through new topics of your own. Asking lots of questions is a great way to stimulate discussion and prevent people from feeling like the only kid at the party.

Conclusions

After reading this you might feel that running a community is too much like hard work. You may decide not bother at all. However, that would be a mistake.

The ultimate harsh truth is that your users will be talking about your website, services and products, whether you want them to or not. The only question is whether you want to engage in that discussion.

10 harsh truths about corporate websites

We all make mistakes running our websites. However the nature of those mistakes varies. As your site and organisation grow, the mistakes begin to change. This post addresses common mistakes in larger organisations.

Most of the clients I work with at Headscape are larger organisations – Universities, large charities, public sector institutions and large companies.

Over the last 7 years I have noticed certain reassuring misconceptions within these organisations. The idea of this post is to dispel these illusions and encourage people to face the harsh reality.

The problem is that if you are reading this post you are probably already aware of these things. However, hopefully this article will be a useful tool for convincing others within your organisation.

Anyway, here are my 10 harsh truths about larger websites.

1. You need a separate web division

In most organisations I work with the website is managed by either the marketing or IT department. However, this inevitably leads to a turf war and the site becoming the victim of internal politics.

In reality running a web strategy is not particularly suited to either group. IT maybe excellent at rolling out complex systems but they are not suited to developing a friendly users experience or establishing an online brand.

Marketing on the other hand is little better. As Jeffrey Zeldman puts it in his article ‘Let there be web divisions‘:

The web is a conversation. Marketing, by contrast, is a monologue… And then there’s all that messy business with semantic markup, CSS, unobtrusive scripting, card-sorting exercises, HTML run-throughs, involving users in accessibility, and the rest of the skills and experience that don’t fall under Marketing’s purview.

Instead the website should be managed by a single unified team. Again Zeldman sums it up when he writes:

Put them in a division that recognizes that your site is not a bastard of your brochures, nor a natural outgrowth of your group calendar. Let there be web divisions.

Screenshot of Zeldman's website

2. Managing your website is a full time job

Not only is the website often split between marketing and IT, it is also normally under resourced. Instead of having a dedicated web team, those responsible for the website are often expected to run it alongside their ‘day job’.

Where a web team is in place they are often over stretched. The vast majority of their time is spent on day to day maintenance rather than longer term strategic thinking.

This situation is further exaggerated because the people hired to ‘maintain’ the website are junior members of staff. They do not have the experience or authority to push the website forward.

It is time for organisations to seriously investing in their websites by hiring full time senior web managers to move their web strategies forward.

3. Periodic redesign is not enough

Because corporate websites are under resourced they are often neglected for long periods of time. They slowly become out of date both in terms of content, design and technology.

Eventually the site becomes such an embarrassment that management step in and demand it is sorted. This inevitably leads to a complete redesign at considerable expense.

As I point out in the website owners manual this a flawed approach. It is a waste of money because when the old site is replaced the investment put into it is lost. It is also tough on cash flow with a large expenditure happening every few years.

A better way is continual investment in your site, so allowing it to evolve over time. Not only is this less wasteful it is also better for the users as is pointed out in Cameron Moll’s post ‘Good Designers Redesign, Great Designers Realign‘.

Screenshot of Cameron Molls Article

4. Your site cannot appeal to everyone

One of the first questions I ask our clients is ‘who is your target audience?’ I am regularly shocked at the length of the reply. Too often it includes a long and detailed list of diverse people.

Inevitably my next question is which of those many demographic groups are most important. Depressingly the answer is that they are all equally important.

The harsh truth is that if you build a site for everybody it will appeal to nobody. It is important to be extremely focused in your audience and cater your design and content around them.

Does this mean you have to ignore your other users? Not at all. Your site should be accessible by all and should not offend or exclude anybody. However, it does need to have a clearly defined audience that the site is primarily aimed at.

5. Your site is not all about you

Where some website managers want their websites to appeal to everybody, others want it to appeal to themselves and their colleagues.

A surprising number of organisations choose to ignore their users entirely and build their websites entirely around an organisational perspective. This typically manifests itself in inappropriate design that caters to the managing directors personal preferences and content full of internal terminology and jargon.

A website should not be about pandering to the preferences of staff but about meeting the needs of users. Too many designs are rejected because the boss doesn’t like green. Equally too much website copy uses acronyms and terms that are only used internally within an organisation.

6. Design by committee brings death

Illustration showing why design by committee fails

The ultimate expression of a larger organisations approach to website management is the committee. A committee is formed to tackle the website because internal politics demand everybody has their say and all considerations are taken into account.

To say that all committees are a bad idea is naive and to suggest that a large corporate website could be developed without consultation is fanciful. However when it comes to design, committees are often the kiss of death.

Design is subjective. The way we respond to a design can be influenced by culture, gender, age, childhood experience or even physical conditions (such as colour blindness). What one person considers great design another could hate. This is why it is so important that design decisions are informed by user testing rather than personal experience. Unfortunately this approach is rarely followed when a committee is involved in design decisions.

Instead, design by committee becomes about compromise. Because different committee members have different opinions about the design, they looks for ways to find common ground. One person hates the blue colour palette while another loves it. This leads to design on the fly when the committee instructs the designer to ‘try a different blue’ in the hopes of finding a middle ground. Unfortunately this can only leads to bland design which neither appeals to, or excites, anybody.

7. You’re not getting value from your web team

Whether they have an in-house web team or use an external agency many organisations fail to get the most from their web designers.

Web designers are much more than pixel pushers. They have a wealth of knowledge about the web and how users interact with it. They also understand design techniques including grid systems, white space, colour theory and much more.

Post from Twitter complaining about being a pixel pusher

It is therefore wasteful to micro manage them by asking for ‘the logo to be made bigger’ or to ‘move that 3 pixels to the left’. By doing so you are reducing their role to that of software operator and wasting the wealth of experience they have.

If you want to get the maximum return from your web team present them with problems not solutions. For example, if you have a site aimed at teenage girls and the designer goes for corporate blue, suggest that the audience might not respond well to the colour. Do not tell them to change it to pink. That way the designer has the freedom to find a solution which might be even better than your choice of pink. You allow them to solve the problem you have presented.

8. A CMS is not a silver bullet

Many of the clients I work with have amazingly unrealistic expectations about content management systems. Those without one think it will solve all of their content woes, while those who do have one moan about it because it hasn’t!

It is certainly true that a content management system can bring a lot of benefits. They…

  • reduce the technical barriers of adding content,
  • all more people to edit and add content,
  • facilitate faster updates,
  • allow greater control.

However, many content management systems are less flexible than their owners wish. They fail to meet the changing demands of the websites they manage.

Website managers also complain that their CMS is hard to use. However, in many cases this is because those using them have not been given adequate training or are not using it regularly enough.

Finally, a content management system may allow for the easy updating of content, but that does not ensure it will be updated or even that the quality of copy will be maintained. Many content managed websites still have out of date content or are filled with poor quality copy. This is because the internal processes have not been put in place to support the content contributors.

If you are looking to a content management system to solve your site maintenance issues you will be disappointed.

9. You have too much content

Part of the problem with content maintenance on larger corporate websites is that there is too much content in the first place. Most of these sites have ‘evolved’ over years with more and more content being added. At no stage has anybody ever reviewed that content and asked what can be taken away.

Many website managers fill their sites with copy nobody will read. This happens because of:

  • A fear of missing something – By putting everything online they believe users will be able to find whatever they want. Unfortunately, with so much information being made available, it is hard to find anything.
  • A fear users will not understand – Whether it is a lack of confidence in their site or in their audience, many website managers feel the need to provide endless instructions to users. Unfortunately, users never read this copy.
  • A desperate desire to convince - Many website managers are desperate to sell their product or communicate their message. Text becomes bloated with sales copy which actually conveys little valuable information.

Steve Krug in his book ‘Don’t make me think’ encourages website managers to ‘Get rid of half the words on each page, then get rid of half of what’s left’. This will reduce the noise level of each page and make useful content more prominent.

10. You are wasting money on social networking

I have been encouraged that increasingly website managers are recognising that a web strategy is about more than running a website. They are using tools like Twitter, Facebook and YouTube to increase their reach and engage with new audiences.

However, although they are using these tools, too often they are doing so ineffectively. Corporate twitter accounts and posting sales demonstrations to YouTube miss the essence of social networking.

Social networking is about people engaging with people. Individuals do not want to build relationships with brands or corporations. They want to talk with other people. Too many organisations are throwing millions into facebook apps and viral videos when could be spending that money on engaging with people in a transparent and open away.

Instead of having a corporate twitter account or indeed even a corporate blog, encourage your employees to start tweeting and blogging themselves. Provide guildelines on acceptable behaviour and the tools they need to start engaging directly with the community that surrounds your products and services. This not only demonstrates a commitment to your community but also a human side to your business.

Screenshot of Microsoft's Channel 9 website

Conclusions

Large organisations do a lot right in the running of their websites. However, they also face some unique challenges that can lead to painful mistakes. Resolving these problems will involve accepting mistakes have been made, overcoming internal politics, and changing the way you control your brand. However, doing so will give you a significant competitive advantage and allow your web strategy to become more effective over the long term.

For more information on how you can make your site more effective read the Website Owners Manual or discuss your site with Paul personally.

There is a followup to this post entitled ‘10 ways to battle site bureaucracy.’ Check it out!

Why speculative design is wrong

Many web design agencies are refusing to do unpaid design work before a contract is signed. This is not because it is damaging to them. It is because they believe it is damaging to their clients. But why?

On the surface asking a web design agency to produce some design concepts before you sign on the dotted line appears to be a good idea. After all, it allows you to assess the quality of their design work and see whether they have understood your brief.

However, if you scratch the surface of this once common practice, you quickly expose the flaws. Here are just five…

1. It costs everybody money

In order to remain in business every company needs to recover their cost of sale. This includes web designers. As speculative work is part of the sales process, they ultimately have to charge you for it. The web designer is forced to roll the cost of that work into the project if they win.

However, it is worse than that. The web designer also has to recover the cost of speculative design done for jobs he did not win. This means that if you choose to work with an agency that produces speculative design, you are paying for their failed sales pitches! Why should you be paying for other people’s design work?

2. It is about selling not delivering

As somebody who used to produce speculative designs for years, I can tell you that doing this type of design work is not about delivering a solution the client actually needs.

Speculative design is about impressing the client and creating the ‘wow factor’. The target audience is the client and not the end user.

Being a good web designer is about encouraging the client to make tough choices. A good designer will challenge your preconceptions and suggest better ways of meeting your business aims. However, they are not going to take that risk in the sales process. They will play safe, showing you what you want to see, rather than telling you what you need to hear.

The danger is that if you then hire this company the speculative design is adopted for your site. Ultimately you end up with a solution that fails to meet your businesses needs.

3. It is wasteful

Even worse than actually using a piece of speculative design is throwing it away. I have worked on many projects where the design work created as part of the sales process is discarded on project commencement.

What was the point of producing a piece of design only to discard it? Because ultimately you (the client) are paying for the design it is absurd that you would then choose not to use it.

Of course the reason you discard it, is because it is not fit for purpose. Not only was the design was created to sell, it is also largely uninformed.

4. It is uninformed

No matter how good the brief you distribute to agencies, they are still not going to have all the facts.

Good design comes from being well informed. The designer needs to understand business objectives, success criteria, brand personality, competition and numerous other factors in order to provide the right solution.

Most of all the design needs to emerge from an understanding of your users. Until the designer can interact and empathise with your users, he can produce nothing more than a superficial solution.

5. It ignores the collaborative nature of design

Finally speculative design ignores the collaborative nature of the design process. Good design is not just about a designer having a moment of inspiration and producing a master piece. Design is not the same thing as art.

Design is a collaborative process between the designer and the client. The designer may have the expertise in design aesthetics and usability, but the client knows their business and target audience.

If the designer works in isolation he cannot hope to produce a rounded design. Without mood boards, sketches and initial concepts there is no dialogue between client and designer. The design will only tell half the story.

Example Mood board

To request speculative design is to deny your own importance in the process.

The alternatives

So where does that leave you? If you should not ask for speculative design, how then can you assess the design skills of agencies?

The answer obviously lies in their portfolios. However, in my opinion it is about more than just looking at ‘pretty pictures’. In order to know whether a design has been successful you need background information.

I recommend that where a portfolio piece is relevant to your sector or project, you request the contact information of the client. This provides you with the opportunity to speak to that client and find out how well the design fulfils their business objectives.

Speaking to the client also gives you the opportunity to find out more about the designers. Did they understand the brief? Did they provide positive suggestions? Did they deal with criticism well? Were they flexible and understanding of broader objectives?

Ultimately there is far more to be learned by talking to existing clients than requesting speculative design.

150. User Manipulation

On this week’s show: Liz Danzico talks about user research. Paul explains how to create an effective call to action and we discover how one button cost $300 million in sales

Download this show.

Launch our podcast player

News and events

The $300 Million Button

Our first news story is an incredibly tale from usability expert Jared Spool, which really shows the power of usability testing.

In the post he writes about a client who had a fairly standard checkout process on his website. The process began with a login form:

The form was simple. The fields were Email Address and Password. The buttons were Login and Register. The link was Forgot Password.

It is the kind of form I have seen on many ecommerce websites. This feature, which had been designed to help repeat customers, created two distinct problems:

  • New users resented the idea of having to register. One user said: "I’m not here to enter into a relationship. I just want to buy something."
  • Repeat users rarely remembered their username or password. They wasted substantial time guessing, before eventually resorted to creating a new account. In fact after examining the database Jared discovered that 45% of all customers had multiple registrations. Some did go as far as clicking on the forgotten password link but of those only 25% went on to place an order.

In the end the site was redesigned, allowing the user to continue without registering. Within a year this created a $300 million increase in sales.

Of course $300 million is a meaningless figure in itself. It is the percentage increase that matters. In this case is was a 45% increase. That is a staggering number and one that really drives home the importance of testing with real users.

Read the ‘$300 million button’

The UK government and graded browser support

A couple of weeks ago I wrote about the importance of graded browser support. In my post I explained how we should not limit our support to the browsers we test and how it is unrealistic to push for identical support across all browsers.

This is an approach which has been adopted by the likes of Yahoo! and the BBC for some time, but which now also extends to public sector website in the UK.

According to The Web Standards Project the rules surrounding browser testing on public sector websites have been changed to better reflect best practice in graded browser support.

Changes include an emphasise on functionality over identical layout across browsers (paragraph 39):

You should check that the content, functionality and display all work as intended. There may be minor differences in the way that the website is displayed. The intent is not that it should be pixel perfect across browsers, but that a user of a particular browser does not notice anything appears wrong.

As well as support for progressive enhancement (paragraphs 17-18):

You should follow a progressive enhancement approach to developing websites to ensure that content is accessible to the widest possible number of browsers.

This is excellent news and certainly provides a great reference for UK designers and website owners looking to convince others of the importance of graded browser support.

BBC Graded Browser Support Table

Read the UK government guidance on browser testing

50 Illustrator tutorials

List of Illustrator tutorials

From development to design now, and a list of 50 tutorials that help you get your head around Adobe Illustrator.

The list is compiled by UK web designer Chris Spooner. He echoes my own experiences when he writes:

Adobe Illustrator can be a little tricky to get your head around, particularly after getting used to the workflow as applications such as Photoshop. The difference between layer use and creating and editing shapes can be especially strange at first hand.

I am a Photoshop man and I have found it very difficult to make the transition to a vector based world, so this list was particularly appealing to me.

Its a great list that you will definitely want to check out, if like me you have never got to grips with Illustrator before.

Read 50 illustrator tutorials every designer should see

A new approach to PNG Support

Finally today I would like to draw your attention to a new technique that has been developed by Drew Diller for using PNG transparency in IE6.

Unlike previous techniques this one allows you to use PNGs as background images instead of just as IMG tags. This opens up a world of possibilities and overcomes one of the most annoying limitations of IE6.

This minor miracle is achieved not by using AlphaImageLoader as has been done in the past, but with VML.

Implementation seems fairly straightforward and involves adding a Javascript library to your page. Because this is for IE6 only you can embed the code within a conditional comment. This means other browsers will not even download it.

Although I have yet to use this approach myself, I have high hopes that this will finally solve the IE6/PNG barrier.

Download DD_belatedPNG now.

Back to top

Interview: Liz Danzico on User Research

Paul: So joining me today for our little interview is Liz Danzico. Liz, why don’t you start off by introducing yourself a little bit. Telling us a bit about yourself and your background.

Liz: Sure. Um, I am a user experience consultant, I am here in New York City, I have been developing web sites and user experiences online for about 12 years now. Um, I do a lot of work with Happy Cog Studios here in New York, with Jeffrey Zeldman and Jason Santa Maria. Um, I’m also chair of the new MFA interactions design program.

Paul: Okay.

Liz: At the School of Visual Arts in New York.

Paul: Excellent. I mean, so, to say that you’re an expert in user experience would be a slight understatement then, Liz.

Liz: Well I wouldn’t go that far.

Paul: You’d be too modest, obviously, to say that. Okay, so we got Liz on the show, I met Liz when I went to Future of Web Design and we got talking. Um, she’s got some fascinating insights into the whole area of user research, and usability generally, so I thought let’s get her on the show and let’s maybe, you know, try and cover things from, from the very basic level, a kind of introduction to this concept of user research. Um, so, perhaps a good place to start, if you’re okay Liz, um, would be, how would you go about defining the area of user research? What would you include, what would you exclude from that?

Liz: Right. So … user research, even today, we’ve been doing user research on the web since, uh, the very beginning, so it’s a very old concept but it’s still fairly controversial. So the basic concept is it tells you what really happens when real people interact with your product or service. So, there are no real rules about what it includes and what it doesn’t [inaudible]. You can basically speculate about what your users want, or you can find that out, um, you know? And uh, and the, uh, the latter is probably a more useful approach for you to take than speculation. But with either one, thinking about your audience is useful no matter what. And so, so there are no real rules, now um, when you disconnect thinking about your audience from your business objectives, and you start getting, you know, very excited about behaviors that they’re doing that are sort of disconnected from the real mission that you’re trying to sort of accomplish, then it becomes, um, a bit murky, and confusing. But thinking about your audience is, just in general, is an extremely useful approach.

Paul: Okay. I mean one of the things that, that, um, I’ve heard said before by, particularly cynical clients I have to say, but I’ve heard it said before, you know, ultimately user research, and all of this kind of stuff feels in some ways like, um, just another way for web designers to suck a bit of extra money out of us, you know that fundamentally how, I know my audience already, is the kind of attitude that many web site owners have, so why do you see it as an important part of the process?

Liz: Well uh, you know, as we’ve been seeing design flaws often translate to lost business opportunities, you know, usability is becoming more important than ever as the number of web sites and products is, you know, increasing more and more every day. So, we design these products and services, and we are at the same time users of them, but there’s no way that we can really tell what are users, um, might want. And the best way to, you know, usability research doesn’t cost a lot of money, so, the best way that you can help your clients kind of understand that you need to do usability research in some way is to let them know that usability research is important and it doesn’t need to, um, suck up a lot of time or money in the, in the process. So there’s a great fantastic book by Steve Krug, called Don’t Make Me Think, which I’m sure you’re probably well aware of.

Paul: Uh huh.

Liz: And in one of the chapters towards the end, he has a chapter called "Usability Research on a Shoestring", or it’s probably better titled, which talks of this approach of going out into the hallway and kind of grabbing people, and just sitting them down, and putting them in front of your product or service, and getting some feedback. So getting some feedback from people, no matter who they are, is better than getting none at all. And so, I think starting there with clients, instead of the, you know, $100,000 user research project that’s going to take you across 8 markets, you know, in the United States, the UK, and Asia, then, is going to be a much better approach than kind of intimidating them with the very extensive projects.

Paul: Mmm, I mean, when it, the kind of one scenario that I’ve come across before, um, is where we’ve come across with clients that say "Well we’ve already done user research, we already know our audience ’cause we’ve got somebody in to do this or that." Is there a difference between user research that’s been done primarily with an offline audience, and those with, you know, when you’re interacting with people online? Is there a difference in the kind of results and information that you’re after, and even the techniques, maybe, that you use?

Liz: So, they are probably, when they say that they’ve done user research, they’re probably talking about focus groups. I would venture to guess that when they talk about that they’re probably talking about either focus groups or surveys of some kind and those are not, well, I wouldn’t say that they are, those are bad things to do, but those are not the kinds of user research techniques that are going to give them feedback about their product’s usability. Those kinds of techniques are going to give them good information about, um, certain kinds of things but they are not going to give them information about whether or not people can use the product or service that they’re looking at. So, you want to find out exactly what kinds of user research they’ve conducted. If they say the words "focus group" then you know you want to move them towards something that is a one on one kind of interview. Focus groups tend to be conducted with groups of people, as the name might suggest, um, and when groups of people get together to talk about, you know, they put forth a question for these people, and when they, you know, groups of people get together to talk about the question they might influence one another in their answers, they’re typically aren’t talking about an interface, they’re typically talking about ideas, so you’re not getting good feedback, like in a one on one kind of scenario. So you want to sort of guide them to a more individual, one on one kind of experience. Surveys, on the other hand, are good, but they don’t get that kind of personal experience with a moderator, sitting with an individual, kind of looking at an interface in a kind of task-based scenario.

Paul: Okay, yeah that makes a lot of sense. I mean, let’s then talk about some of the techniques that can be used to better understand individuals, or how those individuals will interact with your product. What different kind of techniques do you use? I mean, there’s the kind of very basic usability session, but do you do, or are there other things above and beyond that, that you do?

Liz: Right. Well, the sort of big secret is that, there are names and there are certainly techniques, but the big secret is there are really no sort of techniques beyond knowing who your users are, kind of documenting what you’re seeing, and then kind of analyzing/prioritizing the results of what you see. So, you can, I’m gonna tell you a number of techniques that we can go through, but if those basic sort of constructs are there, then you’ve done sort of good user research. Now, that being said, the techniques that you can do are usability testing, usability testing traditionally has taken place in a user lab where a moderator is sitting with an individual looking at a screen, or a product, or a sketch of an interface and going through questions in sort of a task-based way, asking people "Show me how you would search for x" or "Show me how you would check out," or, you know, and seeing, measuring the success or failure of that kind of task. The clients are typically sitting behind a one-way, a one-way glass, or mirror, and observing these kinds of things. People have been not so thrilled about this technique recently, saying that it kind of, um, is not, it doesn’t produce natural reactions from users, but that is one kind of technique. There is, uh, kind of creating personas, and using personas, user personas which are an archetype of your site or product’s users, and getting everyone involved in activities around those personas, whether that be using those personas as your talking through features around, you know, a brainstorming session, and getting people to sort of role-play those personas. That’s another user research method. There are, there’s sort of the ethnography kind of take, where a lot of people have been doing kind of in-home interviews and observations recently. Ethnography, cultural anthropologists and people who have been doing traditional ethnography have been watching closely the design research that we’ve been doing recently, and wondering if we’ve been doing it right and so on, but ethnography, in that sort of observing users in their "natural environment", has been I would say a more successful way recently of watching people use products and services, um, so I would say that those three things, usability testing in a lab, sort of using personas and scenarios, and ethnography or kind of going out into the field and watching users, whether they’re in their homes or their offices, are the three kind of key ways to gather user research with users. The fourth way that I’ll mention, and we can talk about this in a little bit, is not with users directly, but it is certainly user research that’s available more and more now, and that is data on sort of analytics, which you can gather from Google Analytics, Shaun Inman’s Mint, these kinds of things. Watching site data and user behavior through site analytics is another form of user research that gives you, you know, some information, and you can watch these traffic patterns on your site. It doesn’t answer the question "Why?" but it does show you some evidence as to how users are behaving on your site.

Paul: It’s quite interesting that you bring up eth, ethnography, whoa I can’t even speak today, because, that’s of interest to me, because that’s an area that we’re beginning to explore a little bit more, and have kind of discovered the same thing, that there’s a real value of going into you know, somebody’s home, seeing the environment that they access the internet on, you know, do they have kids under their feet? You know, where they access their PC, can they sit comfortably at it? All those kinds of things. Um, I guess it’s also an advantage you don’t have to hire an expensive usability lab and all of the rest of it. But I have to confess, I’m a little bit new at it, so talk me through maybe some of the things, you know, how does it differ from a usability test that you would do in a usability lab, other than that you’re in a different environment?

Liz: Well, uh, it depends. It doesn’t have to differ at all — it depends on the goals of the test. I would say that you could construct a test that’s exactly like one that you’d conduct in a lab, it just happens in someone’s home or office, or in a different environment. But as you said, you get the more realistic interruptions, and that kind of thing, and are they going to be able to complete this task given the natural kind of occurrences of their day. And that, depending on what kind of test you are constructing, that’s either going to inform your results or not. If you are doing task-based testing, so I could maybe talk about the different kind of usability testing that you could do.

Paul: Yeah, that’s good.

Liz: Yeah so there are different ways that you could conduct a usability test. Um, traditionally there is task-based testing, where you set up pre-written questions, before you get to the test, that are based on the goals of the testing. So, if we were testing a photo site, we would test whether or not users could upload photos, could they task photos, you know, those kinds of things. So we would write those kinds of questions up beforehand, and then ask those questions during the test. Um, that’s one kind of test. You could do that in a lab, and you can do that same test in someone’s home. In a lab there would not be the children screaming, and the phone ringing, and that kind of thing, or, if someone say were uploading a photo, you would never be able to tell if sort of, timing out, would be an issue, or if anything with time or space or motion would be an issue. If those kinds of things are a goal of your test, then you might want to think about doing it in real time, in someone’s home environment. Another type of testing is something that, I’ll say it was first coined by Mark Hurst, who is a user experience consultant at Good Experience, I think he coined it, it’s called "Listening Labs". Listening labs are, I’ll call them experimental, but they’ve probably been going on long before I was aware of them, where people are designing usability tests in real time. So in other words, you go into the test with absolutely nothing written down, and you sit down with users, and based on your initial interview with them, you hear who they are, and after understanding a little bit about how they use photos in general, say, then you kind of write the questions on the fly, and then sort of develop a test around who that person is and their behavior, with your product, or product type.

Paul: Which I guess, makes people more engaged with the test, because it’s about what they specifically interested in. Is that the idea?

Liz: Exactly. So it’s a more natural way of doing the test. That’s the idea. That kind of thing you could do either way, and probably is even more rewarding if you’re doing it in someone’s natural environment. And then the third type of test is sort of a web, a web wide kind of test, where you have people just surf the internet, as it were, and uh, and just have them think out loud, and that kind of thing is also, I’ve found, more rewarding and fruitful in someone’s home environment, because they have their bookmarks there, and they have their post-it notes. Whereas you put them in a sort of artificial setting and they don’t have those things around them. So, if you, it kind of just depends on the type of testing that you’re doing. If you’re doing just the first kind I talked about, just task analysis and having people go through that kind of task-based testing, doing it in a traditional usability lab is great, you know, I mean you really do get the answers that you’re looking for, and it just depends on your goals.

Paul: I mean, it’s interesting, going back to Steve Krug’s book that you mentioned, I mean he talks about, I guess his agenda in that book is to get people to do testing who perhaps aren’t previously, and so, you know, he really downplays the demographic of who it is that you test, and that it’s more important that you test than that you get the right people, you know and all of that kind of thing. Um, but when you’re going into somebody’s home, and interacting with them, I’m guessing it’s more important to get the right demographic? Is that right?

Liz: Yeah, I mean one of the, um, I think it’s always important to, it’s always important to get the right demographic. Um, but, well I would say that there is a hierarchy of common mistakes around usability testing that kind of has a trickle down effect. You know, the number one mistake is not conducting any research at all, um, and conducting research on the wrong audience is kind of further down the list. So, you know, yeah if you’re doing research on the wrong audience, it’s not going to affect, whether you do it in a lab or you’re doing it at your desk, or at the water cooler, or at home, it’s going to affect your results and your analysis, you know, no matter where it takes place. So, you know, I think that the drawback is you are going to waste more time going out to that person’s time going out to that person’s time, so it’s going to be a drawback for you, but I don’t think that, it doesn’t matter really where it happens, because if you’re testing on the wrong audience, you’re testing on the wrong audience. Um, you’re probably going to get more information out of that experience if you’re in someone’s home, than if you’re not, so if you’re going to test on the wrong audience, do it in someone’s home, because you’re going to, it’s a richer experience, you’re going to get more information out of it than if you’re just testing in a lab.

Paul: No that makes perfect sense, I kind of see that. No, it’s difficult, isn’t it? Because, uh, obviously finding the right demographic of people, and picking the right people to test on is tricky, you know, it’s a more difficult thing and it can be time consuming. So have you got any advice about that? What really matters here? You know, for example, if you’re designing a web site for an over-60s audience, you know, are you, do you want to concentrate on the age aspect of that? Or the technical literacy aspect of that? You know, is it okay to have somebody younger if they’re not as good with the internet, if your audience is, do you, I’m kind of not wording this very well, but you get the idea — what’s important when you’re trying to match demographics?

Liz: Um, well, it’s very specific to your clients. Developing a, so, whenever you are trying to match demographics, you want to work with your clients to develop what’s called a screener, and a screener is a, I would say, whether you’re trying to develop a pretty rigorous recruiting demographic with a professional recruiter, to say, recruit 300 people for an extensive study, or whether you’re going to go out into the hallway and grab some people, or whether you’re going to recruit from something called Craigslist, which a lot of people are familiar with, um, which a lot of people do, I would say developing a screener which kind of outlines your demographic is a really good idea.

Paul: And what kind of things would that include? Sorry I interrupted you.

Liz: Yeah, what a screener is, it kind of goes through, it’s a questionnaire that outlines a number of questions that you would ask a potential recruit, that says, if this person can answer a particular question we should keep them in or out, so it’s actually a really good exercise to go through that allows you to kind of think through the type of demographic that you would have. So that doesn’t answer your question in any way.

Paul: It’s very interesting, though. Can you give me an example? Sorry, I’m interested in this screener thing, cause I haven’t come across it before. Can you give me an example of the type of questions? I mean obviously they’re going to be specific to the individual client, all the rest of it, but what kind of questions?

Liz: Um, what kind of questions? So, let’s see, would this person, so, let’s see, has this person, I mean typical questions could be around financial demographics, age demographics, you know the sort of typical things. But let me think of some more interesting things. So, is this person a full-time student? Has this person been fired from a job in the last 6 months? Has this person participated in usability research in the last 6 months? Those types of things, so if the person answers yes or no, then they’re not a good candidate. But there are other kinds of things you could put into that screener that would be more specific to the project.

Paul: So could it include something like is this person aware of a certain brand, because you want to associate with that brand?

Liz: Absolutely, so does this person drink Coca-Cola on a regular basis, yes or no? That kind of thing. But I’ve found that the screener, because the clients that you work with are often kind of speaking in those terms about their audience, the screener is a really good way to kind of help them understand how you’re recruiting audiences, and a good tool to kind of work together with them to narrow down who you want to be in the target audience for your testing, or your research in general. So, that said, how do you develop a good kind of set of participants for a research study for, say, a product for people over 60? Um, what’s most important, you know it depends on, and I know I hate to say that it depends, but you’re going to develop a goal for the testing, right? And the goal might be about usability, the goal might be about navigation, it might be about design, it might be about, it’s going to have, you have to first identify the goal, and depending on what that goal is, then you can identify the audience. So, the audience, you know the goal might have nothing to do with age, although the product has to do with age. So you can kind of strip away, you can pull apart the product from the goal of the testing a bit, and sort of just focus on the goal of the test. That’s why developing goals for user research is so critical, um, because often times you can separate those and therefore develop a better set of participants for that user research.

Paul: Mmm, that’s really good. I think what we’ve done here, is, a lot of people that listen to this show probably have a basic understanding of user testing. Maybe they’ve done some basic user testing before, or maybe they’ve even written a persona before, but I think what we’ve done, or what you’ve done, is push people a little bit further to kind of consider it in a little bit more detail what they’re doing in order to kind of refine the results that they’re getting back, and that’s really, really great. I mean, if somebody has just kind of done the very basics, you know, they’ve grabbed some people, they’ve done some user testing, maybe in their own office in front of their own PC, and they’ve got a few people in, um maybe they’ve created a couple of personas, what’s the next step for them? What should they be pushing? Is it through this screener? Is that the number one thing they should be doing? Is the goals more important? Is getting a better demographic more important? What’s the kind of next step for them?

Liz: Mmm, that’s a good question. I think that one of the most, well, doing the research is really key. Analyzing the research and connecting the research to the next iteration of a design is also key. We haven’t talked about that at all.

Paul: No, we haven’t, we ought to.

Liz: It’s often a grey area, um, you know there are lots of reports that are produced, you know, diagrams and things, but there’s a lot of kind of intuition that happens between sort of translating the research and putting that research, feeding that research back into the design. There are hunches, leaps of faith, um, you know kind of between that analysis and design. I mean there are clear cut recommendations that one can make, but then there are a lot of more grey areas. So I would say that, I still think, even though I mentioned we’ve been doing this kind of research for at least, you know, more than a decade online, and you know quite a long time offline, I think we still need to get better at the rigor at which we translate those recommendations and findings. So that’s one place I think we need to focus. Um, in terms of the actual research itself, uh, you know, there’s something, I think there are other sorts of techniques. I’m interested in these kinds of emergent, I would say emergent techniques like the listening labs, um, you know where the kinds of things that we’re looking at today with kind of mobile research, where people are, we need to be looking at how people are using our sites not just in the browser on their desktop but, you know, in the browser on their phone, and how their context is changing constantly and how we need to sort of look at that adaptation. So how do we develop tests that are more emergent and can be a bit more flexible, rIght? So I think there’s something interesting about that listening lab, where we kind of understand the person, and then develop the questions around a person and how they use a product, rather than having a pre-written set of questions. So, something that’s more emergent, I think that’s an area that’s interesting to kind of look at. Then, uh, ethnography, really understanding, goes right along with this sort of, emergent, as you said you’ve been getting more excited about ethnography as well, so, thinking more about kind of fine-tuning our approach to people’s own context, whether that be ethnography, going into their homes, their offices, you know, where people are using our products, whether that be on the street, in the hallway, wherever it is, but really understanding how to find people where they’re using our products and test them or do some research around that, I think that’s really exciting and a really interesting opportunity. Um so that, that’s the next step for us, uh, and I think that the way that people are designing tests and doing some usability testing now, is, you know, is good, I don’t think that there’s a big next step that we can all take together, but I think these are three areas that I think as a discipline that we’re going to see people moving forward together in.

Paul: Excellent. Let’s finish off, then, with a kind of where people should go if, you know, they’ve been excited by this interview, they want to learn a little bit more, um, about user research and user testing. You’ve mentioned Steve Krug’s book. What other resources are out there that people should be looking towards?

Liz: Well, let’s see. You know, I was thinking about, I was thinking about that and there are physical places that people can go, but they’re all in San Francisco in the United States, so that’s not going to help anyone. There is, you know, A List Apart has a User Science topic that often publishes user research related methods-like articles, there’s always BoxesandArrows.com which publishes user research related topics, um, Adaptive Path, which is a user research consultancy, or at least one aspect of what they do, they have published a number of articles but they also do events. A lot of events are in the United States right now, but they may have international events as well. But they do kind of give away a lot of their content. Um, and then last but not least, there’s a new-ish publisher called Rosenfeld Media, and the books that Rosenfeld Media publishes are about methods in user experience and, one recently in web form design, was about the usability of web form design by Luke Wroblewski (called Web Form Design: Filling in the Blanks).

Paul: Yeah, I saw that. That looked very good, I have to say.

Liz: Yeah, so that’s something to keep an eye on as well.

Paul: Excellent. Thank you so much, Liz, that was absolutely superb. And I will be fascinated to get you back on the show in the future to talk more depth about some of these issues. Thank you very much for your time, Liz.

Liz: My pleasure.

Thanks goes to Jason Rhodes for transcribing this interview.

Back to top

Listeners feedback:

Every website should have a call to action, a response you want users to complete. But how do you encourage users to act? How do you create an effective call to action. Read More

Back to top

Snape and Keith, separated at birth?

Video: Introduction to WCAG 2

I recently gave an internal presentation at Headscape about WCAG 2. A number of people expressed an interest in seeing it so I made a point to record it.

At the end the presentation I references a stripped down version of the guidelines found here.

I also refer to a quick reference guide to WCAG 2 that can be found here.

Apologises

Apologises for the poor audio quality of this video. Unfortunately the decision to record the presentation was made at the last minute and so we didn’t have a proper mic setup arranged. You can also tell it is not quite as slick as my normal presentations :)

I would also like to apologise for the lack of transcript of this video. Again, it was not my initial intention to put this video online as this was an internal presentation containing my initial thoughts on WCAG 2. I am still learning a lot about the new guidelines and will publish a more considered article when I have a better understanding of the subject.

Feedback

On that subject, I would be interested to hear your feedback on the thoughts I present. Do you agree with my interpretation of the new guidelines? Have I misunderstood anything? Are there other elements I should have addressed? Your thoughts would be appreciated in the comments.

Update: We now have a transcript!

Thanks go to Anna Debenham who braved the horrendous audio to transcribe the presentation. If you cannot face the video we do at least now have a written version!

Paul: Ok, this has worked out a little bit weird because the idea initially with this presentation was that it was really about bringing us up to speed with WCAG2 now that WCAG2 has been released. But I made the mistake of mentioning it online and several people said “ooh, can you record that?” so now it’s a little bit of both, a little bit of a presentation to you guys and a little bit of a presentation that will go on the web.

Paul: So as you guys probably know, WCAG2 has now been released, and as accessibility is a big part of what we deliver and we talk a lot about accessibility, we need to be up to speed on it and we need to know what we’re doing. Obviously accessibility has become such a part of what we do day in and day out that we don’t necessarily think too much about it, it’s almost an intrinsic part of what we do, but with changes to WCAG2, or with the arrival of WCAG2, there have been differences, changes, things that have altered, so I want to make sure that everybody is up to speed with it. Feel free to butt in with questions, that’s absolutely fine.

Audience: Will the video be able to see the screen?

Paul: The video will be able to see the screen. Ok, so, WCAG2. Basically, WCAG1 came out in 1999 which is a good old time ago, in Internet terms that’s like forever, and there was a real need to make some changes and improve WCAG1. Let me just pop back and just explain.

The Journey to WCAG2

Paul: So, yeah, like I said, WCAG1 came out in 1999, it quickly dated as technology evolved, and some of the guidelines actually became harmful in a way. So you guys know that for example, we don’t always take note of what they say about Access Keys, we don’t always take note of what they say about “make sure you put text in an empty form field” and things like that. And WCAG1 was very much built with HTML in mind, and obviously the web is a lot broader than that and there are a lot more formats about. But unfortunately development of WCAG2 was very slow, and also fraught with controversy. I mean, famously with Joe Clarke who is an accessibility expert wrote on A List Apart “to hell with WCAG2″ because it basically had become a bit of a joke, because it was very generic; they were trying to write a set of guidelines that really made no effort to mention specific technology because they didn’t want it to date like WCAG1, but the result is it became unreadable and nobody could understand it.

WCAG2 Reborn

Paul: But, things did change. Major changes were made to the WCAG2 draft and things did improve dramatically. They really listened to the community, and the language in it now is much clearer. So what I want to do now is talk a little bit through what WCAG2 includes and what it doesn’t, and how we’re then going to go about implementing it and how it affects us.

Principles

Paul: Ok, so let’s look at the structure of WCAG2. Basically WCAG2 has 3 tiers to it that you need to know about. Tier number 1 is the idea of Principles. So this is kind of the most generic of the tiers, you know, it’s really kind of aimed at the kind of things you would tell a board of directors that doesn’t really understand anything technical, that doesn’t really understand accessibility at all. And there are 4 principles which are the foundations of web accessibility and these principles I’ll come onto a little bit later.

Guidelines

Paul: Underneath each of those principles are Guidelines. So, within each principle there are 3 or 4 guidelines or a number of guidelines that is different for each principle. But there are a total of 12 guidelines, and these are goals that you should be working towards in order to make your content more accessible to users.

Success Criteria

Paul: Under each guideline, there are Success Criteria. So now we’ve really hit the nitty-gritty, these are kind of specific, measurable goals that you’ve got to achieve. And this is how you judge whether your site is WCAG2 compliant, if you like. So, this is the really important level if that makes sense, but it’s organised within this hierarchy of guidelines and principles.

Techniques

Paul: Now, actually, there is kind of a 4th tier as well which is techniques. So you’re trying to, maybe as designers, you’re trying to conform to the Success Criteria, well there’s a whole load of different ways and different techniques that you can do that and you could read about those, and you could make up your own techniques if you wanted to, but there are some laid down that can help you get going.

Working with WCAG2

Paul: So those are the 3 levels that WCAG2 is built around. Now let’s dive into those a little bit. I had to think about how much detail I want to go into in this room. Obviously we don’t want to go into every technique that you could possibly apply and we don’t even want to go into necessarily every success criteria. That’s really for you guys to look through afterwards. What we are going to do is look at those guidelines and those principles, and hopefully help you to understand where WCAG2 stands over stuff.

Perceivable

Paul: Ok, so, the first… heh, totally illegible text, isn’t that great. Very accessible!

Audience: (laughter)

Paul: So the number 1 principle is Perceivable, and that’s 1 of your 4 principles that you’ve got here. And perceivable is basically talking about “information and user interface components must be presentable to users in ways that they can perceive”

Audience: (laughter)

Paul: Unlike that! (points to presentation)

Audience: (laughter) Is the rest of the presentation like this?

Paul: Yes.

Audience: (more laughter)

Paul: You actually don’t need to read this anyway which is very useful. So, Perceivable is basically about “can you see it?”, that is it as far as the principle is concerned, and the answer is “no you can’t”. But perceivable then breaks down into a series of guidelines. So, let’s have a look at what these guidelines are. So basically, perceivable is broken down into 4 guidelines. And if we talk through each of those it should give you an idea.

Text Alternatives

Paul: The first one is text alternatives. So this is stuff we already know. “Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.” So this really applies to things like video, audio, forms that you create, and interestingly CAPTCHA is particularly mentioned here. And that is a particular accessibility problem that hasn’t been particularly well solved I don’t think.

Time Based Media

Paul: The next way that Perceivable works itself out is in time-based media. What we’re talking about here is that you need to provide an alternative for anything that is time-based. So here we’re talking about captions for video, sign-language maybe, media alternatives, but it also applies to live and pre-recorded video. So if you’re streaming stuff, then you need to think about this as well as with stuff that’s pre-recorded. Now, it does take into account the difference between “crap, how are we going to make streaming video accessible?”. If you read into the guidelines it does give some good advice there. So that’s not quite as scary as it first sounds.

Adaptable

Paul: Anything that we produce needs to be adaptable. In other words, content can be presented in different ways. For example, a simpler layout maybe for people with cognitive disabilities for example. Really, this boils down to things like using semantic markup, meaningful order in your HTML so that if the CSS is stripped away it still makes sense in the order that it is presented, and not relying on colour and other sensory elements to convey information.

Distinguishable

Paul: And then finally it’s got to be distinguishable. So it’s about making it easier for users to see and hear content including separating foreground from background and that kind of stuff. So we’re talking here about contrast, colour, and control over things like audio and video, that kind of stuff. So that’s where we’re at with perceivable.

Operable

Paul: Let’s move onto the next principle which is Operable. So, Operable is about user interface components and navigation, and making them easy to use so that somebody can use them whatever disability they may have. So this again breaks down into 4 different guidelines, the most obvious of which is Keyboard Access. So everything that we produce has to be accessible via a keyboard. So, for example, the Flash video that we’re currently creating for the Wiltshire Farm Foods home page needs to be keyboard operated, alright? Which I bet it isn’t at the moment! And to be fair, it’s part of production, I’m sure they’d put that in at the end if I hadn’t reminded them. That existed under WCAG1, so there’s nothing different there. So everything needs to be keyboard accessible.

Enough Time

Paul: You also need to provide enough time for people to take in the information that they’re being presented with. So giving the ability to pause, stop and control time based material is really important as well.

Seizures

Paul: You’ve got to take into account seizures, some people can have seizures triggered by animation and that kind of thing, so there are various limits that the guidelines lay down about flashing objects and stuff like that.

Navigable

Paul: And then finally it’s got to be navigable. So this includes things like skipping content, having descriptive page titles, tab order, links that make sense out of context, lot’s of headings, that kind of stuff. Is this all making sense?

Audience: Yes, apart from time-based media, I don’t understand that.

Paul: Time-based media, we’re talking about video and audio. So let’s say you had… one of our podcasts. So, there are certain things we need to ensure. One is that it is operable, in other words, a user can pause the podcast if we get annoying, or they want time to take in the information that we’ve said, but the other thing is that we also need to provide an alternative way of them getting it which is why we provide the show notes that we do and the transcripts and stuff like that.

Audience: Ok, well that kind of fits under Text Alternatives and giving it control so it’s under Operable… I just don’t get where it is under perceivable, as a perceivable thing, it has to be perceivable?

Paul: Yeah, basically.

Audience: Video, audio… all has to be perceivable then?

Paul: Yes. Some of these principles and certainly some of the guidelines do overlap to some degree. But when you draw down to the Success Criteria level, of how you actually apply these things, then there are more specific techniques. I think what they did is create a load of success criteria, and then kind of chunked them together in meaningful groups, but sometimes they’re not so meaningful. But it is a vast improvement on WCAG1 as far as being able to understand it.

Understandable

Paul: Ok, talking of understanding it, our next one is Understandable. So this is the next one of our 4 top-level principles, so everything you produce has to be understandable. So what does that mean? Well that results in 3 guidelines. It has to be Readable, Predictable and has to be able to provide Input Assistance. So how does that work itself out in practice?

Readable

Paul: With Readable, we’re talking about making content readable, text content mainly. So this works out in things like setting the language in your HTML, you know, setting what the language is in the header, avoiding using jargon, finally we’ve got a decent reason to go back to clients and say, you know, “you can’t use that kind of language, nobody understands it!”. Also things like abbreviations need to be explained, and also reading level as well, and that’s something I really want to get through to a lot of our clients because a lot of our clients, especially the public sector clients that we have, have this attitude of “well of course, people that look at our site are of post-graduate degree people, and they have excellent reading level”, but that doesn’t take into account things like people that speak English as a 2nd language, who can be very intelligent but not particularly good at reading, also people with Dyslexia can be incredibly intelligent but not particularly good at reading. So reading level is an important aspect of it.

Predictable

Paul: For it to be understandable it also needs to be predictable. So with this we’re talking about things like consistent navigation, and no uninitiated changes. And this is a particularly important one in our world of AJAX and JavaScript and all this cool stuff that we’re doing where we can often trigger events without asking the user’s permission first. When I say “asking for permission” I mean they haven’t clicked on link or they’ve not initiated it in any way. Users need to initiate these actions… and no pop-up windows without them clicking first to trigger a pop-up and being aware of what’s going to happen. It’s all about making it understandable and making them aware of what’s going on.

Input Assistance

Paul: The last guideline under Understandable is Input Assistance. So this is going into the realms of when we do forms, how do we handle errors, what kind of feedback do we give to the user, what labels – are things clearly marked up as labels, are they descriptive of the fields and the forms and that kind of stuff. We’re also talking about help, what additional help are you provided in terms of tool tip and contextual help and anything else that you care to mention. So that’s Understandable, that’s what that principle is driving at.

Robust

Paul: The final principle is Robust. “Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.” In other words, what we build has to work on everything.

Audience: What about AJAX?

Paul: I think that’s where we get into the realm of progressive enhancement, that it’s fine to use something like AJAX as long as, if the AJAX is taken away, it still operates. Or, you provide an alternative version, the guidelines do actually accept that you can do alternative versions of something. So Gmail is a good example of that, Gmail, it actually doesn’t work if AJAX is turned off but they do provide an HTML only version of it which does the same thing. I’m not a great fan of that because it’s twice as much stuff to maintain, and one version become out of date and all the rest of it. My preferred technique is to build it so it works normally, and then to layer on the JavaScript and AJAX on top of it to provide enhanced functionality, which is what we guys have been doing pretty much all along and we need to continue in doing that.

Compatibility

Paul: So that Robust principle actually only comes down to one guideline which is Compatible, so that’s about maximising compatibility with current… listen to the wording of this… Maximise compatibility with current and future user agents, so we also need to be looking forward as well and predicting the future which is always good. But that’s where it comes back to using solid, good code that is’nt reliant on lots of hacks in order to get it to work, and it goes back to the conversation that we’ve been having recently about browser testing, upgraded browser support and that kind of stuff as well. So Compatibility and Robustness is the last principle. The other thing I should have mentioned with Compatibility is this also includes things like validation, making sure that your code validates, and just generally other markup type stuff.

What, no AAA, AA, A?

Paul: Ok, another thing that might have occurred to you is AAA, AA, A.. Priority 1, 2 and 3. Priority 1, 2 and 3 are still there, there are still those levels of conformance, but I get a real sense from the tome of this document, and this is just my personal opinion, people watching this video who know a lot more about accessibility might jump all over me on this, but my sense is that they were playing down those 3 levels of conformance. To be honest, I think I’m pretty keen on that. I don’t think those levels of conformance have done a lot of good generally speaking, because I think it’s kind of developed a checkbox mentality amongst some of our clients “We must be AA compliant” or “We must be A compliant” and they’re not actually thinking about the needs of the users, they’re just ticking the boxes so they meet some quota that has been established somewhere. One of the things that’s quite interesting, and I’m not sure if it’s a change from WCAG1 or not, I couldn’t find the reference in WCAG1 but again someone will correct me no doubt, but conformance in WCAG2 seems to be on a page-by-page basis. So you’re no longer in a situation where you want to claim conformance so you’re claiming conformance for an entire site, but you’re rather conforming on a page-by-page basis. And this allows you to basically pick-and-mix the level of conformance you want to reach on any particular page which is much, much more sensible because there are some elements where you might be building a particularly complex application that really isn’t going to manage being AAA compliant, whereas the rest of the site is AAA, and this one page isn’t. So it’s giving you the ability to mix and match. In fact, in the guidelines it says “It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content. In other words they’re saying it’s just not possible to be AAA in some situations, so don’t even try.

Start With Basics

Paul: So how does this relate to what we do on a day-to-day basis? Well, I think the language we use with our clients pretty much will remain consistent with how it was with WCAG1 which is that we need to start of by encouraging all our clients to start with the absolute basics. A lot of people are put off of accessibility because of the enormity of it, of all the things they’ve got to do. And even to be single A compliant there is quite a lot to do if you’ve got a site that has never been built to be single A compliant before. So I think our attitude has got to be that you work towards this over time, it is an ongoing process, you don’t need to do it all in one big go and that you need to start with the absolute basics, the quick wins, the stuff… you know, it’s the 80/20 rule, 80% of the problems that people are going to encounter from an accessibility point of view is caused by 20% of the accessibility issues if that makes sense. So we can solve a small number of issues but have a big impact on the site. So we’ll start off with some real basic stuff. Things like putting in “alt” and “title” attributes, providing alternatives to media, things like video and audio, being aware of JavaScript and the problems that JavaScript can create if it’s not implemented correctly, providing resizable text so that the user has the ability to either increase or decrease the text size on sites, to build everything to be standards based because that makes it so much easier in future.

Audience: Aren’t we moving away from resizable text?

Paul: We’re moving away from the resizable interface where the whole thing scales up and down, but there’s no reason why we can’t keep the text itself rescaleable. The layers should be able to push up and down. It has to be said with resizeable text, it is becoming less of an issue. The reason it’s becoming less of an issue is because browsers now have this zoom functionality built into them. But I don’t think we’re quite there yet to be able to drop resizable text entirely is my current feeling… I’ve got mixed feelings about it. But the obvious aim we’re going for here is to be single A compliant.

Build Over Time

Paul: So all of this is about building accessibility over time. Taking the guidelines by themselves is not going to be enough, and taking this checkbox mentality that I talked about earlier is not going to be enough. Once you’ve done these quick fixes, the next step on from that is to start consulting with your community. We need to encourage our clients to start talking to their users and find out what accessibility concerns they have. I also think, which I think we’re quite poor at, that we need to start testing with real users some of the accessibility stuff that we do, and the big problem there is persuading clients to pay for that. It’s really hard to get clients to pay for that kind of testing but I do think that it’s a really useful thing to do, and there are organisations out there that provide people you can get in to do testing, or that you can send sites out and they test with them. So, testing with real disabled users is really worthwhile. I think it’s about identifying major issues and dealing with those first, just pragmatic kind of prioritisation of issues, something you do with usability. With usability you look for the quick wins and the showstoppers and those you deal with first, exactly the same with accessibility. Now, what the major showstoppers are for those navigating the site need to be dealt with. And over time you build towards AA and AAA compliance if you can. But you only do that maybe on some pages. The big concern clients have and the reason they get into this check-box mentality of saying “we’ve got to be double A or we’ve got to conform to the WCAG guidelines” is fear, a fear of litigation. Especially our bigger clients, they’re really worried they’re going to get serious issues. But I think it’s important to stress with clients that litigation doesn’t happen overnight. You don’t suddenly have come through the post a writ saying “you need to come into court about this accessibility issue on your site”. It doesn’t happen like that. What happens in reality is the user complains. And if the user is repeatedly not heard and not listened to, and not responded to and not cared about and rejected, they get angry enough to maybe approach someone like the RNIB who then take it on into litigation for them. That’s the reality of what happens.

Quick Response

Paul: So as a result, you can diffuse that by responding to complaints quickly. So as you’re building up over time with the accessibility policy, if someone does complain, you need to write back to them and you need to deal with that issue straight up. Ok, so that’s how the client should be dealing with all this and there’s loads more I could say on this but I don’t want it to go on forever.

Headscape’s Approach

Paul: Let’s briefly talk about Headscape and our approach and how we should be approaching the subject of accessibility.

Establish Approach With Client

Paul: Well first of all I think everything that we do in our approach should be in conjunction with the client. I don’t think necessarily we talk enough to the client about accessibility. Some clients are just so bamboozled by it that they want us to take control, others want a say in it and what to be reassured that we’re doing something about it. So I think there’s a dialogue that we need to make sure happens. And if a client just wants us to take control of it, that’s great. If they want to be involved in the process, then that’s great to but we need to engage with the client and talk to the client more about it.

Remain Pragmatic

Paul: The second thing and I think this is really important is that we need to remain pragmatic in our approach to accessibility. Everything I’ve been talking about before like building up accessibility gradually, about doing the quick wins first and the show stoppers and that kind of stuff, that’s all pragmatic. I don’t want us on one hand to ignore accessibility, and it needs to be an integral part of everything we do, but on the other hand you can become extremist about it. We could spend hours and hours trying to get something to work in every conceivable user agent in the world and we can worry about every type of disability to the point where it becomes like a paralysis that stops us actually doing anything. So there’s a real balance that we need to strike here. And we need to strike that with our clients and working with our clients.

Have a rationale

Paul: Now I think it’s worth saying that if we decide not to comply with a guideline for whatever reason, we need to have a rationale for that. So we might not conform even to single A compliance in certain situations, although to be honest I can’t think of any off the top of my head, but if we do decide not to conform, we need a damned good reason why not. In other words, we need to have thought about it. And the other thing about accessibility is that we always think about it at the end of the project. It’s too late by then, we’ve built everything. So it really needs to become an intrinsic part of everything that we do.

Responsibilities.

Paul: Let’s talk about the idea of responsibility here and whose responsibility accessibility is within Headscape. Basically I’m going to say, everybody. One of the absolute great things about WCAG2 is because it’s got this 3 tiered approach, it is “accessible” to everybody. It’s understandable by everybody. So therefore it can be everybody’s responsibility to keep an eye on accessibility. And so this is how I think it should split down.

Sales/Client – Principles

Paul: Marcus and Chris and the Client should be worried about principles. The Operable, the Perceivable, those basic top-level principles. And you should be looking at anything that goes out from the company and going “well is that really operable?” So you can take a very top-level approach to it. And I think as you talk to clients as well you take this very top-level approach to it. That’s the level you guys should be working at.

Guidelines – Project Managers

Paul: Project managers, I think you need to be looking and understanding from the guidelines point of view. So you need to go in and read what those guidelines are, and you need to be sure that you understand them. And as you look at any work that goes out from the company, you need to be thinking “does it conform to those guidelines?” You don’t necessarily care about the nitty-gritty of how those are measured, or the nitty-gritty of how they’re achieved, but has that guideline been met? That’s the level you need to be working at.

Success Criteria – Designers and Developers

Paul: Then when it comes to the designers and developers, you need to get right into these guidelines. And you need to understand the success criteria and how to apply the guideline and how to make them work in practice.

Check Everything

Paul: So basically, we need to be checking everything that goes out the company for accessibility. And I have to say I’m making the mistake of saying this on camera, but I think we’ve got a bit lax recently when it comes to accessibility. We reached a point where it was becoming quite intuitive to us, and we were doing it quite naturally, and then as a result of that, we stopped checking because it was the natural process of what we were doing, and then bad habits start to seep in again. So WCAG2 is a great opportunity for us to say “ok, we need to start reviewing everything we’re doing as it goes out again”. So I’d really, really encourage you to check everything.

Needs to be second nature

Paul: basically we need to get to the point where this is second nature to us, so that we’re doing this intuitively again, but not to the point where we’re no longer checking.

Audience: Clients often say “what’s the difference? If I just got for single A compliancy, what won’t my site be reaching?”

Paul: I have to say that I think I would stop talking about double A, triple A and single A compliancy. I don’t think there’s really any value any more in talking about that to the clients.

Audience: I think there is because having the page by page conformance is a really good thing and that we can now argue that yes, we can now make the majority of your site triple A compliant, but for a page full of videos, we can make it single A compliant.

Paul: Ok

Audience: Clients will continue to reference it in briefs. You can’t not talk about it.

Audience: I think it’s actually quite a strong thing.

Audience: is it a page by page compliance, or template by template compliance?

Paul: I think it has to be page by page because the content that goes into the page, into the template, could invalidate it. This is why I think it’s something that should be downplayed. I accept the clients will still talk to us about it, but clients still talk to us about doing speculative design, it doesn’t mean we do it. I think there’s an education thing there whereby we need to move clients away from being obsessed by double A, single A compliance, and to start thinking about accessibility policies. What is there accessibility policy and what is it that they are trying to achieve on their site? Our base mark is going to be single A, it’s always single A, and I think it should continue to be single A.

Audience: but if you don’t talk to them about it, you could argue that less caring clients would just say “well why would I do anything about it, bottom line?”

Paul: Yeah, I said you shouldn’t talk about single A, double A, triple A, but that doesn’t mean you can’t talk to them about accessibility and the improvements that accessibility brings because for people that have got that sort of attitude you don’t want to talk about the disabled if they don’t care about the disabled, you talk about search engines, and that’s the best way to sell accessibility, by talking about search engine placement. That’s the reason you want to be accessible for people who have that kind of attitude. For those that care, and are talking about single A, double A and triple A, you need to say to them “well actually, conforming with any level, it’s great that you want to do accessibility, and certainly single A should be an absolute minimum, but we’d encourage you to start working up an accessibility policy and looking at your site as a whole and say could this area do more in your site, your accessibility policy should do real world testing with real users…” all kinds of things.

Audience: So you think that we should be encouraging large organisations that have accessibility policies themselves that refer to double A, triple A, to try and persuade them to kind of move away from that?

Paul: No, not necessarily, I wouldn’t go that far. Don’t get me wrong, I’m not saying that they’re a bad thing, I’m saying they’re not the be-all and end-all. And at the moment I feel like the vast majority of clients think they are the be-all and end-all. They’re obsessed with putting that little badge on the bottom of the page. And it’s not about putting badges on the page. The trouble with institutions that have these policies of single A, double A and triple A is that these policies are in place for the institution, not for the user. And that’s my problem with them. That’s why I think we should try to break that mentality with clients. And I accept that sometimes we’re going to lose, and that’s fine. Exactly the same goes when we were talking about browser support. I accept sometimes we’re going to lose that battle as well. But it doesn’t mean we shouldn’t try and fight it.

Audience: I just wondered why WCAG2 still does it, because yes, you’re right basically, and accessibility requirements should be based on user requirements and not ticking boxes, so why is it still in there?

Paul: I think it’s in there because… my impression… I hate talking about accessibility on camera! You remember what happened last time in the podcast? It was just a nightmare! I think the reason it’s still in is because some of those success criteria are hard to meet. Some of them are damn difficult. When you start talking about streaming video, you’ve got some difficult challenges there that need to be met. So I think as a result, what the W3C is saying there is that we accept that some of these things are difficult to do. And we accept that you’re not always going to be able to do them, so we’re going to make them triple A. But come on guys, some of this stuff is dead simple and we should be doing it, that’s single A. That’s my impression of the mentality behind it, and that’s a great mentality, but it’s when someone changes that to being guidelines, which is what they are, to being rules, really instilled by Moses and presented to the people. You know it’s not that and I think that’s an important differentiation to make.

Where to Start

Paul: I know what you guys are like, especially designers. Ok I’m making sweeping generalisations here. But, if you guys go along to the WCAG website and you look at the WCAG2 guidelines, it’s horrible! It’s intimidating and it’s scary and it goes on for pages. And there’s a lot of text around it.

Audience: There’s no pictures? (laughter)

Paul: There’s no pictures! The design isn’t even very good. So what I’ve done is I’ve taken that page, I’ve literally all I’ve done is I’ve stripped out the explanation text in front of it, and the waffle at the end of it, and I’ve left you with just the set of guidelines so it looks like a slightly less intimidating list. Not much but slightly. So that’s up at http://www.headscape.co.uk/WCAG2 so if you go to that, you can get just the actual list of criteria. There’s also, on the WCAG2 website, there’s a thing where you can go and you can say my site uses tables, my site uses video, my site has this and that, and you untick the ones that it doesn’t have and it narrows down the list of success criteria to only show you the ones that you need to care about. So you might want to check that one out as well. Ok, so that’s basically all I have to say, are there any other questions before we wrap up?

Questions

Audience: Clients are going to ask us the 1 minute elevator pitch. What’s the difference between WCAG2 and WCAG1? What would you highlight as differences?

Paul: I think there’s a bigger acceptance of things in the world other than HTML, so things like Flash, PDFs, all that kind of stuff, there’s much more reference to that kind of thing. It’s much better written, much better organised. I think it’s more pragmatic. It’s a little bit more… I think it will last the test of time more. It’s hard to pin down exactly what I mean by that. There is actually a document out that talks about the specific differences between WCAG1 and WCAG2 if you wanted to get into that level of detail. And to be honest, I couldn’t tell you what that is yet because I haven’t looked at it in that much depth myself.

Audience: I think you and I do need a couple of the more detailed stuff, to get the guidelines, just one or two examples basically. Something that’s new between WCAG1 and WCAG2, and also some of the differences between single A, double A and triple A. The streaming video is an excellent example.

Paul: Just go along to http://www.headscape.co.uk/WCAG2 and you’ll be able to see those different levels.

Audience: It seems like, an almost unwritten principle, or unwritten in your list of principles. It’s technology agnostic.

Paul: WCAG2 started off as so technologically agnostic that it wasn’t understandable.

Audience: WCAG1, the first line is all about “it must be W3C technologies”.

Paul: Yeah, it will pretty much accommodate anything. You know, it talks in terms of audio and video. It doesn’t mention Flash for example specifically, at least I don’t think it does, but it refers to those kinds of things. It refers to documents that are not HTML. I’m saying this as much for the video as anything else, I’m still learning about it as well. So I think it’s going to be a learning process for a while for us to really get to grips with this, and truth be told we probably should have started a little sooner than this, but it’s not radically different from WCAG1. This is as much getting us back into the habit of thinking about accessibility as anything else really. Ok?

Audience: 1 more question. Are they new Keynote animations?

Paul: Yeah, they are new Keynote animations.