The forum is dead, long live Vanilla

In a world dominated by Twitter and Facebook it is easy to forget that the humble forum is one of the most effective ways of building a community. But not all forum software was created equal.

In a world of social media and post Web 2.0. it would be easy to view forums as obsolete. In some ways they feel very much like a Web 1.0 technology. However in reality they are still a valuable way of building community.

Why forums are not dead

Forums have many advantages over other forms of social media. While the new generation of tools such as Twitter and Facebook focus on encouraging communication between friends, forums focus on creating community around topics. This makes them an excellent tool for building a community around a website or brand.

Forums also encourage a ‘many to many’ relationship. This helps to build a much richer community where everybody is interlinked. All communication is open and accessible to everybody, allowing people to search through the conversations of others to find information that may be useful to them. This is why forums are so popular as a support tool on many websites. Support queries can be addressed by other users rather than relying on central support staff.

Dell Forum

It is for these reasons that Boagworld has a small but active forum. It helps to build relationships between Boagworld listeners as well as act as a valuable resource for those with questions about designing or running their website.

Enter Vanilla

When we initially decided to have a forum I was shocked to discover that there was very little choice in terms of web standard compliant software. At the time the vast majority of forums was still dominated by table-based design. The exception that stood head and shoulders above the rest was Vanilla.

We ran entirely happily using the Vanilla 1 software for a number of years. I knew that a second generation of the software had been released but saw no real reason to upgrade because I was happy with the original. However eventually I decided to take the plunge and can say categorically that Vanilla 2 is by far the best forum software currently available.

Vanilla Website

I have been so impressed that I wanted to share with you just a few of the features that make it stand head and shoulders above the competition.

Twitter and facebook integration

One of my favourite features of Vanilla 2 is that it allows users to login via Twitter or Facebook. For us at Boagworld this solves two problems. First login via Twitter or Facebook significantly reduces the amount of spam our forum receives. This is because the majority of spam bots do not own a Twitter or Facebook account!

Vanilla Social Connect

The second problem that Twitter and Facebook integration overcomes is the barrier of registration. With Vanilla 1 users were required to complete a form before they could post to the forum. Now users can simply login to Twitter or Facebook and post-straightaway. I found this an invaluable way to increase engagement and to encourage my Twitter followers to join in discussions on the forum. It has opened up a whole new realm of possibilities for discussion where a conversation can be initiated on Twitter without the inherent limitations that Twitter has.

WordPress integration

But Vanilla doesn’t just integrate with Facebook and Twitter. It also has superb integration with WordPress. This manifests itself in a couple of ways. First, Vanilla offers a single sign-on feature which means that if the user is registered with WordPress they also have the ability to automatically log into the forum. This creates a much more integrated approach between the two systems and avoids the user having to remember multiple usernames.

Vanilla's WordPress integration

Secondly, Vanilla offers a range of WordPress widgets that allow you to show various information on your WordPress blog. For example, you can show latest discussions in a particular category (or across the whole forum), currently active users or recent activity in the forum. Alongside Vanilla’s ability to have custom themes these widgets allow you to make your forum and WordPress installation look like a single integrated site.

Easily customisable

Talking of themes, Vanilla is it incredibly easy to customise and if you’re familiar with doing so in WordPress then this will be a breeze. You have the ability to edit both HTML and CSS. You can also either tweak an existing theme or override the CSS of any theme completely by adding your own CSS styling.

Gorgeous customisable themes

Even creating a theme from scratch is not that intimidating. The tagging is incredibly simple and you can turn round a fairly sophisticated design is only a few hours. I have to confess the guys at Vanilla helped me with my theme but I was gobsmacked quite how quickly they did it.

Outstanding customer support

It is that kind of outstanding customer service that probably impresses me most of all about Vanilla. Mark (the founder of vanilla) was unbelievably helpful in the transition from Vanilla 1 to Vanilla 2. He responded almost instantly to all of my questions and was very forgiving when I made a number of stupid mistakes! It is obvious that they really care about their customers and want their forums to be as good as possible.

You may be thinking that I received above-average service because of the profile of the Boagworld site. However it is worth saying that our forum is actually very small with very low levels of traffic. It really is not that high profile. In addition I’ve spoken to a number of other people who use Vanilla and they have all said they received the same level of superb service.

Customer support is often the downfall of open source projects so it is great to see such exceptional support on a product like this.

Hosted or not

Another thing I like about Vanilla 2 is that they now offer a hosted version for those of you who do not want to host the forum yourself. We found that having an active forum can put considerable load on your server so having the option to have someone else manage that problem was very appealing.

Not that Vanilla 2 has to be a hosted service. You still have the option to download it and install it on your own server. However I have to say having them host it has removed a lot of headaches for us. In particular they are very careful about which plug-ins they allow you to run which dramatically improves reliability. One of the strengths of the Vanilla platform is that it has this plug-in architecture very much like WordPress. They have a vibrant community of plug-in developers however like any such community you’re not always sure about the quality of a particular plug-in. We found that this was having a detrimental effect on the performance of our previous installation of Vanilla. With the hosted solution, this problem goes away as all the plug-ins used are carefully vetted.

Powerful yet elegantly simple

I think the thing that attracts me most to Vanilla is its simplicity and elegance. Sure, it is incredibly powerful however this is not at the expense of usability. The admin interface is beautifully designed and intuitive to use. You can add categories, manage users, send out announcements and indeed do everything else you would expect without any documentation or training. It’s just obvious.

Vanilla Stats Dashboard

In addition it has some great graphs and charts for tracking the statistics on your forum. Even these are beautifully presented and easy to understand.

The plug-in architecture means that if there is any functionality missing that you require on your forum, the chances are there is a plug-in that already exists which will do the job. If there isn’t it is worth dropping the guys at Vanilla an e-mail because they seem very willing to build custom plug-ins if there is enough interest. They also seem able to do so incredibly quickly!

Next generation of forum

If I had to sum up my initial impressions of Vanilla 2, I would have to say it feels like the next generation of forums. They seem to have learnt from the latest in social media and integrated that back into a forum environment. For example, each user has a profile page containing an activity stream much like you would see on Twitter or your Facebook wall. It also uses Ajax extensively to create a more application like feel.

If you are looking for a forum to integrate with your website I could not recommend Vanilla 2 enough.

Building and running a successful community

Patrick O’Keefe joined us on the 200th episode of Boagworld to talk about building and running a successful online community.

Patrick: Hello? Can you hear me?

Paul: Excellent stuff Patrick. Oh, we got a picture on the wall.

Patrick O'Keefe

Image Source

Ryan: Oh, yes.

Patrick: Our night begins.

Paul: Lets set you up then Patrick. You know, it’s a real pleasure to get to speak to you. I don’t know, this is where you gonna say: “Yes, have met hundreds of times.” Have we actually MET before?

Patrick: At SXSW.

Paul: Damn!

Patrick: We went for dinner, remember that? You send a tweet out, and I showed up, I think you were at the Omni? Maybe? And we had dinner.

Paul: I remember, yes!

Patrick: And [fox?] was there.

Paul: Yes, yes, yes. I am being really thick, I am sorry.

Patrick: It was really brief. So it’s evening out. It was at SXSW, so no one really remembers much.

Paul: You have no idea how many names I have already got wrong today, and how much I have screwed up. But by this stage in the affair, I am gonna let myself off of that. Patrick, thank you soo much for coming on to the show at the point where we are beginning to lose the plot.

Patrick: Thanks for having me.

Paul: If we are not coherent in our questions and we are not making sense, then please feel free to make up your own questions, and answer them yourself.

Patrick: I have got a list right here.

Paul: Why don’t you start by introducing yourself for people that don’t know you.

Patrick: Sure, so again I am Patrick O’Keefe. I run the iFroggy Network at ifroggy.com. It’s a network of websites that is covering various interests, communities, blogs, etc. I have been managing online communities for over nine years, coming up on ten years. And I wrote a book called “Managing online forums”, which is a practical guide to managing online communities and social spaces.

iFroggy Network

Paul: OK. It sounds like you said that a few times before. That was very slick.

Patrick: I have, it needs to be short.

Paul: I guess so. We were just saying you also do a podcast now, the SitePoint podcast? So you are obviously a professional podcaster, very slick.

Patrick: Euhm … [starts laughing]

Paul: Euh…

Patrick: No, I have been hosting podcasts for a few years. I hosted a show called “The Community of Men” show, about managing online communities, for a while, for a year and a half, like 2005 to 2006. We posted a SitePoint podcast from pilot to now, I think it’s episode 49ish, it’s temporal lead, and I also host a show called , which is about plagiarism and copyright infringement, co-hosted with Jonathan Bailey.

Paul: Cool. I really enjoyed the SitePoint show. It’s really good, and I was just encouraging people to subscribe to it.

Patrick: I heard that. Thank you.

Paul: But where I get really passionate is with your interesting …

Marcus: Passionate Paul, passionate.

Paul: Oh, I am not allowed to say passionate. It’s the banned word for the day. Don’t ask me why. Where I get really enthusiastic then, is with all of the stuff that you do in relationship to community. Community is something that I have been involved with since the very early days of the web, I was involved with one of the first online communities called The Well, I was involved with the early days of GeoCities. So to see you writing a book on communities and forums, and that kind of thing, it’s just soo cool to see people addressing that kind of issue, and talking about that.

Tell us a little bit about the book and why you felt the need to write it, and what kind of things it covers.

Patrick: Well, thank you first and foremost for the kind words, but you know, I write, I don’t know, I like to think I am writer. I have been a writer, for you know, 10 years for various online publications and so one, and I am passionate about online community. As I said I have been doing it for 10 years, direct management, responsibility, it’s something I enjoy doing, it’s something I have done for a long time, and that is sort of how the book came about, putting two things together. Having experiences that I wanted to share, that I thought could help people, because that is really the value: if you help people or not. And I like to write, so I put the two together, so the book took me about five years in all, from idea to publishing, I took my time, and I went on my own schedule, threw everything in there that I thought would be good. Everything that I know is in that book. So that is sort of how it came about, I just wanted to share that knowledge, and it is something I am passionate about.

Paul: Cool. Obviously the thing that may jump into people’s minds is that you started writing this book five years ago, and the landscape has changed massively over that time, and now there is social media and all of this kind of stuff, you know it is no longer just about managing forums, it’s about managing communities that are dispersed over lots of different places, from Twitter to Facebook, to everywhere else.

Do you feel that the principles are still pretty much the same?

Managing online forums

Patrick: Well, I like to think that, or actually a friend of mine Lee LeFever of CommonCraft who said that “forums or sort of the basis or part of the foundation of social media”, so all these tools that we have now … I love Facebook, I love Twitter, but we have all these tools, and they are all great in their own way, but forums are sort of a standby, I don’t think forums are going away, I think the text based communication in a thread is basically what a forum is, when you really get down to the nuts and bolds, and I think that is something we will want to do. For as long as I can see people want to talk to each other on text, they don’t want to see each other necessarily, like we are right now, they don’t want to talk to each other maybe all of the time, but text, I think, is here to stay. And we are dealing with a lot of text based mediums and I think a lot of the same principles apply, whether you are talking about a chat room, a group, people still use Yahoo groups, called groups, I am on a Yahoo groups mailing list right now! So for communities that’s great. But there are all these older tools that we have, like mailing lists and so on, and they are text based, and the same principle sort of applies: having guidelines, and making sure those guidelines are followed, and encouraging healthy discussion between members, regardless of whatever kind of space it is. Those values tend to stay true.

Paul: Yeah, because ultimately people are people. And community is about people, rather than about the technology and the mechanisms through which they communicate.

Patrick: Right. That is basically it, and I think even though the title of the book, or I might talk about forums A LOT, forums are just one thing. When you look at Facebook, you see forum like components. You see threaded conversations, you see text discussions, the discussion tab on Facebook groups, and fan pages. You look at MySpace, there is similar things, you know. It’s hard to draw comparison to Twitter, but you are looking at threaded conversations, then I think all these community spaces have local rules, things that not need to be adjusted and accounted for, that are for them only, but at the same time there are overriding guiding principles that apply to a community in general.

Paul: Yeah, absolutely, I entirely agree with that. I mean, there are still a group of people that are kind of somewhat hesitant about communities, and about social media. Especially website owners, especially for relatively large websites, there is a fear associated with running a community, they might even pursue social media being a bit of a bandwagon thing that everyone needs to get involved with. Why do you think that website owners like that really should be taking communities seriously, and engaging with the people that visit their websites?

Patrick: Well I think there is a couple of different things.

First, I like to think that everyone has a community. Whether or not if you are a business or a public persona -obviously private persons are not included in that category. But if you are company, if you are a public personality, someone who is out there trying to sell something, trying to get an audience, you have a community. Now, that community is the community who uses your products, who like what you do. Everyone who does something like that, from toilet paper to anything else, has a community. People who like their product. And the question is whether or not you acknowledge that community and engage with it. And you don’t have to necessarily engage with it. There are companies that have been around for a long time, that probably don’t engage with their customers as they should be. They offer a good price, and you know that should be the focus, and that is why people use it. But, at the same time, you know, this community of people who is behind you, can be very valuable in all sorts of ways: improving your product, spreading news. It is effectively a captive audience of people who want to know whatever it is you are doing.

So, if you can take advantage of that, obviously you can be doing yourself a service as a business, and there is a lot of different benefits to that as well. It doesn’t have to be an onsite community, it can be Twitter or Facebook. You know, there is different needs, and you need to filter through the different services. But, if you go where that community is, there is usually not a whole lot of downside to creating a relationship.

Paul: No, I mean, yeah, you are spot on there in everything you are saying, and I have been trying to encourage clients for a long time to really engage with communities. What can of different ways do you think a website owner can do to go about engaging with their visitors? What are the different options that are available to them?

Patrick: Well, I mean there is [an endless list?] of different options. I think if you are talking about it actually being on the website, you are probably talking about some form of hosted community, and if it’s forum software, or if it’s even a blog – a blog is a community, it has comments, you know it’s a community – and maybe blogging is an easy place to start for someone, where they could simply talk about the business, talk about the things they are doing, initiatives they are being undertaken, ask questions, that’s an obvious one, ask questions of customers and see what they say. I think that is a simple thing that you can do on your website. Forums are a little more engaging, a little more responsibility there, a bit more work I would say, but it can be very rewarding. Because if you can cultivate the community on your site that is around a brand – that is kind of a challenge – especially for smaller brands, that is a pretty big challenge, but if you can do it, then again, I think you have that really strong captive audience that is sort of waiting for whatever cool thing you have coming next. And a way to share it, and to talk about it, to help improve it, and that is a golden thing. That is the main way that businesses make money from community that actually sell a product.

Actually you can make money through advertising and other things, but a business that has a product to sell, a community like that are just waiting for the next product to come out, and they want to talk about, share it, and prove it, and buy it.

SitePoint Podcast

Paul: Yeah. I mean one of the big things you do see a lot of people, established communities, established organisations, a lot of communities, recognise the value of it, jump in there, they get a forum build on their site, they open a Twitter account, they start their Facebook page and then they are disappointed with the results. It doesn’t turn out as they expect. What are the kind of common mistakes you are seeing from organisations, as they are trying to build communities. Where are they going wrong?

Patrick: I think though, the biggest thing is: community is hard. I mean, it is easy to have people out there talking about you, but it is a whole different thing to actually build a community on your site, and have a lot of people contribute. This is a hard thing to do.

BUT, I think one key to it is that first of all there needs to be commitment, from an organisational standpoint. I think that if you launch a forum, and you expect it to be active in a month or you are cutting the cord, just don’t do it at all. Don’t even make the commitment in the first place. There needs to be a long term commitment – and I got this from Shaun Diddy Combs – but he says that he is not a sprinter, he is a marathon runner. That’s how your community is. It’s a marathon run, it’s not getting from point A to point B in sixty seconds, it’s a long term commitment, and that is resources, that is people, that is money. And if you are not going to make that commitment then I don’t think you should go all out, and you know, regardless of what you do, starting small is always a good idea.

So if you start with, let’s say a Facebook fan page, then you get some traction there, you get some activity, get some discussion going on. Then maybe you have the community, you have the ware with all to launch a stand alone community on your own site, and engage in a deeper way, you have people actually on your website, you have a deeper access to them.

But starting small, and growing, not trying to do too much at once, not launching a full forum, a blog, a Facebook page, a Twitter account, and every other social profile you can think of, all at one time. More often than not, I think that might lead to just a lot of inactive profiles, and I think at the end of the day you might want to have 1 active one, versus 10 inactive ones or 10 moderately inactive ones.

Paul: Hmmm. I do think a lot of people jump into traditional forums way too early. I mean, there is some really obvious challenges with forums, where you are having threaded conversations and there isn’t a lot of traffic, there is not a lot of people who are using it, you know, messages can get lost in this kind of hierarchy of threads and you can feel like the only person at the party. While compared to something like a Facebook page where the discussion is very linear and everybody sees what’s being written, or even a mailing list or something like that, they are much kind of entry level tools, in my opinion. Is that the same kind of approach that you take?

Patrick: Well, I started with forums, so that’s my perspective on it. I think it was a different time when I started launching online communities. In 2001 I launched KarateForums.com, so eight years later, nine years later – God I feel old – but you know I think that it depends. I think it really depends on the situation, what your needs are, what you can do. I think that when you look at a Facebook fan page, what do you see? A lot of short comments. And I think that is what it is primarily build for. Even though people can sit there and type for a while and post a long comment, they just don’t know, there is a discussion tab, but you can’t tell me that that discussions area is more intuitive than a forum. People aren’t usually familiar with that format. It’s just not, and I mean, I think that is even a bigger challenge maybe once you have the Facebook fan page, transitioning those people into having a deeper discussion, rather than having them just drawing by and say “Hey, I love this product!” You know, how do you connect to those people? How do you get talking to them? And I find that Facebook fan page questions maybe aren’t the best way to do that, but at the same time they are better than nothing. There is a lower barrier entry, it’s a lot easier to get started with a Facebook fan page. No forums, community in general, managing a community you are directly responsible for, not just a fan page, but an entire operation, it’s hard. Like I said, and if you can build that kind of community before launching a forum, that is helpful.

Another idea you can do is, to just, well hopefully you have some means of communicating with your customers already. You have a fan club, a mailing list, even the bills thing. However you contact them on a regular basis, you must have some way of saying “Hey, by the way, we are launching this community in the future, and we would like to invite you behind the scenes for an exclusive look, and get your feedback on it, and have you help us improve it. We love your thoughts, we love you to be part of this exclusive community that’s invite only”. And maybe you get 10, 20 people, people who love the product, people who responded to that call out. And then you start building a private community behind the scenes, before you launch, so there is activity already there. And then by the time it does come time to actually launch, then you have some momentum already going, and that makes it a lot easier. So I think for the most part I always like to have some pre-launch community, some sort of private access community that is going on, and we where we can have something going the moment we launch.

Paul: Yeah. That is the big thing, isn’t it, ending up with an empty community the moment you kick off, and then you do have that problem of being the lonely person in the room. I mean, what about, one of the big things that people worry about is scaling their community. So as their community grows, it becomes harder and harder to manage and it could get expensive, and you want a return on investment. What kind of advice do you give in terms of growing a community?

Patrick: I think, Darren Rowse at problogger, on a panel he said something that I think that is pretty fitting. He said: “If you have three people, love those three people.” I think that is how I look at community building. We grow one by one by one. And maybe for some it’s one, two, three, four, five. Maybe for others it’s one … two … and so on. But as [..] going only one person at the time. So the people you already have on your community, those are the people that you should be spending a large amount of your time embracing and encouraging and appreciating. And if you appreciate those people then it will grow through those people: word-of-mouth etc. Having that activity helps you grow. Now as far as supporting a community in general, I mean it’s a website, so a lot of the same online marketing principles apply of course, but I think activity is just a big thing. I think being involved.

A lot of people launch a community – and I hope this is going down in occurrences – but it seems, and I don’t know if it is, where people just expect it to happen, and they go away. Community isn’t like something you come and visit just once a week. I mean you can visit every other day, that’ll be OK, but it’s something you need to be there for. You need to engage and participate, start threads, reply to people, ask questions, talk about things. Whatever presences you have already, promote it through that – if you have a website already in place – obviously it should be linked – a lot of people don’t do that very well. If you have a Facebook fan page already, then it all should be integrated into working together.

When it comes to growing activity, things like contests or give-aways obviously are not novel or new concepts, but they can be effective. I like contests that give you something tangible, not like referral contests where people can sign up for a member, and that member never posts. But actual contributions and articles, and things that can be judged on their merit. They really add to the community, those can be really helpful things. Activity is just a big thing, because all your marketing endeavours, if you spend money on Google Adwords, if you buy advertising for your site, the effectiveness of those campaigns all go back to whether or not your community is already active. Because when people come, that’s one of the things they’ll use to make a decision on whether or not they’ll stay.

Paul: Yeah. Absolutely. How do you deal with … , a problem that we have with Boagworld is that I could only invest so much time in the forum, but there was a real desire from the community for the forum to grow, they wanted to get into the forum. And the way that I solved the problem was actually to take those people that were most enthusiastic about the forum and give it over to them, and give them the power, make them community leaders. Is that the kind of approach you would encourage? Does that work? Can we volunteer community leaders? Or have I done it horrible wrong and should I fire them all?

Patrick: I don’t think you have done it horribly wrong. That makes sense. I am a one man operation, with little resources, I’ll be honest.

So I run a network of forums, and I am primarily responsible for them. I do have a volunteer staff that have very little requirements. They are people who have enjoyed the community, most of the time it is them giving back and maintain something that they themselves have benefitted greatly from. Obviously there are small benefits in there as well. But at their core, they are volunteers, and I think that is a great thing, to have people be passionate about the community. I mean I am passionate about the community so that’s ironic, but I think that’s a great thing, but I think it is important to have guidelines for those people, so that they know exactly what their responsibilities are, how they are supposed to go about these responsibilities, and so on. And that there is someone who is overseeing it, I guess, is what I always say. Because I review things that my staff members do, so if they remove a post, or if there is some sort of violation, we have a system of documentation behind the scenes that they logged it in there, and now I see it, and 90% of the time, 95% of the time, what they did is in line perfectly with what our guidelines say, what I want them to do. But there is that 5% where I want to correct it, so that we are consistent so that members are treated 100% the right way, to set the tone for any future things that they should do. Because I always want it to be a 100% correct whenever we take some staff related action, so I think having some sort of over sighting documentation system is important, but beyond that, having the volunteers that love the community is a great thing to do.

Paul: So you talked about providing guidelines to your community leaders. The question that comes out of that is: What kind of guidelines are we talking about? What is it that community leaders need to know in order to be able to effectively run the communities effectively for you.

Patrick: So in my case they are more moderators. I don’t really let anybody have … For example I am the only one who bans people. The less people you have who can ban people, the more consistent the bans are. So that’s why I have it that way, but other than that they have moderator authority to remove threads, any thread or post in public, just contact members to notify them about those violations, and etc. So I have a set of example staff guidelines on the book website, where people can download and see what my guidelines look like.

Paul: Where is that?

Patrick: That’s managingonlineforums.com and there is a link in the sideboard Downloadable Templates and you can download the staff guidelines that I use myself, and you kind of can get a sense. But, basically what they are, they talk about what you do.

So for example: You can remove threads. What do you do? Do you delete them totally or do you move them to a private forum where we can see them later? Or we can have them if something should come up in the future. That sort of thing.

So we tell what their responsibilities are, how they go about executing, what is expected of them? That could be staff related duties, that could be “We expect you to be an example to everyone of this community.” I kind of view my staff members as not just moderators, but people that other members should follow. In an example they should be the example member, so that everyone sees the ideal way of participating in our community. So it just talks about … think of it like: at a corporation you might have an employee manual, it’s not that hard core maybe, but it provides some guidance and some details, because I think if you have nothing then people can do anything. And you know it’s easy to say common sense should apply, but my version of common sense and someone else’s version of common sense may differ greatly. It’s good to have something I can point to and say OK, well this is how we do this, it’s right here in the guidelines, and keep it in mind for the future. And it’s always easier to do that then say: “I had this thought in my head, which no-one has access to”. Perhaps you shouldn’t do that.

Paul: Yeah, and you got to present something to people where they got a really solid line. They know what they are doing, they know where they stand, and there is no uncertainty in the situation, but both in terms of your community leaders, the rules that they abide by, but also that of the entire community I guess.

Patrick: Right. Exactly.

Paul: So, looking forward. How do you think communities are going to evolve on the web over the immediate future. Do you think we are going to see some substantial changes on how communities grow and how communities interact with one another, and how organisations can make use of community.

Patrick: You know, I think what tends to change is the technology. You know, and that is not to say that forums themselves, or … I mean like video for example. YouTube is a community, a video community, there are video communities out there, it’s not that really around text based, although text based comments tend to be a big part of it. I think technology is for the most part what changes, we see new things come up, like a new platform like Twitter, a few years ago, or Facebook etc. where you have this community space. As we talked about earlier, some of the same principles still apply. I think good management strategy doesn’t change as easily as software.

That is why, in my book, I didn’t talk about phpBB version 1 or [..] version this or BBPress or whatever, it’s not about the software, there is tons of good software out there, and there will be more good software out there. What will determine your community success in the end, is the people part of it. How you manage people, how you cultivate their community, and all those things that are actually going into managing actual people, that are irregardless of software. Software doesn’t matter. You have tons of good options these days, so much different from when I started ten years ago, and there was phpBB version 1, and that was it. Like, I mean, literally, that was IT. There was uBB back then, which cost a ton, and now you have so many good options, so many good open source options, software is no longer the issue, it’s the people that matter, and I don’t think that will ever change.

Paul: Yeah. I mean, ultimately the same rules … almost the majority of the rules that you would apply to an online community would equally apply to running an offline community.

Patrick: Right.

Paul: Because ultimately it is about people.

Patrick: Yeah, exactly. Offline community and online community, you know are similar. I always try to take that stigma away from it, because there are people who think: “Online community: it’s not genuine. This is online, you’re at a screen, a computer screen, you are not face-to-face to people, that is not REAL community”. But it is, I mean, why do people meet offline? Because they have common interests for the most part. They want to talk about something in common. Why do they meet online? Same thing, you know? So that’s how I view it.

Paul: I mean, I guess, the major difference, at least from my experience is that people are less reserved online. They will be blunter and things, especially textual communication, things can be misunderstood easier. So there is a … do you perhaps need to think twice before responding online, you know compared to offline. But other than that it is very similar, very similar.

Patrick: Right. And yes, [..] “irregardless” is not a word. Thank you, thank you very much.

[Laughter]

Patrick: I knew it as soon as I said it, OK, I am just kidding.

But yeah, I think that is very true, and I think obviously what I have to say is that the online world, the internet as a whole, has made the good things better, you know, you look at charity endeavours and things, and you see like Haiti and whatever, and just the amount of the money that was raised it can’t be duplicated 10, 15, 20 years ago. There is just no way.

Paul: Yeah.

Patrick: But is also makes the bad things worse. It makes bad people, it gives them more of an anonymous opportunity where they are not as easily spotted maybe, as they would be offline. So good things better, bad things worse. And that applies to community, it applies to how you handle yourself online and how much that amplifies. You just said “being careful of what you say”, but hey, it’s also access to those people who want to have conversations and to share information.

Paul: Mmmm. Well excellent! Absolutely excellent! Really enjoyed chatting with you Patrick. I wish we could chat for longer, but Ryan has got carried away with endless guests, more than you can possible ever image on one show.

Patrick: You know we have been talking about having you on the SitePoint podcast, and us, or one of us on your podcast.

Paul: Yeah.

Patrick: So you know, maybe just one day it won’t be just talk.

Paul: Yeah, one day. Perhaps we ought to do a joint show. That’s what we should do. And then we can double it up and get twice as muchfor our money.

Patrick: Well, I appreciate you having me. And congratulations on having the 200th episode. And I guess we’ll see you at SXSW.

Paul: You certainly will. Can’t wait for it. Look forward to meeting you there. Bye.

Ryan: See you later.

Marcus: Bye, bye.

Paul: Brilliant stuff, I mean I love the subject “community”, and it’s something I could talk about absolutely endlessly. Possibly, I mean, for fear of getting gushy, possibly because Boagworld has been the success it has been because of the people that pitched in, and you know, from Ryan, to Paul, to Anna and then all of our community leaders as well. And all the people that transcribe the show. I am constantly amazed at how much effort people will put in, to something that, really they don’t get a lot benefit back other than listening me waffle at them once a week.

What are you laughing at Marcus?

Marcus: Emma Bolton here, seemed to have totally missed Boagworld 200: “Can anyone give me a summary of what was just said?”

[Lots of laughing]

Marcus: Superb.

Paul: Yeah, that’s not going to happen, I am sorry to say.

Marcus: But we are recording all of it.

Paul: We are recording all of that. I think that the further into this I go, the more I think we need to basically release this content in every possible way, to justify the amount of effort has gone into doing it.

Ryan: I have now squeezed Jonathan Snook into our last free half-an-hour.

Paul: Oh, for crying out loud!

Web Design News 13/04/10

This week: How to be the worlds worst project manager and how to alienate visitors. Also, why FAQs are failing and why page weight still matters.

How to be the world’s worst project manager

Project management is a thankless job. Most of us undertake it reluctantly and yet moan about those who do it as a full time job.

At Headscape we have 3 project managers for a company of 18. Sounds like a lot doesn’t it? However, we have learnt that setting our designers and developers free from the burden of project management does wonders for their productivity and having somebody constantly available for our clients makes a dramatic difference to customer satisfaction.

Unfortunately smaller agencies or freelancers do not have project managers. This shifts the burden of project management onto the client or the person actually building the website. The problem is that these people often do not have much experience or training on how to run projects smoothly.

Fortunately Sitepoint has a bit of advice for those of you who are landed with managing projects. Entitled “14 Ways to Be the World’s Worst Web Project Manager” the post outlines a number of ways you can improve how you manage projects. It does this by highlighting 14 ways things can go wrong and explaining how to avoid these pitfalls.

Whether you are a website owner running a project or a freelancer dealing with clients this article is a good read.

sambarnes.com

Infrequently asked questions

Does your website have an FAQ section? Chances are it does. Most websites seem to have them these days.

The question is why? Do we have FAQs because users find them invaluable or do we have them as a sales tool or dumping area for stuff we don’t know where else to put?

image of question mark

Stephen Gracey certainly doesn’t have much time for them. He writes on A List Apart

FAQs often read like a fictitious back-and-forth conversation between the eager, inexperienced user and the wise, venerable expert, covering all the basics from the beginning, and urging purchase at every step:

Q: What is this product?
A: It’s a widget. It’s the best widget you’ll ever find. You should buy one.

Q: Is it hard to use?
A: NO! It’s the easiest widget on the market. You should buy one…

On the whole, FAQs like these patronize users.

Personally I tend to agree. For a long time I built websites with FAQ sections. However I have seen them abused so many times, that I have lost faith in them.

In his post Stephen goes on to ask if FAQs are ever appropriate and if so how they should be used.

Despite his negative attitude to FAQs he actually writes a constructive article that suggests the best ways FAQs can be used and outlines scenarios where they are actually appropriate.

If your website has an FAQ section or you are considering adding one, please read this post.

Loses some weight

You work out everyday and eat a healthy diet. However you could really do with losing some weight.

No I am not encouraging anorexia, I am referring to your website.

fat stomach

For fear of sounding old, I remember the days when websites had to be under 50k to be usable. Anything larger would take too long to download.

However todays websites have become fat and bloated. What made us suddenly think this is acceptable?

Sure, most of us have broadband and so speed is not as big an issue. However as Sitepoint explains in “minimising page weight matters” there are still 3 good reasons for keeping your website lean…

  • 10% of users in western countries still use dialup.
  • Internet use in Asia and Africa is exploding. However their connection speed is typically slower.
  • Mobile devices are quickly becoming a major method of accessing the web and yet have slower connections than their PC cousin.

Personally I would add a couple more reasons to the list…

  • Google is considering making performance a factor in how they rank websites.
  • Jacob Nielsen reports that speed considerably impacts a sites usability.

Fortunately there are loads of things you can do to make your website faster. For a start you can read my post ‘5 ways to give your site a speed boost in less than 30 minutes‘.

How not to alienate visitors

Engagement is the ‘in’ phrase at the moment. We should all be ‘engaging’ with our users. Marketeers and website owners are particularly enthusiastic about the idea and not surprisingly. Talking to your users provides a lot of benefits…

  • It can improve your product and site
  • It can reduce costs
  • It can encourage users to promote your brand
  • It improves customer satisfaction

The list goes on.

However, despite this enthusiasm among marketeers and website owners many seem to continually put barriers in the way of that engagement. From hiding phone numbers to overly demanding forms, it would seem that many are actively trying to discourage their users from talking to them.

Sample feedback form

In his post for boagworld, Andy Wickes looks at the problem and suggests a number of ways you can make yourself more accessible to your users. In particular he looks like…

  • Social networks
  • The telephone
  • Contact forms
  • Asking questions
  • Thanking users

If you are struggling to engage with users this may be a useful starting point for identifying what is going wrong.

Kevin Rose on Community

At this years at Future of Web Apps I was fortunate enough to interview Kevin Rose, the founder of digg.com about running online community.

Paul: Ok, so I’m really pleased to have joining me today Kevin Rose from Digg and Diggnation. Good to have you on the show.

Kevin: Thanks for having me.

Paul: So, Kevin we had your keynote this morning at Future of Web Apps, which was brilliant, really enjoyed that, and you talked about some really interesting concepts around the subject of community building and that whole complexity that goes into that, and you made some really good points about how to encourage and engage people in community, and you talked particularly about this idea of massaging egos, which I thought was very interesting. Maybe you could share a little bit about that?

Kevin: Well I just think that people don’t really talk about that side of things, it’s kind of like it’s a black art in some ways. People are like “anything that would stroke the ego is a bad thing, and we shouldn’t do that!” but we’re doing that all the time in the features that we build. And you see it even in the most successful sites out there, I think, have figured a way to inflate an individuals self worth, in a way, when they use their products.

Paul: So you want to give us some examples, perhaps?

Kevin: I think that one of the biggest one is Twitter and the follower count and the idea that when you look at that number it’s “whose is bigger” contest between whoever is playing the game, right. So it could be between a couple of different plumbers, that have competing plumbing companies, they have Twitter accounts, any celebrities that are on there. And that’s just one of just a whole slew of different examples from Farmville, which is a really popular Facebook application, that figure out ways to give you certain awards every time you do different things and give you different badges and levels and things like that. I don’t use it as a way to drive the idea of the feature, so I’m not backing into it saying: “Ok, how can I massage the ego?” I think of, what does the community need? What features are we building? And I want to always make sure that person is rewarded in some form of fashion, and that can either be like, I’m digging a story and this is important to me so I want to show that I’ve added one to the overall count and in my profile it can be something where I achieve a certain level based on my contributions to the system, so I’m leveling up inside of a system. And there are so many ways to go about this.

Paul: One of the ones that you mentioned were leader boards, about how in the early days of Digg you had this leader board and then you decided to remove it. The thing that always strikes me from my experience of working with leader boards is that they can actually be gamed in a negative way, which ends up actually damaging the community. And is that why you removed them from Dig? And how did you get around that problem?

Kevin: Yeah, in the early days it was based on the total amount of stories that reached the front page, the stories that you submitted. And so it became this game that for the first six months was a lot of fun for pretty much everyone on the site, because they would look at the number one slot and say: “Ok that’s something I can achieve if I put in a decent amount and effort and work into trying to play this game.” As they grew hundreds and hundreds of stories deep to where you’d have to have a thousand front page stories, people were having a hard enough time getting one story on the front page of Digg, let alone a thousand. So it would discourage a lot of the other people and all of a sudden we had this press articles about how Dig is controller by very small subset of its user base bla bla bla.. so it was something we decided to remove because there was no real way for anyone to break into it once it hit a certain level. Some of the stuff we’re looking at now, well there is a couple of things: one, we plan on opening up a promotion of stories to a whole slew of different, like an open taxonomy, a whole slew of tags, so if you’re in something very niche, like rock climbing or road bikes, you’ll be able to jump into that section and see stories getting promoted in there. And so it’s not necessarily about just that one home page that sees a hundred and some stories a day, it can be about these other small verticals. And inside of those verticals we want to highlight the users data really finding the quality content. One ways that this can be gamed is if you’re saying: ok it’s only by the people that submit stories. Because some people are, I don’t know if they sleep or not, but they happen to be the first one to go out there and always find the best stories and be the first submitter. So, ways that we can get around this is not look at submissions, but also looking at the people that dug this early on, and how accurate they are at predicting whether something is going to be very popular. So, let’s say you’re in the road bikes section and there may be someone who diggs 50 articles a day, but let’s say you only digg 5 a day, but the ones you always digg eventually become very popular within the ecosystem. That means that you’re a very prescient user, you are a user that is very good at predicting what the community is going to enjoy.

Paul: Quality rather than quantity

Kevin: Exactly, so if we can start to structure our leader boards around those concepts, those are very difficult things to game, because even if you do game them you’re really providing the masses with what they want, high quality content. So, and then also lowering that window, so instead of saying it’s an all-time leader board, something that the sum all of your activities over time that would be hard to penetrate, you can say this is leader board of the best users in the last 30 day, or the best users in the last week or two weeks.

Paul: Constantly resetting

Kevin: Resetting, refreshing always making sure, and there might be some people who stick and some that go on vacation or holiday for a couple of weeks and then all of a sudden they’re back to square one.

Paul: Talking about your users, you talked a little bit about putting content live and then seeing how people responded to that and adjusting accordingly. Do you actually ever do any formal usability testing where you get people in and try stuff out?

Kevin: Absolutely

Paul: Ok, so how do you go about doing that, do you select people from the community or how does it go?

Kevin: We typically do it into three different sets of groups: we’ll have what we call our “lurkers to the site”, so people that are aware of Digg but they don’t participate. So they like the home page and understand what we’re doing we’ll invite them in for some usability testing, and then we’ll invite some peop

le that have no idea what Digg is, they’ve never heard of it before. And then we’ll invite our hard-core, on-Digg-24/7, the big stream users, and we’ll take those three groups of users probably 10-15 per group, set them down in front of a bunch of computers and then just walk them through a bunch of different scenarios.

Paul: One of the kinds of advantages of being a well established brand, whether it be pamps(?) or Digg or whatever else, you can try stuff out and you’ll get a reaction from your community and people will tolerate that backwards and forwards. But if you’re a startup – we just interviewed a guy earlier today who literally is him and his mate and they’re launching a startup – they only get one opportunity to make a good impression, really. So this idea of putting stuff out and testing it do you think that always applies?

Kevin: Yeah I do, I think that if you have just bad ideas and you can’t get a product to where at least people are like “that’s interesting enough to where I want to play with it” then you have to go back to square one. So that initial launch is not proving itself then maybe you need to try a different idea, but for us I think that we’ve been very fortunate in that first initial ideas that we’ve launch with have been sticky enough to have a group of users that wanted to continue using the product, and that’s the point where your starting to get feedback from these users or they’re starting to ask you “I’m having a bug or problem with this particular feature, or I want to see this or that” and that’s where I truly believe in the fact that you should release, iterate and continue to evolve as fast as possible.

Paul: Ok, that’s interesting. Can we talk briefly about community and community culture, because I’m fascinated by this idea that as the different applications launch they all develop little cultures of their own, if that makes sense, and Digg has got this reputation as being quite an edgy and has this kind of edginess to it, where there’s the classic one about posting the key for (something??) and they’re quite bulshy, they know what they think, they are very opinionated. How much do you think that that is born out of Diggnation and the fact that you guys present a certain persona in Diggnation and that’s kind of trickled through to who you’ve attracted on the site and how people have chosen to interact on the site?

Kevin: I haven’t really put that much thought into it, but I know that initially during the early days, well we launched before Diggnation so we always kind of had it was an edgy group to begin with and so

Paul: Perhaps it’s just the people you know

Kevin: Yeah, maybe I have some shady friends, no, but I think that there was some of the people that initially came to the site were fans of TagTV, which was the television network that I was involved in and all that, and so these were early adopter geeks and then we started the podcast later and that grew along with the site, but I think that today I really wish there was as many people listening to the podcast as there are diggers, ’cause right now last month I think we did around 40 million uniques on the site and on Diggnation site 150,000-200,000 people, so it’s kind of separated.

Paul: Perhaps the culture was established before has perpetuated.

Kevin: Sure

Paul: Have you found that a problem as you’ve expanded out into new areas? As different people come into the site, are they finding it quite hard to break in?

Kevin: Yeah, I think so absolutely. There’s no one single universal homepage that’s going to suit everyone and I don’t think that you’re ever going to be able to throw millions of people into the same chat room-slash-comment stream and expect them to all get along. So our big push with some of the new redesign and stuff that we’re doing with the next version of Digg is going to be to break up these sandboxes into smaller areas and service a lot more of the long tail of content, so that if my mom comes onto Digg there’ll be something for her to jump into. Versus today, she would look at the front page and be like “I don’t understand all these crazy Internet memes”

Paul: From our point of view as web designers, even the Tech section is too broad for us, we want our own Web Design subsection so that suits us perfectly

Kevin: Absolutely. I’ve been hearing that from the Linux and Unix candy(?) for a long time.

Paul: You talk about this redesign that you’re working on at the moment and we’ve had Daniel on the show a few times and he did our SXSW special where he was very rude to me – but we’ll gloss over that. You talked about in your presentation about how Daniel talked about this idea of simplicity “what can we take away”. Do you want to talk a little bit more about that because that’s something we hark on about a lot so it’s nice to hear you say it too.

Kevin: I think that there is, especially when you get to a certain size, it’s very easy when you’re a small company an you’re five people, like-minded individuals and you’re all trying to build a core product and you know what’s good for the web. Then as you grow into a larger 20, 30, 50-plus person company, you get different opinions and different takes on how to build websites. You have a biz-dev that says “wouldn’t it be great if we had this feature,” marketing that says “it would be great if we could have another banner ad here,” you have the CEO that wants a little something else – there’s so many cooks in the kitchen. It’s important, I think, to always strive to have as least clutter and just a clean, light-weight experience that people can grock(?). People tend to forget that and it’s very easy to say “I want the entire kitchen sink as a feature-set and present all on the same page”. Hopefully there’s someone in charge of the company that can fight those battles, because as you get bigger there’s more and more battles to fight when it comes to that kind of stuff.

Paul: We do a lot of large public sector and very bureaucratic websites – that’s the kind of work that we do – and that’s terrible for that because they have entire committees that are arguing over what content to put on their site, so it’s something I’m very familiar with. There’s a great book which you might have read called “Laws of Simplicity” – have you read that?

Kevin: I haven’t read it, no.

Paul: Superb book! Which talks about exactly this and how to go about simplifying anything, from your life right the way through to a website. It’s really interesting stuff. John Madda, I think.

Kevin: I have to write that down. I am typing it to the iPhone as we speak.

Paul: Do you have any questions you wanted to ask?

Stanton: Yeah, one of the key things I took away from your talk is when you said: “stop thinking you understand your users and learn what they actually do”. You said you do user testing, is there anything else?

Kevin: To be honest I don’t even like user testing. I think user testing is great for the big gotchas, like where you’ll slap your forehead and say “oh boy, I don’t know how we were about to miss that one” just before their products went live. I remember even before launching Digg – I was probably about 3 weeks out – and I was showing my friends, who I respect their opinion on all things Internet, I was showing them what Digg was. And several of them were like “I just don’t get it,” “I kinda understand what you’re trying to do” In my mind, there’s been so many times when you have so many well-educated people give you an opinion one way or another on whether or not something’s gonna work, but until you actually release it and get it in real users hands, you really don’t know what’s gonna happen – and it can go either way. I’m not saying there isn’t stuff you can do to, hopefully, make it go into a positive way. Like when you’re developing a feature, you’re bouncing it off the right types of advisors and people that you trust in the community that can think through some of these problems. But I think that 9 times out of 10 it’s better, rather than try and over-think it and sit there and say “we absolutely have to have this as part of the release” or arguing for weeks on end over how something should go, I’d rather take that time, make a decision: develop it, release it, and if it doesn’t work – worst case – you change it. That’s worst case! So many people forget that, they think it has to be perfect before they get it out there and it’s like “Get it out there!” because they’re just wasting time. It kills me when I watch people going on and on for weeks debating things. When in the same amount of time they could’ve released it, fixed the problems and re-released the code.

Paul: There’s seems to be this perception that the web is some kind of fixed thing that once it’s out there, people have almost got the attitude that it’s like printing a book; there’s no going back.

Kevin: Without a doubt! They think it’s like printing a book. And the other thing is they think that failure is a horrible thing. I don’t see it like that. If you fail at least you’re being real with your user-base. Jump on the blog, write a post and say “You know what, we fucked up there. That was a bad feature, we should’ve done it like this. Thanks for your feedback. Here’s the new feature.”

Paul: There’s a great quote from Winston Churchill who said once that “Success is going from failure to failure without losing enthusiasm” which just sums it up brilliantly. Any other things?

Stanton: You mentioned building a group of advisors, a group of people you trust and can not be afraid of to show ideas to and get their feedback, even if its bad feedback. And you talked about not necessarily designers or developers. What kind of advisors do you have, not necessarily for Digg ’cause I guess they’re quite high-business-level people, but for small ideas that you have that just bounce off people?

Kevin: I don’t have any official advisory roles on my other projects, but if you’re fortunate enough to befriend people in the industry that you really respect their opinion – I’m always bouncing ideas off of Tony from Zappos or like some of the WeFollow Twitter directory stuff off of Ed from Twitter – you need these guys. Even if you don’t have official advisory roles with them where you’re giving them shares, just to be able to sit down and have a coffee and brainstorm is just such a valuable thing. Even some of our angel investors, some of the best angels can be advisors as well; they’re not just investors, but hopefully you’re allowing them to invest in your company because they’re adding value outside of just the money that they’re contributing. So some of our angels are just extremely well-connected people in the Bay area or wherever, and to just be able to go to them and say “you know I’m having a really hard time with image storage or scalability in this area” and they go “oh, well I’ve worked with a guy here, I know this guy here and let me just set up a lunch “and they send 2 emails and because we both mutually respect that investor, they’re willing to get together with you. Little things like that can be really valuable.

Paul: Kevin, thank you so much. I know you’ve gotta go on and do other stuff, so thank you for taking time to come on the show and maybe we’ll talk to you in future.

Kevin: Sounds good, thanks for having me.

Thanks goes to Simon Hamp for transcribing this interview.

Vimeo: Lessons in customer care and community

In my post I shared my negative experiences with Vimeo. In this video I look at the lessons we can all learn about handling customers and engaging with communities.

I believe in learning from every experience whether positive or negative. I therefore thought it only appropriate to ask myself what I (and by extension every other website owner) can learn from the mistakes of Vimeo.

And of course I simply had to share my thoughts in a ‘non commercial’ video format ;-)

You can read my original Vimeo post here.

Alternatives to Vimeo

Several people have asked me where they can move their videos to avoid Vimeo’s draconian and erratic policies.

If you video is truly ‘non-commerical’ and your concern is not Vimeo’s commercial policy but its limitations on where your video can be displayed then I would recommend Viddler.

However, if like me some of your videos do have commercial content then I would recommend Vzaar which is essentially Vimeo for business. That is where I have moved and have so far been impressed.

Vzaar

10 problems your content management system will not solve and how to overcome them

Content management systems are often perceived as a silver bullet that will solve all your content problems. In reality having a CMS is not enough. You must also address broader issues associated with the content of your website.

So many website owners hate their content management system. This is often because it has failed to live up to their unrealistic expectations.

Many organisations purchased their CMS hoping to solve a wide range of issues surrounding content production and delivery. In reality, a CMS is only capable of overcoming relatively few. In fact often a content management system will solve one set of problems only to create more. It is these new problems that I wish to address here.

What follows is a list of 10 issues that are either directly created by content management systems or that a CMS will fail to solve.

1. A lack of editorial control

One of the primary reasons organisations purchase a content management system is to de-centralise control of content and therefore remove the bottlenecks that surround posting content to the web.

The consequence of this approach is a lack of central control to ensure the quality and accuracy of copy produced. This can lead to contradictions and varying styles of writing across the site.

Although many content management systems provide the tools for central editorial control, they are not always used and require somebody with the editorial experience.

The Solution: Get an editor

Unfortunately this is one problem that technology cannot solve. What is required is a content editor. Somebody who checks what is being produced and ensures it communicates a consistent message in a consistent tone.

Ideally this should be somebody who has experience in writing and editing online copy. However, the most important thing is that this person feels confident in editing copy, and has the authority to remove inappropriate material.

This person will also require a vision for the site and in particular what personality it should be projecting.

2. A lack of personality

Many websites lack real personality. They either ooze marketing BS or come across as singularly bland. This is largely due to the fact that they have been written by people more interested in communicating facts or selling stuff, than wishing to engage with users.

Websites with great copy that is full of personality, stand out from the crowd. They do more than convey information. They actively seek to make a connection with users in much the same way people do face to face.

Unfortunately the distributed nature of content production through the use of a CMS undermines that.

The solution: Decide on your sites personality

The first step towards overcoming this problem is to define who you are. If your website was a person what type of person would it be? What words best describe your sites character? Is it playful, serious, enthusiastic, or friendly?

Next put together a content style guide. This will include examples of writing styles that should be used on your website. It will also include guidelines in terms of tone and wording. This document should then be distributed to your content providers.

Producing an effective content style guide is not an easy task. You might wish to consider employing a freelance web copy writer if you do not have somebody in house. However once it has been produced, it should provide everything your content providers need to add some
personality into your copy.

Of course that does still require your content providers to be committed to the cause.

3. Uncommitted contributors

One of the great selling points of having a content management system is that they allow anybody to post to your website. Unfortunately, just because your staff can edit the site, does not mean they will.

It is not unusual to find that content management systems go unused except for by a few individuals. The belief that content management can be easily decentralised is false. There are two primary reasons for this.

Firstly, some people do not see it as their responsibility to provide web content. They see the website as a marketing or sales tool and so should be managed by marketeers.

The second reason is that most people do not have the time. Writing web content is often seen as a low priority and constantly gets pushed out by “real work.”

The solution: Recognise the importance of the web

The solution to this problem has to come from senior management.

The website needs to be seen as a critical business tool and job descriptions must reflect this by making site maintenance a key component of people’s job. This should include website duties being apart of employee assessment.

There is however another reason people do not using the CMS – they don’t know how to use it.

4. Poorly trained authors

When an organisation rolls out a new content management system they almost always offer some form of training. However, in many cases it is not enough.

Normally training consists of an intimidating manual and one off training session. For the few people who are updating the website regularly this is probably enough. However for more infrequent content providers, this is inadequate.

The trouble with one off initial training sessions is that by the time the content provider comes to update the website, they have forgotten what they learnt. Admittedly the information they need may well be contained in the manual, but who reads those?

This can easily lead to only a few people capable of making updates to the site, thereby undermining the very reason for having a CMS in the first place.

The solution: Provide video training material

The combination of occasional users and new employees, means that most organisations need a long term strategy for training people in the use of their content management systems.

We have found that a series of short video tutorials covering key functionality works much better than training sessions or intimidating manuals.

We still run training sessions for frequent users. However, the video tutorials allow users to work through the material at their own pace. Also, unlike a training course they can learn only the parts of the system they actually need.

However, training in the technology is only half the battle. Content contributors also need to know how to write compelling copy.

5. Bad copywriting

The harsh truth is that not everybody can write good web copy. Even somebody who writes brilliantly in print, does not necessarily write well for the web.

There is an art and science to writing good web copy that many people are unaware of. Copy written by content providers is often verbose, un-engaging and hard to scan.

The solution: Provide a structure for content production

The solution is three fold:

  • First, the introduction of an editor means that content providers do not have to worry about writing perfect copy. It should be the job of the editor to take the raw copy they provide and re-write it for the web.
  • Second, the training provided with a content management system should extend beyond the functionality and also include advice on writing good web copy.
  • Finally, by producing a basic template for content providers you can help them focus their writing. A content template should ask questions such as who is the audience, what is the key message for this page and what is the call to action?

However, the problem is not just limited to the quality of content but also the quantity.

6. Bloated websites

Much like this post, most websites end up far too bloated. This is a problem that content management systems only serve to exaggerate.

By removing the barriers to putting content online, you encourage people to add more. However, more is not always better.

Content providers often approach the website with entirely the wrong mentality. They look at the content they have or can easily produce, and decide to put it online because “somebody will find it useful.” They are driven by what content is available, rather than user’s need.

The problem is that the more they put online, the harder it is for users to find the content they want. It is like trying to find a needle in a haystack.

The solution: Focus on users and remove

The best solution is to prevent this from occurring in the first place. This is done by fixating on user needs. Before putting anything online ask two questions:

  • Is the content aimed at your primary audience?
  • Is the content essential for helping those users complete their objectives?

If you cannot answer yes to both questions, then seriously consider whether putting the content on your website will cause more harm than good.

Of course, you may already have a bloated website. If this is the case then you need to review each page of your site and apply the principles above. If a page fails to cater for a specific use case of your primary audience, then it maybe time for it to be removed.

The problem is that most organisations have people responsible for adding content to their websites. However, few have somebody charged with removing it. This is an important role and one your web editor should have the power and time to do.

However, user needs is not the only criteria for judging the worth of content. There are also calls to action.

7. No clear calls to action

As I have already said, most content providers are focusing on conveying information rather than meeting users needs. However, they are also neglecting the business needs too.

With the exception of marketeers and sales people, few content providers are thinking about calls to action. What is it that you want users to do next? How do you wish them to respond?

Even when content providers are thinking about calls to action, they are focusing on the big actions such as “contact us.” Until the user is ready to take those major steps they are left to wander around the website.

The solution: Always guide the user to the next action

It is important to consider the main calls to action for the entire site. Typically they consist of one or two major actions such as buying a product or completing a contact form.

However, there is also a need to think about the calls to action of each page. Avoid leaving your user with no obvious next step.

Take for example this page. Directly below this article you can take three actions:

  • Leave a comment
  • Provide feedback – That leads to videos offering a number of next steps
  • Read a related post

At no stage is the user left without a next action.

A big source of next actions is your information architecture. Unfortunately most navigation is not focused on users needs, let alone business objectives.

8. An organisational focused IA

An unfortunate side effect of running a content management system is that it encourages information architecture built around organisational structure rather than users needs.

If you look at most organisations CMS driven websites, their information architecture closely mirrors their internal structures. This is because it is easier to divide up responsibility for updating various parts of the site if it is structured along departmental lines.

The problem with this approach is that users do not think in terms of organisational structure. They are task focused and so often an organisational IA is entirely inappropriate. It leads to confusion and frustration among users.

The solution: Focus on user tasks

The only solution to this problem is to stop structuring sites around organisations and start focusing them on users.

Although it is easier in most content management systems to allocate permissions based on a per section basis, there is not normally a specific need to do so. It is just as feasible to give access on a per page basis making it unnecessary to organise around internal structure.

Ultimately your site should be about your users and that includes your IA. However, it does not stop there. The community you build around your site is important too.

9. No sense of community

Increasingly content management systems come with some great community tools. They have forums, comments and integrate with everything from Facebook to Twitter. However, great technology does not build great communities.

Many organisations implement these community features on their site and are disappointed when they are not used.

Worst still some organisations launch these features but moderate so heavily that users respond negatively. Eventually the functionality is removed entirely.

The solution: Build relationship not functionality

It is important to realise that online communities are about relationships and not technology. If you want to build a successful community around your website, you need to actively and regularly engage with users.

This involves having people within your organisation who are constantly talk to users, asking and answering questions, and getting to know people through open and honest relationship.

Of course, the problem here is the same as content production. This is not seen as an official role. Instead it often falls to enthusiastic individuals. If you want your community to succeed you are going to require passionate people who have the time and resources to sink into that community.

And it is a lack of resources that leads us to our final problem that content management systems cannot solve – single language content.

10. Single language content

The majority of invitations to tender Headscape receive for content management builds, request multi-lingual support.

In the end few of the sites we build actually make use of that functionality. In effect they are paying money for something they will never actually implement.

There are two many reasons for this.

The first is aspirational. Many organisations request multi-lingual support because they have dreams of expanding in the future and unfortunately those dreams do not come true. I can at least respect this viewpoint. There is nothing wrong with planning for functionality you might need at some point in the future.

However, the second reason is not so admirable. A lot of sites fail to implement their multi-lingual support because they have not fully thought through what that involves.

Implementing a CMS with multi-lingual support is easy. Creating a multi-lingual website is hard. You have to decide what content is going to be translated. You need to find a translator and then you also need to maintain that content over the long term.

The solution: Think twice before requesting multi-lingual support

There has to be a good business case for implementing a multi-lingual website. Unless you are sure that you are going to make money from a foreign market, it is probably not worth investing in language support.

If you aren’t serious about supporting other languages do not add it to your ITT, at least not as a primary requirement. There is no reason to rule out a CMS for not supporting multiple languages unless you are sure you are going to use that functionality.

Conclusions

You could interpret this post as a criticism of content management systems. That is not the case. I believe content management systems are a valuable addition to most websites. However, as I said at the beginning they are not the silver bullet may perceive them to be.

The success of your CMS is largely reliant on you being aware of its limitations and being prepared to deal with these restrictions. If you do then a CMS could be the best investment you ever make.

10 ways to get more involved with Boagworld

Boagworld is no longer just my personal blog. It has become a community. Why not get involved.

What started out as my own personal blog has become so much more and its great to see so many people keen to contribute.

If you enjoy Boagworld and want to take part there are a 1o ways you can do so.

1. Join the forum

By far the best way to get involved is to join our forum. It is full of designers, developers and website owners keen to answer your questions. You can chat about the challenges of web design or share cool tips and tricks you have learnt.

Join the forum now

Screenshot of forum

2. Suggest a topic

We are always looking for ideas to use on the show or the blog. In my experience it is you guys that have the best suggestions for topics. Why not let us know your ideas using the suggestion widget in the right hand menu.

Screenshot of suggestion widget

3. Leave a voice message

Did you know you can leave a voicemail for us to use on the show? If you are in the UK call 020 8133 5122. If you are outside the UK call Boagworldshow on skype.

4. Write a blog post

As I have already said Boagworld is no longer just my blog, it is the community’s blog. If you have a great idea for a blog post we would love to hear it. Write it for your own blog, send us the link and we will republish it.

Some of our most popular blog posts are by guest authors.

5. Rate our posts

We are always looking to hear your feedback on what we post. At the bottom of each article you will notice we now ask for your vote. Take a moment to vote for the posts you like (or dislike). That way we can improve the quality of what we post here.

What did you think about this post

6. Produce a review

From time to time we like to include reviews on the show. If you have used a great piece of software or web application why not record a 5 minute audio review and email it to the show.

7. Follow us on Twitter

If all you do is read this blog or listen to the podcast, then you are missing out. The real action happens on Twitter. There are two accounts worth following:

  • @Boagworld – This is my personal twitter account. I tend to talk about a lot of web design stuff and post daily audio web design tips.
  • @Boaglinks – As the name implies this twitter account includes lots of useful web design news and links.

@Boagworld also provides you the opportunity to chat with me, share ideas and ask questions.

8. Join our Facebook Page

Like all good online communities we have a Facebook Page. To be honest I am not entirely sure what to do with it. However, you are welcome to join. You might even give me some ideas about how I can make more use of it!

The Boagworld Facebook Page

9. Do a consultancy clinic

One of my biggest frustration is that I cannot answer everybody’s questions. One option is to ask your question in the forum instead.

However, I know people sometimes would prefer the opportunity to discuss ideas with me on a one to one basis.

The compromise I have come up with is the Headscape consultancy clinic. This enables you to chat with me via Skype and get advice on your business, while at the same time allowing me to pay my bills!

I hope you agree it is a fair compromise :)

Headscape Consultancy Clinic Website

10. Micro podcasts with AudioBoo

As I mentioned early I have also started recording daily audioboos. These are short audio posts (lasting up to 3 minutes) that you can subscribe to via iTunes. They contain advice and tips about designing, developing and running websites.

Audioboo Website

The great thing about Audioboo is that you can record your own. If you tag them with “for boagworld” we will look at including them on the podcast.

Conclusions

Obviously this list does not include the podcast itself, this blog or the interesting links found in the footer. However, hopefully it shows we are keen to include the community in anyway we can.

If you have other ideas of how we could include people please post them in the comments.

8 tools & techniques to improve your blogging

Blogging is hard. However, as with everything in life it is easier if you have the right tools for the job. Here are 8 which help me.

I have been blogging for over 4 years now. The vast majority of people give up within 3 months. That is because blogging can be hard work. The effort of coming up with subject matter, the sheer mechanics of writing and publishing a post, can all be too much effort.

To be honest I am amazed I still blog. I am lazy, I don’t like hard work. However, I have kept it up because I have discovered a number of tools and techniques which have made the job easier. I thought I would share them with you.

Making idea generation painless

The biggest challenge most bloggers face is picking subjects. The longer you blog the harder it gets. Often you feel you have completely dried up. Fortunately, I have discovered four tools that help me:

1. Find inspiration using Google Reader and Newsstand

I read a hell of a lot. I am subscribed to hundreds of RSS feeds. I find them a massive source of inspiration for blog subjects of my own.

When I arrive at work in the morning I open up Google Reader and scan through any stories that have come in over night. If I am interested in a post I send it to Instapaper to read later.

Screenshot of Google Reader

In the evening I repeat the process but this time I an on my iPhone and I use Newsstand. Newsstand is a superb iPhone App that integrates into Google Reader as well as allowing me to tweet about a link, send it to Instapaper or email it to myself.

2. Engage with your community using cotweet

Asking your readers for suggestions is also an excellent way to get inspiration for posts. I have found twitter a superb source of ideas.

However, I have found that time differences can make twitter a challenge when it comes to soliciting suggestions for blog topics. If I only ask for suggestions when I am awake, I will never hear from those who live further afield. Also even if they do spot my tweet, it would be easy for me to miss their responses.

I have got around this problem by using a web application called cotweet. Among other things cotweet allows me to schedule tasks so I can post requests for ideas even when I am asleep. It also allows me to track @replies I receive and ensure I have read everything suggested to me.

Screenshot of cotweet

Obviously there are many other twitter clients, but this is currently my favourite.

3. Collect ideas with Omnifocus

Inspiration can strike anytime but you can be sure of one thing – when you sit down to write a blog post your mind will go blank. That is why it is so important to keep a note of all your ideas.

Basically all you need is a list. This could be produced in notepad or scribbled on a piece of paper. However, for me those ideas live in Omnifocus along with the rest of my life.

Omnifocus Screenshot

The reason I like using Omnifocus is because I can easily add ideas either from my laptop or iPhone. Also it is extremely quick to add those ideas whether they are submitted by users via email or just pop into my head while lying in bed. Finally, I can flesh out those ideas by adding notes within Omnifocus.

4. Discover popular subjects with PostRank

With any luck you will have too many ideas to write about. So how do you narrow down the choice. One way is to look at previous posts and see what content proves popular. However, judging popularity is more than the number of people who read a post. What about those who save the post to delicious or tweet and comment on it? A good article should not just be read, it should encourage engagement.

Fortunately I have just recently discovered a tool that identifies these engaging posts. PostRank looks at all forms of engagement and ranks the popularity of your posts. In a single glance you can see what types of post works and what doesn’t.

Streamlining the production process

Once you have take the pain out of idea generation, the next area for improvement is how you write the posts. From dealing with resizing and uploading images to the risk of losing unsaved work, it is important to have the right processes in place.

5. Post easily with Posterous

On some blogs like this one, you want to add well considered and constructed posts. On others you just want to throw something up as quickly and easily as possible.

I wanted to start a personal blog that was more like the latter of the two options. I wanted to be able to put a thought online in a matter of seconds or grab something I have seen elsewhere and repost it.

The answer was Posterous. Posterous allows me to post directly to my site via email. It also allows me to clip video, text or images from a website using a bookmarklet and then republish my post to twitter, facebook, flickr and more.

Posterous Screenshot

It’s fully customisable and takes absolutely zero time to setup.

6. Write and preview in Marsedit

For the longest time I posted directly to my WordPress blog using the WordPress interface designed by HappyCog. It is intuitive, beautifully designed and did everything I needed.

Wordpress Admin Screenshot

However, more recently I began to get frustrated with my connectivity. Sometimes I wanted to write a post when I was without a connection or my connection to the web was particularly slow. In such situations I prefered a desktop editor. After trying a few I settled on Marsedit.

MarsEdit Screenshot

Marsedit has a couple of things going for it that finally convinced me.

First, I could configure keyboard shortcuts for elements I found myself regularly adding to a post. For example I have a keyboard shortcut setup to automatically paste the current URL in the clipboard to an A tag.

Second, it has an excellent preview facility that allows me to view my post as it will look on the live site.

7. Hassle free image management with Skitch

Imagery has always proved a headache when blogging. Not only do you have to source imagery, it needs resizing and then uploading before you can finally add it to your blog post (once you have copied and pasted the url).

I streamline this process using a screen capture program called Skitch. Skitch allows me to capture anything visible on my desktop, resize it and upload it in a matter of seconds. What is more when it uploads to your web server, it copies the url to your clipboard so you can immediately paste it into your blog. You can even configure it to provide you with a complete IMG tag if you wish.

Since installing Skitch I have found myself adding considerably more images to my blog posts.

8. Focus with isolator

Finally, I am somebody who gets distracted easily. Email, Twitter, IM, they all lure me away from the job in hand – writing a blog post. Personally, I have found this is a particular problem since moving to a mac. Unlike windows it is easy for your screen to become cluttered with open applications. I find this clutter distracting.

Screen capture of my cluttered desktop

What I want is to be able to hide all of this distraction and focus on my writing. The answer is a little application called Isolator.

My desktop with Isolator turned on

Isolator does one thing, it blacks out everything other than the active window. All of your other applications are still running but are hidden. Perfect when trying to write a blog post.

What tools do you use?

So that is my list of techniques and tools to aid you’re blogging. However, I am acutely aware that it is a personal list. For a start it mainly has mac apps.

What tools do you use to help you’re blogging? Share your experiences in the comments below.

10 Harsh Truths About Corporate Blogging

Every company in western civilization seems to have a blog these days. But are they worth it, and why are so many terrible?

I have reached the conclusion that most organisations have a blog simply because they feel they should. Many marketing departments fail to ‘get’ blogging and have poorly visited blogs with few comments. Because their blog fails to perform they conclude that blogging is an ineffective marketing tool and either remove it entirely or leave it to languish.

However, it does not need to be this way. Corporate blogs can be a powerful communication tool that builds brand awareness and nurtures a sense of engagement. You only need to look at the vibrant community surrounding the 37Signals blog to know that corporate blogging can work.

A screenshot of the 37Signals blog showing a large number of comments

This post asks the questions – why are most corporate blogs failing and why do the few succeed? To do this we need to face a few harsh truths.

1. A blog does not magically generate traffic

When companies first started launching corporate websites they perceived them as a marketing channel that would generate leads. They had a ‘build it and they will come’ mentality. Over time they realised that a website is more like a storefront. A few people might wander in off the street, but most of the time you need to advertise to attract trade.

Many marketing departments are making a similar mistake with corporate blogs. They perceive them as a way to generate new traffic, when that is not their primary role. Admittedly the keyword heavy nature of a blog will help your organic rankings, but that is a secondary benefit.

The real role of a blog is to generate repeat traffic which is considerably more likely to complete a call to action. A successful blog has a regular readership who is being constantly reminded of your brand and products.

Of course building up a readership takes time.

2. Blogging takes long term commitment

Building a readership is a long term commitment. It can take months for users to recognise your blog as a consistent source of useful information. Only then will they start visiting it regularly and recommending it to others.

It doesn’t just take time, it also takes commitment. That means posting regularly and to a schedule. Users are more likely to visit your blog if they know you release a post on a certain day each week.

Of course ultimately you want them to subscribe so they don’t need to continually check your site for new content.

3. Teaser feeds are a wasted opportunity

Users can subscribe in a couple of ways. They can either sign up to receive email notifications or subscribe to an RSS feed. This is a crucial step in engaging readers. That is because users are effectively giving you permission to  remind them about your site and brand.

However, it is remarkable how many organisations fail to grasp this opportunity. Instead of using the chance to push content to users, they only provide a teaser of blog posts. This means users have to click through to view the whole post.

This practice is born out of a false belief that users need to see your site. They don’t. Unless your revenue is driven by site advertising, there is no need for users to click through to read your blog.

The purpose of most corporate blogs is to build and maintain brand awareness while motivating users to engage. None of that needs to happen on site. The blog post itself builds and maintains awareness, while requests for comments or calls to action motivates users to engage. Users do not need to see the rest of your site to respond to the copy of a blog post. Of course for that to be true, posts need to be engaging.

4. Your not ‘engaging’ anyone

The most successful blogs are more than a broadcast tool. They are a dialogue between the individuals within your organisation and your users. It is important to listen, as well as speak.

Unfortunately the majority of corporate blogs fail to engage. Instead they focus on telling readers how great their products and services are. Rarely do they ask for feedback or ask questions. In fact it is not unusual for companies to disable comments for fear of criticism.

Instead you should be encouraging users to contribute to your blog through comments and constructive criticism. It is a superb opportunity to get free feedback from your customers, something many organisations pay market researchers for.

Part of the problem is that most corporate blogs offer nothing more than rehashed press releases.

5. Press releases shouldn’t appear on a blog

Let’s set aside the debate over whether press releases  have a role in today’s web centric world. Whether they do or don’t, you need to realise that a press release preforms a different role to that of corporate blog.

As the name implies a press releases is meant for professional journalists. It is designed to encourage journalists to write about your product or service. It is not designed for your customers.

A blog on the other hand is meant to be read by prospective and existing customers. It should be engaging, informative and helpful. When writing a blog post you should always have the end reader in mind. What will they learn? What insight will this give them into who we are? How will it help build our relationship with the reader? You should never simply copy and paste press releases or news stories.

The other problem with press releases is that they are corporate statements. A blog should have a more personal tone.

6. You sound like a faceless corporation

People don’t like interacting with organisations, corporations or machines. People like conversing with people. One of the things I have learnt about selling web design services is that once people have established that you offer a good service at a reasonable price, the next thing they care about is you. Do they like you? Do they trust you? Do they think they can work with you?

People don’t like, trust or want to work with corporations. We associated those feelings with individuals, not companies. It is therefore important that a corporate blog is about the people within your organisation, not the organisation itself. Your blog should focus on different people and the role they perform with your company. They should be able to demonstrate some of their personality as well as share their expertise.

A blog is a place to let readers see behind the marketing spin and glimpse the real people within your organisation.

7. You need to show the warts and all

If you are a marketeer this may all sound a little scary. Its hard to control ‘the message’ when you are blogging. You have multiple bloggers from across your organisation who are effectively becoming corporate spokespeople, and you are allowing users to publicly criticise you on your own blog. This is a long way from traditional marketing.

However today’s consumers are very savvy. They are distrustful of traditional marketing and can sense when they are being sold at. A softer approach is required, one that is more ‘real’ and less managed. One part of that is admitting when you make mistakes.

A screenshot of GetSatisfaction.com

Dell constantly ignored criticism they received about poor customer service. They ignored the voice that the web provided their customers, until eventually a single disgruntled user stirred up a major PR nightmare with a single post entitled ‘Dell lies. Dell sucks.

Contrast this with the ‘warts and all’ approach adopted by photo sharing site Flickr. When faced with community criticism over the poor performance of their website they wrote a post on their blog entitled ‘Sometimes we suck.’ They acknowledged the problem and laid out a plan for correcting it. This non traditional approach to their brand image allowed Flickr to quickly defuse a situation that could have grown out of control.

A blog post on flickr entitled 'Sometimes we suck'

Perhaps when it comes to corporate blogging, marketing is not always best equipped to handle the task.

8. Marketeers often make bad bloggers

Let me be clear. I am not saying that all marketeers should be banned from blogging. What I am saying is that traditional marketing skills are not always best suited to the medium. Because blogging should be personal, transparent and not shy away from an organisations flaws, it can seem an uncomfortable communication tool for some marketeers. Also the traditional writing style of many marketeers does not fit well with the informal style of a successful blog.

If you are a marketeer responsible for the corporate blog, look for ways to encourage others within your organisation to blog. Think of yourself as an editor rather than an author. Target people who are particularly knowledgeable or already act as spokespeople for your organisation. Encourage them to blog and act as a copy editor tweaking and refining what they write.

You may find it hard to encourage others to blog. If that is the case try interviewing them instead. You can then turn those interviews into blog posts and hopefully encourage them to respond to comments. But remember, whether you are posting an interview or an article, do not expect too much from your readers.

9. You expect too much from your readers

Most of the corporate blog posts I have read are long, text heavy and boring. They take considerable commitment to wade through. In short, they ask too much from readers.

With so many blogs online you need to make your posts stand out from the crowd. Always ensure users can get the gist of what you are saying by just scanning the post. This can be achieved using a number of techniques…

  • Summarise a post at the beginning and in the title. Don’t leave users guessing what the subject is.
  • Be controversial to grab users attention.
  • Use headings as a way of grabbing attention and summarising content.
  • Use images to break up the copy and communicate key points.

Do not feel all of your posts need to be an essay. Short posts that propose a question or draw the readers attention to another site are just as engaging. Anything that is of value to the user is worth posting.

Finally, remember that not all blog posts need to be textual. Consider buying a flipcam and recording some video interviews with people around the company. Record an audio interview or post some photographs of corporate events. Just don’t expect users to read lots of copy. The only people who do that are your competition.

10. Your competitors will read your blog – Get over it!

I am amazed at how many organisations will sensor their corporate blogs because they are worried their competition will read it and rip off their expertise and ideas. Although it is true that your competition will do exactly this, what is the alternative? One the primary opportunities a blog provides is the chance to demonstrate your expertise. People will be motivated to buy from you because they understand you ‘know your stuff.’ However, if you don’t talk about your expertise, how will they know? You might be the best in your field but if nobody knows it then what is the point?

I write about my knowledge of web design all the time. I know that many of those who read my posts are competitors and learn from what I share. However, I know a lot of prospective clients read the content too. Should I silence myself for fear of being copied or should I prove to my clients that I know what I am talking about? I think the answer is clear.

Conclusions

Many organisations are still finding their voice online and corporate blogging is one way they can achieve this. It is not surprising that they are still making mistakes. The secret to success is accepting that a blog is not a traditional marketing tool. In my opinion, it has more in common with a customer services. Once you realise that and release it from the shackles of press releases and corporate news, it will begin to generate return on investment.

161. In or Out

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

Play

Download this show.

Launch our podcast player

Housekeeping

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

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

I am therefore pleased to announce Micro-Boagworld…

View Micro-Boagworld posts here

Subscribe to the RSS feed here

Boagworld AudioBoo Homepage

Back to top

News

Pricing and projects

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

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

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

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

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

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

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

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

IE8 and IE6

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

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

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

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

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

Once IE6 is gone we will be able to…

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

Simple and impressive design techniques

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

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

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

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

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

Influencing user behaviour

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

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

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

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

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

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

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

Back to top

Feature: When to outsource web work

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

Read the full article

Back to top

Listeners feedback:

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

A good introduction to Javascript

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

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

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

A good but free survey tool

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

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

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

A review of Clicktales

Peter shares his experiences of Clicktales…

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

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

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

Web Design for ROI

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

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

Rich adds: I agree this is an excellent book.

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

Pro Paypal e-commerce

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

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

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

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

Back to top

 

160. Education, Education, Education

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

Play

Download this show.

Launch our podcast player

Housekeeping

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

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

News

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

How to create a great web design CV

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

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

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

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

For the complete list of tips read the whole post.

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

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

Design: Make it Memorable

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

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

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

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

Statistics and website owners

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

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

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

That has often been my experience too.

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

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

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

Specialist vs. Generalist: Who Wins?

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

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

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

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

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

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

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

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

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

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

Back to top

Interview: Aarron Walter on Interact

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

Aarron: Thanks for having me.

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

Aarron: Yeah, yeah.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Aarron: Thanks for having me.

Thanks goes to Andrew Marquis for transcribing this interview.

Back to top

Listeners feedback:

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

Remote user testing

Our first email is from Steve. He writes…

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

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

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

What do you think of this method?

Sounds interesting although it would not be my preferred approach.

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

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

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

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

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

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

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

Finding a job

Our second email is a rather despondent one from Andrew…

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

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

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

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

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

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

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

Back to top

Series: Building A Better Web Application by Ryan Carson

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

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

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

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

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

Back to top

159. Special Guest

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

Play

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

Download this show.

Launch our podcast player

News

Alkaline

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

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

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

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

16 design tools for prototyping and wireframing

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

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

10 Lessons every freelancer should learn

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

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

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

Back to top

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

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

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

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

Sarah: Yup

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

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

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

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

Sarah: Really?

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

Ryan: To spend in the pub (laughs)

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

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

Paul: Yeah, pays the bills.

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

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

Sarah: Really?

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

Ryan: and a mac to develop on

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

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

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

Sarah: the app store!

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

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

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

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

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

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

Sarah: No, he was an old man.

Ryan: Oh, right. OK

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

Paul: Was he in just a pair of shorts?

Sarah: Yeah

Ryan: A pair of shorts and a smile?

Sarah: No, and a newspaper.

Paul: Strategically placed.

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

Paul: That’s OK.

Sarah: Oh, sorry.

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

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

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

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

Ryan: Yes, we only like the nice clients.

Sarah: Yes, we all like nice clients.

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

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

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

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

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

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

Sarah: Yeah.

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

Sarah: Do you skim-read them?

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

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

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

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

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

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

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

Sarah: Of course! (all laugh)

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

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

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

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

Sarah: Exactly.

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

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

Ryan: Er, yes.

Paul: Yes, ah the Nettuts, oh yeah.

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

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

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

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

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

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

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

Back to top

Listeners Questions:

Is Using Off-The-Shelf Software Wrong?

Jon Writes:

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

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

Thanks and keep up the good work!

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

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

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

Therefore, the pro’s are:

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

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

Don’t implement something you don’t understand!

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

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

How do you price and quote different projects?

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

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

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

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

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

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

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.

What's with the attitude?

We face many challenges as designers and developers – IE6, the fast pace or change, meeting the needs of disabled users. However, I am coming to believe that our biggest challenge is our own attitude.

This post started off as a bit of fun. It was going to be another spoof, this time in the form of a top 10 list of harsh truths. However, as I began writing I found myself actually believing many of the points. In the end I was forced to scrap that draft and start from scratch.

I am worried about how people see us as web designers. More than that, I am worried how we behave as web designers, both with our clients and towards one another.

Let me explain what I mean, starting with the more obvious and damaging area – our attitude towards clients.

Our attitude towards clients

I speak to a lot of web designers and in all of those conversations I rarely hear a positive word said about the people who keep us employed.

The overwhelming attitude towards clients is one of disdain. Oh, we hide our feelings reasonably well when dealing with them face to face. However, behind their backs we are often critical and derisive.

We see clients as stupid, awkward, or intent on derailing the project. In short we see them as the enemy.

We have to change this attitude. Not only is it damaging to the relationship, it is also untrue. Just because somebody doesn’t understand the web, does not make them an idiot. Without a doubt they will be far more knowledgeable than you in many, many areas.

You cannot have it both ways. On one hand we set ourselves up as experts who should be listened to. On the other, we are surprised that the client doesn’t instinctively know, understand and except everything we suggest. If they could, we would not be the expert!

We need to recognise the critical role the client brings to the web design process and stop trying to exclude them for fear they might bring something different to the table we might not like.

Stop treating your clients like children and start treating them as peers. That means listening to their contributions even when it does not sit comfortably with your own views. This involves us losing our sense of moral superiority.

You do not have the moral high ground

I do not hide the fact that I am an evangelical christian. That means associating myself with some people who have an enormous sense of smug satisfaction and moral superiority. Some of these people really think they are ‘Gods gift,’ literally! However, they pale in comparison to the moral and intellectual snobbery I encounter in the web design community.

I am fed up with web designers who judge others (and their own clients) with such passion and vigour it borders on the fanatical.

We are not poets, artists or preachers. We do not have the luxury of free thinking theory. We should be pragmatists that work in the real world and solve real world problems.

The problem is that most of our high minded ideals are nothing more than ego. It is about exalting ourselves at the expense of others. Let me give you a few examples of what I mean…

Why doesn’t your site validate?

I can’t believe they code in .net

He is always asking people to retweet his posts.

Oh, they are just link baiting

Comments like that are just about pulling others down. Validation isn’t everything and how can you judge somebody’s decision to code in a certain language without any background information? Hell, what does it matter to you anyway? As for link baiting and retweeting – what is wrong with wanting to drive traffic? There seems to be an attitude that desiring your site to be popular and working towards that end, is in someway wrong! Admittedly new traffic is not the whole story but it is a part of it.

Promoting your sites or services is not desperate or needy. It is good business. If all you offer clients is moral superiority and a well built site, then you are only offering them half a service.

I am not saying there are no lines. I do not condone black hat SEO techniques and I hate SPAM as much as the next person. However, I think we need to drop the attitude and consider the broader picture. We need to consider the business behind the site.

Stop trying to be intellectually superior

Unfortunately we do not just like to feel morally superior, we also like to feel intellectually superior.

We dress our profession up in impenetrable jargon and give ourselves fancy job titles. In many ways we are like teenagers trying to appear more grown up by smoking and drinking.

I guess this is not surprising. Our industry is barely in its teens. We are trying to find our identity and justify our existence. However, in the process we are in danger of becoming elitist and inaccessible to outsiders.

Take for example the recent rash of Top 10 posts. It is something I have started doing myself and have received a massive amount of criticism for it. I have been accused of dumbing down, catering for the lowest common denominator and being desperate for traffic.

Indeed top 10 posts do drive more traffic. That is because people like them. They like them because they are accessible. They are easy to scan and easy to assimilate. In what way is that bad?

Those who criticise do so because they feel that in some way these posts cheapen the industry or devalue what we do. I get the same criticism about my podcast. We joke on the show and have fun. We make the information accessible. Therefore we must be devaluing it.

In my opinion this is a view driven by insecurity. By wrapping up what you say in long words and impenetrable jargon you can hide the truth. You can sound better than you really are.

Unfortunately this just isn’t true. By making it impenetrable you are actually hiding its worth. By explaining what you know in a clear and accessible way you demonstrate its real value.

The desire for exclusivity

All of this is driven by a desire to the ‘cool kid’. Perhaps it is a hang over from our school days when geeks were far from popular. We try to impress and dominate, when we should be empathising and working together.

Another manifestation of this cool kid mentality is our rejection of anything mainstream. As soon as something becomes popular we drop it like a stone. Now our clients are talking about twitter, we accuse them of ruining it and start looking for the next thing. We want to be exclusive, special, different.

The trouble is the mainstream pays the bills. We need to break out of our exclusive little bubble and try to associate more closely with that mainstream. We need to understand what the general populace are embracing and go with that, even if it means still supporting IE6.

Conclusion

This post is aimed as much at myself as anybody else. I catch myself doing many of the things I have written about here.

In many ways the web design community is awesome. There are not many industries where direct competitors talk to one another so openly and freely. However in doing so we have become somewhat insular and very intense. I think sometimes we are under the impression that we are shaping the future and that every choice we make is of crucial importance.

At the end of the day we are just building websites. We need to get some perspective.

Thus ends the rant :p

7 Harsh Truths about running online communities

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

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

A well run community can…

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

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

1. Technology does not create community

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

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

Vanilla Website

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

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

2. Show some commitment

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

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

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

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

3. Learn how to lead

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

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

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

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

Photograph of Barak Obama

4. An antisocial community is your fault

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

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

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

Diggnation Homepage

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

5. You need to swallow your pride

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

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

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

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

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

flickr blog post - Sometimes we suck

6. Stop trying to control the message

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

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

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

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

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

Adobe complaints on Get Satisfaction

7. Nobody likes to be alone

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

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

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

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

Conclusions

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

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

10 harsh truths about corporate websites

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

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

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

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

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

1. You need a separate web division

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

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

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

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

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

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

Screenshot of Zeldman's website

2. Managing your website is a full time job

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

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

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

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

3. Periodic redesign is not enough

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

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

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

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

Screenshot of Cameron Molls Article

4. Your site cannot appeal to everyone

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

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

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

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

5. Your site is not all about you

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

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

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

6. Design by committee brings death

Illustration showing why design by committee fails

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

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

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

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

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

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

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

Post from Twitter complaining about being a pixel pusher

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

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

8. A CMS is not a silver bullet

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

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

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

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

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

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

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

9. You have too much content

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

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

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

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

10. You are wasting money on social networking

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

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

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

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

Screenshot of Microsoft's Channel 9 website

Conclusions

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

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

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