You're a failure: Deal with it

Every website has points of failure. It is inevitable. The question is do you know what they are and are you doing something about them?

Nobody likes to think of themselves as a failure and no website owner likes to dwell too much on the shortcomings of his website. However, all websites have weaknesses and it is important we know exactly what they are in order to do something about them.

What is more, all websites develop new weaknesses over time. As content is added, structure is changed and designs are tweaked, we introduce problems into our sites that were not previously there.

We therefore need a system in place that continually monitor for failures so that they can be addressed quickly before causing too much damage.

image of broken chain

Torian, Shutterstock

Implementing such a system does not need to be onerous. It simply consists of three simple reviews that should take place on a monthly basis. These are…

  • Monthly user testing
  • Identifying dropout points
  • Analyse search queries

Let’s begin with user testing.

Monthly user testing

Steve Krug’s latest book Rocket Surgery Made Easy takes usability testing in a radical new direction that is both perfect for identifying the constantly evolving weaknesses in our sites and also inexpensive to implement.

He proposes an ongoing programme of quick and dirty user testing that takes place every month. The idea is that on a set date each month you schedule a morning of user testing with only 3 participants.

Your entire web team watches the user testing and analyses the results over lunch. By the end of lunch you will have identified the biggest problems that need to be addressed before the next month’s testing.

Image of Rocket Surgery Made Easy

Jason Alley, Flickr

This is a great approach for detecting and eliminating problems on your website. It is…

  • Lightweight – Only requiring one morning a month for testing and debrief.
  • Regular – Ensuring that it picks up on problems that creep into the site over time.
  • Action orientated – By the end of the session you have a plan of how to tackle the failings in your website.
  • Fixed – Because the user testing is always on the same day every month it is less likely to be bumped for more ‘important‘ things.
  • Prioritised – With only a short time to test and debrief the emphasis is placed on the most important failings rather than being caught up in nuances.

Although user testing is useful it should not be used in isolation. Testing only 3 participants enables lightweight and regular testing, but it does have its limitations. Ultimately 3 people are not going to be representative of the whole and even if they were, they are not interacting naturally with the website. For that you need to look at web statistics.

Identifying drop out points

Website statistics can be very enlightening when used correctly. Unfortunately few people know what they are looking for and so either give up try or never get past page views and unique visitors.

One aspect of web stats that is particularly interesting is exit points. Where do users leave your site? This may help identify potential points of weakness in the site and areas you wish to test in your next user test session.

Most statistic packages make it easy to view a list of top exit pages. However make sure you are viewing pages with the top percentage of exits, because popular pages will be exited more often. Look for pages that are popular but are also exit points. These are the biggest problem areas. Google Analytics actually allows you to view pages that meet this exact criteria.

Google Analytics - Top exit pages

Once you have this list ask yourself the following questions?

  • Is this the final page in a call to action process? For example is this an order confirmation at the end of a purchase process. You would expect pages such as this to be a typical exit point.
  • Has the user visited any other pages before exiting? If the user has viewed only this one page then the chances are they were simply at the wrong site. To make sure check the dwell time. If they were only on the page a few seconds before leaving then it is fair to conclude they had arrived by accident. Also check how they arrived on the site. If they came via a search engine, what search term did they use? If the term wasn’t relevant to your site then don’t worry.
  • What type of content does the page contain? If the page is a blog post for example the chances are the user was more interested in the content than anything else you offer. They will read the one article and then leave. Obviously this is not what you want and should work hard to encourage them deeper into the site. However, the reality is that pages of this type will have a higher exit rate.
  • Is the bounce rate significantly higher than elsewhere on the site? If so this could indicate a weakness in the page.

If users have viewed multiple pages and then given up on a particular page, it is a problem which needs addressing. Possible problems could include…

  • No obvious next steps – Are you telling the user what to do next.
  • Too many optionsToo many choices can cause users to give up.
  • The content fails to convince – Is the content of the page telling the user what they want to hear, or are you saying something that alienates them?
  • Too much content – Is the page packed with large amounts of densely written copy. This can put users off.
  • The content is not relevant – They have arrived from a search engine query and the page hasn’t provided what they want. Instead of looking elsewhere in the site they have returned to the search engine to view another result.

Unfortunately although web stats can be very good at identifying problem pages it is not so good at diagnosing the cause. That is why it is important to user test as well.

Of course another possibility is that a user has given up simply because the site doesn’t appear to have what they are looking for. That is where you need to analyse search queries.

Analyse search queries

What users searched for provides an excellent insight into potential failures of your website.

Take for example the top search queries that lead people to a page with an exceptionally high bounce rate. Which of those queries cause most of the bounces? What are the user expecting to find on the page and do not? The page must be relevant in someway otherwise the search engine wouldn’t refer them. However, perhaps the way you are presenting the information is wrong. Does the search term give any indication of how you could be presenting things better?

What about the terms that create the highest bounce across the site. Sometimes users find themselves on a site that a search engine believes is relevant but doesn’t directly address their issue. Could you retailor your content to more directly address these search queries?

Keyword search terms as shown in Google Analytics

However it is not just external search engines you need to be looking at. What about your internal search engine?

When a user arrives at your site after entering a search term into Google, you can be sure that at least some content on that subject exists. Otherwise Google would not have referred them. However, when a user types something into your site search, there is no guarantee it will be a topic you have addressed at all. This is a perfect way to identify content lacking from your website.

Repeat each of the top searches yourself and look at the results. Are you addressing the search terms directly? Are you addressing them at all! If not you have identified a weakness that needs dealing with.

Rinse and repeat

The secret to success when it comes to irradiating the failures on your site is to establish a monthly cycle of work. Each month you need to user test, delve into your web stats and analyse your search results. By combining these three techniques you should be able to establish a programme of work for the coming month. By repeating this process month on month you can slowly evolve your site so that its shortcomings have less and less of an impact on conversion.

Of course, this is not all that can be done to identify problems with your site. These are simply those that have worked best for me. What about you? How do you find the shortcomings on your site? Do you even do this kind of ongoing maintenance? Let me know in the comments below.

Web Design News 26/07/10

This week: Why the fold doesn’t matter, big wins with quick changes and what’s the best size for a search box?

Life below 600px

If there’s one thing that clients mention that makes designers and developers see the red mist it’s the concept of ‘the fold’. A popular concept from the print era, when newspaper headlines were displayed at the top so that they could be read when the paper was folded, it migrated to the computer age and denotes where content disappears below the bottom edge of the screen. The majority of designers know that most users know how to scroll, and the increase in screen resolutions mean that the fold is a vague concept rather than a defined limit, yet we often struggle to explain this properly to our clients when challenged.

Graphic showing the location of a mouse scrollwheel

Paddy Donnelly has written a fantastic article which is a physical explanation why the fold doesn’t matter, and why designing for a fold may even damage your site goals in certain situations. It’s written in a way where you could send the link to your client and let them learn exactly why the fold doesn’t matter as much as they think it does. So the next time your client asks where the fold is, send them here!

Big wins with quick changes

Lather, rinse and repeat. If there’s one thing shampoo bottles have taught us, it’s that we shouldn’t just do something once, we should keep trying until we’re happy, or our shampoo runs out. In the web design world, iterative design is an effective method of ensuring your site is effective, and responds to user feedback.

Ryan Carson shares a recent iteration of the Think Vitamin Membership site, explaining how the original wireframes how they reworked the wireframes and the site based on this feedback and made some changes to their microcopy which resolved the issues they had in a reactive fashion in a short amount of time.

What’s the best search box size?

Search is an important component of any large website, especially online retailers, yet little thought really goes into how that search box works, and how many characters should be viewable. Luckily for us, Christian Watson has trawled the top 30 websites out of the Internet Retailers top 500 list, and determined the average number of characters that these sites use in their search boxes.

Search boxes from major online retailers

Wether this actually makes a difference or not is yet to be seen, but when that time comes when you have to decide how large to make that search box, remember this little piece of research which will help you make up your mind.

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.

Why I don't get SEO

I don’t get why people invest in SEO. I am not trying to start an argument. I just want to explain my doubts so somebody can correct me.

I like to think of myself as an intelligent guy. I have worked on the web since 1994 and like to stay informed. However, over that time I have never understood website owners’ obsession with SEO.

Many organisations invest vast sums of money in SEO companies that promise to improve their rankings. Although SEO can make a difference, I am far from convinced it is the best way to spend your marketing budget.

Below are five reasons why I have my doubts. My hope is that people can convince me I am wrong in the comments. We shall see.

A continual investment with no guarantees

The thing with SEO is that it is not a one-off cost like many believe. It is not just a matter of getting to be number one for your chosen keywords, its about staying there too. This involves an ongoing investment.

Also unlike pay-per-click (PPC) advertising there are no guarantees. There are SEO companies who guarantee you the top spot, but they are lying. You pay your SEO company in the hope they can improve your placement, but a good SEO company will not commit to how much.

It is a bit like buying a newspaper ad, but being given no guarantee as to what page it will appear on or how big the ad will be.

Classified ads in a newspaper

Image Source

At least with PPC you know how much you will pay and what you get in return.

You’re manipulating the system

My second concern is that essentially SEO is about playing the system. Google exists to connect its users with the information they require. They have a sophisticated algorithm to do that. It is also an algorithm that is getting better all of the time.

SEO on the other hand is about creating as much exposure for your website as possible. They do this by guessing what the Google algorithm does and using that in your site’s favour.

The problem is that the algorithm is unknown to anybody other than Google and it changes all of the time.

Hacking Circuits

Image Source

To me it seems more sensible to work with Google’s known goal – to provide great content to its users, rather than trying to manipulate a system we do not fully understand.

Instead of spending money on SEO, spend it on producing better content that provides Google’s users with more value.

It can damage the user experience

I am not saying that SEO does not work. I am saying that it is not worth the cost. That cost is not just in terms of money spent on SEO. It is also in user experience.

I have worked with a number of SEO companies over the years (at the request of our clients) and it has always ended up damaging the user experience.

For example, SEO often leads to an excessive amount of copy, changes to the code order (that creates problems for screen readers) and keyword heavy navigation (which reduces scanability).

Example of keyword stuffing

SEO may increase the level of traffic to your site. However, it often undermines the conversion rate.

It is a passive form of marketing

It is not just SEO I have a problem with, it is the emphasis on search engines.

Website owners seem obsessed with being ‘number one’ on Google. However, it is not a particularly effective method of marketing.

Search engines are passive because they require the searcher to have a pre-existing need for your product or service. On one hand this makes search more targeted because it only reaches people who are interested in your product. On the other, it does not allow you as a marketeer to create a need or raise the profile of a new brand or product.

Father and son sleeping on a counch

Image Source

When compared to social media or other forms of advertising, investing in SEO seems very passive.

It carries no weight

My final problem with SEO is that it lacks the weight of personal recommendation. By focusing on SEO you are merely shaping your site to cater for an algorithm. You are not making your website appeal to people.

Trying out http://www.flairbuilder.com on the recommendation from @boagworld

Instead, I would invest in making your site better for users and encouraging them to recommend it through social networks and linking. This puts the weight of personal recommendation behind your site and we all know that word of mouth is the most effective form of advertising.

Conclusions

Let me say it one more time – I am not questioning whether SEO works. However, it is my belief there are better ways of spending your money.

I believe investing in your users brings a substantially better return. It increases conversion, encourages word of mouth recommendation and ultimately improves your ranking through links back to your site.

My recommendation to clients is that we build their websites to be accessible to search engines but tailored towards users not search engines.

The question is – am I wrong in that advice, and if so why? Enlighten me in the comments.

Does Google personalised listings affect your ranking?

Google has added a number of tools that allow users to personalise the search results they see. The question is – does this affect how you approach SEO?

I recently received the following from Peter Bennett:

In response to show 199, you said on some of your specific search results, headscape has been pushed to the top. However since show 199 I have since seen 4 new features at the end of each search result that appear when logged in.

I don’t know how long they have been there but i think they deserve a mention. These features are:

  • Where You can Promote listings – which will then place the selected website at the top of your personal google results.
  • You can also ‘demote‘ any websites which you previously Promoted – Which google call Restore
  • You can also add comments for each individual listings which other users can see.
  • Finally you can remove – this will totally remove the chosen listing from your future search results.

In my opinion (although I am not sure), if listings get promoted numerous times by different users, maybe this could affect each listings search position in the long term with Google being able to collate each users preferences.

What do you think?

Google personalised search results

These are exactly the features I was talking about in Show 199 and they have actually been around for a while.

As to whether Google will use these features to inform their rankings, who knows! Even if they do it will be in a minor way. Only the smallest fraction of people searching on Google will use these tools and so Google will not rely too heavily on them.

Bizarrely there has already been extensive debate about whether these features will impact SEO. From my perspective it is a pointless discussion.

Too many website owners spend too much time and money obsessing about Google listings. I am not denying that SEO works. It is possible to manipulate your rankings. However, I would argue that the return on investment is non existence.

SEO building blocks

I was recently talking to one website owner who ran an ecommerce site. He spent thousands of pounds on trying to improve his placement on Google. He succeeded, but he calculates it made him less than £1000 in extra revenue. In short he made a net loss.

I would argue that the only SEO needed, is work you would do anyway. That includes writing relevant, useful copy and ensuring your website is accessible to the broadest possible audience.

At the end of the day none of us will ever know how Google calculates its listings. However we do know that Google wants to connect its searchers with the best content out there. Lets work on making our content the best and making it accessible. Google will do the rest.

199. Time to generalise

This week on Boagworld: The changing role of web designers, Colin Firth on content and Becky Jones talks about the changes at Google.

Play

Download this show.

Launch our podcast player

Having trouble listening to 199?

Housekeeping

Next week is our 200th show! Hard to believe isn’t it.

To celebrate this momentous achievement we are going to do a 12 hour live podcast marathon.

The show starts at 10AM on Friday the 12th February and finishes at 10PM that evening (times are UK based). We have too many guests to mention, but lets just say you will not be disappointed!

To listen to the live show go to boagworld.com/live/.

Obviously we will not be recording the whole show but hopefully will release edited highlights over the coming weeks.

Back to top

News

SVG is back?

There are a lot of articles this week about SVG. A List apart describes SVG as…

Scalable Vector Graphics (SVG) consist of circles, rectangles, and paths created in XML and combined into drawings on web pages. You can apply solid colors, gradients, and a sophisticated number of filters to SVG—although not all browsers implement all filter types. You can incorporate text, as well as images, and you can copy and clone your SVG as much as you want. Mostly, we use SVG for graphics programs, charts, illustrations, or animations.

In principle SVG has always sounded like an exciting tool. However it became a casualty of the browser wars, where support was patchy at best.

It also was somewhat surpassed by Adobe Flash, that became the standard for vector based graphics.

However, browser support has significantly improved and so we are seeing more interest in the technology again. This week alone there are articles on both A List Apart and Sitepoint.

Although it is interesting to read what SVG can do, I have to confess I do not understand the continued interest in this technology. I admit I am no expert on the subject, but it strikes me be that SVG is somewhat pointless for three reasons…

  • It’s still not supported natively in Internet Explorer. Although there are ways of overcoming this, it is a significant barrier to adoption.
  • The near universal adoption of flash makes this a far more obvious choice. Also, now that Adobe have opened up the platform many of the old arguments against flash are less relevant.
  • All modern browsers now support page zoom and so there is less need for a technology whose primary benefit is its ability to scale.

Perhaps I am missing the point and if so please correct me in the comments. However, the only ray of hope I see for SVG is Apples stubborn refusal to add flash support to devices like the iPod Touch, iPhone and iPad.

The best products sell themselves

When I saw the title of Andy Budd’s latest post ‘The Best Products Sell Themselves‘ I was ready to disagree with him.

I thought Andy was going to claim that if you have a great product you do not have to promote it. I thought he was going to argue that in the age of social networking, word of mouth recommendation was enough.

Instead I read a passionate article about providing a delightful experience that inspired and challenged me…

To sell products in a networked world, you need to differentiate yourself by more than just brand attributes and a check-list of features. You need to create remarkable products that rise above the competition and get noticed. Products that your users will rate, recommend and tweet about. In fact, what you need to create isn’t a product at all, but an experience.

He goes on to write…

Mediocrity just doesn’t cut it anymore. Instead, we need to create products that sell themselves. Does this mean that marketing no longer has a place in the networked society? Far from it. Marketers often understand customer needs and pain points better than anybody. In fact, this can sometimes be the cause of frustration in itself. I know plenty of people (myself included) who’ve been wooed by the notion of integrated phone, TV and Internet services only to find yourself dealing with completely separate business units and billing systems. The marketers were ahead of the curve. It’s the product that was lagging behind.

The idea of delighting your users by going above and beyond expectations is something that has been very much on my mind at the moment. It is something I am keen to introduce more into the work we produce at Headscape. Andy’s article could therefore not have been more timely.

I am reading a book at the moment called Made to Stick. In this book it gives the example of a departmental store that prides itself on delighting its customers. They give two examples in the book. The first was a member of staff who ironed the shirt for a customer going to a business meeting. The second was of clerk who gift wrapped items bought from a competitors store.

This is the kind of exceptional service website owners should be incorporating into their websites, and web designers should be providing their clients.

The principle of proximity in web design

I seem to be featuring a lot of posts on the basics of design recently. I think this is for several reasons…

  • Everybody involved in the web has to do some elements of design.
  • There are a lot of people listening to the show who are just starting out.
  • The website owners listening need to understand design principles if they are to work with a designer.

This week’s contribution to the cause is ‘The Principles of Proximity in Web Design.’ It is essentially a post on layout. It takes principles that have existed for a long time in print and applies them to the web.

It is a solid introduction to layout and tackles issues such as:

  • Whitespace
  • Visually grouping elements
  • Creating visual hierarchy
  • Improving scanability
  • The use of grids
  • Leading the user

The article concludes by summing up the benefits of understanding these principles…

Proper visual hierarchy by way of proximity helps users delve deeper into your website without worrying about where they’ve been or where they’re going.

They’ll always feel comfortable, and they’ll get to the most important sections of your website quickly and efficiently.

A worthwhile read for anybody new to design and a useful reminder to those of us who are old hands.

Google is changing and it will affect your website

Have to noticed that Google has been changing a lot recently? Probably not. You may have noticed the fade effect on the homepage. However, there are many more subtle and yet significant changes going on.

In an article for boagworld Becky Jones outlines some of these changes and how they may affect your website.

Changes include the introduction of…

  • Real time results
  • Breadcrumbs
  • Personalised search (even when not logged in)
  • Regions
  • Search features in the search bar
  • Anchor links in search results

What is significant about the list above is that they each have an influence on your rankings.

These changes really are turning the world of SEO upside down and having an influence on how websites are built.

However, what interests me the most is the new prominence of real time results. With posts from Twitter being placed at the top of listings, this makes social media a crucial component of search engine optimisation.

If you care about your website’s ranking (which we all do) then this is a must read.

Back to top

Feature: Website owners need more than web designers

Why is it many website owners are changing their web designer even when he or she has built them a great looking, usable website? What more are they looking for?

Read ‘Website owners need more than web designers’

Back to top

Colin James Firth: Content is King

If ‘content is king’ then the designer is like the King’s tailor – there to make the King look fabulous without taking any of the limelight for themselves.

Read ‘Content is king’

Back to top

Google is changing and it will affect your site

Google are never one to rest on their laurels, and the past few months have seen a lot of changes to Google’s search pages that you might have easily missed.

Some of the changes at Google are more visible than others, and some more useful than others, but it goes to show that Google aren’t quite ready to let things stagnate just yet after the launch of Microsoft’s Bing.

Realtime results

OK, so maybe you have to be using another search engine to miss it, but a list of recent search result changes would be incomplete without mentioning this big one.

For some search terms Google are now displaying realtime results: effectively results from Twitter, Facebook, and other social networks. Undoubtedly this will have an effect on search engine optimisation, but whether that means more up to date (and more relevant) results are being returned or simply people will spam Twitter to be featured at the top of Google’s search results remains to be seen.

google realtime results

Site owners might also start registering their search keywords as a Twitter account, in the same vein of buying web site URLs with keywords to get their keywords at the top of the search engine results pages. If this happens, this could drastically change the way Twitter (and Twitter username choices) is seen.

Breadcrumbs

For those web site pages that contain breadcrumbs, Google are starting to show them underneath the search result listings. It’s not available just yet with every site, but for those listings that do contain them I can see this feature being particularly useful to the end user, showing for example direct links to a product’s category for an online shop’s listing.

google breadcrumbs

Web site owners can take advantage of this now by introducing breadcrumbs to their sites on any relevant pages. It’s always worth adding them to pages, as even if Google don’t add them to your site’s listing, it’s good practice to add them anyway because breadcrumbs not only improve usability but they could also help with your search engine ranking.

Personalised search for everybody

Google Personalised Search now works even for people who aren’t logged in. This is a big one for search ranking, as this might result in your site getting a different ranking for each visitor who performs a search.

If a result has been clicked a number of times, then that site will start to appear higher up in the search rankings for that visitor, with the user’s search and click activity being stored for 180 days. This will mean that you don’t need to be logged in and have search history enabled for search results to be tailored to your habits and preferred sites, which will result in more more relevant searches in the long term for more people.

But this is bad news for web site owners who care about search engine optimisation: you can no longer be certain where your site will rank. You can have an idea, but if searchers click on other sites, your link might be pushed from page one to page two without you knowing about it.

Region

Another useful one for users if they want to know at a glance which country a web site is based. Web site owners that are registered with Google Webmaster Tools can now set their geographical location, which is displayed next to the page URL.

google location

The region is only shown for results that don’t have country top level domains (for example .com and .net), and the region you are searching from isn’t shown (so if you’re searching from the UK, web sites set as being from there won’t show the UK region name).

This feature, however, could also be confusing if it doesn’t work properly. If a site owner sets their site to be based in the United States but it’s got worldwide appeal, potential visitors from other countries might be turned away before they even visit. So this is a great feature, but it’s certainly one to be used wisely, to ensure you get the right target audience and don’t turn anybody away who might otherwise be interested in your site.

If you want to set your web site’s region, you can do this in Google Webmaster Tools by selecting Site Configuration > Settings > Geographic Target.

Search features in search bar

Those handy search features that Google provide are now available in the search bar of the google.com homepage.

Search for “london weather” and get the weather in London for the next four days. Enter for “diaphanous” and find out what it means. Type in a unit conversion or maths sum and get the answer. All displayed at the top of the auto-suggest box without having to wait for the results page. You can also type some site names such as “Twitter” and the twitter homepage is suggested at the top of the list.

google weather

This update is only available on google.com, so if you’re not based in the United States you’ll have to click on the “go to google.com” link before this works.

In addition to this, the “Google Search” and “I’m Feeling Lucky” buttons are now displayed inside the auto-suggest box. This is a tiny update you barely notice, but it’s also an update which makes usability that little bit better. For those who don’t press the return key to perform a search, the buttons are now visible and selectable straight away, rather than hidden underneath a drop down box that needs to be closed before they can be clicked.

Anchor links in results

For those pages with internal anchor links, Google have started to show these on search result pages. In addition to this, a “Jump to” link is also shown in the result if the relevant area of the page is after an anchor.

It’s hard to say how Google decides which listings to show these with, but chances of having them for your site’s listings are higher if you use semantic anchor names, show a table of contents, and logically split the sections.

Local public transit next to location

For major attractions, the location and map details are starting to show nearest public transit details.

google pubic transit

There probably isn’t much you can do to influence your business or premises containing these details, obviously it’s very location specific. But it wouldn’t harm to submit your site and business details to Google Maps and ensure your full location details are completed.

Bigger image results thumbnails

This is a small change to the image thumbnails that appear on the main search results page. There’s now a new layout which includes larger images, depending on the quality of the thumbnails.

google image

Lessons to be learnt from the new Google homepage

Have you noticed the new Google homepage? It is now the simplest it has ever been. I believe there is a lot we can learn not only from this simplicity but also to how Google has achieved it.

There is a lot of debate about the new Google homepage with its fading of secondary content. It amazes me that some web designers see it as a mistake. Personally it perfectly sums up my attitude towards simplicity in web design, and I would like to see more website owners have the confidence to follow suit.

However, as Leesy points out in the Boagworld forum, it is not just the simplicity of the google homepage that is exciting. It is also the way they have achieved that simplicity. It is their attention to detail.

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?

In many situations the decision to develop in-house or outsource is not down to you. Either an internal team already exists, or you are forced to outsource because you cannot fund in-house staff. However, occasionally you will have a choice. How do you decide between developing your website in-house or outsourcing to an external agency?

Lets take a moment to compare the choices.

Illustration of two people holding placards. One reads 'Vote for IN' the other reads 'Vote for OUT'

Using an in-house team

Using in-house staff provides a number of benefits…

  • Internal teams are more cost effective for long-term projects and ongoing maintenance.
  • Because in-house teams work within the business they can understand organizational objectives and target audience, better than an external agency.
  • An internal team is committed to evolving the website over time. They are constantly looking for ways to improve the site.
  • An in-house team is able to promote the website internally and ensure it does not become neglected.
  • Because an internal team is not juggling multiple clients they can (if well managed) be more responsive than an external agency.

Outsourcing to a web design agency

However, outsourcing can also bring some substantial benefits…

  • Outsourcing is more cost effective for short projects where the expenses of hiring, salary, training and equipment would be prohibitive for an in-house team.
  • An external agency brings a fresh perspective that institutionalized in-house teams cannot offer.
  • External agencies have a broader perspective of the whole industry, rather than what is happening within a single company.
  • An external agency needs to constantly ensure it is cutting-edge to stay competitive. This ensures that the quality of work is consistently high.
  • Because external agencies tend to be larger than in house teams they have more specialized and highly skilled staff.

The choice

There are good reasons to go with either approach. It comes down to two things, the length of the project and the funding available. If your website needs constant development and will evolve on an ongoing basis then an in-house team may be more appropriate. Of course, supporting an in-house team can be expensive. There are the initial costs of recruitment and equipment, as well as the ongoing expenses of salary and training. For shorter development projects the benefits and cost savings of outsourcing may outweigh the convenience of an in-house team.

In reality, the decision isn’t between internal or external. There is no reason why you cannot combine both approaches. For example, an external agency could be used for development work while ongoing maintenance could be handled by an internal web editor. Equally, you could do the bulk of development internally, but bring in external agencies for specialist work such as search engine optimization or user testing. This hybrid approach works well because it combines the strengths of both in-house and external.

This is an extract from Paul’s book – The Website Owners Manual

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.

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.

Rent a room at Headscape

Unfortunately our previous tenant has moved out so we now have a spare room available at the Headscape office. If you fancy working alongside a group of amazing designers and developers in the heart of rural Hampshire, read on.

Headscape has a gorgeous converted barn in the beautiful Hampshire countryside. It is a truly inspiring place to work especially for those seeking to escape the rat race.

We are currently looking for a freelancer or partnership interested in renting a spacious room at the Barn. Not only will you benefit from the wonderful surroundings, you will also get to work alongside some the brightest minds in the industry (if we do say so ourselves!).

What you get

We have tried to keep things simple. The monthly rent includes everything with the exception of your phone line*. This includes…

  • Your own private room
  • A desk and chair for your new office
  • Free coffee and tea
  • 24 hour access with your own key
  • Use of the meeting room
  • The use of the kitchen
  • A lovely view over fields and forest
  • A fun and vibrant working environment!
  • An invite to our summer BBQs :)

* There is an existing phone line installed. All you need to do is get it transferred.

Location

Our offices are in Lockerley‎, Hampshire. Lockerley is a lovely little village with all mod-cons. These include exciting attractions such as…

  • A village shop
  • A pub (nearby)
  • A village green
  • A postbox

What more could you want :)

The cost

It’s £336 per month, and you’ll need to pay a one-month deposit (to cover furniture, etc).

Interested?

If you are interested in learning about having an office at the Barn then call Paul on 07760 123 120 or email [email protected]

10 ways to Battle Site Bureaucracy

Running a large institutional website is frustrating. Your site is often held back by internal politics and bureaucracy. Let me show you 10 ways to cut through the crap and get results.

My recent post ‘10 harsh truths about corporate websites‘ generated a huge number of comments both on my own blog and on Smashing Magazine. I seemed to tap into an undercurrent of frustration that exists within the industry.

However, although there was a lot of agreement about the points I raised, there was also resignation. There was a feeling that little could be done to overcome these problems because institutional websites are too entrenched in bureaucracy and politics.

Although I can sympathise with this position and have myself suffered from the problem, I am not one to give up! Over the last decade of working on these sites, I have developed a number of techniques which (sometimes) help to smooth their evolution. Hopefully they will help you too.

1. Educate and inform

At the heart of any technique for dealing with politics and bureaucracy has to be education.

Although there are occasions when people are just ‘trying to be difficult’, in most cases their objections are based on ignorance.

You cannot expect people to be as knowledgeable as you about the web. If you want people to make informed, sensible decisions you must educate them.

Education is also not just about giving them the background to a specific decision so they understand ‘why you are right’. It is about increasing your organisations general understanding of the web.

Run workshops, publish email newsletters, do anything that informs people about the latest web innovations. Increasingly I am invited into organisations to run short seminars on everything from accessibility to facebook! This kind of ongoing education means people are better informed when tough decisions need to be made.

2. Hold stakeholder interviews

One technique that we find very effective at Headscape are stakeholder interviews.

Stakeholder interviews involves meeting individually with anybody who has a ‘stake’ (interest) in the website. This is typically members of the marketing and IT teams, as well as departmental heads and senior management. However it should also include suppliers, customers and users of your website.

These one-to-one meetings provide two opportunities…

  • Requirements gathering – It is easy for website owners to live in isolated bubbles, separate from the rest of the organisation. These meetings provide an opportunity to understand the real needs and objectives of others within the business. It will highlight ways that your website can help, which you might not have previously considered.
  • To be inclusive – Stakeholder interviews offer a ‘political benefit’ as well. By meeting with people individually they feel included in the process. They feel their opinions are valued and listened to (which they should be!). People are much less likely to object if they have been consulted before a decision is reached.

People often complain about the website in stakeholder interviews. Allow them to do this and avoid becoming defensive. They will feel more favourably towards you and your website, if you listen to their concerns. We all like to be heard.

3. Avoid group committee meetings

The key to stakeholder interviews is their one-to-one nature. Group meetings can be very destructive. This is for a number of reasons…

  • The need to defend – In large organisations that have internal politics, everybody feels the need to defend their own ‘turf’. If somebody criticise the website, you are forced to defend it to ‘save face’ in front of others. Equally others feel the need to defend their own positions for the same reason.
  • A tendency to compromise - When two individuals in a group reach an impasse, the others try to find a compromise. This kind of ‘design on the fly’ inevitably leads to a bland solution. It will neither offend or inspire anybody. Unfortunately, to create a successful website you need to make tough choices that some will not like. A group approach does not lend itself to this.
  • A loss of control – It is easy for you to loss control in a group meeting. One-to-one meetings work better because you can divide and conquer. Only you know what the other stakeholders said. This puts you in charge and allows you to ‘cheery pick’ the feedback you receive. In a group meeting things can easily get out of hand and decisions are made without your buy-in.
  • The dominant individual - Every group has one or two dominant individuals. These are the people who bounce the rest of the group into agreeing with them, forcing their agenda through. A dominant individual drowns out quieter members, who become resentful later that nobody listened to them. Meeting with people individually prevents this because the dominant individuals cannot force their point of view on others or overwhelm quieter ones.

One cannot expect a larger organisation to run its website without some form of committee. However, there is no reason why that committee needs to meet as a group.

4. Target your influencers

Talking of dominant individuals, another successful tactic is to target influencers.

An influencer is somebody that others respect and follow. Their opinion is incredibly valuable and if you can sway them to your cause, others will fall into line. However, be careful not to confuse dominant people with influencers. A dominant person will ‘bully’ others into publicly agreeing with them. An influencer will fundamentally alter somebody’s attitude.

Identify who influences your decision makers and speak to them personally. This person might not even be a decision maker themselves, but they carry enough clout to make them worth your time.

When you meet with your influencers, really listen to what they have to say. They often have valuable insights which may change your strategy significantly. Do not go into a meeting with an influencer simply intent on pushing your own agenda. Instead try and shape your approach around their perspective.

If you get an influencer enthusiastic about your project it can make a huge difference.

5. Use third party experts

A variation on the influencers technique is to back up your ideas with third party expert opinion. This can be done in two ways…

  • Reference the work of a third party expert – For example, if you wish to discourage internal stakeholders from overwhelming users with options on the homepage, you might refer them to Steve Krug or Jakob Nielsen who have both written on the subject.
  • Hire a third party expert - I often find myself brought into companies simply to confirm what in-house staff have already been saying. Unfortunately, decision makers often doubt the opinion of their web team because they either undervalue them or feel they are pushing a hidden agenda. An independent expert can add creditability to your opinions.

Of course, for this approach to work the stakeholders need to respect the expert. There is no point referencing Steve Krug or hiring Jakob Nielsen, if the decision makers have never heard of them. It is often necessary to sell the credibility of your expert first.

6. Rely on evidence, not opinion

Sometimes it is better to avoid personal opinion entirely (even if that is the opinion of an expert). In such cases statistics can be your friend.

Nothing is more powerful for driving home a point than referring decision makers to Google Analytics. However web stats are not the only evidence you can draw upon. Others include…

  • Surveys and polls are an excellent way of getting feedback from your users that can then be presented to decision makers.
  • Twitter search and Google Alerts can be used to gauge how people view your site and brand. These can be powerful testimonials to present decision makers.
  • Heat maps can be used to take some of the subjectivity out of design.

Of course one of the most powerful evidence you can present is the results of usability testing.

7. Focus on the user

As website owners we know that a successful website is user focused. However, not all our decision makers will understand this and even those who do may get ‘distracted’ sometimes.

It is therefore important to constantly move our decision makers away from their own personal preferences and back on the needs of users.

User testing is one way of doing this. Being able to show decision makers how real users interact with your website is incredibly powerful. It helps them empathise with the needs of users rather than thinking only about their own agenda. Play them video clips of users interacting with your site or at the very least quote them the feedback of users.

However, even if you involve decision makers in user testing, they can still get caught up in their own agendas. One gentle way of preventing this is to word your questions carefully. When you need a decision makers response to something don’t ask…

What do you think?

Instead ask them…

How do you think users will respond to this?

This will keep them focused on the needs of users.

8. Control the feedback

As well as wording questions carefully there is also a need to control the feedback you receive. This is important if you want the decision makers to make considered decisions.

Take for example design sign off – never ask a decision marker if they like a design. It is too broad a question that will lead to a plethora of uninformed and ill considered responses. Instead ask them more specific questions such as…

  • Does the design conform to the brand guidelines?
  • Does the design meet the needs of our users?
  • Does the design emphasis the right content?
  • Does the design have a clear call to action?
  • Does the design fulfil our business objectives?

This prevents the decision maker from falling back on their gut reaction (i like it / I dislike it). It forces them to focus on the issues that define whether the design is successful or not and ignore personal preference for specific colours or layout.

Of course, sometimes you will not like the answer to these specific questions. When that happens you need to ask why.

9. Ask why

This is probably the most powerful of all the techniques I have listed here and yet by far the simplest.

When you face opposition to your plans, always ask why. Too often we switch to defensive mode and focus on better communicating our own position rather than understanding the opinion of the person opposing us. This is a mistake.

The question why is powerful for three reasons…

  • It informs – Often the objection raised initially is not the true underlying issue. By asking why you get to the root of the problem and that allows you to offer alternative solutions. Asking why ensures you have all the information required to deal with the issue.
  • It can confound – Most of us make decisions based on an intuitive leap. We do not always think through our decisions and so find it hard to articulate the underlying reason. By asking why you force people to stop and consider their logic. When they struggle to express the underlying reasons, they weaken their position.
  • It shows interest – By asking why you allow them to have their say. You demonstrate an interest in their opinion and establish empathy with their point of view.
  • Ultimately asking why avoids the disagreement from turning into an argument with entrenched position.

    10. Avoid confrontation

    I avoid confrontation at all costs. Going head-to-head with somebody especially in front of their colleagues achieves nothing. You can rarely get somebody to shift their position through confrontation.

    Once a disagreement escalates into a confrontation, nobody can afford to ‘lose face’ by backing down. It becomes a matter of ego, where pride dictates the outcome. Your website will almost certainly be caught in the cross fire.

    A better approach is to agree. The word yes can be immensely powerful. Whenever somebody suggests something to me, no matter how stupid, I will do the following…

    • Acknowledge and thank them for their input.
    • Say yes we could do that.
    • Go on to explain the consequences if we did.
    • Offer an alternative which could achieve the same aims.

    In short I tend to go around problems rather than bashing my head against them. I always look to work with others rather than against them.

    Conclusions

    So there you go, 10 techniques for battling site bureaucracy. I do not claim these techniques are foolproof. Neither do I suggest they are always appropriate. However, they are useful techniques in your arsenal which you may want to call upon from time to time.

    Finally, this is not a definitive list. I could have written more but then it wouldn’t have been a ‘top ten list!’ However, I would be interested to hear what works for you. Post your techniques in the comments.