User experience is not just about your website

As web designers and website owners we obsess about user experience. However, good user experience is about a lot more than having a great website.

Meet Jill. Jill is in the market to buy a reasonable quality digital SLR. She’s fed up with her point-and-shoot camera and wants something a little more sophisticated. However Jill doesn’t want to rush into a purchase as digital SLR’s are not cheap. Instead she has been researching the options online.

Jill holding her camera

Video

Eventually she discovers a video review on YouTube for camera that looks perfect. The video has been produced by a company called “Professional Cameras”. The review was very thorough and provided her with all the information she required.

Search Engine Optimisation

Once settled on which camera to get Jill searches Google to find the best price. Among the search engine results she sees “Professional Cameras” again. They are not the cheapest, but because she was so impressed by the video she decides to take a look at their site.

The website

The website was incredibly useful. It was well-designed, easy-to-use, and answered all the questions she had about purchasing from “Professional Cameras”. However by this stage Jill was keen to get her hands on her new camera and didn’t want to wait for it to be delivered. She decided she was willing to pay a bit extra to buy it from her local Currys. She got in her car and drove into town.

Mobile website

Much to her disappointment none of her local shops stocked the particular camera she wanted. However she remembered that the “Professional Cameras” website said something about next day delivery for a small additional charge. Although there were other cameras in Currys she didn’t want to settle for second best. So while still in store she used her iPhone to connect to the “Professional Cameras” website. She was delighted to find that they had an easy-to-use mobile version of their site that made it incredibly straightforward for her to place an order. Within 2 minutes she was done and the camera was due to arrive next day.

Support forum

Jill excitedly waiting for the camera to be delivered the next day. As promised it arrived on time and she was over the moon. She spent most of the day out snapping pictures, but when she returned home that evening she discovered a problem. Unfortunately no matter how much she tried she could not get the camera to transfer photographs to her computer.

In desperation Jill returned to the “Professional Cameras” website and visited the support forum looking for help. Unfortunately she couldn’t find the answer she wanted and because it was outside business hours she was unable to contact the supplier.

Social media monitoring

In her frustration she posted a tweet expressing her dissatisfaction with “Professional Cameras” even though she knew that it probably was not their fault. She was just so disappointed.

On logging in the following morning Jill discovered that somebody from “Professional Cameras” had responded to her tweet apologising for the problem and suggesting that she either calls customer services or uses the live chat facility on their website.

Customer services

Jill decided to use the live chat feature because she hated talking on the phone. She was blown away by the customer service she received. They offered to replace the camera no questions asked. However they suggested that a software update may solve the problem. Using the features built into the live chat they took her to the appropriate page and showed her how to download the drivers. This solved the problem and Jill went awayhappy.

An ongoing relationship

Jill was so impressed by the service she received from “Professional Cameras” that she decided to like their Facebook page and tell her friends about the excellent service she had been given. Most importantly when she received future e-mails from the company suggesting alternative products that she might wish to consider she was not so quick to consign them to her junk folder. In fact it turns out that the e-mails she received were incredibly targeted and suggested a number of excellent accessories and provided her with tips on how to get the most out of her new camera.

The moral of the story

So why do I tell you the story of Jill? It is to demonstrate that users online relationship with a company extends far beyond the website. More importantly it is vital that the different aspects which make up this online relationship work well together. Traditionally website owners have employed a web designer to build their site, an SEO company for their search engine rankings and marketing people to deal with social media and e-mail. However often this can lead to a fragmented approach.

If we are really to provide customers with an exceptional user experience it is vitally important that we provide a unified experience which involves the various specialists working together in extremely close relationship. It is time to look beyond the website and see the larger picture that makes up a great user experience.

If you recognise that the mobile web is important and you need help deciding on a strategy, then book a mobile consultancy clinic.

Book a consultancy clinic or contact Rob about a more in-depth review.

Making user testing happen

We all know we should be doing more usability testing than we are. Fortunately there are some great tools available to make the job easier.

Every time I see Steve Krug’s book “rocket surgery made easy” I feel guilty. I know I should do more usability testing than I do, but somehow it never quite works out that way.

Steve is right when he says we should all be doing usability testing every month. He even makes it incredibly easy by reducing the number of participants to only three people per month. Yet even this we struggle to do.

However I have learnt one valuable lesson from my disastrous DIY experiments. If you have the right tools the job it is a lot easier. In my experience this applies as much to usability testing as to DIY. Fortunately these days there are some amazing tools available and I’ve listed my favourites below. Be sure to check them out.

Flash tests

Flashing testing is where you show a user your website for a few seconds and then asked them to recall as many page elements as they can. This is a great way to discover if you have the correct visual hierarchy for your pages.

Where previously you would need to do this kind of exercise face-to-face, there is now an app for that! ClueApp.com takes a screenshot of your website and presents it to the user for five seconds before asking them to recall what they’ve seen. This is a great tool for testing initial sketches, design comps, or non-interactive wireframes.

ClueApp.com

Face-to-face testing

One of the big problems with face-to-face testing is recording everything that happened. Video cameras can be very intimidating as can having other people in the room taking notes. Silverback does a great job at making this kind of recording as unobtrusive as possible.

Using your Mac’s built-in web cam and mic it records everything the user says as well as their facial expressions and what they do on screen. When you next do face-to-face user testing make sure you have a copy of silverback installed.

Silverbackapp.com

Card sorting

Card sorting is an excellent way to ensure your information architecture is as user centric as possible. It involves allowing the user to organise cards that represent different content areas into their own hierarchy. Unfortunately the process can be time-consuming and it can be difficult to find an adequate number of users to make the exercise worthwhile.

Fortunately there is now an app called websort.net, which allows you to do card sorting exercises online using real users directly from your website.

websort.net

A/B testing

By exposing possible design variations to a small segment of site visitors you get an insight into how a new design is going to work in the live environment. Many argue this is by far the most effective type of usability testing. Although there are free tools such as Google website optimiser, my favourite is visual website optimiser.

What sets this tool part from its competition is the ability for client to carry out their own multivariate testing without the need to understand HTML code. Admittedly this is both a benefit and a curse. However, it encourages users to develop their websites on an ongoing basis.

visualwebsiteoptimizer.com/

Live interactive remote testing

It can sometimes be difficult to meet face-to-face with user participants who are potentially spread around the globe. One solution is to use screen sharing software that allows remote testing to take place. My favourite tool for doing this kind of testing is GoToMeeting. Although it does not currently support video you can share screens and speak directly to the participant. Best of all it seems to suffer from very little lag which is a crucial requirement when testing.

Gotomeeting.com

Un-facilitated remote testing

If you simply do not have the time to recruit participants and test yourself then you may wish to consider a service such as usertesting.com. For a low fee per user you can define a test (such as placing an order) and usertesting.com will find participants and record them completing the test.

All participants have been trained to talk out loud when completing tasks so you get a good idea of what they are thinking as they complete the test. Although not as good as interactive testing it is certainly better than no testing at all.

usertesting.com

Recruiting participants

Finding participants that match your requirements is possibly the hardest part of usability testing. Although it is not as important as many people think to have a demographic match for your participants, it can still be time consuming to find anybody at all.

If you simply do not have the time to recruit participants consider a service such as ethnio.com. This service will allow you to recruit participants directly from your own website. It will also allow you to manage these participants and find exactly the type of people you require.

Ethnio.com

No excuse

With so many tools available there really is no excuse for not carrying out regular usability testing. Just think, if you start doing monthly user testing you won’t need to feel guilty every time you look at Steve Krug’s book!

A great user experience extends beyond the website

As web designers we can only do so much for you the client. You can have the best website in the world, but if your customer service stinks users won’t come back.

I went to meet with a new client yesterday and was blown away by their commitment to customer service. Not only had they addressed every one of their customers points of pain, they had gone above and beyond in so many ways.

Update: Are you a web designer? Have you found yourself nodding at this post? Then before you get too smug you better read: “You’re a hypocrite (and so am I)“.

An unbelievable returns policy

The most stunning example of this was their returns policy. If you are lucky a website will offer you a 30 day return policy if the goods are unopened and so can be resold. If you are unlucky they will not accept returns at all or charge a restocking fee. However, with our new client things are radically different. They offer a 365 day return policy! However, they don’t stop there. You can return products that have been used and cannot be resold. Better still they will even pay the postage for you to return the goods.

It is truly staggering. So much so that the problem is convincing the user the offer is genuine!

A culture of service

However, it is more than that. They have the right culture too. I was fortunate enough to chat with their call centre staff. Currently they offer customers three ways to contact them…

  • Phone
  • Email
  • Live chat

I asked which contact method they preferred. I expected them to say email first, followed by live chat and finally phone. After all, when on the phone you can only deal with a single customer at a time. Email and live chat are much more cost effective. However my expectations were entirely wrong. The answer was the phone because “it is the quickest way customers could get their problems resolved”.

Cartoon in which the web designer is asked to remove the phone number from a site

Davi Sales Batista, Shutterstock

A growing trend

What’s interesting is that this client is not alone. More and more companies are realising that to compete on the web they cannot sell on product and price alone. The problem is that competition is fierce and the chances of having a unique product low. With your competition only a click away and savvy customers doing price comparison you are left with two choices – be the cheapest or be the best.

What this new breed of web businesses are realising is that racing to be the cheapest is a losers game. Eventually there is only so much that can reduce your margins. Instead they have discovered that customers (especially online) are willing to pay more for convenience. In today’s society time is as important a currency as money and users will often choose a more expensive option if it saves them time quibbling over returns or being on hold with customer services.

There are many poster children for this movement including the likes of Zappos. What these pioneers are proving is that the increase in revenue outweighs the costs involved.

zappos

On face value limiting customer service may seem like a good idea. However, in doing so you are putting short term objectives over the long term health of your business.

Think long term

Recently I wrote a post in which I said that business objectives are more important than users needs. However, that is not an excuse for neglecting your users. If you care about achieving long term business success, then you have to put great customer service and the user’s needs at the heart of what you do.

As web designers we can help you. We can make intuitive sites that are both painless and pleasurable to use. However, that is only half the battle. We also need you (the website owner) to continue that pleasurable experience in terms of customers service. What happens offline is as important as what happens on.

What about you?

So ask yourself – how could you be helping your customers more? Have you hidden away your phone number because you don’t want users calling you? Have you added in extra fields to your contact form so you can collect demographic data for spamming? Have you limited your returns policy for fear of people abusing it? What about hidden costs? Are there charges for returns or delivery?

Whether you are running an ecommerce site or an informational one the message is the same, provide outstanding user experience both on the site and off.

Lou Rosenfeld on Search Analytics

Lou Rosenfeld shares how the search terms used on our websites can reveal a lot about our users.

Lou is kindly offering any Boagworld reader a 20% discount off of any product at RosenfeldMedia.com. Just use the code BOAGWORLD at checkout.

Paul: So joining me today is Lou Rosenfield, good to have you on the show Lou

Lou: Thanks Paul

Paul: So just in case one of the three people in the world that have never heard of you before is listening to this show right now, do you want to give yourself a bit of an introduction, just a little bit about who you are and how you come to be in the world that is web.

Lou: Sure, I once was a librarian and I moved into Information Architecture at a time when it was sort of seen as librarianship for the web and sometime in the mid nineties I co-wrote a book with Peter Morville called Information Architecture for the world wide web for O’Reilly, which is now in it’s third addition and a lot of people look to that book when they want to learn about information architecture. I have been involved in a lot of things in the IA community and more recently in the broader UX community User Experience and one of those things is as a publisher of User Experience books. My company is called Rosenfield Media, with seven titles out hopefully the eighth or ninth will be my new book which I am co-writing with Marko Hurst on site search analytics.

Rosenfeld Media

Paul: OK

Lou: so that’s what we are going to be talking about today and hopefully the book will be out by the end of the year.

Paul: ahh, that’s brilliant stuff, so I mean you have just done a virtual seminar for Jared Spool on this kind of subject as well and it is something that kind of peaked ny interest so I thought it would be great to get you on and talk about this subject, in someways you are very honoured if I may say so Lou because you are the first of our kind of one-off interviews that aren’t a part of the main Boagworld show because we are not doing that at the moment. But it was such an exciting area and something that really interested me that I was really keen to get you on and talk about this. So why don’t you tell us how analytics generally, not just search analytics but analytics generally how do you feel they inform the user experience ? Why should we be caring about this ? What difference does it make ?

Lou: Well a lot of people who do user experience work are both on the design side and the evaluation and research side we are not necessarily all that comfortable with the numbers and in fact many of us are in the neck of the woods of this profession that we are in because there is no a huge pressure to do statistical analysis and I think that is too bad I think that one of the things that really hurts us is that we are numbers adverse and with something like site search analytics you can actually learn quite a bit of information that will help inform your design work, with just an excel spreadsheet and a little bit of data that you already have, if you have a search engine, at some point there is some way, you may already be gathering, some way of gathering the data, you may already be gathering it somewhere and you don’t have to be a statistician. In fact one of the really interesting things about this type of data is that it is not all numbers it is actually very semantically rich. So what I am talking about with site search analytics is we are basically harvesting users’ search queries that are being executed on our own site search engines and they are telling us in their own words what it is they want from us and so we are not just doing statistical analysis we are actually looking at the semantic nature of what their interests are

Paul: Yeah

Lou: what their information needs are, so it is interesting as that is a little different from most analytics so if you shy away from analytics you might think about taking a special look at site search analytics and if you are an analytics person what I found paul is most analytics people don’t pay much attention into this area either, some are certainly good at SEO and looking at web searches that are drawing people to a particular site but once people are searching on the site it is sort of someone else’s table if you will. So site search analytics is kind of like the orphan child of these two fields that don’t pay much attention to it,web analytics and user research and I am hoping that our book helps change that a bit.

Paul: So what would, lets be clear what we are talking about here. We are talking about taking the search terms that people have searched for on your site and analysing that. To what end ? What benefits do you get from that ?

Lou: Well there are so many that I almost don’t know where to begin but a few basic ones, one is that you can very quickly by simply sorting the queries from most frequent to least frequent, in other words from like the ones that got three thousand instances, in other words a query that was search three thousand times last week might be your most frequent query and at the other end of the long tail the one that are only used once. if you know what that short head is you can actually by improving performance for those top few most frequent queries really improve the user experience overall. So we find that if you map it out that, I wish we could do this visually but it is something that is like a hockey stick curve, it is called the zip distribution, what you start seeing is that something like you top ten most frequent queries may account for something like ten or twenty percent of all the search activity in a given time period, and you know the top twenty or thirty queries you are still are talking about a pretty huge volume of all of search activity. So by doing things like for example adding best bet search results to the most frequent queries or by looking for queries that are finding nothing that are really common and plugging the content gaps or improving the meta data, labelling that content as or should as so as that content gets found you can really very quickly make a very big improvement and it gets even better than that Paul because if you start doing that type of tuning for the most frequent queries the ones that people most care about and do that on a regular basis say every month you are doing a great tuning process adjusting your sites performance to your users needs. The more you do things like that the more you can avoid what for me is just like the most dirty word in the industry and that is redesign.

Paul: [laughs] yeah absolutely.

Lou: so if we can do tuning the more we are going to fight of the urge to throw a million dollars or pounds at a big problem that we are really take on the wrong way so tuning over redesign any day. Site search analytics is a great component in the tuning process.

Paul: yes I talk about evolution rather then revolution, instead of redesigning which is this huge undertaking continually evolving your site and anything that helps to inform that has got to be incredibly valuable

Lou: Absolutely

Paul: But I mean a lot, something that a lot of people may already be doing is they may already be looking at the google results they are getting, the analytics they are getting there, what are the advantages of looking at your own internal search rather than the results that have been generated by google.

Lou: well if you look at the most common google or world wide keywords that are bringing people to your site often what you are going to see as the top ones are the name of organisation or some variant on it. So now lets say you just get rid of those, because those are not that interesting and you want to look at the things that are more open ended searches where people happen to not be looking for use to specifically find their way round your site, they are certainly going to be a lot of overlap but the sense I have is that first of all the people who are searching your site have more specific needs. They already know something about you it maybe that they are a different type of user we don’t only care about bringing people to our site and make sure they get there we also worry about the people who are native to your site who maybe repeat visitors and they may already be loyal customers we care about them retaining the customers is a lot less expensive then recruiting one.

Paul:so yes

Lou: so eh what can we do to learn about their needs specifically and I will tell you exactly, I have a theory I haven’t really been able to prove it yet but I think that the nature of the queries that come into your site on your search engine are going to be more specific and more finely grained than those that are coming in from the web that being the case you know what more specific, it is almost like a predictor what web searches are going to be in the future. In other words the assumption is that peoples’ searches get more specific over time so you could probably use your site search terms to help you figure out more specific and less expensive keywords to bid on in adwords

Paul: yes

Lou: So there might be a secret little approach you could take there to do a better job than instead of bidding on the general search terms in google that are going to be really expensive and not really going to be helping you that much

Paul: I guess there is also going to be an element of the fact that for somebody to arrive at your site from google on a particular search term then your site has to already have to have content to have been listed on google for the search term they typed in. While with internal search engine they could quite easily type in something that isn’t a term that you use on your website and as you talked about earlier you need to plug the gap of that, but you are never going to get that from google because they wouldn’t have been referring to your site if you did not have any content relating to that particular term. Does that kind of make any sense.

Lou: that is absolutely right and then there is another important way that you are going to benefit from analysing searching within your site again we don’t just care about getting people to a site, we care about their experience once they are there. One of the things we can learn about is where navigation fails. So let’s imagine that we know your site has, we sell thirty different products on your site and each product has it’s own main page, it’s overview page it is really interesting to do apple and apple comparisons of pages and what types of queries those pages create. Let me put it in a slightly better way if you are looking at your product over a few pages and look at the queries that start from those pages.

Paul: yeah

Lou: You start learning about our patterns of information needs once people have found their way to a particular product and you may see that that kind of deep horizontal or contextual navigation which you are generating raw, you can start seeing patterns where people are saying I am on our product page and I don’t see the navigation that is going to get me to the review page or to the forums page or whatever

Paul: right

Lou: So maybe there are links that you have there but they are not prominent enough or you are not labelling them well or maybe those links aren’t there at all. So now you can start coming up with some ideas hypotheses what the problem is there and just go and think about it and say I trust my hypotheses here that you know we are missing links or you can start doing some qualitative research, you could do some user testing to validate your hypotheses so it depends how you are going to make your decisions but you have got some great hypotheses and by the way that’s what analytics is really for it is not going to tell you why, it is not going to validate your hypotheses it is going to help you come up with good hypotheses that are data driven and analytics tells you what is happening, it tells you about behaviour and not why things are happening, that’s were you really need to bring in qualitative research.

Lou Rosenfeld

Flickr, eraserandcrowbar

Paul: Yes, that was really the next question I was going to ask is how does analytics sit along side traditional approaches to improving usability which is like user testing basically,

Lou: right

Paul: because traditionally when we want improve the user experience we turn to user testing we sit users down we show them stuff and there is a real value in that kind of back and forth dialogue that you have and you don’t get that from analytics you are saying they perform different roles.

Lou: They absolutely perform different roles and this is one of the things that I am finding in my consulting, i’m a publisher but I still have to make a living so I do a lot of consulting still and I am seeing organisations that have incredible staff and resources in their analytics groups and separately their user research groups and too infrequently the twain meet and there is a big disconnect there, that they are suffering from because they have, I mean many organisations have just great analytics now they have great tools like armature and they only can really know about what is happening they can not really know why things are happening but they don’t … there is a disconnect in terms of them have the people who can do the qualitative user research and take the next step and actually do some testing and try and learn about this hypotheses and show which ones are actually real so sometimes it is really straightforward like erm you know you want to do task analysis, which is a qualitative approach it is not like any other user testing it is not cheap to do but if you had informed the kind of task that you are going to be testing by looking at your top queries you would be doing a better job it is going to point you and help you devote that expensive work, that qualitative research budget in a more efficient and effective way. What about when you are developing personas why not take if you can, get that audience segmented queries and start building those as a expression of the information needs for each, within each persona. You know we were just talking there it reminded me of a great story years ago I believe it was at Lands End, a US clothing retailer

Paul: OK

Lou: and they were looking in their search logs and they saw a preponderance of SKUs, er product ids but those codes were not on their website and they were really confused

Paul: yes

Lou: so they didn’t know why those were there and they knew what to do which was to start supporting the inclusion of SKUs into product pages so people would actually be able to get that information right away but then they followed up the site search analytics work they did with an ethnographic study where they went out into the field and watched how their customers were interacting with the information in the columns and what they found was, it was probably about ten years ago, that people were not comfortable using the website catalogue to do research they were used to using the printed catalogue, it is familiar it is high res easy to use so they would do their shopping browsing the catalogue but then they did not want to use the catalogue mail order or the 800 number ordering systems instead they went onto the website for Lands end and entered the SKUs and did their shopping there

Paul: aaahhhh yes

Lou: so there is interesting things that all types of data when folded in with user research can tell us and certainly site search analytics is no exception to that.

Paul: hmmm, I mean the thing is, is that collecting the data is the easy part and there are so many great tools out there you know and so many free great tools that enable you to collect this search data or other analytics data but collecting data is easy interpretation on the other hand is much harder I think a lot of people when they are faced with this kind of information are a little bit overwhelmed on where to start or how to get information out of it, earlier you were saying that this is relatively easy but it doesn’t feel like it when you are faced with it so what should we be looking at to better understand how our sites are being used, what should we be doing with this data.

Lou: Right here’s the beauty of the what I described early the zip distribution is that it really promotes scalability in terms of your efforts so if you have an hour I recommend looking at those top ten queries

Paul: Sure

Lou: and seeing what is going on, even just testing them out and see how they are performing and that is something you can do in a very small amount of time, maybe you only need the top five. It is not a lot of work and it has a real big impact.

Paul: Sorry so when you say testing them out what do you mean by that how would you test them out.

Lou: so you casn take those queries and just go ahead and search them on your site

Paul: and see what’s returned

Lou: and see what’s returned and do you think they are returning good search results do you think there are important things that are being missed if so why? Start testing it out and actually hmmmm, there is a really great case study that Vanguard did, Vanguard is a US based financial services company and they have really invested heavily in this we are actually profiling their work in our book and what I can do is provide you a url for the case study and there is a presentation and it is really eye-opening, I will give you the url Paul so maybe you can share it along with the podcast.

Paul: Great

Lou: but I don’t have it at my fingertips right now

Paul: no that is fine, that’s OK

Lou: your question was?

Paul: essentially yes, that, erm no I have forgotten it myself now [laughs] brain’s gone dead

Lou: I was just going to say there is not only this issue of just a little bit of work will go very far but a lot of times people are overwhelmed when they see the analytics reports and part of the problem is those reports are canned reports some of them are pretty universally useful and interesting regardless of what kind of organisation you are in so it is good to see things like your most recent queries or which queries are failing, retrieving zero results but I really encourage people to get at the data and roll their sleeves up themselves and basically wade in and play with the data. So get beyond the canned reports and if you got just even get your hands on a couple hundred of your top queries and put them in excel and then just play with them. By play with them I mean looking for clusters or categories and just things that might emerge like wow there is some unique outliers here there is interesting queries, like Lands End did finding a lot of SKU searches in their logs, that is not necessarily, there is no right or wrong way to do it just the idea of just sort of experimenting and doing what the statisticians call exploratory data analysis so you are really literally just playing with the data. You might even map it out and chart it out in Excel and just sort of see what comes from it.

Paul: Yes

Lou: So one thing I encourage people to do is to try to categorise the data in other words gee it seems like there is a lot of queries here about physical places, maybe our organisation has different offices or campuses or different buildings, look for things that seem to be people or different topics that emerge what you start doing is that you force yourself to get very close to the way users are thinking because you are looking at what their needs are, and actually it is a good way of looking at what sort of metadata your site ought to have and what kinds of content type people seem to be asking for and it might even help you do things like prioritise your next content migration because you start getting a sense of what are the really important content types that people seem to be requesting when they are searching so there are other things which you might delve into. Queries, you might see a lot of queries that are like dates, and I know the Financial Times did that and they now support sorting search results by date, filtering them by date. You know one of the things the Financial Times does, it is a great example, is they look for spikes in names of people and companies.

Paul: OK

Lou: and when they see that it is all of a sudden this person is being searched for a lot they compare those names, the spikes to the recent week of editorial coverage and if there is a discrepancy they bring this up to the editorial board

Paul: Wow

Lou: and they say hey, you know we are getting a lot of searches for so and so or this company and then the editors can decide if they want to have their beat reporters look into it, in a way it is almost a way of predicting the future.

Paul: So it is even more than informing the website, it is actually informing their editorial policy

Lou: Absolutely and of course those things are increasingly one and the same in many organisations

Paul: Yes absolutely

Information Architecture for the World Wide Web

Lou: so when you look actually when you do this over time they see a very strong seasonal effect in many organisation’s cases so what you might find is that even at different times of day people are looking at different types of information and that can inform the way you do things like put information on your main page or in other parts of your site that are high traffic pages and by the way one of the nice things about doing that is it helps to start beating down decision makers who want the main page to be about them, you know it is a political thing and if you can bring data that shows what users really want to those type of discussions you have a much better case, likelihood of heading off political battles over prime real estate on your site.

Paul: yeah, absolutely. Do you think the trouble with analytics is that it can be you know read in so many different ways and do you think there are occasions where your analytics can be misleading in understanding a site’s user experience.

Lou: Absolutely

Paul: if so where do things often go wrong ? What should we be looking out for ?

Lou: Well one of the problems is that you know there is no one tool that should solve all of our problems, and I am the first to say that site search analytics is not the end or the be all it is one thing that should influence our decision making alongside a nice robust collection of research methods qualitative and quantative, behavioural and attitudinal that should make up our research toolkits. That said you know when you are interpreting data one of the real mistakes I think we make is we leave that interpretation to one person for a huge organisation and I am a big proponent of merging both the quantative data that is often in the hands of a single analyst with the type of user research we are doing in other areas. In other words put the data in the hands of users

Paul: OK

Lou: So when I was describing to you for example a moment ago looking at top queries and sort of doing clustering and sorting with it and playing with it yourself what I actually really recommend is you have a bunch of users or subjects to do that.

Paul: Wow

Lou: So I am going to learn something about what my taxonomy out to be, or what types of meta data I should support or my content types might be I can do that myself but I would rather something along the lines of a modified card sort

Paul: yeah

Lou: with five or ten users, you know maybe I do not have to do that every month, if I do that every year or two. But when I put that in the hands of users and that is just a beautiful hybrid of the best of quantative and qualitative research.

Paul: hmmm, yes I like that a lot, kind of combining those approaches and yes that makes a lot of sense to me. I mean we talk very much so far about search analytics but obviously a lot of these principals you are talking about apply broader than that into kind of general analytics

Lou: right

Paul: but I am interested in what your thoughts are on you know even broader analytics tools or related analytic tools things like polls and surveys, I mean you see a lot of organisations have feedback widgets or they have, they do surveys and polls on your website and I am always a little unsure of the value of these things you know. On one had I can see

Lou: I am too

Paul: oh you are too? I am glad it is not just me, so what is your perspective on that kind of thing

Lou: Well in general I think all tools have there purposes and the real problem comes when we try and make one tool you know a hammer not only hammer nails put somehow put screws in and so forth

Paul: yeah

Lou: So I am really not a big fan of like relying on polls and surveys as a way to get a comprehensive view of users needs because of the self selection bias they introduce right off the bat

Paul: What you mean because there, you tend to get polarised results people are either really exceptionally happy and feel the need to tell you or more commonly they are just very pissed off

Lou: Exactly

Paul: you know if they are in the middle ground they are not likely to bother filling in the survey or a poll

Lou: Right, so I would say well you know that is useful information take it with a grain of salt like you just described I would then want to have a few other methods. Each of these methods is a lens on reality but an incomplete lens it’s a, it’s the blind man with the elephant nobody has the full picture you need to have a few that said something like polling or asking for feedback can be done more intelligently if it is, you think about doing it in a real contextual way. So for example if someone does a search you have seen these widgets that say did you find what you are looking for

Paul: Yes

Lou: I think that is a better way of doing it, because you are not just asking did you like us

Paul: Yes, absolutely yes

Lou: it is not before you leave were you happy ? of course you are going to get a really polarised maybe too open ended kind of data from that but if it is focused and contextual then you can knowingly better data but then you can also ask for a little more. if someone says I did not receive what I… I did not find what I was looking for when I did a search that is really a good time to ask for more information like what did you want to find when you did this search and then you are actually sort of closing pretty important feedback loop no just between the user and the site but you can take that feedback and send it back to the appropriate content owners side of the organisation and draw them into the process. So that is one of the big problems is that we have great content but our content owners don’t seem to want to get beyond the fact that their content is part of a much larger collection of information and that’s why they don’t bother following labelling guidelines or titling guidelines or applying meta data well. So if we can start showing them that their content isn’t just their content but it is part of something bigger, it is part of a natural marketplace of information that makes up the site and start showing them that their information is not being found when it should be found and showing them some data that suggests that you know they are falling down on the job then we have a much better change of getting them to follow content authoring and labelling and tagging policies and procedures that we may have set up for them. So a lot of organisations try to force people to them and it never seems to work too well but if you can educate people by showing them some data that suggests that their content would for example succeed if they would do something differently like following policies then it actually works.

Paul: yes there is something very powerful about presenting users, not not users internal stakeholders with data to back up your arguments and what they need to be doing. There is one question I kind of want to end up with really it is something I am really interested to hear your perspective on someone who spends a lot of time with analytics which is almost really a kind of moral question that you do feel that we can gather a huge amount of analytical data on our users and there are even tools, I don’t know if you have come across click tales.

Lou: hmmm hmm

Paul: that can go further and record user action and see people using and moving around the site is there a kind of line here as to what is kind of acceptable to do and what is not. It is almost a moral question in a way and I was just interested in your perspective on how much can we pry into user’s behaviour.

Lou: Right, so that is a really good one Paul, and if fact in terms of search analytics there was a really interesting yet somewhat unpleasant case about three years ago that made the front page of the New York Times you may have come across there were some AoL researchers who had a whole bunch of search data from the AoL site web search engine and they released it for research purposes however that data had people’s user ids not there names but their user id and this is like hundred’s of thousands of users and millions of queries and what people started doing within a day was to grab the data from the database and start searching just for one id and based on looking at all the queries associated with that one user id they could figure out who that user was

Paul: shee whizz

Lou: as well as what they were searching and in fact the New York Times reporters tried doing it themselves and they identified a woman in Georgia here in the states and they called her up and said is this you and she said yes. I am sure it was a disquieting moment for her

Paul: Absolutely

Lou: and much more disquieting for the individuals that were doing things like searching on child pornography

Paul: yes

Lou: so erm I think the issue is if you are going to do this work you have to be really careful to look at it as an exploration of collective behaviour, you have to be very careful to block opportunities for data to leak out or for someone else to get hold of data in way that will show individual behaviours and help identify who an individual is, and with or book what we are doing is looking at sets of data that tell us nothing about individuals and only looking at it collectively and that is how we think you should do it. Let’s worry about serving the majority of the people that are visiting our site the major audiences and not worry so much about individuals and let’s protect their privacy.

Paul: How does that relate mind when you start looking at e-commerce sites, you know that obviously use analytics heavily to recommend products and stuff. I am always a bit torn over that one because you know one one hand that obviously provides a real benefit to users and I quite like the fact that when I go to Amazon it will remind me the latest Battlestar Galactica DVD is out because it knows I like that but there is a line isn’t there where that analytics data steps over when it stops being useful to when it becomes creepy I am not really sure where that is – it is funny that isn’t it.

Lou: I think it has so much to do with how much you as a user or customer trusts that organisation.

Paul: yeah

Lou: So although they drive me nuts as a publisher Amazon is great to it’s customers and I think they manage to us that data in ways that delight us because they have some really smart and really careful designers and researchers there that are sensitive to these types of issues and they have got a great track record of customer service so we would feel a little differently maybe if we went to whatever large organisation that we are uncomfortable with at the moment, wether it is the government or I don’t know I can’t think of a good example but I think it comes down to your personal feelings about who is using that information. I would like to see in many respects more organisations doing just that I mean image your university experience if you could see the courses you were taking were taken by, what others were taking the courses you were taking you could learn a little bit more in a very disciplined way, that would be a delightful way to use that information yeah absolutely, but do you trust that institution – hopefully we trust the institution that is educating us in that particular example.

Paul: One would hope so [laughs]. Lou that has been absolutely brilliant it has been so fascinating to think through some of the power of the data that we are collecting and you know we are all collecting this data but I don’t think we are utilising it or know what to do with it so it has been absolutely fascinating to talk to you and thank you so much for taking the time to come on the show and hopefully we will get you back again soon.

Lou Rosenfeld Blog

Lou: Paul it’s a pleasure I really appreciate the opportunity thanks very much.

Paul: Thank you.

About Lou Rosenfeld

Louis Rosenfeld is an independent information architecture consultant and founder of Rosenfeld Media, a user experience publishing house.

He has been instrumental in helping establish the field of information architecture, and in articulating the role and value of librarianship within the field.

Lou has helped such organizations as PayPal, AT&T, Caterpillar, Ford, Microsoft and the CDC make their information easier to find.

He is co-author of Information Architecture for the World Wide Web, considered the bible of the field, and has been a regular contributor to Web Review, Internet World, and CIO magazines.

Lou is co-founder of the Information Architecture Institute and helped found the Information Architecture Summit. He blogs regularly at www.louisrosenfeld.com, and tweets even more regularly @louisrosenfeld .

Lou is kindly offering any Boagworld reader a 20% discount off of any product at RosenfeldMedia.com. Just use the code BOAGWORLD at checkout.

Web Design News 22/06/10

This week: The Boagworld Podcast goes off air, how to design better and faster, using stories in your design ideas and how to think from a users perspective.

Boagworld Podcast takes a break

The biggest news of the week (at least if you are listening to this… maybe) is that this will be the last Boagworld Podcast in its present format.

As I announced this week on the Boagworld blog we are taking a 6 month break from podcasting before returning with a new show and a new format.

To be honest at this stage we are not quite sure what that will be. That is why we wanted to take 6 months off to experiment with new formats and different material.

Between now and the end of the year we will still be putting out just as much content as we are now, but in a variety of different formats as we experiment with where to take Boagworld.

In fact we are starting these experimentations with a niche Webinar that we will be holding on the 21st July. If you work as part on an in-house web team then you maybe interested in joining us for a free interactive session where we talk about battling bureaucracy and ensuring the website gets the attention it deserves. To register your place email me on [email protected]. Remember to secure a place you need to be a permanent member of a web team in a large(ish) corporate or public sector organisation.

This will no doubt be just the first of more niche content that addresses the different needs of different members of the web community.

Dolphins saying 'So long and thanks for all the fish'

ShopArtGallery, Shutterstock

Design Better And Faster With Rapid Prototyping

If you have watched my presentation about Pain Free Design Signoff you will know I am a great believer in working collaboratively with our clients and showing them everything from initial sketches to final comps.

However considering the looks I get from some other web designers when I suggest such a hands on role for the client, I was beginning to wonder if I was alone in this view.

Fortunately an article entitled “Design Better And Faster With Rapid Prototyping” on Smashing Magazine has reassured me otherwise.

When talking about engaging all stakeholders in the design and prototyping process the author writes…

Doing this rapidly and iteratively generates feedback early and often in the process, improving the final design and reducing the need for changes during development.

He goes on to say…

Rapid prototyping helps teams experiment with multiple approaches and ideas, it facilitates discussion through visuals instead of words, it ensures that everyone shares a common understanding, and it reduces risk and avoids missed requirements, leading to a better design faster.

I couldn’t agree more!

The post goes on to look at how best to use prototyping and client interaction in the design process. In particular it looks at the fidelity of your prototypes in terms of design, functionality and content.

A graph describing the different levels of fidelity in prototypes from sketches to fully interactive websites using real content

He also provides a great list of do’s and don’ts that includes my favourite line in the post…

Do work collaboratively with users, business and IT stakeholders while rapid prototyping. Apart from giving valuable feedback, they also gain a sense of ownership of the final product.

This is a great article and definitely worth reading.

Using Stories for Design Ideas

Prototyping is a great way for discussing possible solutions. However, often there is a need to communicate and discuss the underlying problem first.

Before we can agree that a new feature is required, we first need to agree what problem it is solving. To do that we need to understand what the user wants.

User testing can partly help, however it doesn’t really focus on understanding the users ‘story’ or their motivation.

An article on Johnny Holland Magazine talks about how stories can guide our design process and inform what we do on our websites.

This is a new concept for me and one I am still wrapping my head around. However, as I understand it the idea is to take the problems we believe users are experiencing and weave them into a ‘story.’ This story that not only identifies the problem but also how the user feels and behaves.

Once you have the story it becomes easier to rewrite with a ‘happy ending.’ An ending where your website solves the user’s problem.

It’s a hard concept to explain so I recommend checking out the post. It contains lots of examples of how to turn a basic problem into a story and then how to use that story to generate a solution.

In essence it is an alternative to brainstorming that is ideal for the collaborative approach I have been talking about. This is because everybody is working from the same stories and so understands the problem that needs solving and the proposed solution.

An example of user centric thinking

While on the subject of understanding the users thinking, I want to conclude with an example and how it can solve very real problems.

The problem I want to look at is checkout abandonment. More and more people are abandoning the checkout process when purchasing from an ecommerce site. Of those users a whopping 29% are giving up because they are forced to register. That is second only to hidden charges being applied at checkout.

Abadnoned shopping cart

Sam Aronov, Shutterstock

In order to solve this problem you need to understand how users think. Why do they hate registering so much?

According to econsultancy the reasons are as follows…

  • Completing my purchase will take much longer than if I didn’t register.
  • I will need to provide lots more personal information.
  • I will start getting spammed with offers and promotions.
  • The retailer will pass my personal details on to third parties, who will also start spamming me.
  • Why do they need me to register? All I want to do is buy this one thing.

After reading that list you can understand the users point of view. The question then arises – why not remove registration entirely? As econsultancy points out, there are a lot of benefits for both the customer and retailer in registering. It’s just that the user cannot see that.

The real genius of the econsultancy post is what it does next. After identifying the feelings of both customer and retailers the post focuses on the crux of the problem…

The ironic thing about the whole ‘encourage customers register’ challenge is that when you break it all down, all new customers should be required to simply complete is one additional field – the create password field.

By understanding the users objections on a granular level you discover quite how small a problem is how obvious the solution.

Instead of asking the user to register up front you move the password creation field to the end of the checkout accompanied by the question “Would you like to save your details for next time?”

Actually I think it could be made even more compelling by asking “Would you like to save time when you next purchase?”

By understanding that while purchasing the user is focused on the buying process rather than registration, it becomes much easier to find the right solution.

This is user centric thinking in action.

Web Design News 09 /03/10

This week: Giving and receiving design feedback, are you bored of your sites design, CSS typography and helping users when they are too busy to read.

Helping users when they are too busy to read

As is pointed out this week on 52weeksofux the days of reading help manuals are over. In a world of twitter, facebook, mobile phones and email we just don’t have the opportunity to spend long lengths of time learning a new system or website.

As the post suggests…

We don’t have two hours to read a help manual. We probably don’t even have 20 minutes. Instead, we learn a bit here and a slice there, all adding up to real learning but not in contiguous time.

In short we learn as we go along.

This should have a considerable impact on how we design our websites. We can no longer except users to consult a help section or contact you for advice when they cannot use your website. According to 52weeksofux we need to change our approach:

In its place is embedded support: directions, tips, cues, and other signposts that can nudge us back on track. One example of this type of inline hand-holding is microcopy: the small, useful copy that helps answer contextual questions and defray concerns.

An example of Microcopy

So what about your site? Do you provide enough support to help users learn about your site as they go? Are your error messages and instructional text clear and descriptive? Perhaps it is time to revisit your website copy.

Critiquing design

One of the most controversial areas of the web design process is design sign off. Everybody (including clients) has strong opinions about what they like or dislike. Designers on the other hand are often overly sensitive about their work and so this can lead to a lot of friction.

Being able to give and receive criticism as well as discuss design in a constructive manner is a skill both designers and website owners require.

Fortunately an article on Smashing Magazine called “Web Design Criticism: A How-To” guides us through the process.

The article explores the subject of design critiques before suggesting 8 pieces of advice on how best to give feedback. It’s a valuable article and well worth reading.

In my opinion design critiques are extremely important, especially in teams of designers. It is always good to have another designer looking at your work and provide feedback. As a designer it is easy to become too close to your project. A fresh perspective is always valuable.

If you are a freelancer and don’t have anybody to discuss your designs with why not try the website critique section of the boagworld forum.

design critique

Image source

Are old designs boring users?

Talking of design, I am constantly amazed how many websites still go through regular redesigns that involve major overhauls of the look and feel.

I can understand designers desire to do something new and fresh. However, even website owners seem to want something new.

The problem is that although you might get a kick out of doing a major overhaul of your sites look and feel, users often do not respond so well.

In Gerry McGovern’s latest post he points to Facebook as an example of what can happen when you redesign:

“After a redesign in March, a Facebook poll revealed that 94 percent of users didn’t like the changes,” Caitlin McDevitt wrote for Slate in February 2010. “When Facebook introduced its News Feed in 2006, students organized to protest against it.”

In fact most users like familiarity and dislike change. This is because users do not want to be excited by a new design, they just want to get things done. Gerry goes on to say…

The vast majority of them are at your website to get something done as quickly as possible. The only people who are likely to complain about your website design are website designers. Craigslist is constantly being told that its site is boring. “But the people I hear it from,” Craigslist CEO Jim Buckmaster told Wired in 2009, “are invariably working for firms that want the job of redoing the site.”

Sites should evolve over time rather than go through sporadic redesign.

Does this mean our websites should never change. Absolutely not. However, we need to examine our motives for change and when we do change it should be an evolution not a revolution.

CSS typography

There has been a lot of excitement recently about services such as Typekit and Fontdeck that allow designers the ability to use custom fonts on their websites.

However, custom fonts are only the beginning of what can be done with typography using CSS. Unfortunately it can be hard to keep up with all the latest innovations so it is good to see a post by Yaili about CSS typography.

The post on Smashing Magazine is a comprehensive overview of everything you can do with type using CSS. This includes:

  • White space
  • Word wrap
  • Word and letter spacing
  • Indentation and hanging punctuation
  • Web fonts
  • Text shadow
  • And some new emerging text decoration

For a beautiful web site

With all of these tools at our disposal it is looking like the days of Cufon, Flash replacement or image replacement are numbered.

Web design news 23/02/10

This week: Why speculative work suck, progressive enhancement explained, how to be different and should designers be able to code?

Why speculative design suck

The debate over speculative design has once again raised its head this week.

In case you are unfamiliar with the concept of speculative design, it is best described as the process of producing free work for a prospective client in the hopes of winning a project.

Many agencies (including Headscape) have long since rejected the idea of speculative design. However, it is still common practice within the web design community.

This week Andy Budd lays out his arguments against speculative work. Although Andy raises some good points I feel he misses the heart of the issue which is that speculative work is bad for the client.

A closed website

A better argument is put forward by one Belgium Agency who is currently on strike protesting against speculative work. They write on their website

Pitches use up energy. Energy an agency would normally use to provide its existing, paying customers with the best possible work. So the logical conclusion of the system as it now stands is that at some point you will become a victim of it yourself. The day will eventually come when your agency has to divert the creative and strategic energy you’re paying it for into a pitch for someone else’s business.

I put it even more bluntly in my own article on the subject

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?

So before you next request speculative work I would encourage you to read my post on the subject.

What is progressive enhancement?

As web designers we do love our jargon. One example is the phrase ‘progressive enhancement’. I have even been known to throw the term around casually on the show with little in the way of explanation. However, I bet that a considerable number of the website owners listening (and probably more than a few of the web professionals) do not know what the term means.

Fortunately our very own Paul Stanton has provided a great analogy that explains progressive enhancement.

He explains how progressive enhancement can be seen in video games all the time, especially the big sports titles that span all of the various consoles. Each console has different capabilities with an xbox having consider more processing power than your iPhone.

Image showing the difference between the game on the Wii (left) and the 360 (right)

The result is that although it is fundamentally the same game on all platforms it is actually subtly different in terms of game play and graphics.

Paul explains that this is very similar to progressive enhancement on the web. Each browser has different capabilities and as web designers we build to make the most of what each browser can do. It is the same website but subtly different depending on the platform.

Its a good analogy that I will be using in the future because it draws on something that the majority of people can associate with – video games.

How to be different

We walk a fine line with our websites. On one hand we want them to meet user expectations and avoid making users think too hard. On the other we want our sites to stand out from the crowd and be memorable.

In a new article on the Carsonified blog Kat Neville attempts to walk that line while challenging us to move away from Cookie Cutter websites.

A particularly narrow website

The article is a challenge both to designers who tend to get caught up in the latest trend, and websites owners who are often overly conservative in terms of design. It aims to inspire with some great examples of sites that break the mould and do things differently.

Of course the suggestions are not going to be relevant to every site. You need to carefully consider your target audience to establish how far from the norm you are able to push a design. However whatever your site, it will challenge you to ask if you are just following the crowd or really thinking about design.

Should web designers be able to code?

Ven Diagram showing an overlap between designers and developers when creating HTML and CSS

An interesting argument has exploded on twitter this week and has since spilled over into the blogosphere too. The argument was sparked by Elliot Jay Stocks who wrote:

I’m shocked that in 2010 I’m still coming across ‘web designers’ who can’t code their own designs.

It would appear this was a somewhat controversial comment and led to a massive backlash from designers who do not code.

For fear of inflaming the debate further, I have to say I am amazed anybody could disagree with this statement. Admittedly not every web designer does code, however they should at least know how.

I am not going to layout the arguments for this position here. However, I would suggest you read three excellent posts on the subject…

If you happen to be a designer who cannot code, I strongly recommend you read these posts. I honestly believe you are limiting your potential and undermining the product you provide your clients.

How site personas can enhance your site

If your website was a person, what type of person would it be?

It is an interesting question. Take a look at your website for a moment. Look at the design, read some of the copy. Can you picture a single person that represents your site? If the answer is no, then you may benefit from the creation a site persona.

What is a site persona?

Essentially a site persona is similar to a user persona. It is a fictional individual who represents your site. You could chose to give that person a name, an age or even decide  how he or she looks. However, the most important aspect of a persona is the character. Is your sites persona enthusiastic and charismatic or considered and reliable? Is it professional or trendy? These character traits can define the whole direction of your site.

Why does a site persona matter?

In my opinion the most important role of a site persona is to create  consistency between design and copy. Often design is produced in isolation and the designer find himself developing templates that will have copy dropped into them later. This is far from ideal. Design and copy should be closely integrated. However, although many designers encourage clients to provide copy upfront, this is not always possible. The next best option is to have a site persona that influences the nature of both copy and design.

A site persona provides both the designer and content providers a structure within which to work. It helps to define the design and provide a tone of voice for the copy. At the same time it ensures the two work well together. The persona is particularly important where multiple content providers are writing copy that needs a single voice.

Finally this tone of voice is important beyond the website too. The site persona also ensures that user engagements via Facebook, YouTube or Twitter also occur with the same voice found on the website. It projects a single consistent image.

How do you create a site persona?

Deciding on the character of your online presence is not easy. However, at its core a site persona is essentially a list of words or phrases that define its personality (e.g. conservative or energetic). Fortunately, there are a number of sources that can help choose those phrases. These include:

  • Existing prom0tional material - By looking through existing marketing material, you maybe able to identify a tone of voice that could define your persona.
  • Business strategy documentation – Documents like annual reports, mission statements and vision documents can provide a sense of the overall vision and personality of your organization. This can be fed back into your persona.
  • Key organizational figures - If your organization has key figureheads (think Steve Jobs) then these people will probably heavily influence your site persona. If these people are the public face of your company, their personalities should certainly be reflected on your site.
  • Your target audience – Look to your target audience as a source of inspiration for your persona. However, do not feel like your persona has to exactly reflect your target audience. For example, a prospective university student does not expect the tone of a university website to be that of a 18 year old. They are looking for an older persona who can still relate to them. That is a subtly different thing.

Of course, using the sources listed above will establish what your persona actually is rather than what you would like it to be. To take your persona to the next stage, you need to be more aspirational in your choice of phrases. However, although it is good to create a persona that reflects the type of organization you wish to become, do not get carried away. Users will treat a persona with suspicion if it is radically different from their preconception.

How to avoid being schizophrenic?

Although many organizations lack a site persona simply because it never occurred to them to create one, some lack one because they have rejected the idea. The reasons given typically fall into two categories:

  • Our target audiences are too diverse – How can we possibly present a consistent persona when we have to speak to such a diverse group of people?
  • We want to focus on people not institutions – We don’t want to hide our content providers behind a corporate facade. We want them to express their own personality in their writing.

Let’s address each of these in turn.

Diverse audiences

This concern is born out of the belief that a site persona should essentially match that of the target audience. If the target audience is diverse then the persona would have to be schizophrenic. However, as I have already said successful communication does not require a site persona and user persona to match.

Take for example my own personality. Whether I am speaking to a board of directors at some public sector institution or running my local youth group, I am still me. I may slightly alter the language I use and the way I behave, but basically I have the same personality. I am just as enthusiastic whether I am presenting plans for a website strategy or participating in a food fight!

As humans we adjust the way we speak all the time depending on our audience, but our essential personality remains unchanged. A successful persona can adapt to suit a variety of audiences.

People not institutions

I am very sympathetic towards the desire to focus on people not institutions. After all, we converse with individuals not organizations. It is good practice to be as open and transparent as possible both online and off. In no way would I suggest you hide the individual personalities behind your organization. However, that does not mean you should not have a consistent overarching persona.

Newspapers are a good example of this in action. A newspaper has multiple columnists, each of which express their own personality when they write. However, each newspaper also have an overarching style. There is for example a distinct difference between reading the Sun and the Times.

It is this balance between personal expression and encompassing persona that our sites need to achieve.

Conclusions

I am acutely aware that this post has lacked detail in places. I haven’t for example provided a site persona for you to use as a template. That is because I don’t think there is a right or wrong way of doing this kind of thing. What you chose to include or exclude from your persona is largely up to you. The aim is not to create a persona for its own sake. The aim is to create a tool that can be used to define the character of your site. This will in turn inform the design and content.

I would be interested to hear whether you have considered using site personas before and if so what your expeirences has been? I would also like to know what problems you see with this approach. This is very much an area where my thinking is evolving so please provide feedback in the comments.

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.

161. In or Out

On this week’s show: Paul announces Micro-Boagworld, we discuss the pros and cons of outsourcing web work and see what recommendation the Boagworld forum has to offer.

Play

Download this show.

Launch our podcast player

Housekeeping

For a while I have been toying with the idea of doing a Micro-podcast that works in a similar way to Twitter but with audio. It would provide the opportunity to share hits, tricks and reviews too short for the main show. My problem was that I needed an application which made this as easy as posting a tweet. Anything more and it would prove too demanding.

Fortunately a new iPhone application has launched that does exactly that. Called AudioBoo it allows you to record 3 minute audio snippets that then get posted to a website, twitter, facebook and a podcast feed.

I am therefore pleased to announce Micro-Boagworld…

View Micro-Boagworld posts here

Subscribe to the RSS feed here

Boagworld AudioBoo Homepage

Back to top

News

Pricing and projects

Alyssa Gregory has written two good posts this week both relating to the pricing of web projects.

The first post tackles the notoriously difficult subject of How To Estimate Time For A Project. After all, time is money.

Estimating how long a project will take is tricky and although this post doesn’t provide any magic formulas it does provide good solid advice.

As well as considering the obvious deliverables Alyssa also recommends time for project management, reviewing work, debugging and client turn around. Finally, she recommends adding a buffer for the unexpected.

Of course, she doesn’t discuss how all of this time translates into your final price. How much you charge is a matter of conjecture. However, in a second post she does explore a related subject – How To Raise Your Rates.

In this post, she handles the sensitive subject of how to tell a client that you will be raising your rates for future projects. She suggests five techniques you should employ…

  • Give Notice
  • Set a schedule (make increases annual for example)
  • Make it fair (keep the increments small and manageable by the client)
  • Send it in writing
  • Balance it out (Balance your increase with an incentive – e.g. a special, a one-time discount)

Its all good advice and important too. As your skills and experience increase, you will need to ensure your rates reflect that. Knowing how to hand those rate increases is vital if you want to keep your clients happy.

IE8 and IE6

Microsoft have announced that IE8 will be released via the Windows Automatic Update starting on the third week of April.

The final version of the browser has been available since March and yet adoption has been sluggish. Hopefully Automatic update will change this trend significantly. However, it does not guarantee universal adoption. Although the update will be marked as important users will not be forced to upgrade. In fact Microsoft has released a blocker toolkit so corporate users can avoid the update entirely.

Worst of all, it is likely that the update will impact the numbers using IE7 more than IE6. IE6 users tend to be hold outs and are unlikely to upgrade now when they did not upgrade to IE7.

The only hope is that many IT departments have a policy of running a version behind the current release. If that is the case, the arrival of IE8 may encourage some of them to adopt IE7.

The entire web design community is keen to reduce its level of support for IE6 and hopefully this update will allow that. In fact, another post this week entitled – 10 Cool Things We’ll Be Able To Do Once IE6 Is Dead – points out just what a wonderful world it would be.

Once IE6 is gone we will be able to…

  • Use child selectors
  • Make full use of 24-bit PNGs
  • Use attribute selectors
  • Use a wider range of display properties
  • Use min-width and max-width
  • Throw away 90% of CSS hacks (and 90% of the reasons for needing them!)
  • Add abbreviations that everyone can see
  • Trust z-index again
  • Save time and money
  • Enjoy ourselves again!

Simple and impressive design techniques

Last week I was doing a consultancy clinic with a developer who wanted advice on designing his website. He was a great coder but did not have much experience designing.

Although I recommended The Principles of Beautiful Web Design by Jason Beaird it would have been great to point him at the latest Smashing Magazine post – 10 Simple and Impressive Design Techniques.

This post has some easy to implement techniques that are ideal for developers trying to improve their design skills. Techniques include…

  • Adding Contrast
  • Using Gradients
  • A Better Use of Colour
  • Improved Letter Spacing
  • Changing Case
  • Use of Anti-Aliasing
  • Adding Imperfections
  • Implementing blurring
  • Careful Alignment
  • Trimming the Fat

Read the whole articles for more details and great examples of these techniques in action.

Influencing user behaviour

A big part of good design is guiding the user to complete the actions you want. Influencing user behaviour can be achieved through a variety of techniques. However, it can often be hard to know where to begin.

One resource that might help you influence user behaviour is The Design with Intent Toolkit. This is essentially a printable ‘cheat sheet’ that suggests a variety of techniques you can apply to your projects.

The techniques do not just apply to web design but all aspects of design. Consequently not all of the techniques will apply. However a lot do, ranging from the use of metaphors to setting up good default options.

Some of the techniques contained in this cheat sheet are also beautifully demonstrated in another post I wanted to mention. Entitled 12 Excellent Examples of "Lazy Registration" it addresses the problem of user signup.

Essentially it is a post that showcases methods for getting around the problem of user registration. As the post itself says…

Signup forms have long irked the casual visitor. During the process of discovery, nobody wants to stop and fill out details before they can "unlock" the rest of the site’s potential.

It has certainly been my experience that signup forms are a barrier and so it is interesting to see how different web applications have overcome the problem.

Back to top

Feature: When to outsource web work

Your in charge of your organisations website. It has become moderately successful and now you have a decision. Do you hire a full time web designer or outsource to a web design agency?

Read the full article

Back to top

Listeners feedback:

In this week’s listener feedback section we look at a series of recommendations from the Boagworld forum…

A good introduction to Javascript

Jake writes: I’m curious as to whether or not anyone on the forum has strong opinions on a good introductory javascript book? And by introductory I mean something that’s more about initial learning steps such as syntax, etc. and then talks about best practices.

Doug answers: You might want to look at one of the books out for coding in jQuery, if you’re planning on going in that direction anyway. As for how to learn javascript I usually push people towards Lynda.com.

Matt also replies: Awesome book – DOM Scripting – I’d start with this before jQuery as I think you need some javascript knowledge to use jQuery to its fullest.

A good but free survey tool

Simon asks: I want to create some simple(ish) survey’s to get clients to fill out after a training session. I know of some paid for solutions, but does anyone have any suggestions for any free tools?

Laura replies: For something short, I’d use the survey function on PollDaddy. You can get up to 100 responses, and I think ten questions. Ten isn’t many, but you can do conditional branching for free, which is rare, and good.

I’ve also used SurveyMonkey before, it’s clean and simple.

A review of Clicktales

Peter shares his experiences of Clicktales…

On the recommendation of Paul, I tired out ClickTales.com; and I have to say the results have been interesting (sad, in my personal case) to say the least.

For those of you not in "the know", or missed episode 141, ClickTales is an app that lets you record and review the actions of your website’s visitors. And I’d agree with Paul: inexpensive, revealing, but limited in essence because you can witness what a user goes through.

In my case it was most effective because my results have been telling me that I should redesign my website’s structure completely… so I decided I should start from scratch all together and redesign. :)

Web Design for ROI

Bill reviews Web Design for ROI by Lance Loveday & Sandra Niehaus…

Each year I find one or two books that really stand out. This book, Web Design for ROI, changed the way I look at current eCommerce projects and helped me identify better strategies for building web sites.

Rich adds: I agree this is an excellent book.

Not too much new for a seasoned pro like myself, but I did still learn a fair bit and I’d recommend it to anyone with an interest in websites that make money.

Pro Paypal e-commerce

Finally, Ian shares an extensive review of the book ‘Pro Paypal e-commerce‘. Ian writes a very thorough review but here are a couple of highlights.

I thought this was a great read. It’s not often you finish a book and feel confident you have all the information you’re going to need to complete your project. The book isn’t just technical but also has lots of useful nuggets on business practices and background on payment systems in general for those that are unfamiliar with them at this level.

I feel confident in recommending this book to anyone who is involved with developing E-commerce systems or is going to be in the future. The author Damon Williams has a very readable style that is mercifully faux-humour free but never dull and explains everything clearly and concisely and despite its relatively low page count at 260 pages or so, still manages to cover a lot of ground without ever feeling as if it’s being too terse.

For more reviews about everything from web design books to software visit the Boagworld forum. We are also going to do some cool new stuff on the forum over the coming weeks. Keep an eye on it. We have already added a Jobs category for those of you who are looking to hire a web designer, so be sure to check that out.

Back to top

 

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

159. Special Guest

On this week’s show: The northerners are back with special guest host Sarah Parmenter.

Play

On this week’s show: The northerners are back with special guest host Sarah Parmenter. We answer your questions on how to quote for projects and whether using off-the-shelf software is wrong and we have a chat with Sarah on her experiences in the industry and the difference between developing for clients and developing for yourself.

Download this show.

Launch our podcast player

News

Alkaline

Our first story for is a new product by the guys over at Litmus, you may have come across their Browser and Email testing apps before and they’ve just released a new Mac app called Alkaline, this is a Mac front-end to their online browser testing suite and lets you test your website designs across not only 17 different Windows browsers which they mention on the site, but also all of the Mac and Linux browsers that the online Litmus services test against.

Alkaline grabs screenshots of your site rendered in all major browsers, the number of which depends on your chosen pricing plan, It’s free to test against IE7 and FF2 and if you need to test across all browsers, it’s available under the standard Litmus pricing plan which offers both individual and team monthly subscriptions, and a handy day-pass if you only do this kind of testing every now & then. Litmus also stores a history of your screenshots so you can see the evolution of your design and also reports your HTML and CSS errors.

There’s plugins available for Textmate and Coda, and you can preview the sites right inside Coda 1.6’s preview window, however because Alkaline grabs screenshots of your pages it’s not possible to do any live updating of CSS and see the results in all browsers.

Paul at Litmus also informed me that throughout April, they’re offering full access to the Litmus service for free on Weekends, so on Saturday and Sunday you can test across all the browsers (using Alkaline or the Litmus site) and all the email clients, even if you only have a free account.

16 design tools for prototyping and wireframing

It’s no secret that prototyping or wireframing can really help in the overall design process, and there’s now a wide range of tools on the market that aim to help you in this process. A recent Sitepoint article lists 16 of these tools and rates their usefulness.

The list of tools is good, convering favourites such as Omnigraffle, Axure and Balsamiq to other applications which can be used to wireframe such as Powerpoint or Keynote. If you’ve not looked into these kind of apps before then do check it out, they also lists the price of the apps so you’re sure to find something within your budget.

10 Lessons every freelancer should learn

If I remember rightly, I came across this link from one of the people I follow on Twitter and it covers some killer tips on how to be a better freelancer, covering everything from self promotion, organising your workflow, finding time for your own projects, keeping motivated and how to charge appropriately, this is a must-read for anyone considering freelancing, or indeed those already in the freelance world.

Some great tips come in the way of keeping customers happy and generating repeat business and I’d like to squeeze in a forth link here to another Sitepoint article (sorry) which covers how to upsell additional services to clients as a freelancer you should be looking at maximising the amount of money you can make from each project through added services, whether it’s packaged services such as hosting, logo design or business cards.

I don’t really freelance but I do manage a couple of small sites I built on a freelance basis, and I get recurring revenue by hosting them on a small reseller account. I’ve also been able to tempt the customers into paying for a years hosting rather than a monthly cost by rounding the amount down to an even figure, which while it’s only a couple of pounds cheaper, always got chosen.

Back to top

Interview: Sarah Parmenter on the difference between developing for clients and developing for yourself

Ryan: OK, so onto our interview section and what we are going to do today is an off-the-cuff interview with you, Sarah, er, so for people who don’t know who you are, er, do you want to introduce yourself.

Sarah: Sure, my name’s Sarah, I’m based in Leigh On Sea in sunny old Essex and I own a company called ‘You Know Who Design‘ that’s been going for about nearly seven years now, um, and I just do web development and sometimes I dabble in a bit of graphic design. Um, when I started off when I was younger, it was more graphic design than web but now it’s purely web and, er, yeah, it’s what I love doing.

Ryan: Right, OK, and we think a good topic to have a chat with you about would be the difference between developing for clients and developing for yourself.

Sarah: Yup

Ryan: So, er, let’s start off. Do you give yourself time to work on personal projects?

Sarah: I do, but not as much as other people do; whenever I see on Twitter, there’s a lot of people who have a lot of personal projects on the go and it generally tens to be on a Friday as well (all laugh), you see Twitter on a Friday, generally full of people, um, doing their own stuff but I tend to, if I’m doing something I tend to, maybe, give myself a couple of hours if I’ve got a spare, if I’m waiting for a client to get back to me on something and I can’t proceed with anything. I put client work first, and I don’t know if that’s a good thing or a bad thing, but that’s the thing that pays the bills, so, um, they always come first and if I’ve got a bit of downtime, I’ve always got projects that I want to work on, but possibly haven’t got the amount of time to dedicate to them as I’d like. I think it’s probably the case with everyone.

Sarah: Yeah, absolutely. You get some time, don’t you, through work?

Paul: Er, well we did sweet talk our boss into giving us 5% time, which was supposed to be like Google’s 20% time, where they get a whole day to work on personal projects, if it benefits the company.

Sarah: Really?

Paul: Yeah, well we got, like an afternoon on a Friday, which is kind of sidelined at the moment.

Ryan: To spend in the pub (laughs)

Paul: That’s personal projects, I’m sure. No, it’s kind of sidelined at the moment, we’ve got some major projects on which are taking up all our time with some heavy deadlines, so we’ve had to shuffle that. Hopefully we’ll start to get that back over the summer and work on some cool stuff instead of the business stuff.

Sarah: I think it’s rea
lly difficult, because obviously your client stuff does have to come first, and even if you’ve dedicated an afternoon or a couple of hours, if something comes up that morning, or if you’ve got a problem that needs sorting, unfortunately, it’s just the way it is, your client work has got to come first.

Paul: Yeah, pays the bills.

Sarah: I mean, a lot of personal projects, a lot of people’s personal projects, do end up very lucrative for them, and you could argue that it’s just as lucrative to just go along with your own personal projects, but I think in general, most people would find that their client work would, er, would have to come first.

Paul: We’re trying to convince our boss to let us build, er, an iPhone app

Sarah: Really?

Paul: and sell it on the app store. He’s not having none of it, because we’ve told him we all need iPhones to test it on, he just won’t buy them for us.

Ryan: and a mac to develop on

Paul: a Mac to develop on, yeah. For some reason, he’s not warming to the idea.

Ryan: he can’t understand the thirty grand, you know, outlay to…

Paul: We’ll easily make that in a day on the app store (all laugh), I keep telling him this.

Sarah: the app store!

Paul: Yeah, the app’s 50p, you know…

Ryan: Er, completely sidetracked there, erm. What differences do you find, er, between developing for clients and developing for yourself? What major differences do you find?

Sarah: I find, when I’m doing stuff for myself, I’m actually a lot less decisive on stuff. I sort of, because I’m immersed in, maybe my own branding, or sometimes it’s really good to look at it from an outsider’s point of view. If you’re doing stuff for clients, I think sometimes it’s easier to look at stuff and go ‘well, that needs to go there and that needs to be there to catch someone’s attention’ or you need to move that or make that a different colour, and when it’s your own stuff I think you tend to be either really creative and you don’t really care if you get stuff wrong, or if, do you know what I mean? It’s more, sort of… the boundaries aren’t there, you’re not time-constrained, there’s no brief, you just go off on one, doing whatever you want, whereas with client stuff, there tends to be a bit more, erm, what’s the word, consistency across everything, and I find, personally, when I’m doing my personal stuff, I could sit in front of Photoshop pushing something from the left-hand side of the screen to the right-hand side of the screen for two hours, wondering whether it looks right or not, whereas if it’s a client site, I think ‘right, I have to make a decision on this – where would this go, or where would it be best placed, and you make a decision and you move on, because otherwise the more time you, you take going backwards and forwards is, er, less money that you’re earning, so I think I tend to be more decisive with client work and with my own I tend to be a bit more, erm, easy-going and, er, possibly a bit more creative, in the sense of trying things that I haven’t tried before. Erm, yeah, I think it’s just good to be (pause – all laugh).

Paul: I think personal projects give you time to play with the stuff that you wouldn’t normally risk putting into a client’s site, things that might take you a week to figure out.

Sarah: That’s what I, sorry a man just walked past my window in a pair of shorts, as I was answering that question, which completely put me off,

Ryan: Was it an ugly man, or a good-looking man?

Sarah: No, he was an old man.

Ryan: Oh, right. OK

Sarah: I wondered if he had dementia or something, and he thought it was summer.

Paul: Was he in just a pair of shorts?

Sarah: Yeah

Ryan: A pair of shorts and a smile?

Sarah: No, and a newspaper.

Paul: Strategically placed.

Sarah: It just completely sidetracked my thinking pattern, then.

Paul: That’s OK.

Sarah: Oh, sorry.

Ryan: Where were we? So, which do you prefer, developing for clients, because obviously you’re doing that every day, or do you prefer developing for yourself?

Sarah: I actually prefer developing for clients, erm. I prefer getting a brief and thinking ‘right, how can I best interpret this brief, and get the objectives that they want, er, they want to get out of this website, how can I do that in the best possible way?’ Whereas, I think that when you do stuff for yourself, you don’t necessarily write down a brief as strict as you’d get when a client is sending through something. So, I, I actually prefer developing for clients, I really like, I don’t, I really like doing all the end, getting to the end product with a client. I think I get more satisfaction out of that than I do when I’ve done it for myself, because I still look at it in a very critical point of view, I still think, ‘oh well, maybe I could make those buttons a slightly different hint of green and it will look better’; whereas, with client stuff I think it’s just all about decision making, I think you tend to make more decisive decisions with client work than you do with your own. You think of your own as an ever-ongoing project that you can forever tweak and make changes to, whereas with client stuff you, once it’s live, it’s pretty much. You might get to update…

Ryan: Yeah, it’s difficult to come back, isn’t it?

Sarah: Yeah. Exactly. So I much prefer developing for clients, when they’re nice clients!

Ryan: Yes, we only like the nice clients.

Sarah: Yes, we all like nice clients.

Ryan: But do you think personal development time is important, do you think it’s important to develop your own projects?

Sarah: Yeah, I do I think it’s important from the sense of being, when I personally do lots of my own stuff, I find that I tend to be a bit more, erm, creative, in the sense of I’ll try stuff that I might think ‘oh, that’ll look awful, I won’t bother doing that for a client site’, but I might try it and actually surprise myself and think ‘oh no, actually, that’s a really good technique to use’ or do something a bit different because you’re not constrained by time when you’re doing stuff for yourself, necessarily. But I think, I do think it’s really important to do your own, your own thing, because I think it’s also a learning curve, you might try out different systems to use, you might decide to learn something, you might decide to use something like, if you’ve never used WordPress, you might decide to go and bolt WordPress onto your site just to see how you get on with it, you might try different apps. I think it’s important, because it frees the mind to use other things that you might not necessarily get to use when you’re in an office environment or, or perhaps even day to day because you don’t have the time to learn it, so I do think it’s important, but I don’t think it’s the, er, the be all and end all of everything.

Ryan: I think, er, a good tie-in question, not specifically about developing for clients and, er, yourself. Erm, keeping it with blogs and stuff, do you allot yourself a, like, time to read your feeds and, er, things like that, and to keep up with them, because I’ve been so busy in the last two weeks, my feeds have just gone like – you know when Google Reader says ’1000+’ and that’s it, it’s just stopped counting, it’s gone ‘look man, give up on these feeds, you’ve passed a thousand.’

Paul: You need to declare feed bankruptcy, I think.

Sarah: I tend to do this really annoying thing, where if someone posts a good link on Twitter, I’ll open it up in a browser window in a tab, and then if someone else posts, I’ll open that in another browser tab, so I’ve got about 100 tabs open in Firefox that I never get round to, to looking at, which slows the whole thing down and end up having to then bookmark them in a little folder called ‘Interesting Links’, that I never get around to reading.

Ryan: When you look back, they’re four years old and completely out of date.

Sarah: Yeah.

Paul: The shocking thing, because I do the research for the, the Boagworld news and push it all through the links, I probably churn through 150-200 feeds a day (Sarah: gasp), which is so many feeds that I haven’t got time to read them, which is shocking; I get so much information, so many good things that I’m pushing out to other people, that I just don’t have time to read them, there’s too much information.

Sarah: Do you skim-read them?

Paul: I do, I skim-read, I usually read the first few paragraphs, just to see what the article was about, clip out the interesting bits of text for the previews and then send it on it’s merry way out of Twitter and then I’ve written a function that, every time someone clicks a link on Twitter, it kind of lets me know, tracks back and so I can see, right, which… and I watch it, I’ve got live stats and streaming on one of the spare monitors, so as this link goes out onto Twitter, I can see it being read, so I can actually what’s actually what the people are reading, what’s been interesting that way, instead of me thinking ‘that’s genius, we’ll use that on the show’. It’s actually kind of crowd-sourcing information like this.

Sarah: Yeah, that’s a better way of doing it, isn’t it? It’s more productive.

Paul: Yeah, but I do the same, it’s like something I really want to read, I’ll open it in a tab and I’ve got the permatabs thing on Firefox, so I’ll set it so that I can’t delete it until I’ve read through it, but usually it just ends up there for weeks.

Ryan: I tag them in Delicious, so I’ve got like tutorials and stuff that I think ‘oh, that looks fantastic’ and I’ve got a ‘to try’ thing, which is slowly increasing in number and I never sit down and have a go through the tutorials or anything like that.

Paul: Yeah, I think the key is to follow a few key, key things and not try and follow too much information, and then just look at what everyone else around you, the people that you respect, in what they’re sending out and try not to get overwhelmed because there’s a lot of information out there.

Sarah: Dead right, there’s so many, it seems to be a new thing on Twitter to actually post those sort of links, day in, day out, which is really handy because there’s a lot of people who have a lot of good stuff on Twitter.

Paul: Oh twitter.com/boaglinks is the premier source of all this information, of course.

Sarah: Of course! (all laugh)

Ryan: Er, OK, so I think the final question to you, then Sarah, is, erm, what inspires you to pursue your personal projects?

Sarah: Erm, oh, that’s a difficult one. I kind of get inspired in strange places, when I came back from the Future of Web Design and Future of Web Apps, I kind of get inspired by other people, not necessarily the apps that they’re producing, or work that other people are producing, but I sort of feed off other people’s energy, strangely. If other people come away from something really, erm, excited about something, I tend to think ‘oh, yeah, that sounds like a good, like when Adobe Air came out, that was a kind of a buzz around that for a while and it got me thinking ‘um, what can you develop with that that would, you know, might be interesting to other people or that other, that other web designers might want to use?’ but that’s kind of what happened with my own app, Olive, it’s kind of on the backburner at the moment, but there was a problem that came up at work and it was coming up time and time again and I thought ‘there must be something out there that actually addresses this issue of, of erm, client management, so went around, couldn’t find anything and then ended up building it, and it was actually built more for me, rather than other people and when I sent it out to a few people, they really liked, and got into using it and, erm, it’s just kind of handy if you build something that’s, that’s great for you, but equally other people find interesting as well. It’s, erm, it’s a win-win, really. I mean, I use it all the time, and there’s other people who do as well, bu
t at the moment it’s, er, needs a lot of updating, because I’ve been so busy with client stuff, but maybe I should have put that first, but clients pay the bills unfortunately.

Ryan: Absolutely, absolutely. I think I, erm, I think I overthink things, so I think to myself ‘oh, I’d love, love for this to exist’ and then I think to myself ‘I could spend the next three years developing that’ and, and someone would do it better than me, you know and just finding time as well.

Paul: Yeah, I think it’s right what Sarah says, you’ve got to scratch your own itch, you’ve got to find something that you would want to use so much that you would spend that amount of time to build it, and then if it’s for you, it doesn’t really matter that much if no one else wants to use it because it does something that you want it to do.

Sarah: Exactly.

Paul: And it’s a learning process, you can choose any language. If you want to learn a new language, if you want to learn Django or Python or something, you could build it in that, just to learn that language, erm, and then send it out in the world, see if people use it.

Sarah: Exactly, that’s kind of what happened. I was learning quite a bit about Ruby at the time, because Olive, Olive’s built on the Ruby on Rails platform and it was so interesting just to get an insight into how different developing with Ruby is compared to PHP. That was just worth it in it’s own right, really because I find that I learn much better with real world examples rather than looking at a load of code. I find that if, if I ever get something like that, I have to take it apart, almost, and then try and work out how to put it all back together so that it works. I think I learn better by doing that and a lot of people do. If you going on to any of the tutorial sites now, there tends to be a lean towards developing an app or something small; I think on the Nettuts at the moment, website – do you guys know that one?

Ryan: Er, yes.

Paul: Yes, ah the Nettuts, oh yeah.

Sarah: Yeah, there’s a, there’s a sway towards actually building like login systems from scratch and things like that on there, where it’s actually showing you the code and then showing you how it works in real world situations which I think is really good, for me, I don’t know about you two, but I personally prefer picking stuff apart (laughs).

Paul: Yeah, absolutely. I usually start at the very lowest common denominator, like a user access system, and I’m learning CakePHP now which is, kind of a Ruby clone for PHP and instead of using their in-build methods which will do it all for you with build this, just write these classes and it’s like ‘No, it’s like the most basic thing I can do in this language, let me learn how to do it’, and I’ll learn that way.

Sarah: Yeah, yeah, that’s, I think when, erm, when I looked at using Ruby for, er, for Olive, I didn’t build it, it was built by a guy, a brilliant guy, Adam Cooke, but I was still really interested to know how it would work and how Ruby is different and the first thing I did was built a, erm, a basic recipe, sort of database thing with, it was off of a tutorial site and I think it’s great if it gives you just a little bit of insight into something that you might not have already realised or known about building your own stuff, then I think you have that sort of passion to go forward with it, you have that confidence to then think ‘oh, well I’ve done that tiny thing, maybe I can do something else with it. Whereas, if you’re doing it for clients, you don’t, you wouldn’t really venture into using another programming language that you weren’t comfortable with on a client site, unless you were a bit silly.

Ryan: Absolutely, absolutely. Paul told me a really funny thing, in between, er, when he told me he was learning CakePHP. He said, I’m trying to remember what it was that you told me, it was ‘if Ruby’s French, CakePHP is French with an English accent’

Paul: Yeah, its kind of the same, just not quite as elegant.

Ryan: Yeah, I thought that was fantastic, that was so fantastic, I made it into, I have some rotating quotes on my web-site, and that made it into my quotes, that was fantastic.

Much thanks goes to Simon Douglas for transcribing this interview so quickly!

Back to top

Listeners Questions:

Is Using Off-The-Shelf Software Wrong?

Jon Writes:

I guess my question is about the use of off-the-shelf software. I must admit I feel slightly uncomfortable using it at all. As a decent sized agency of 9 people, with our own very capable developers, I can’t escape the nagging feeling that we are “cheating” slightly by using an off-the-shelf platform at all. Although we adhere strictly to licensing requirements, most of our customers do not know that their stores are powered by what is essentially a ready made system, which we then skin, configure and populate.

What are your views about off-the-shelf stuff and the pros and cons of using it on client work?

Thanks and keep up the good work!

I think the main source of your discomfort is the fact that your clients don’t know you are using off-the-shelf software for their projects, which raises the question why not?

Your clients have approached you to provide them with a service they cannot perform themselves. Whether that is building a system from scratch or integrating and customizing an third-party system to meet their needs, you are still the expert.

There are very powerful off-the-shelf e-commerce systems, blog engines and CMS’s that should be thought of as weapons in your arsenal rather than “cheating”. Explaining to your clients why you are going to use a particular system for their project can be hugely beneficial. It shows that you don’t want to waist their time and money re-inventing the wheel.

Therefore, the pro’s are:

  • It meets there project aims
  • You are experienced with the system
  • It’s supported by a third-party team of developers who are dedicated to that one product and includes a vast community of other users who support each other
  • It can be implemented in a shorter period of time than building from scratch (i.e. cheaper for the client all round)
  • It’s a tried and tested system (You could even give your client a list of other successful companies that are using it)
  • It is also more than likely that a third-party product that has been around for several years is a more reliable and robust system than the one you develop in a couple of months.

That said there are always inherent risks in using anything third-party, whether it be API’s, frameworks, libraries or software and I have a general rule of thumb that I try to always adhere
to:

Don’t implement something you don’t understand!

If it breaks, it costs you time and money to fix the problem, and that’s once you’ve diagnosed what that problem is. The longer it takes you to fix the higher the risk that your client is going to lose confidence in your ability to deliver.

So take the time to do some dissecting and learn how to use your tools as fully as you can prior to implementation.

How do you price and quote different projects?

Jamie who’s just started up his own web development company is having trouble working out how to price and quote different projects and wonders if we have any tips that we’ve found helpful when quoting for clients?

One of the hardest things when starting out, and even for established businesses is finding your feet with pricing. I think the biggest lesson I learnt is not to under-quote just to gain the business, even though you are in need of clients. It makes no business sense to work for peanuts, you’re better holding off for a client who respects the work you do and pays honestly for that work rather than being a design machine churning out work just to make ends meet.

The other important thing I learnt in my first year of business is, clients who barter with your prices are generally bad news. We’ve all heard it, “if you can do this one at x-amount we have plenty of other work in the pipeline we want to use you for” – while this sounds tempting, 9 times out of 10 the promise of the further work never comes off, even if it does they would normally expect further work at the “cheap” price they paid you before, as you accepted it so you must be happy to work for that right? Wrong.

I always find it helpful to ask the client for a ballpark figure prior to laying out the full proposal, this negates you wasting time putting together the proposal of cost plus terms and conditions only to find the client wants to build ebay on a budget of £300.

I also find ballpark figures helpful because I find it easier to provide the client with options, even if they have a relatively small budget there is normally still something you can do, even if it is very basic – but it gives you a starting block to explain if their budget was a bigger they could bolt on a CMS system or have a better shopping cart, then explain the benefits of those. You’d be suprised how much the budgets are then increased by.

It’s all about providing the client with the best solution for their project at the end of the day, and if you think the best solution would be bolting on Expression Engine or the like, you need to give the client the choice to do this and expand their budget if necessary rather than cut them out of the equation because of it, it’s all about educating the client.

158. Home

On this week’s show: We share the highlights of SXSW, discuss home working, and interview Rob Borley about project management.

Play

Download this show.

Launch our podcast player

Housekeeping

Headscape still recruiting!

Headscape is still recruiting. We are looking for an enthusiastic, talented developer to join our team, working from of our offices in Hampshire. For more information see the job advertisement on Boagworld.

Back to top

News and events

The best of SXSW

Well, SXSW is over and I am back in the UK. But what happened at the conference? What was the big news this year?

That is actually a hard question to answer. There is so much at SXSW that it is almost impossible to get a sense of everything that is going on. Even if you could attend every panel that isn’t always where the real action takes place.

The real conference often happens at the parties and in the corridors. In fact, more than one spontaneous panel was started via Twitter, thanks to official panels being full.

Panels this year ranged from the downright dull to all out flame wars! One that I unfortunately missed was "Is Spec Work Evil!". However, Marcus attended and tells me it was particularly fiery. Personally, I am very much against speculative work as I have said before. However, not everybody would agree and the panel seemed to reflect this diverse opinion.

One panel I did make was Paul Annett’s amazingly inspirational talk on Easter Eggs and design twists. The talk focused on the little things you can add to your site to make users go ‘oooo that’s clever’.

Too often I neglect such ‘bells and whistles’ in favour of usability and accessibility. Paul demonstrated how these different priorities can sit side by side without compromising each other. He showed some great examples including the hidden arrow in the FedEx logo and the vines on the Silverback website.

fedex logo

The final panel I want to mention is ‘Being a UX Team of One‘ by Leah Burley of Adaptive Path. To be honest the title of this one was a little misleading (at least from my perspective).

What I took away from this session was that design should not be a solitary activity, solely reliant on the creative inspiration of one individual. Leah seemed to be arguing for a more collaborative approach especially at the wireframe stage. She proposed that all of those involved in the project should sit down together and hammer out the wireframe designs.

This addressed two separate problems we have been having at Headscape

  • The developers concerns at not being involved early enough in the process.
  • The question of who should do wireframing – the designer or the IA person.

Best of all Leah’s presentation was very pragmatic. She provided lots of practical approaches that encourage idea generation and collaboration. I highly recommend listening to the podcast of this when it is released.

Browser testing and IE6

In other news, there seems to have been a lot written about browsers this past week. Three stories in particular caught my eye…

  • .net Magazine seems to have hopped on the ‘dump IE6′ bandwagon – My opinion is the same as that of Jeremy Keith as expressed in last weeks show. It is not a matter of dropping IE6. We should instead being deciding whether we wish to offer it the same level of support as modern browsers. I am entirely in favour of providing IE6 with a basic stylesheet that avoids its shortcomings. However, I dislike the idea of dropping it entirely.
  • Microsoft has released SuperPreview this week that allows Windows users to test different versions of IE simultaneously. I have to say this looks like an impressive tool. It allows you to view IE6 and IE7 side by side. It also has many other tools that may also be useful. Support for IE8 and other browsers will follow and although it is currently in beta, I think it will quickly become an indispensable tool for Windows based web designers. Just a shame there is no mac support!
  • Finally, Sitepoint have written a brief outline of how to create the perfect browser testing suite. Ideally for those starting out it lists various online browser simulators, virtual machines and desktop browser emulators.

Browser testing continues to be a pain in the neck and I for one would be willing to pay for a decent way of streamlining this whole process. This is especially true now that IE8 has been officially released and we have another browser to add into the mix.

Screenshot of Superpreview

A simplicity case study

A few weeks ago I wrote about the importance of simplifying your website. Well, this week Gerry McGovern has written the perfect case study to support the argument I was putting forward.

Removing poor quality content increases customer satisfaction‘ talks about how the Microsoft website consists of a staggering 10 millions pages. Of those pages 3 million have never been viewed!

The post goes on to explain how the Microsoft Office team took a different approach with their site by removing irrelevant pages. According to McGovern…

By weeding the garden, the top task pages became easier to find. But just as importantly it became harder to find a minor task page when you were looking for a top task page.

In short, removing pages reduced noise. Disturbing though it sounds, I think we could all learn something from Microsoft’s example.

An introduction to Microformats

My final post today comes from Richard Rutter’s blog. It is basically an introduction to Microformats aimed at the non-geek. He wrote the post because he recently found himself trying to explain microformats to a client and could not think of a good post that covered the subject from their perspective.

Personally, I am not sure it is necessary to tell a client you are implementing Microformats. The cost of adding them is so small and the benefits so hard to explain, that you maybe better off just doing it.

That said, this is an excellent post and if you are struggling to understand the point of Microformats, this is certainly worth reading.

Back to top

Interview: Rob Borley on Project Management

Paul: So, joining me today is Mr. Rob Borley. Hello Rob.

Rob: Hi Paul, how are you doing?

Paul: Very well indeed. Good to have you on the show. It’s been a little while.

Rob: It has, It has. It’s weird hearing the show above you, um rather than being below.

Paul: Oh yes, because you sit upstairs, don’t you?

Rob: Indeed.

Paul: Do you actually hear it?

Rob: I do. It’s like have a little base bin ?

Paul: Awh. So, um, we have kind of been thinking for a little while that we need to get someone on the show to talk about project management. And the idea was we’d get some high profile web design project manager to come in and talk about web design project management. Then I realised, um, that I can’t actually think of any. You know, I really don’t know of any kind of web design project managers out there, other than obviously the people that work at Headscape.

Rob: Well, maybe there’s a gap in the market.

Paul: I think there is a gap in the market.

Rob: (unintelligible) celebrity project manager.

Paul: Well I think that’s somewhat of an oxymoron, but setting that aside, lets shift around a bit, yeah, so, um, so we thought, lets get you on the show. Um, now, you’re quite and interesting case because you started of as a techie.

Rob: Yes.

Paul: And you became a project manager.

Rob: Yes.

Paul: And, so, um, let’s start by talking about the role of project manager. How would you describe your core role? What is it that you do? I should know this I guess.

Rob: Well, you mean other than manage projects.

Paul: Ok, you just have to make a joke out of it. But you know what I’m getting at.

Rob: Yeah yeah. I mean, I guess, um, the main thing that we do is shovel shit, really. We deal with crap. You know, the main thing project manager would do is a filter between clients and the production team for the project. I mean, there are a couple of stages I guess. So you’ve got the planning part of the job, which is essentially working out what it is you need to do, um, making sure you got the results to do it, plotting a nice time line so they can all fit as far as having deadline. And then you’ve got the people said, because really project management is a people job. You need to know how to get the most out of all the people that are in your project team, um including the client. You need to include the client in your thinking, always. Yah, that’s essentially what we do.

Paul: Yah. It’s a people person thing. I always thought you were so charasmatic. Ok, so, I mean, I guess the question is, if you look at the kind of, if you look at Headscape, and the way that we’re organised, we’ve got four developers, four designers, and three project managers. I mean, that’s a lot of project managers. And, you know the question is, why, why have project mangers at all? Why couldn’t the designers and the developers do the job? Why couldn’t it be spread across multiple people? Justify you exsistance, Rob.

Rob: Yeah, this question kind of makes me nervous here. I feel like I’m re-interviewing for my own job. Not that I interviewed in the first place, but, I guess in one sense, if you were in a small project environment, you could almost get away with one person. If, you know, its a one person job, you could get away with them managing themselves for a limited amount of time. Um, but, as soon as you get beyond jobs which are more than one person, um, and go on for an extended period of time, you start needing to provide some glue to stick things together. You need someone whose got an overview of everything that’s going on. You know, the developers have got a very developer mindset about the way things happen. Designers are the same way, they know about the design stuff. Um, but actually translating what the client wants and feeding that into both areas and bring them together is what’s missing, if you don’t have a project manager.

Paul: So, to some degree, project management becomes necessary with scale. The bigger the projects, and the more complex the projects, then the more a need for a dedicated project manager.

Rob: Yeah, definitely. I mean, I guess the real role of a project manager in these situations is the facilitator. You’ve got all of these tools which are basically your resources, your developers, your designers, um, and you need to be able to enable them to work effectively together to produce what the end product is going to be.

Paul: So here’s a question that I didn’t pre-give you, in advance, which is always the best type. Why, why, why become a project manager? What made you – because you were heading up our technical development team, you were, you know, you were doing very well. Why did you feel the need to get involved in what you call shit shoveling?

Rob: Well, I think my main motivation was, Headscape was growing, and we started employing all of these younger, more dynamic, much more talented, better looking developers, that were basically going to show me up. So I figured that before I got shown in true light that I was going to need to move somewhere else. Um, no, well that’s partly true. Really, I think, its the people’s aspect that I’m really interested in. A good project manager is someone who is able to understand how his resources or how her resources work and how your clients work, and joining the two together. Um, while I quite like writing code really, I’m not passionate about it. So that side of it, you know, I reached as far as I wanted to go, and I really enjoy the people thing.

Paul: Ok. So what other, I mean, what other kind of characteristics do you think make a good project manager, obviously the people skills you talked about, what other, I mean if there are other people out there going well actually I’m not that passionate about coding, or I’m not that passionate about design, but I am passionate about the web, I do like the web design process, perhaps project management is the way I ought to be going. You know, what skills, what characteristics do they need, what personality traits do they need?

Rob: I think well, you need to be able to plan. Um, you know, planning is very very important. If you plan well, then your project will usually go well.

Paul: I like the cornification in that.

Rob: You have to be able to predict the future is helpful.

Paul: Yes.

Rob: A major part of what we de in the planning stages is assessing risk. You know, so, we’ve got what we’re starting with, we’ve got what we want to achieve, and we’ve got a time scale, now we need to work out what things might appear that are unforeseen, which are going to affect us reaching the time scale. So being able to foresee the future is helpful. Um, and so planning, being quite analytical and thorough. The logical background I have from being a programmer, a developer, is really helpful because you have to approach project management in a very analytical way, to make sure you don’t miss things. So there’s that side of it. And then there’s communication skills. You not only need to be able to communicate with a client affectively so they show that you understand what they want, um, and they understand where you are with the project, and they’re happy because a happy client makes everyone happy. But you also then need to communicate that with the various personalities in your team. You know, whether thats the developers locked up in a dark room with no social skills, or the crazy charismatic designers who…

Paul: You’ve just gone with stereotypes that so don’t apply. If I look at our team, no offense to our designers, they’re the ones that sit in the darkened room with their nose right pressed against the screen. And the developers are the ones that are crazy and never do any work.

Rob: (unintelligible) something about reading personalities. No, but you see my point. You’ve got these almost extremes, especially in the web, I guess, in the web world, you’ve got these extremes of personailities which somehow you need to be able to communicate with and put it all together and so, yeah, that’s an important skill. I think the third area, is to be quite relaxed about life. Because things will go wrong and do go wrong, it doesn’t matter how well you plan and how good you are at predicting the future. Stuff will appear that is completely unforeseen and will completely throw (unintelligible). And everyone gets really upset and people will shout at you and it goes a bit nuts. Um, and if you go nuts as well, you project team falls apart, because they look at you as the calm rudder in the storms of life. I can feel my other project manager buddies laughing at me, um, but if you’re calm and you can not get stressed at that but actually see, try and find a clear path through a very stressful situation, then really helps.

Paul: I would so be the worst project manager in the world. I’ve got the attention span of a newt, I’ve got no organisational abilities and I get stressed at everything. So overall, I think I’d fail.

Rob: Yeah, stick to web celeb.

Paul: Yes, I’ll come up with some other title that sounds good. Um, ok, so you talked about this really is, I can honestly say, a foreign area to me. Right? You talk about planning a project upfront. I’m not a planning person. Right? And there seems to be so many variables involved in a project and so much as you say, that can potentially go wrong. How do you plan it? I mean, you know, the kind of thing that you always talk about, when you talk about project management is endless gantt charts that seem to be outdated in about 5 minutes, sort of kicking a project off. How to you effectively plan a project?

Rob: Um, well, we do use a gantt. We always start a project with a gantt. And, um because it seems like thats what project managers are supposed to do, so we justify the time with a gantt. Um, but you do need, um, I think assessing risk is something that is vital in successful project management. Its something that we’ve been doing at Headscape, um, increasingly more over the last year or so otherwise this need to actually spend time highlighting what could actually go wrong here. So, you look at, I’m not going to be able to think of any examples now, but a particular, let’s say you building a shop or something. So potential things which could delay that project would be: the client not getting around to telling you what the products are on the shelf and content population is a big risk on meeting a project deadline, because it is out of your control. So, its like, I need the content by this date, and he needs to put the content in by X date. If the client doesn’t do it, there’s nothing you can do about it.

Paul: I’m guessing integration must always be a big risk. Integrating with third party applications.

Rob: Exactly, so if you’ve got some sort of third party database or a web service you’ve got to pull in, something that you’ve done a bit before, but you don’t know anything about, that’s a risk. Because you can guesstimate what’s going to happen, but its unforeseen. And so, the trick is basically, to find all the tasks that have these risks and then multiply (unintelligible) an hour by some random number. And then make the rest up as you go along.

Paul: So what about once the project gets going, how, what techniques and tools maybe do you use for monitoring and controlling the process and trying to keep on top of everything.

Rob: Yeah, I mean, there are lots of tools out there, obviously, lots of funky web-based ones, um, there is no substitute for talking to you team. Um, trying to (unintelligible) email or basecamp or something is impossibly without talking to you team. So, communicate. It’s a big part of what we do. You have to talk to the people doing the work, you have to talk to the clients, um you have to keep the lines of communication open. Um, but as far as actually keeping track of what’s going on, we do use basecamp, um which is great for managing lists, basically, you manage lists. So from our gantt shell, we’ll break it up into a series of tasks if you like, wide areas, um, and then, (unintelligible) ask people to add comments to them and take them off and then we’ve got kind of an overview of where our project is. Um, and hopefully from there, and when we’ve got the gant shell, we’ve got some dates, some milestones and reminders like you should have done this by then, um and so, you use that to kind of keep track of where you are.

Paul: Cool. What about, so that’s kind of dealing with the internal side of things. What about when it comes to the client, I mean, you talked about, you said earlier, a happy client makes everybody happy kind of thing. So what makes a client happy? What are the things that really, or perhaps turn it around the other way, what are the things that really piss of a client and where can it really go wrong?

Rob: This is really where the people side of it really comes in because every client is different. Some clients want you to talk to them for five hours a day, hold their hand, you know, spoon feed them, and some clients just want to know when it’s finished. So initially, when you’re kind of trying to assess your project team, if you like, your resources and what you’ve got, assessing the personality of your client early on, will really put you in a good place. Um, but, I guess, general principles, if you’re honest, it helps. Um, so, be realistic about what you’re telling your client is going to happen. Don’t promise the Earth by yesterday. Because then you won’t deliver and then they’ll get upset. If there’s going to be a problem, if things have slipped for some unknown reason, then tell them as soon as you know. Tell them as quickly as you possibly can. Um, manage their expectations is kind of the phrase that we use a lot. You gotta manage you clients expectations so that they’re not expecting something that you can’t deliver. And um, and then that limits the amount of upsetness that they get.

Paul: Slippage is a big one, isn’t it? This kinda whole area of things like, you know problems you kinda face, things, like slippage, scope creep, non-delivery, I mean, how do you have any kind of broad techniques for dealing with these kinds of things, or is it just kinda communications thing again.

Rob: It’s mainly I think a communication thing again. Um, part of the planning stage is trying to asses these risks and so you try and build in contingency to cope with those, and if you’re building enough contingency, you deliver the project early and that makes everyone really happy, even if its a long project, you deliver it early, you’ve exceeded their expectation also. Um, so I think, if somethings going to slip, I think you should say you’ve got to be honest. Sometimes things are just out of your control, so you’re two weeks before the end of a project, you in the middle of snagging, your lead developer goes down with appendicitis. There’s nothing you can do about that, and so you just need to communicate with the client and hope they take it well.

Paul: So wishing everything works out, I’m loving that approach. Ok, so, um, let’s finish of with a piece of generic advice. Either people starting out in project management or those that have had project management foisted upon them. You know, whats the kind of one piece of advice that you would leave for people?

Rob: Get to know your team. I think that’s the main thing I would say. Um, its kind of like, when you drive you car, you’re environment is a very organic, dynamic thing, you know what it really what’s going to happen and the only thing you’ve got to get you through it is that you understand you car. You know almost instinctively how it works, how to drive it it, if you get to that situation with your team, then whatever the project throws at you, you kind of, you can deal with it. If you understand how you client is going to react to a certain situtation, you can intincfully deal with it. And it keeps the stress levels low. You need to find ways of managing your stress levels.

Paul: There you go, that’s great advice. Thank you vert much for that, it was wonderful. I really appreciate you coming on the show.

Rob: My pleasure.

Thanks goes to Meredith Marsh for transcibing this interview.

Back to top

Feature: Home Working

I was recently contacted by a friend of mine Marieke Guy about writing a guest post for her blog on remote working.

I have been working at home for over 7 years now and am a great believer in the benefits. However when I actually sat down to write the post, I realised just how long it has taken me to find the right way of working.

As a large number of people who listen to this podcast work from home, I thought I would share my experiences to date and my hopes of where remote working will take me in the future.

The reality of home working

Back to top

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.