Boagworld

A blog, podcast and community for all those who design, develop and run websites.

Skip to content
Boagworld
Menu Subscribe
  • Boagworld
  • Podcast
  • Archive
  • Forum
  • Books & Talks
  • About me
  • Hire me
  • Boagworld
  • Podcast
  • Archive
  • Forum
  • Books & Talks
  • About me
  • Hire me
Subscribe Now
First time visitor to boagworld? Find out how the site can help you with our Guide to getting the most out of boagworld

Tag Archives: sign up

Post navigation

← Older posts

186. Mobile Web

Posted in Classic shows on October 7, 2009 by Paul Boag

On this week’s show: Brian Suda talks about the mobile web and Marcus suggests ways of responding to email inquires.

Play

Podcast: Download (33.8MB)

Download this show.

Launch our podcast player

Win Pitches, Charm Clients and Get Signoff

Being a great designer or developer is only half the battle. You also need to be able to promote and sell your services. Unfortunately many web designers and freelancers struggle to engage with clients.

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

It takes place on the 23rd of October in London. If you book soon the price is £375 although if you quote the code CWPB_09 you can get an additional 15% off.

Book Your Place Now!

Back to top

News

Sign up, Log in

Everybody hates signing up for new services. We also hate having to log in especially when we have ticked that little ‘remember me’ checkbox (or at least we think we did).

There is so much that can go wrong with sign up and log in, from lost passwords to mistyping. It is therefore vital that the usability of these forms is as good as possible.

This week I have come across two posts that might help.

The first is a post by Jeremy Keith in which he challenges two current practices for sign up and log in forms. The first is the practice of requiring users to enter an email address or password twice. The second is the default on ‘remember me’ buttons, which generally seems to be unchecked.

The second post I wanted to mention is a brief review by Techcrunch of the new Facebook Connect Wizard.

In case you haven’t come across the Facebook Connect Wizard, it is an easy way for anybody to add Facebook Connect to their website even if you have no coding knowledge. The wizard seems to consist of three simple steps that take a matter of minutes. Once complete users can log in to your site using Facebook. One less username and password for people to remember.

Search results design

Smashing Magazine has released a post that looks at how a large cross section of websites deal with search design. This follows on well from the recent A List Apart edition that dealt with search and we mentioned on last weeks show.

The Smashing Magazine post analysis’s the search design for a whole range of sites from Google to Walmart, and draws some interesting conclusions. These include some great advice such as:

  • Visited links should be indicated
  • Where possible, results pages should have RSS feeds or “subscribe” options
  • To monitor future improvements, request feedback from users after searches are conducted
  • If results span different sections of the site, indicate this by sub-headings or other dividers
  • Should allow re-sorting or filtering of results

Of course, just because a lot of websites have a certain approach to search, does not mean it is best practice. I have often seen bad practice copied from one site to another. That said, the list of recommendations seem solid. To read the complete list of suggestions check out the post on their site.

Is Windows 7 about to make our lives easier?

I was reading a post on Sitepoint this week entitled ‘Why Windows 7 Will Revolutionize Your Browser Testing‘ and it has started me thinking.

The part of the post that particularly caught my eye was XP Mode. This allows users to run IE6 for specific web applications under Windows 7. However, their default browser will still be IE8.

This will change everything. As I have said numerous times before, the reason IE6 survives is because of legacy systems within large corporates. In a single move this will overcome the problem. If they can use IE6 for these systems and IE8 for everything else then life is rosy.

There is a lot of positive buzz around Windows 7, and I know many large organisations who skipped Vista entirely are now serious considering upgrading. If that is the case we should see the number of instances of people running IE6 fall through the floor over the next year.

Finally we can move on!

CSS: From beginners to advanced

With the increasing buzz around CSS3 it appears CSS is having a renaissance. There are a growing number of articles which focus on emerging CSS support and browser manufacturers are falling over themselves to add new features.

This week Firefox 3.6 Alpha has been released adding support for a number of interesting new CSS features.

Sitepoint’s post ‘CSS3: To Infinity and Beyond‘ catalogues some of these additions and looks at how wide browser support for these now are.

The list of new features include:

  • Background resizing
  • Multiple background images
  • CSS gradients

Of course, unsurprisingly IE support is scares. However, with the proper application of graded browser support this should not be a major issue.

If you are starting out with CSS all of this talk of CSS3 may seem overwhelming. However, there is still some great advice being posted for you guys too.

One post you might want to check out is ‘30 CSS best practices for beginners‘. As the name suggests this should get you up and running fairly quickly and ensure you are building sites in the right way.

However, one word of warning. A few of these best practices are not so much… best practice. In fact some of the advice is down right bad! But do not let that put you off of reading the post. The editor has actually responded to the bad advice explaining why he believes it to be wrong. As long as you read his comments too you will be fine.

Back to top

Interview: Brian Suda talks mobile

Paul: so joining me on the show today is Brian Suda. who is on to talk about mobile web, good to have you on Brian.

Brian: Thank you very much.

Paul: Thank you so much for coming on, I think a good place to start would be if you tell the listeners a little about yourself and why the mobile web, and why we are talking to you about that in particular.

Brian: My background is originally in programming and software systems. I did my undergrad in massuri US, from there i moved on to the uk and Scotland, where I studied more about infomatics. So im really interestedin the background aspects, all the technical issues. But alot of the things iv developed when i started working on sites is more the front end and the usability, the way people think about mobile. Recently I’ve been working on lots of little mobile sites here and there as a freelancer all these new kind of mobile. Its getting much bigger and i think now is about the time the customer should be looking into it and the right time for them put their feet into the water or take what they have and maybe take it to the next step.

Paul: hmmmm, i mean one thing that’s knocking around a lot that people talk about when it comes to the web is the one site fits all mentality. Which raises the question of do we need to be doing things specifically for mobile devices or if we build out websites right can we avoid the whole problem.

Brian: It’s a very interesting question. Because the W3C does push this concept of the one web and there are definite pros and cons to it. The definite pro is maintenance costs, if your only dealing with one website you don’t have to worry about updating and keeping things in sync with data and things on a constant basis. But at the same time there are certainly different aspect to the way people use the site. One of the things that we really try to do is keep the one web in mind and really that means all the same information is available. It doesn’t have too look exactly the same or being the exact same format, it just needs to be available to the end customer.
So one of the things we’ve been stressing is that we don’t like the words “mobile web”, were trying to find a better term for that. Mainly because “mobile web” infers that your using a mobile phone or some sort of mobile device but thats not necessarily the case i mean the way we picture the mobile web is its about mobility. I think they’ve got mobile as a noun and it should be mobile as a verb. You are moving, your mobile. So really the same kind of site doesn’t always work. A good example of this is if you have a fancy iphone or ipod touch and your at home sitting on the couch you have no quarms about viewing the full bbc website. Your on wifi nice fast connection no big deal. But if your out on the move, want to catch the tube, or your late for the bus you want the mobile version of the site. Because you want it quick, you might be on GPRS or edge, you don’t have the time or the energy to download the full bbc website. So its not really about the device, its more about the situation.

Paul: Thats quite interesting that you raise, obviously the iphone is going to come up in the conversation when we talk about the mobile web as does android and the various other new operating systems that are emerging. The one kind of trait all these have is they have this rich browser experience, you know quite powerful browsers and again the other question i guess people are saying is the idea of designing for mobile devices going to disappear because the browsers are so capable. But i guess this issue of environment and situation applies whether or not the browser is sophisticated.

Brian: theres also going to be situations where even if you have a very robust browser, form input is always going to be a pain. So even though you may basically have safari replicated for the iphone it maybe easier to just have a phone number. I mean you have a device in your hand designed for making phone calls, thats what it’s number one purpose is. To force someone to fill out a form can just become a ridiculous pain, it disappears into the web somewhere and maybe someone will answer in 48 hours, but you maybe sat in an airport having lost your luggage. You know you want to talk to a real person immediately, not fill out a form. So i think there is always going to be situations where the medium or the situation is going to define what you want to do.

Paul: i guess also you were mentioning there about whatever mobile device your going to be using its difficult to fill out a form. I mean that brings up the whole issue of the user interface, that mobile devices are very different in terms of it’s not a mouse and a keyboard theres lots of different interfaces and i’m guessing thats problematic as well.

Brian: certainly, i mean navigating either between tab, the opera browser will do it one way where the down button will scroll through the page through the links, where the iphone everything is done with your fingers. So yeh its going to be different interfaces means different ways of doing things. Some flyout menus when you do on hover just don’t work on some devices. And i guess that comes back to basic web 101 accessibility and progressive enhancement. You know, make sure it works without javascript, without a mouse, just a keyboard and then start layering the information on top of that.

Paul: does that mean that there is going to need to be a lot of device sniffing to identify your on an iphone there for you have a touch interface, your using an older mobile device there for your using a keyboard or whatever else. Or is there another way of doing that?

Brian: unfortunately yeh, browser sniffing is one of those things that everyone says you shouldn’t do and it technically usually its done in a bad way i mean we all experience browser sniffing when we go to out banking website and the website says “sorry you must have firefox2 or higher” and you know you’ve got version 3, you scratch your head and figure they can’t do the math. Its usually because they browser sniff and then restrict what you can do. Where you should do it the other way around and say heres a working website, we are going to try and determine what browser you have and then layer extra functionality on top of it. And again this is one of those things you can skim the surface or you can spend working on it and tweaking your site, and its going to really depend on your audience. So with someone like the bbc who might have loads and loads of resources might want to go through and wrap loads of if statements around all different parts of their website. But then it becomes a trade of between maintenance and usability vs how much of a good experience your customers get.

Paul: I mean you eluded earlier to this issue of context, the environment and surroundings that people are in and i heard Cameron mold* SP speak on a similar subject. I’m just interested in your take on that an you know what kind of elements come into it. I know we’ve talked about user interface but what other element of context are important to consider.

Brian: can you give an example?

Paul: well, the one that springs to mind i guess is environment. You talked about being at the bus stop is an issue, there are other things like that.

Brian: sure, Google a few years aog did some really deep research into all of their properties Gmail, docs and everything like that and they realised that their mobile user base fell into 1 of 3 categories. There was a sort of “bored now” – people saying ok i’m waiting for coffee, i’m waiting for a friend i’ve got 10 minutes to kill I want to go do something, just to keep me occupied. And youtube does a good job of this, they say “we know you just want to waste some time so heres the top 10 most interesting videos”. So its not so much browsing and searching its just keep me occupied. Another category is the “urgent now” – so theres been an accident outside or the powers been cut. Thats good example of because if your power is cut your internet connection and regular computer might also be down, but you want the phone number of the electric company to report the outage or see how long this is going to take, maybe the only way to do this is through the mobile interface. This si one of thing you want to bubble up, if your the clientele your expecting this kind of information your wanting to bubble this information upto the top. We did some work for some airlines and we realised this is one of the categories “have i missed my flight” don’t burry this information 5 levels deep. The last category is “repetitive now” people who want to check their stock, the weather and they are done. They’re not here to browse necessarily or spend 30 minutes looking at the website, they are looking for one key piece of information and they are done. So depending that your customer base is these will kind of lead or guide your design decisions and usability and how you layout your website.

Paul: thats really interesting in terms of the different kind of content that you bubble up depending on the kind of device your on and the situation your in. I mean i guess that leads on to a more question in that there are a lot of website owners that are listening to the show, you said at the beginning that people need to be thinking about the mobile web, how do you go about deciding whether your content and what you provide as a website owner is relevant for a mobile device or ifits not. And then what out of your content is worth taking across to the mobile site, and whats not relevant.

Brian: sure, you can probably ask that same question of a regular website. The guy on the corner who is a corner, does he need a website and does he even need a mobile website. Maybe he needs a mobile website more than he needs a real website. Again its so easy to get started in the mobile area because you don’t need to learn anything new, you can do it with all the existing html and web standards now that you already have. Its just a matter a repurposing it or thinking in the context of a mobile device. A lot of that is just realising screen width, bandwidth information you can cram on a page, there is a few things to learn, but its not that difficult to get you feet wet and i would argue that its best to get started on the cheap and easy and see if it works. Try early and fail fast. From there you will kind of learn what your customers want, one of the things we kind of keep in mind is we don’t like the term mobile website so what we’ve tried to come up with a new term. We tried to think of sugar free or fat free. So we kind of framed the situation as the traditional desktop website we call that either full flavour or full fat, and then what people call the mobile web we call the sugar free or fat free. People understand fat free and full fat, everyone understands those concepts. So because its about the situation we might say ok im at my desk and im getting a million phone calls about x y z. sometimes its easier for me to look at the mobile website on the desktop computer because there is no ads and there no company history or anything. It’s just the raw information i need. So if you start think about it in the terms of fat free of full fat its other side consequence is if you are developing a mobile site and you boss may say we need this this and this. Your like ok its mobile site we can just add another navigation item, but if you start talking about things in terms of fat free when your boss comes to you and says we need this, you can say well is you site still fat free if we are adding more and more navigation links? And its a way to argue against feature creep.
P. yeh, that sounds very sensible. You said something very interesting there, you said its very easy to get started on the mobile web. And i can’t remember where i heard this, it may have been from you but someone once said something like as web designers you get really annoyed when a print agency turns around and says we can do the web as well. And yet web designer oh yeh we can deliver the mobile web. So i’m just interested in your perspective as to whether web designer should even be trying to do this kind of development or whether its really down to a new breed of mobile web specialists because there are different element involved in it. So is its something web designers should be doing and should websites owners be looking to them to do it, or should they be looking elsewhere?

Brian: thats very good question. I like the analogy of print design, because there will be loads of people who’ve bought a computer and get on indesign and all of a sudden think they are a print house. I think form a technical point of view there is nothing greatly different between a mobile and normal website. Its the same html, same knowledge, same standards and code. The bigger difference is the usability and the way people use the device, how you lay it out. You can probably make the same argument between web designers doing websites, like business card websites and web apps. There is still a lot of design element and design ideologies that transfer between both of them. Maybe in another year or two there will be a bigger niche for someone who specialises in mobile websites and usability. It’s one of these things people are hammering on the door mobile is the next best thing, for 5 or 6 years now and it’s always next year. Maybe it will be the same with specialist, but maybe again it’s a chicken and the egg and we need specialists before we get mobile websites. It’s a good question i don’t know.

Paul: ok, fairenough. I mean you talk there about technically its relatively straight forward to get going maybe you could kind of give us some ideas of where to start. There are web designers here that want to kind of explore it from a technical point of view, what are the common mistakes and what do they need to be aware of?

Brian: erm, well there’s a few of them i guess. Depending on the audience, that’s the first slice you need to taste. Who am i developing the site for? Sometimes it maybe internal to a company and sometimes it maybe very high profile and you realise most these people aren’t going to have iphone they will have blackberry or something similar. You need to figure out what your audience will mostly be using. This is just base line. The bbc would have a different set of rules, but this will get you started. Find out what their device is and what they are capable of. Most of the newer devices have a decent web browser, maybe running webkit or some other new browser that can handle html and xhtml. And then you can code up your sites like you do normally. Some older browsers and phones don’t necessarily handle all the css or everything in the same way, and then people argue its like coding for the web cerc 1999. You need to get back to tables etc it’s not pretty. Again it’s all down to how far and how deep you want to go. For things to get start there lots of good resources out there i know dev.opera put a few article up about introducing / getting into the mobile web. Theres lots of stuff on the web as you said Cameron mold *sp. I could send you some links for the show notes.

Paul: yeh that would be really useful people are always keen to take these in and move on with them.

Brian: i think it’s also a bit of stigma that everyone kind of assumes its quite difficult because they here these buzz words like 3G and WAP when in reality a lot of it has past now because the phones of today are capable of rendering html. I think people are just a little gun nshy of where to get started. I think it’s not as mystic of an area as people assume.

Paul: ok so, presuming then that the technology side isn’t too bad, let’s talk about the design side, the layout and the usability that kind of thing. Which is a different environment that we have been used to designing desktop applications. Tell us about some of the common issues and mistakes.

Brian: certainly, the biggest one is probably realising the vast variety of phones and browsers outhere. The physical device itself varies in just screen width and colours and what each is capable of. Where on a desktop it’s probably ranges from 800 to 1600 pixels and we have all these grid designs. Really in the mobile world it breaks down to screen from anywhere such as 88px to 120px all the way to the iphone at 480 in landscape. So how do you design for this, most of the time it ends up being a stack, where you stack them on top of each other, much like the iphone navigation. That at the moment seems to be what is falling into place. It’s probably like the rules of the web in 1999 when you have navigation in your left and then header and body area. As things develop trend and design of how things will flow evolve as well. Design wise things like the iphone handle lots of css just fine, some phones don’t. This kind of forces you to all the little tips and tricks with css where you put in h1 then indent text with negative marging and replace with background image. But it doesn’t always work when you get to mobile, maybe it won’t show background images. Maybe the blackberry doesn’t display images at all due to bandwidth. So there are always little catches here and there, it’s just a matter of testing, its going to come into alot of time on device. People assume testing, you’ve got to buy an iphone.

Paul: I was about to ask that.

Brian: the simplest way is you probably look around the office, maybe now everyone has an iphone. You code it up, you go around everyone and look at everyones phone. You go around and spot any issues. There a few other companies out there who you can buy time. I think device anywhere who will rent time on their server farm, you load a little java app…basically a webcam and you can see the phone in front of you. And you can say no i want to try on this and this phone. It allows you to get a quick grasp of what’s going on. Again nothing is ever going to be pixel perfect but once you realise, ok background images don’t work you have to do it this way. You get into a rhythm after one or two go around of what does and doesn’t work. if your a freelancder or do it for your company, you build up a nice little template and test suite so you know what works and doesn’t. So next time you pull out your template and your pretty much there already.

Paul: you mentioned there about what everybody in the office is going to have an iphone. I’m picking up a kind of trend that everybody within the web design community are excited about the iphone or love the iphone. It’s got a very capable browser that can do a lot and they know there is a good audience there and they are just going building application or websites that are optimise for the iphone. Do you think it’s a mistake, should we be looking to produce web content for a broader range of devices or is it ok just to target one or 2 deivces.

Brian: i would personally say that it’s a bad idea because I’m more of the thought that it should build a baseline set that works everywhere and build on it. That being said google said that 505 or more of its traffic is coming from the iphone so it’s a massive player in the audience that you can’t ignore. If those are your customers and your trying to sell something and you want to give them the best experience possible you may have to spend a bit more time and optimise for the iphone. Again whoever is the main one in the market, the iphone at the moment, the competition is going to build to that spec. So if you optimise for what’s in the lead and the other ones will come along to meet it. Again it’s not a great philosophy, again you at the click here for IE click here for netscape type thing. Best viewed in iphone browser. Which i prefer to avoid but it seems not be the way its going right now.

Paul: i guess you also need to take into account how people are using those phones. For example we know there are phones out there that are more popular than the iphone but iphone users are the ones accessing the web so it’s the number of people using the web using the device rather than number of handsets out there i guess.

Brian: yeh, the most famous kind of quote number against it are nokia 1100 phone little candybar phone, for everyone 1 iphone out there, there are 14 of these nokia phones, but they are the old green screen doing sms and that’s about it. Like you said the iphone isn’t a high percentage of the phones out there but it is a high percentage of those who are using the web.

Paul: its ultimately ROI that if you’ve got limited budget for this your better of concentrating on the device which the users are actually using the web. I guess to some degree that you also know iphone users are relevantly affluent if you’re selling something. If its an ecommerce site then that’s worse considering too i guess.

Brian: very true, very true.

Paul: so just to kind of wrap up here, where should people start where should they go from here. They’ve herad this interview, maybe they are a website owner or designer what should those 2 audiences next step be in investigating the mobile web be?

Brian: from a technical point of the easiest thing to is to make a few mock ups, that’s probably low cost to just get your feet wet. Test it on a phone or two and then show it to a boss or the rest of the team and say hi look, this took me an afternoon, i’ve learnt something new look how great it is. From that you don’t need to make it public, some of the sites we have done in the past have stayed within the company for 6 months maybe a year, sometimes even never launched. Just to kind of get internally the feel of is this we want is this what we want the public face to be. Can we actually release because this it has less features. So t’s not a huge commitment you don’t have to announce it to the world, i guess that’s one view of developer. From a design perspective i guess it’s just how and the usability works, what you can and can’t do. A lot of css doesn’t work, understanding that will give you a leg up when you want to develop a real website. If you developing a traditional website you may use x hours in photoshop and x to cut it up, if you quote the same thing for a mobile website you will probably be well of, a lot of going back and forth. So learning some of this early on is probably going to help you alter on when you want to pick up and quote on a job or you want tp pitch something. Your going to be more realistic and it will certainly take more hours. Some skills will transfer but it will be a bit of learning curve.

Paul: ok thats really great thanks for coming on the show and we will include those links if you send them over. Thanks very much for your time.

Thanks goes to Andy Kinsey for transcribing this interview.

Back to top

Listeners feedback:

We have been collecting some subject suggestions via Skribit. Some of the suggestions do not justify an entire blog post so we thought we would respond to a couple here.

If you want to submit an idea, use the Skribit widget in the right hand column of this blog.

Responding to email enquiries

When we receive an email asking for a quote how do we follow it up?

Well, the honest answer is… it depends! People get in touch in a number of ways and with varying levels of detail in their enquiry emails. Blunt honesty is usually the best policy so I will say that the first thing I am trying to gauge on any enquiry is whether or not we are a good fit financially with the prospective client and whether or not we can deliver whatever ‘it’ is within the requested timescales.

I have talked about this in the past so won’t dwell on it too long but, I have been bitten too many times not to consider it important. Only a few months back I spent nearly a week putting together a proposal for a prospective client that was dismissed out of hand because it was too expensive. What an utter waste of my time and, please note, a fairly large waste of this particular client’s time too. It takes a fair amount of time to wade through a hundred page document and, if they had provided budget information I would probably have passed thereby leaving the way for another agency who may well have been their first choice. Grrrr…..

Calm… calm…

So, before getting into any serious detail about a project I will ask people about their budget. If they don’t know then I will talk about the kind of prices associated with a particular type of project. If the figures seem to fit reasonably with expectations then I will ask about delivery deadlines (and why they exist). Often deadlines exist because people think they should have one but equally there may be a flagship conference or similar that the ‘site’ must be completed by.If we can reach a rough agreement on budget and timescales then the next thing is usually for us to put together some kind of quote or create a proposal.

For pretty much any job I will ask the client for a brief describing the work. In fact, most enquiries have some sort of brief attached to them (for those who don’t I often direct people to a questionnaire on the Headscape site that asks for the kind of information we need to put together a proposal). But often, briefs are extremely well written and can therefore easily be interpreted into a project. Often they’re not and require a lot of discussion to get to the bottom of what a client is looking for. Usually this will be done via the phone and email but often for larger more complex projects we will want to meet face-to-face prior to creating a proposal. Geography can be a big factor on whether that happens though!

All in all, it’s a balancing act. I have to carefully judge whether something coming is a good fit with us. This usually means being quite direct with a potential client (I’ve learned that beating around the bush doesn’t work!) but, of course, I really don’t want to upset anyone or give an arrogant or aloof impression which is possible if you’re trying to tell someone that they can’t afford you!!

It’s so hard being me. Please send more jokes to cheer me up.

Back to top

162. Social Media (Yuck!)

Posted in Classic shows on April 21, 2009 by Paul Boag

On this week’s show: Paul interviews Mel Kirk about using social media for marketing. Marcus, explains why you need a thick skin as a web designer and we give you the chance to interview Elliot Jay Stocks.

Play

Podcast: Download (35.1MB)

Download this show.

Launch our podcast player

Housekeeping

In last week’s show I promised exciting things to come in the boagworld forum, and this week we begin to deliver on that promise.

Listening to the interviews with top web designers on this podcast is interesting, but wouldn’t it be even better if you could be the one asking the questions? What would you ask one of Britain’s most talented young web designers? Would you ask him about Photoshop techniques or about what makes his career a success? Well, now you have the chance.

Elliot Jay Stocks used to be the Senior Designer at Carsonified before going freelance. His clients now include WordPress, Blue Flavor and FreeAgent Central. He produces some truly stunning work and is considered one of the best web designers around.

He has kindly agreed to take questions from the boagworld community over the coming week. So starting on Wednesday 22nd April you can visit the Boagworld forum and ask him whatever you want. This is an amazing opportunity to really understand the working practices of another designer and discover the secret of his success. It is a rare opportunity to see how somebody else approaches the challenges of building an effective website.

Ask Elliot a question now.

Back to top

News

Website management: you can’t automate everything

Sometimes I think I have experienced some kind of mind meld with Gerry McGovern. I continually find myself nodding furiously when I read his stuff. This is certainly true of his post recent post “Website management: you can’t automate everything“.

Gerry is writing about something I have mentioned on this show many times before – content management systems are not enough to solve your content problems. Gerry writes…

The school of content management brought us such developments as portals, customization, personalization, and distributed publishing. These management-free, technology-driven solutions have led to public websites and intranets teeming with poor quality, badly organized, out-of-date content.

What do you get when you personalize crap content? Personalized crap content. What do you get when you distribute publishing rights to people who can’t write, don’t care about what they write, think metadata is a country bordering Outer Mongolia, and will never, ever review or remove what they publish? You get the website you deserve.

He goes on to say…

Technology is important, even critical, but we still need quality people to manage websites if we want those websites to deliver value to the organization.

Amen to that!

IE6 Update: Pure evil!

While Gerry McGovern rants about content management, I want to do the same about a terrible website from people that should know better.

IE6Update has good intentions but its approach is at best misguided and at worse evil and manipulative.

The aim of IE6Update is to encourage IE6 users to update to a modern browser. I think we can all agree with that objective. IE6 lacks the functionality of modern browsers and its rendering engine struggles to handle modern websites. What is more, its a pain in the ass for developers.

That said, the end does not justify the means. IE6Update provides a Javascript ‘snippet’ that can be added to any website. This code displays a notice to IE6 users telling them that their browser is out of date and they should upgrade. So far so good. I consider that an acceptable thing to do presuming IE6 users can still access your content.

My problem lies in the way they do this. Instead of displaying a styled message consistent with the rest of the site, they choose to disguise the message as an official IE notification bar. This tricks the user into believing they are being asked to perform the upgrade by Microsoft.

Screenshot of the IE6Update bar

This is the kind of approach you normally associate with malware or dodgy advertising. It is not the kind of thing you expect to come out of the web design community.

I spend half my life trying to explain to clients why they should treat users with respect. Something like this undermines that work by legitimising deception. If you want to tell IE6 users to upgrade then that is fine. However explain the benefits of upgrading, don’t trick them into doing it!

Where Have All the Flexible Designs Gone?

Craig Buckler asks an interesting question over at Sitepoint – Where Have All the Flexible Designs Gone?

Flexible sites are those which adapt to fill the whole browser window no matter how it is resized. As Craig points out, traditionally these have been considered good practice because they work at any resolution and the user is put in control of sizing.

However as Craig goes on to say, there has been a decline in flexible sites recently, with an increasing number of designers adopting a fixed width approach. Craig cites a number of reasons for this including…

  • Their consistency with design mock-ups
  • The pixel perfect control they provide
  • The additional cost of building flexible sites

Although these are valid reasons for fixed width design, they are nothing new. Flexible sites have been around for years. Why then are they dying out now?

There are two reasons why I generally no longer recommend flexible sites to clients…

  • Support for page zooming – All modern browsers now support page zooming. This removes the needs for sites to accommodate increased text sizes. If the user wants the site to fill the screen they simply zoom in. What is more a flexible site can cause horizontal scrolling when zoomed so creating a usability problem. This is especially in IE7.
  • Graded browser support – Because I deliver different experiences to different browsers using different stylesheets it is no longer necessary to have a “one design suits all mentality.” I can deliver one stylesheet to capable browsers and another to small screen devices.
  • Although there are still reasons to use Flexible design, the argument is no longer as convincing as once it was. The return on investment often no longer justifies it.

    Help your site convert

    Smashing Magazine have released two posts that provide excellent advice on encouraging users to complete a call to action.

    The first, imaginatively titled Design To Sell: 8 Useful Tips To Help Your Website Convert, covers subjects such as…

    • Subliminal Suggestion
    • Preventing Choice Paralysis
    • Try before you buy
    • The Gutenberg rule

    The followup post 7 More Useful Tips To Help Your Site Convert goes on to cover…

    • A/B Testing
    • Scannable Feature Lists
    • Streamline The Sign-Up Process

    Both articles offer lots more tips than those listed here, providing explanations and examples for each.

    It is easy to believe only ecommerce sites need to convert. However, that is not true. All sites need some form of call to action, so these two posts should be required reading for all website owners and designers.

    Back to top

    Interview: Mel Kirk social media for marketing

    Paul: So I’m very excited today to have joining me, Mel Kirk. Hello Mel, how are you?

    Mel: I’m very good thank you. How are you?

    Paul: Very good. It’s good to have you on the show. Feels like I’ve had so much to do with you and yet we never had you on the show and that is a sin and I am truly sorry.

    Mel: No problem. We have known each other for years now I think so…

    Paul: We have, haven’t we. Let’s start with a little bit of an introduction for those people out there who maybe don’t know you as well as myself. Can you tell me a little bit about your background and where you come from and what kind of stuff you’re involved with, that kind of thing?

    Mel: Yeah, absolutely. So I moved into web space about four or five years ago when I started work at Carsonified, which was Carson Systems at the time and what was arranging their events, Future of Web Apps and Future of Web Design. And from there I heavily became involved in promoting the apps that they were building and then eventually moved on to communities manager before I finally left, which was about eighteen months ago. And then after that joined Aardman Animations, Wallace and Gromit…

    Paul: Aah, yes

    Mel: Everyone recognizes it when you say Wallace and Gromit and my main project there was to work on a video platform called Formations. Which was a joint venture with Channel 4 which was in effect, it’s like a YouTube for animation…

    Paul: OK

    Mel: …which was brand new when I joined so my work was really around building a community around the new site there and getting that to launch, which we did. And then most recently I joined WhiteLabelDating.com as marketing manager of, so I see some very interesting sites.

    Paul: Yes, that’s an interesting career move. I didn’t know about the last one. That’s fascinating. Ooh, we’ll have to come onto that one later.

    Mel: Absolutely. Um so yeah, now I’m kind of responsible for researching our target audiences and their behaviors and reviewing user perspectives and brand building, all of that kind of stuff.

    Paul: So is it fair to say you describe yourself as a marketeer?

    Mel: Absolutely, yeah.

    Paul: So, that’s good because we haven’t had a marketeer on the show before and I’ve gotta say I think that there area lot of web designers out there that are a little bit snobbish when it comes to marketing and so I think it’s a good subject for us to cover on the show and talk about, a little bit about online marketing and how to approach that kind of thing, so it’s good to have you here.

    Mel: Thank you.

    Paul: Right, where to begin. Um, OK let’s start at the beginning. Let’s say that somebody has got a really good product or company that they’re very proud of, they’re very excited about but they need to generate some kind of awareness online of who they are or what they do. Where do they start? Where do they begin that process?

    Mel: I think for me the main thing before you implement any kind of strategy is research. So knowing your market inside out. Taking the time to work out how those people communicate and where are those discussions taking place. And then becoming a part of that conversation but doing it genuinely with something to offer. So don’t be afraid to say that you’re bringing something new to the table and that you’re obviously there to promote what you have to offer but in return being able to go into forums for example and answer questions for people, to be seen to have an opinion on current topics so that gradually you build yourself up to be seen as an expert in your field so that people have confidence in the service that you’re offering or the product that you’re trying to sell to them.

    Paul: Sure. So it’s about establishing yourself as an expert more than it is pimping your product or service.

    Mel: Absolutely, and I think nowadays people are used to being marketed to so they turn off as soon as you start to kind of start to heavily sell a product to them so you have to really be going there with a genuine interest and wanting to help those people in some way and they’ll be receptive to that.

    Paul: Now you talk there about researching and going and finding out where people congregate and where they are online. How do you go about doing that process? You know, what’s involved in researching?

    Mel: So, first of all you need to know kind of who you’re targeting your product at so know your product inside out before you go out there to start to try to find where those people are. Then once you know the kind of topics they’re likely to be discussing or the types of people that you’re after, looking for groups. User groups, Google is fantastic resource that should be used fully. I know it’s so simple, but so many people don’t spend enough time fully researching on Google kind of the different sites that are available or the different social networks that they can join so the first thing that I do, I know that everybody kind of mentions it now but having a look on Facebook, seeing what kind of groups are out there, checking LinkedIn, seeing what activities are taking place already. Setting up Google Alerts, using TweetDeck with alerts on there so that you’re currently being updated with the conversation as it’s taking place and then you’re kind of in a position to join that and to have something that you feel will be valuable that you can contribute to that.

    Paul: So those alerts and things that you’re setting up aren’t necessarily alerts
    directly related to your own brand or your own products but alerts to what things that your target audience might be interested in?

    Mel: Yes, so for me I would set up alerts that were dating specific so that I know the current issues that are going on. I then may set up alerts thinking “OK, well our target audience is 18 to 35. Generally, what’s of interest to these people?” And setting up alerts, it can be completely abstract, searches out there. For example, if you’re targeting guys, I know it’s stereotypical I guess, but um, new beer brands, new video games. Things that you know that they’re likely to have an interest in that you can start to build some commonality there.

    Paul: So you’re not even, in that situation you’re not necessarily, I’m guessing with dating you go after guys quite heavily. They’re a big audience to you so you wouldn’t necessarily go after alerts for dating related stuff, it could necessarily be kind of alerts for anything your target audience are interested in, just so you can work out where they are I’m guessing.

    Mel: Absolutely. I mean if you look at the dating industry as an example. If we’re targeting guys, we may know that guys in that age have certain interests whether that’s gaming or socializing with friends that may not consider going on a dating site but if you’re already talking to them and raising your own brand awareness then when they get to the point they’re considering a dating site, you’ve already built that brand with them and they recognize you as a name so.

    Paul: Sure. I think the thing that often strikes me that both clients and web designers maybe aren’t involved in in marketing is that they often underestimate how long all this stuff takes. To build that relationship and that brand takes a considerable time. It doesn’t kind of happen overnight and often people seem to expect instant results which surprises me. I saw one other thing as a use of Twitter that kind of grabbed my attention and I wondered if you did the same thing was that he would create alerts on questions, whether it be whatever, so that when somebody asks a question, you can go in and respond. Is that the kind of thing you do as well?

    Mel: Absolutely. It’s not just about going in and leeching off the community. It’s about going out there to give them the answers to their questions so that you are actually providing a service and some value to them rather than just spamming them and I think that really is the difference. It’s about wanting what’s best for your users rather than just trying to sell your service.

    Paul: Yeah. I’m guessing that people can kind of see through anything that’s more direct these days and are uncomfortable with it.

    Mel: Well there’s so much of it, unfortunately.

    Paul: Yeah, there is. Let’s talk about techniques then, or techniques and tools. You’ve already talked about TweetDeck, you talked about Twitter, you know you mentioned alerts, Google Alerts and that kind of thing. What other kind of tools do you use for reaching people that you, your target audience? What other tools are available to you?

    Mel: Um, so for us a big thing is the blog. Being able to have an open conversation with our community. Whether that’s with partners that are using us or the end members that are signing up to the sites. I think for me one of the biggest things with the blog was probably with Formations when we didn’t actually have a product, but we already had people waiting to use it by the time we launched it. And that was purely by going out there saying, “We’re going out as a new venture. We totally want your opinion. We want to know what it is that you are looking for from our service.” And then when you finally go out there and you roll out your new service or your product and you’ve built in their feedback then all of a sudden you give them a sense of ownership and they become your brand advocate so I can’t talk highly enough about the blogs but that’s assuming you actually listen to the feedback. Having a blog and just having it be one way would never work.

    Paul: I mean it’s interesting there that you talked about having an open conversation through your blogs…

    Mel: Yeah

    Paul: …and using the feedback that you receive. How do you go about that? How do you stimulate conversation? I mean I’ve had clients that have set up a blog and they’ve written a lot of article and never a comment will appear, you know. What kind of ways do you use for stimulating that conversation?

    Mel: OK, I probably shouldn’t say this. Oh, no, it’s all gonna go down hill, but poking friends, I know it sounds bad. Poking friends to try to get them to spread the word for you. You never know what contacts those people will have. You will have built up a network of people yourself and it’s about not being afraid to ask those people for help. Everybody needs help at some point so asking them to spread a link if they can. But then also when you’re going out there and you’re talking to people that you think are going to have some interest in your blog don’t be afraid to go into conversation, add something and drop your link there, but that’s not going in and purely just linking, like link baiting at all. Have something valuable to say, but don’t be afraid to link that to your own site.

    Paul: But what if you’ve kind of got people that are coming to your blog but they’re not engaging, they’re not posting comments? So you’ve got an audience but they’re a very passive audience. Is there stuff you can do to encourage them to participate more?

    Mel: Very much. I think the way that the blog is used can be critical on how many comments and how interactive that then becomes. I think Gary Vaynerchuk does a fantastic job on his blog where at the end of each video he tells you to comment. It’s very very easy to see as soon as you hit his page, what you need to do to leave a comment or to contact him on Twitter. The call to action there is very very clear. And similarly the videos that I do at Random Mel, the first and last thing I do is to put the URL at the start and end of the video and then if I want someone’s comments on something specifically then I make sure that I tell them what to do. You can’t just assume that your users are going to know, or want to comment, so you have to really prompt that from them.

    Paul: Yeah, I mean I’ve seen that a lot in blog posts where the blog post has been written as this diatribe of “I’m the expert. I know what I’m talking about. Here’s the stuff,” and you’ve got nowhere to go as far as responding to it. It’s almost like the person doesn’t want a response. They’re certainly not asking for feedback, or they’re not asking any kind of question you can respond to.< /p>

    Mel: Absolutely, and at the end of the day it doesn’t matter how senior you may be within your industry or how much you know. There’s always something that you can be learning from these people. And being able to get feedback from those, that’s information and data that these huge organizations that aren’t up to speed with social media yet would pay thousands of pounds for. So it’s a real advantage if you use it properly.

    Paul: I mean there’s a kind of follow on issue here that you’ve kind of built some excitement around whatever your product or service is, you may have done enough work to get in the position that you’re currently in of actually having a group of passionate people there waiting for your product to launch, and creating that initial buzz is easy, or easier but it’s maintaining that buzz over a long period of time and maintaining that engagement with users so I’m interested in how you go about keeping that relationship going over the longer term. What kinds of things do you do there?

    Mel: So one of the main things here I think is having content available to them. Having something new so they have an incentive to come back. You can’t just expect to launch and for that high wave to be maintained. But I also think that it’s worthwhile bearing in mind that you should be there just to facilitate the conversation between them. If it’s some kind of website that you have, for example, for people to communicate with one another. It’s not necessarily for them to communicate with you, but you’re helping them to achieve whatever it is that they want to get out of your service.

    Paul: Yeah.

    Mel: So continually trying to update your service to make it the best that it can possibly be and to actually have a look back and to not be afraid to change it if you can see that users are using the service in a slightly different way than you thought they were going to. Not being afraid to go, “OK, well it’s not quite what we had planned, but let’s go along that route.” Just as flickr was born I guess.

    Paul: Yeah.

    Mel: So being able to change that and giving the users a sense of ownership. I can’t stress how important that is. Because they become your advocates and no matter how well you communicate with these people, you’re always going to be the person that is promoting a product or service, whereas your users are doing it because they genuinely believe in you.

    Paul: There’s a kind of interesting potential problem in that, that if you as a marketing person is the person that is engaging with the community and if the community is feeding back ideas about the product and service and you’re wanting to take those on board, there’s gotta be a very good relationship between marketing and the people actually developing the product or service. How has that worked in the past? Have you found that people have been very receptive to that?

    Mel: Um, so we’ve had something very very similar here at White Label where we are now positioned with the development team, because as far as I see it, marketing and development very much fit as one. And marketing now own all of the projects that we’re doing so that we were able to take our users needs to drive that forward and to prioritize that. Development is incredibly important, but it really does have to be the users’ needs that drive forward what’s most important to them. And so we have regular updates with the development teams but like I say we very much take responsibility for new features and functionality which is added there.

    Paul: That’s very interesting. There’ll be a lot of people that’s listening to this podcast that are probably deeply uncomfortable with the idea of new features being driven out of marketing.

    Mel: Yeah.

    Paul: Why do you think it should be marketing where that’s based rather than the development team?

    Mel: I say marketing simply because in terms of my role I very much kind of look at the usability of the site…

    Paul: OK

    Mel: …so trying to increase user experience so maybe that’s kind of somewhere in between I guess, rather than traditional marketing. But if I can see conversations that are taking place and I can see how users are kind of functioning on the site and how we might want to implement changes then it’s kind of easier to get buy in from the development team when I can go to them with hard evidence as to what it is our users actually want.

    Paul: I mean that’s quite a quantum shift in the way that marketing operates. Do you get a sense that marketing as a discipline is changing quite radically and if so, in what kind of ways?

    Mel: Absolutely. I guess when you introduced me as a marketeer I cringed slightly because I did marketing years back when I worked in a bank and things were very very different back then. But I would say that marketing now has very much come along the lines that it is grass roots and that’s what I feel comfortable with. It’s not necessarily acting as a marketing function but it’s about being a user advocate and working out what can we possibly do to make their lives as easy as possible and to delight them? So not just give them the service that they’re expecting but that little bit extra as well. And I think that’s where marketing comes in now because then as soon as they’re happy, there are so many tools out there for those tools to vocalize whether they’re happy with the service or not, they do the rest of the work for you.

    Paul: So do you find that largely it’s about creating a passionate, enthusiastic community that then does peer to peer word of mouth marketing rather than sinking large amounts of money into banner advertising or whatever else?

    Mel: Totally and we find that it’s sustainable whereas if you pay for PPC and as soon as you stop that you’ll tend find that traffic to the site will stop as well. Whereas if you’ve got an active community out there that are truly engaged with what you have to offer then that’s going to be sustainable in the long run.

    Paul: Of course the downside to that is that you’re not in control of the message in the same way as you would be with traditional marketing and that you are very dependent on the good will of your community for that to succeed. So the question then arises, what do you do when things go tits up? What do you when things go wrong and there’s negative publicity and people are bitching and moaning online? How do you manage that ki
    nd of situation?

    Mel: I think from my point of view it would be to not be scared to hold your hands up and to admit when you’ve made a mistake. If you can be totally transparent in what you’re doing and you can explain why something hasn’t gone quite right. If you look at Facebook and how they took a step back not that long ago I think that was quite a brave move for them, but then you become an approachable company that people realize it’s humans behind the brand and as soon as you have that they become a lot more forgiving. Obviously there are going to be some people out there that bitch about you no matter what and unfortunately they are going to exist but all that you can do is kind of educate them as well as you can so they’re portraying the right message for you and then if it is as case that you’ve done something that your community don’t agree with, holding your hands up and not being afraid to change that to their demand.

    Paul: I mean it’s interesting there that you talk about exposing the humans behind the brand, that increasingly seems to be the philosophy of a lot of companies, to encourage their employees to blog and to twitter and to do all of these kinds of things. But I think in a lot of other companies there’s quite a high level of fear again about losing control of the message and that traditionally that’s something that marketing want to do and the idea of opening it up to everybody within the company seems quite horrendous. How would you reassure people that are having those kinds of doubts?

    Mel: I think if there’s a small-scale project that you can start that on to prove that the fear is often a lot worse than the actual reality behind it then that’s always a good way to begin. I would say that enabling your staff to have a voice is always a great way if they’re able to blog or to tweet. That’s not to say that you don’t go out there and say, “OK. If you’re going to be associated with the company, you need to be careful,” for their own rights as well as ours. You still have to be sensible with what you’re doing out there, but at the end of the day people buy from people they don’t buy from big companies. And the most successful companies out there are the ones where their employees truly believe in the products and they kind of do a lot of the work for you rather than just marketing function.

    Paul: Very interesting. I mean to some degree mind these days, increasingly all of us online are having to be marketeers to some extent. We’re all managing our own personal brands and our own personal identities and who we are and how we’re perceived online. I’m quite interested in your perspective of that, because I know that you have been amazingly honest and open online and that that’s come back to bite you on some occasions. So what kinds of hints and tips would you give to people that are trying to manage their online identity? I hate that phrase, that sounds awful, but you know what I mean. You know what I mean.

    Mel: Yeah. So, I think my biggest word of advice would be to be yourself. I think at the end of the day, if you can go to bed at night and you can sleep knowing that you’ve been true to yourself and you haven’t gone out there and tried to scam anyone or anything like that then I think that’s the biggest hurdle. There will always be some people that will question or criticize whatever moves you make but that’s a sign that they’re actually paying attention so although that may not be positive, it’s kind of the old PR way I guess, that any publicity is better than no publicity. And I guess for me, work with companies that fit your ethos. So, I’ve been approached by companies before where I’ve felt really kind of uncomfortable around the product that they’re offering. I don’t feel that I could sell it whole heartedly. I know that that will reflect personally on me so I will only associate myself with products and services that I truly believe in. I think that then kind of maintains people’s perspective of you I guess. But yeah, being honest is the main thing I think.

    Paul: What about in regards to how open you are? I mean we’ve talked a lot about open and transparency. Is there a line do you think? Is there a point where you should just shut your mouth and not speak, so to speak?

    Mel: I think that there is, and I think that that varies for each individual and it really depends on how comfortable you feel online. Some people are quite happy putting everything out there, and so that’s absolutely fine for them, that works. I’m probably among one of those. Exhibitionist, if you will. And then there are other people, they don’t want everybody to see what’s going on on Facebook. They don’t want everyone to know what’s going on in their personal lives. And that’s absolutely fine too. So you have to do whatever fits with you best. I mean, for me personally, I’m very very out there in the space and that’s just because that’s the way that I choose to lead my life. That said, you generally, apart from me on Twitter saying that boys smell, won’t find me talking about relationships or stuff that’s hugely personal to me. It will be about my lifestyle, it will be about my work, but it won’t be incredibly personal stuff. That’s my line, so. What’s your line?

    Paul: I don’t know what my line is. I knew you were going to say that. That’s just because I’ve just posted on Twitter that I’m chronically depressed and don’t want to work anymore. So you’re picking me up on that. No, I think for me, I tend to say everything slightly tongue in cheek, but then there will always be a kind of element of truth in it. So I perhaps am more personal than I think I am online, but I just dress it up in humor to kind of cover it up so, I mean that comment, for example. Yeah, I’m a bit pissed off today and I’m not really in the mood for working, so I’ll exaggerate it and make a joke out of it and make a bit of fun out of it. Sometimes that can be really dangerous. Humor does not translate very well, especially into text format. So yeah, it’s difficult isn’t it? It’s kind of, you have to feel it out and work it out for yourselves I guess. Anyway this is supposed to be me interviewing you, you’re not allowed to ask questions to me.

    Mel: I’m sorry.

    Paul: You’re breaking the rules Mel. OK, one last question to wrap up with. Which is that, let’s face it, social media has become a little bit of a dirty word at the moment.

    Mel: I hate that now.

    Paul: I know, it’s horrible, horrible, horrible. And there’s so many people out there that are kind of piggy-backing off of the back of it and I’m fed up. If I have one more person decide to follow me on Twitter that’s got the words “social media” in their title I’m gonna scream, but underlying all of that, actually there is something of value there and it’s this whole, you know, what we’ve been talking about really, this whole kind of community driven aspect to marketing and to our product development and all of that good stuff. But, here’s your chance to rant Mel. Give us some of the things that really anno
    y you about social media. Some myths maybe that surround social media that need dispelling.

    Mel: Oh my goodness, and this is to wrap up?

    Paul: Yeah. Something light and breezy to end with.

    Mel: OK. So, for me, everybody saying that social media is really really easy would be my biggest thing. It’s easy enough to do, if you know what you’re doing, but not everyone can do it. Some people know how to communicate with communities, other people don’t. And it’s kind of about knowing your strengths so, for example, some people may be hugely technical, but when it comes to knowing how to market themselves they aren’t always that forthcoming. And so it really does depend on the person that you’ve got doing your social media for you I guess. My next big one would be that giving away ideas and content shouldn’t be free, that you should be charging for that in some way. I know there are plenty of people out there that say that. But if you’re going to be seen as an expert, you have to prove yourself. You can’t walk into a space and kind of stamp your feet and say, “OK, look. Pay me as a social media expert because I know so much.” You have to provide something to people, show that you know what you’re doing and be prepared to do a lot of work for free in the meanwhile and then gradually those paid projects will come along. Next one would probably be viral campaigns. Easy. They’re very hit and miss. Everyone now thinks they can upload a video to YouTube and now hit the big time and it’s really not the case. It really does depend on the audience and how they react to each piece that’s put out there. And then I guess my last one, and it’s my last one, I promise, will be that there’s now way of tracking the effectiveness of a social media campaign. I just don’t believe that at all. I think that no matter what you’re working on you should always set yourself targets. Now whether that’s a number of comments that you want to appear on a blog post or a number of members that you want to sign up, search engine optimization. There are so many things that you can track, but everyone still believes it’s slightly fluffy, and are nice to have and I couldn’t disagree with that more. So…

    Paul: I like that one. That’s a really good one. I totally support you in that, that I think that making things measurable, even if you don’t meet those targets, I think having targets and aiming towards them is vitally important.

    Mel: Absolutely. And anybody who comes in and says that they can do social media for you without those, I wouldn’t trust in a million years.

    Paul: Excellent Mel! That was really interesting! It’s really good for us to kind of branch out and look at these things. You know the Web is becoming so much more than just putting up websites and we need to be talking about this kind of stuff more so it’s great to have you on the show. Thank you for your time.

    Mel: Thank you for inviting me.

    Paul: We’ll have you back again soon, no doubt. Goodbye!

    Mel: Thank you.

    Much thanks goes to Todd Dietrich for transcribing this interview

    Back to top

    Listeners feedback:

    In this week’s listeners section, Marcus answers a question about handling criticism from clients and we hear from Japh about Internet Explorers future.

    The need for having a thick skin

    This question in from Bill:

    Currently my working life seems to be one long string of criticism and rejection. I try to get involved in debate as guys like you recommend I should, but my ‘real-world’ take on things usually gets shot down.

    Trying to win work is even worse. I try to make sure that I don’t give too much away to potential clients up front and I try to discuss sensible budgets with them, but their expectation is that I will redesign their homepage for nothing to ‘see if I’m good enough’ and any budget request is met with ‘you tell me’.

    Even though Paul and I pretend to be big and tough, nothing-can-touch-us types, the truth is rather different. My constant need for adoration and Paul’s megalomania mean that we both take criticism very hard. Ok, I’m joking, but there is a grain of truth in there.

    No-one likes criticism or rejection, so what’s the best way to soften any blows?

    All of the people

    If you decide to lay your soul bare in a blog or regularly provide advice in a forum or through articles, then chances are someone will disagree with you. Quite often they’ll be rude and destructive in their criticism as well.

    Try and take any positive criticism as an addition to any debate and get wholeheartedly involved. But, be prepared to accept that, sometimes, you might just actually be wrong.

    To those people who are intent on using you as a punch-bag – ignore them. Getting into any kind of argument will almost certainly end up with you looking and feeling worse. You will tend to find that you have a lot of allies in situations like these – let them fight on your behalf.

    So, accept it, you cannot please all of the people all of the time.

    Go for it

    All that said, you should still get involved in debate, post questions and views and comment as much as you can. You will get yourself known and even if that’s as the ‘real world’ guy then so be it.v

    I’m guessing that the work you are trying to win is fairly low-end. Getting involved in discussion is a very effective way of promoting yourself. It shows that you are keen and (hopefully) that you know what you are talking about. This should start to attract a better calibre of client.

    However, this does not happen overnight, so be patient.

    You’re worth it

    Trust you’re ‘gut’ when dealing with potential clients. Quite often people are genuine when they say that they have no idea of budget. This doesn’t automatically mean that they are a waste of time; just that they need educating in your processes.

    However, if someone is trying to manipulate you into doing work for free – and that doesn’t necessarily mean doing unpaid mock-ups, it can just as easily mean scoping out an idea (why should you not be paid for being creative?) – then walk away. You will regret it if you don’t.

    Walk away.

    Talk money

    I’ve said this before so apologies for the repetition but I think it’s important.

    Ask people, up front, what their budget is. Explain that you need to know it to respond with the most appropriate solution for them. You may only be able to squeeze in a quick 2 or 3 page flat site within their budget or you may be able to offer a huge variety of functionality and testing.

    If you don’t get anywhere by asking (and, as I mentioned previously, they really may not have a clue) then create a 2 or 3 paragraph solution with associated tasks (a mini proposal if you like) and email that to them with an associated ballpark price.

    This will either stimulate discussion or get you dismissed out of hand. Both outcomes are good news.

    Stick to your guns

    We decided, quite a while back, and for very good reason, that we would not do any unpaid mock-up design work. In some cases this
    has been seen as a positive thing (once it has been explained) but with other potential projects I’m sure it has adversely affected our chances of winning the work. However, we should stick to what we believe is right. Chopping and changing presents a negative image to both potential clients and our staff.

    If you do decide to present initial mock-up ideas don’t be tempted into iterating them further. Any client who asks for is again asking for free work and is most definitely to be avoided.

    Stay calm!

    Sometimes the people we have to deal with are mouth-open-wide-unbelievable in their arrogance, rudeness, pickiness, narrow-mindedness, impatience etc etc…

    Sometimes we are manipulated into doing work for free.

    Sometimes we are strung along through a pitch process when we have no chance of winning it.

    This can be a little irksome and, at times, we may feel that an adversarial approach is the right one! It isn’t. It can only damage your reputation.

    Even if you don’t see eye-to-eye with someone it doesn’t mean that they will never hire you or recommend you to someone else.

    So, in essence, work on your patience, cherish your good clients and keep your skin thick.

    IE6 and IE8

    Finally, Japh has posted an Audioboo on last week’s discussion about the future of Internet Explorer.

    Hi. So, there’s been a lot of talk lately about the IE8 being moved to an important update hopefully to prompt people to upgrade form IE7 or whatever previous version to IE8. So, I just wanted to put in my two cents and specifically I guess this is a response to Paul Boag’s recent audio review about this topic. I agree with Paul that IE8 being an important update won’t kill IE6, mostly due to corporations. As IE7 was made a high security update quite some time ago and a lot of users upgraded before then and since then from IE6 to 7. I think those users will proceed as they have been and upgrade to IE8 like the good little lemmings that they are. And it will be the corporates that are stuck back in IE6. Mostly, I think, this has to do with maintenance periods and things like that and the various support deals that corporations have with Microsoft. But there is some good news there as well in as much as Windows XP’s life span is being reduced. Microsoft’s reducing support on that to be the extended support instead of their main line support which basically means you only get security fixes and that’s all. So, for corporations, even though they’ve paid up and so they get it little bit longer than everybody else it’s kind of a bit of a kick in the pants for them and telling them they need to move into high gear and start upgrading their standard operating environments to include the latest operating system which will include hopefully the latest browser – IE7 at least if not IE8. And I think that’s probably going to start happening early to mid next year. So, it’s not too far off before we would have , you know, hopefully, complete death of IE6. That’s my two cents.

    If you are an iPhone user then why not submit a question via AudioBoo yourself? Go to Audioboo.fm for more information. Once you have recorded your boo tag it with “for boagworld”. No iPhone? No problem. You can also submit comments by skyping “boagworldshow” or emailing us an MP3 file.

    Back to top

    5 common ecommerce mistakes

    Posted in Web strategy on April 20, 2009 by James Greenwood

    In the first of a series of guest posts James Greenwood shares some common ecommerce mistakes.

    Ecommerce has revolutionised the way trading is being carried out, has created completely new enterprises and has provided existing retailers with a platform to trade 24 hours a day, seven days a week.

    However, having developed and worked with retailers over the last 10 years to help them create their ecommerce offering, there are still critical mistakes being made.

    Given this article has been written for Boagworld, and that Paul in particular loves a “top five” list, here’s my top five mistakes being made by e-retailers:

    Mistake 1: Poor checkout Procedure

    www.jjbsports.com

    Unless you’re one of the “big boys”, forcing shoppers to register an account with you is likely to be a big mistake. There are very few online shops which get our repeat purchases and so warrant an account. On a big name site, I’m happy to sign up for an account as I’m more than likely going to use you again. Think Amazon.

    However, for most eCommerce sites, I’d recommend the following:

    • From the basket screen, collect the customer details (Billing Address, Delivery Address etc). This should all be on one page, and not the “Step 1 of 5” method of 10 years ago!
    • Once this data has been collected, ask the user if they’d like to store their details with a password. Inform them that by doing so, it would enable them to retrieve their details when they next purchase, that they’ll be able to track their order or that they’ll be added to a mailing list. The key is to offer them something in return!
    • Take the order regardless of account creation or not.

    You’ve not put anyone off from purchasing with you and also tidied up your mailing list to one of genuinely interested contacts.

    Mistake 2: Failing to analyse all of your data

    And, no, I don’t just mean check Google Analytics (although of course, you should be doing).

    Every visitor to your site, whether they purchase from you or not, is revealing a wealth of information which if used properly, can improve your offer to the e-shopper. In fact, visitors who are not purchasing from you are almost more important to you than those that are….

    Firstly, a good eCommerce platform should store lots of data about your shoppers. Basket data should be stored in the database, and any free text searches that are made on your site should also be stored too.

    Get in to the habit of checking to see what items are being put into baskets versus the items being sold – you may well find that an offer on a particular line means you sell more. It might highlight that you need to reduce the price on a particular line, or it may highlight an issue with UI. Either way, using basket data allows you to react – this data is gold.

    The same principal applies for free text search – knowing what people are searching for on your site allows you to cater for their needs.

    Mistake 3: Confusing shoppers with categories

    We’ve all seen them – categories with nothing in, categories with one product in or multiple categories on an eCommerce platform with a handful of products.

    Screenshot showing lots of catagories

    Don’t die by category overload – arrange them logically and simply, and provide your shoppers with means of filtering their results so they can find what they are looking for without having to rummage around surplus categories.

    Mistake 4: Not being aware of how users are shopping

    The advent of the tabbed browser has caused a problem for many e-retailers. Shoppers can now compare products side by side more easily now. Even less experienced Web users who only use the browser that came with their machine are now being encouraged by Internet Explorer to browse using tabs.

    Screenshot showing tabbed browsing

    Ensure pictures are sharp and informative, ensure descriptions are complete and full (there’s an SEO benefit in this too) and ensure that your prices are competitive. Oh, and don’t milk delivery charges!

    Following this advice should mean than when side by side with a competitor, your store is the one which gets the cash.

    Mistake 5: Not looking after your hard earned shoppers

    It is easier to look after an existing shopper than it is to attract a new one. Don’t hide telephone numbers or email addresses on your site; always ensure that they are prominent. It might be that I want to ask a question before purchasing – encourage me to do so!

    Once I’ve purchased, keep me informed with what’s happening with my order – if it’s on backorder unexpectedly, let me know. The chances are that I’ll understand, but by not informing me, my reaction is likely to be different. Don’t make me chase you to find out about my order – get in first!

    So, selling online is as easy as that then?

    To ensure a high percentage of visitors purchase, is it really as easy as making your checkout procedure easy, analysing data to find out what it is that I want to buy, ensuring I can find the product I want easily and then offering me a great deal on price and customer service values?

    Well, yes, actually it is.

    However, a great looking site that’s easy to find in the search engines, is marketed well online and offline and is easy to navigate also helps. That’s another article….

    About the Author: James Greenwood

    James is a director at media agency Strawberry and keeps a blog with articles and site portfolio. You can also follow him on twitter.

    156. IE8

    Posted in Classic shows on March 11, 2009 by Paul Boag

    On this week’s show: Ryan talks to Andy Clarke about Internet Explorer 8, Paul looks at how to simplify your site, and Michael argues that marketing should run the company website.

    Play

    Podcast: Download (27.7MB)

    Download this show.

    Launch our podcast player

    Housekeeping

    Don’t forget our SXSW coverage

    Just a quick reminder that next week is our live boagworld show from SXSW. If you are attending the conference please sign up on upcoming and come along. If you aren’t then you can watch via uStream. The show is being recorded at 6.30PM (CST) at the Hilton Hotel, Room B.

    Whether you can attend or not we would love to receive your questions for the panel. Email them to me ASAP!

    You can also follow coverage of SXSW on the boagworld website, so check that out too.

    A Website Owners Manual Discount

    For those who don’t already know I have now finished the ‘Website Owners Manual‘. This means the book is moving into production where they give it the final design and replace my terrible illustrations. Hopefully this process should be finish by July when the book will finally be released.

    However, the entire draft manuscript is available now in ebook format for those who cannot wait. Also with Manning’s early access programme you can preorder the printed book and get a copy of the draft ebook to read immediately.

    To further sweeten the deal you can get a massive 40% discount if you use the code ‘AUPROMO40‘ at checkout.

    To order go to boagworld.com/websiteownersmanual.

    Back to top

    News and events

    If only IE played nice

    Let’s kick off with two posts that really makes you wish IE played nicely!

    First up isFluid Grids, an A List Apart article that discusses fluid layout and the limitations of IE. In particular it focuses on IE6 and its failure to allow page scaling. When combined with the smaller resolutions of many netbook PCs, it is apparently that fluid layout remains an ongoing requirement for many sites.

    An example grid

    The article takes you step by step through the process of creating a fluid grid system. Although it is very comprehensive, it does involve some serious maths and leaves you with an even deeper hatred for IE.

    The second post I wanted to mention is written by Rachel Andrew and is entitled Developing CSS for IE6 and 7. This is a great introduction to building websites using CSS and surviving to tell the tale!

    The emphasis is on the development process and how to address common IE problems. It is a very pragmatic article that is not afraid to mention the use of conditional comments and hacks. In fact in many ways it is the total opposite of a recent post on Sitepoint entitled SitePoint » 5 Reasons to Avoid CSS Hacks and Conditional Stylesheets. That post borders on naivety.

    Its nice to see a resurgence of posts on CSS. They disappeared for a while and yet I believe there is still room for improvement in how we build sites.

    Why Friends Reunited Failed

    In last week’s show I talked about the harsh truths of running an online community. If that was relevant for you, then you should visit Andy Budd’s site and read this insightful post – Why Friends Reunited Failed

    Friends Reunited Homepage

    In his post Andy compares the failure of "Friends Reunited" compared to the success of Facebook.

    The gist of Andy’s argument is two fold. Firstly, the site provided little to keep users coming back. Andy writes…

    So with Friends Reunited once you’d registered, seen what your old friends were doing, connected with the ones you’d wanted to and had a laugh at the (hopefully) tragic lives of your childhood tormentors, there was very little reason to stick around.

    Second, they decided to charge for membership, thereby changing the relationship…

    Charging for a service changes the whole dynamic of a site and causes people to game the system in order to get the maximum return on their investment. So it becomes less of a community and more of a commercial relationship. Like a lot of commercial relationships, once the value runs out, people will stop paying and leave.

    Its an interesting read and helps emphasis the importance of providing tangible value to your users.

    WordPress overload

    As you will know if you follow me on Twitter, I am currently in the process of moving Boagworld from Movable Type to WordPress. The primary reason for the move is WordPress’ vibrant development community. There are literally thousands of plugins available and endless tutorials and supporting material.

    WordPress Homepage

    Although Boagworld does provide some marketing benefits to Headscape, it is still a side project. As a result, the time I can invest in it is minimal. Plug-ins allow me to add functionality and make usability improvements with minimal effort.

    Interestingly as I have been making this transition, I have noticed a substantial increase in the number of WordPress related posts in our news stream. I am not sure if this is because I am more aware with them or Paul Stanton thinks I need a bit of help. Either way they have been useful reading.

    Three in particular have caught my attention…

    • 11 Non-Traditional Uses of WordPress – A great little post that demonstrates the flexibility of WordPress. It shows the blogging platform being used for everything from a Wiki to Contact Manager.
    • More than 10 "Must Have" WordPress Plugins – A collection of plugins which helps (among other things) to keep your content fresh, improve SEO and manage comments.
    • 15 Useful Twitter Hacks and Plug-Ins For WordPress – Some great code snippets and plug-ins that allow you to do everything from encourage people to tweet your content to create an entire twitter page.

    Back to top

    Interview: Andy Clarke on the release of IE8

    Ryan Taylor: Joining me today is Andy Clarke. Hello, Andy.

    Andy Clarke: Hi, how are you doing?

    Ryan: Not so bad. And we’ve asked you on today to talk about the upcoming release of Internet Explorer 8.

    Andy: Browsers, my favorite subject!

    Ryan: Yes, well you seem to blog a lot about browsers at the minute, you seem to be talking a lot about Internet Explorer 8 especially.

    Andy: Well, I’m kind of a bit of a grumpy old bastard, really, when it comes to browsers. And, so the topic of the moment, certainly of the last couple of weeks has been what are they going to do with IE8.

    Ryan: Yeah, so should we be excited?

    Andy: I don’t know whether we should be excited or whether or not the thing is a little bit of a anti-climax, to be perfectly honest. I think that there’s a huge difference between people like me who develop websites for normal people out there, conusmers who use the internet, and people like me who are aware of standards and passionate about CSS and maybe thinking about progressive enhancement and some of these other things. A huge difference between people like me and the army of people I know who work inside corporate environments. People who develop big banking finance applications, for example, where Internet Explorer is usually the vehicle that people access that content with. And I think that for those people, IE8 is a big deal. Particularly over what happened with IE7. So I think that for those kind of people, it’s going to be a ride again. But for people like me, you know it’s kind of a bit of a non-event, to be perfectly honest.

    Ryan: And do you think they’ll start changing the way that they build websites because of IE8 then?

    Andy: There’s an interesting kind of back story that goes on with what Microsoft did with IE, and generally speaking a lot of the problems that they have in developing that browser come because the people who build applications that are predominantly used by IE8 are not the people who are generally standards-aware. And this is why Microsoft has gotten themselves into so much trouble in the past when they have, let’s face it, done the right thing in improving the browser, particularly with IE7. And of course IE6 was famously full of colourful bugs, and all credit to the guys at Microsoft, who I know fairly well, in, you know they were very passionate about getting those things fixed. But of course when IE7 comes along and people that developed code for IE6 all of a sudden found their applications breaking, they didn’t look in the mirror and think, “Why is this stuff breaking? Is it my code? Is it something that we’ve done wrong or that we need to fix?” They blamed Microsoft. And Microsoft has this big thing about not releasing something that is going to, say, break the web. Well it won’t break the web, but what it might do is break applications and break websites that were based on a broken browser. So it’s not a simple issue, unfortunately, and this is something that Microsoft struggled with for quite some time, and I know that they’re going to be struggling with again in IE8.

    Ryan: You mentioned that the way that you build websites for your blogs isn’t going to change, but CSS tables are going to be available in IE8. Do you think that we’re going to see CSS tables more widely spread and adopted in web design?

    Andy: I’m sure we are, I mean I’m always really pleased whenever there’s a piece of CSS that’s more widely adopted. IE in itself has been dragging its feet about CSS tables behind all other browsers. I think that, where appropriate, yes CSS tables are going to be useful, but I think there was a lot of excitement, I think wrongly, to do with CSS tables, in people thinking that all of a sudden we had a good way, or a new way of making CSS layouts. Something that was perhaps more reliable than using floats of positioning, and I think that the more and more that I look at that, the more I think that it’s essentially going down a wrong and a backwards route, if we think that mentally we start thinking about table cells again. What we do is we again start to tie what we see on the screen, in terms of the presentation, to form the structure of our markup, and that is always, always wrong. CSS tables do require that we order markup in a certain way, just like HTML tables did, and I think if people start to go down that route, then I think they’ll soon find that really there is absolutely no advantage, in effect, in replacing HTML table layouts with a bunch of divs and other structural elements and styling them like tables.

    Ryan: Ok, so there’s going to be some improvements in IE8 over the previous browsers, but they’re introducing this compatability feature. Can you explain what that is? And share your views on it?

    Andy: Aw, the famous compatability feature. Well, for those people who haven’t been following this thing for a while, and this goes back to what I was saying at the beginning about Microsoft’s core market, they have to be very careful that they aren’t seen as the ones who are, in their words, breaking the web when they fix some of the problems that they introduced before. So a little while ago they introduced this idea of using a meta element which would essentially tell the rendering engine inside of IE which version of IE that you wanted a page to look like. So, for example, if you were to use the IE7 meta tag inside the head of your document, IE8 would render your page as if it were IE7. Which, of course, is a great idea for these people who build these enormous IE-based corporate applications, because they don’t have to worry about IE8. They can simply stick this plaster on, this band-aid on, and go away and think “Great, I don’t have to think about IE8 now.” It gives them a little bit of breathing room. Now Microsoft originally wanted to introduce this thing as an opt-out process. Basically, the browser would render like IE7 unless you told it that you actually wanted it to render like IE8, which was completely backwards. So, a bunch of people – Jeremy Keith was the most eloquent as always – argued that this was a complete crock of shit and would essentially hold back any incentive for people to move to a better way of working, to use CSS and markup in better ways because of IE8. So Microsoft changd their minds, and they made it an opt-in rather than an opt-out. And
    certain people took credit for them making that decision. I think only Microsoft know why they made that change. But interestingly in the last couple of weeks, it came to light over on the IE blog that they’re introducing this compatability feature which would essentially mean that anytime anybody pressed the “View in IE7” button, or used that feature, it would talk back to Microsoft. And then Microsoft would compile a list of sites that people clicked compatability-mode on, and then automatically, and perhaps without the viewers asking if they’d already opted into this thing, the browser would then hit a certain site and render as IE7 rather than IE8. That’s an interesting thing. A lot of people have been talking about the standards implications of that, and about the incentive for corporates to switch to coding in better ways. One of the things that hasn’t been talked about much is the privacy thing, the privacy angle. Essentially your browser is talking back to Microsoft in Redmond every time you look at a page. So I wonder, I’m a little concerned about this. I can understand why Microsoft do it, and I can understand why they want to try to find a way of not upsetting their core marketplace. And Chris Wilson, who’s a friend of mine and head of the IE team, wrote on Twitter, “Well can you think of a better idea for our customers, so that they don’t think,” I’m paraphrasing here, “so that they don’t think that we’ve broken the web when we launch a new browser?” And my answer to that is – it’s not your problem! If you make the browser, if Microsoft make the browser the best they can possibly make it, with the best of their efforts, and they are really smart people, then if websites break in IE8 that’s not their problem! It’s a problem for people like me, and it’s a problem for website owners and web designers that need to make their sites work in IE8. So I think, again, Microsoft are kind of barking up the wrong tree, but I can see why they have to think that they do it.

    Ryan: Okay, well IE8 is also missing a few of the other more popular CSS3 selectors that are available in other browsers, like border-radius and things like that. Is this a setback for CSS3?

    Andy: No, I mean it’s a shame that Microsoft haven’t introduced more of the CSS3 features to date, it’s frustrating for me because I do like to do the whole progressive enhancement/progressive enrichment type of thing, that I can’t have something that looks fantastic in Safari or Firefox, or possibly Opera, looking as good in the browser that obviously most people use. But I think that there’s a bigger issue here in that there’s a technique available for browser makers, to implement some not quite ready features of CSS3 at the time that they choose. That’s this whole kind of “-moz, -webkit” thing. And it’s a very good way, it was designed obviously for browser makers to test implementations of CSS3 properties so that then they wouldn’t break when they switch to the real thing. So if you do –moz border-radius, you could then switch to border-radius and it would do the same thing. So it’s a great way for people to be able to test these features. The interesting thing, though, and this is the wider issue, is that there’s no strategic plan, either from the browser makers or, most importantly, from the CSS working group, where they plan in a timetable implementation of these new features. Now we’re not talking about the big design of CSS, and when are we going to get new layout features and things like that, but simple things like for example CSS columns? Webkit implements CSS columns, Mozilla implements CSS columns, but they do it independently, they do it when they want to on their own timetable, and what I’d really like to see is for these browser makers to get together and say “You know what in September, we’re going to introduce these columns across the board, and in October, or in our next release, we’re going to implement this across the board.” I would like to see them working together so that actually we can start to look at different implementations of, for example, columns. We can look at them in Firefox and we can look at them in Webkit, and we can go “He gets it right, that one’s slightly wrong” and then they’ve got a playing field to work on. And it’s much wider than the overall kind of “Is IE going to implement this or not?” The wider issue there, as I keep going on about over the years, is the whole process of developing CSS3 and the role of the working group.

    Ryan: Yeah, it’d be nice if they’d collaborate on more things, not just CSS! So there are some new government guidelines in place which you blogged about recently for cross-browser testing. Is this going to affect the way you approach building websites, especially now that IE8’s coming out, and with looking at IE6 and all that. Are the guidelines going to affect you in any way?

    Andy: Day to day, probably not. First of all, because I don’t build websites for government institutions. I don’t tend to do any kind of public sector stuff, for various reasons. And these are guidelines for government websites. So no, in terms of them affecting me on a day to day basis, no, because irrespective of my clients, I try to push as hard on the CSS progressive enhancement thing as I can. I think it’s very, very interesting and it’s a nice and mature approach that whoever’s drawn up these guidelines is taking, to actually understand that websites don’t need to look the same in every browser, and in fact they shouldn’t look the same in every browser. I think that’s a mature approach, and I think the one thing that these guidelines will do to help me is when, on the rare occasion, I perhaps haven’t explained something properly to a client and they come back to me go, “Do you know what? I’ve looked at this thing in Firefox and Safari, and it’s got these rounded corners on the boxes, but I’m looking at it in IE7, and they don’t have rounded corners. Why is this?” And then the whole topic of progressive enhancement comes up, and sometimes people get it, and sometimes people don’t. But actually having something there as a little bit of a thing in your armory, to be able to say, “You know what, websites aren’t supposed to look the same in every browser, and if you need more than my opinion on that, then take a look at these government guidelines.” Then yeah, I think that’s really, really good news for people who want to take this approach with CSS.

    Ryan: Ok, that’s great! Thanks for coming on the show, and good talking to you.

    Andy: Yep, my pleasure, nice to talk to a northerner for once, rather than that soft southerner that I sometimes get to speak to.

    Ryan: Haha, okay, thank you very much.

    Andy: He’s naught but a shandy drinker, you know that!

    Ryan: He is but a shandy drinker.

    Andy: Take care, see ya.

    Thanks goes to Jason Rhodes for transcribing this interview.

    Back to top

    Listeners feedback:

    Should the web team sit under marketing?

    Michael from Leeds recent me the following email which I want to share with you. I am not sure I agree with everything he says, but he puts together a good argument and I thought that was worth sharing.

    I just wanted to drop you a line about your blogpost, 10 harsh truths about corporate websites that you featured on your podcast as well. I was sat listening to that and wanted to pick up on harsh truth #1.

    You and Marcus were debating the issue of separate web divisions and whether web responsibility should lie within IT, marketing or your preferred option of a separate web division.

    There is no doubt in my mind that a corporate website has to remain the responsibility of the marketing department. There is no other place for it.

    The role of marketing is to assess a market and identify a need. Marketing then drives product development and the positioning of the product, developing the messages that convey what the product or service does. The final step is to choose through which channels these messages are best put in front of the target audience.

    The website is part of that communication mix. The website for any business needs to be created with a view to acknowledging that a problem exists and convincing the visitor that it has a solution. It then needs to convince that visitor to act. Where else then can the website sit? Who else should be approving the messages the website conveys?

    Where I think you guys are coming from (and your experience is not one that is alien to me after over ten years in digital on the agency side) is this. Often the person in marketing responsible for the website doesn’t have the knowledge, vision, experience or perhaps understanding to brief, specify, approve or even give a valid opinion on whether a website does the job. That is a problem with marketing, and not a reason to set up a separate web division.

    I believe wholeheartedly that marketing needs a digital specialist within it. If a website is to be developed in-house then a specialist team (certainly not in IT) should be developed, but responsibility for the website needs to remain under the control of marketing. Just because someone in marketing hasn’t done a TV commercial before doesn’t mean that IT should handle that project!!

    Even in seemingly non-commercial websites such as charities or universities there is a communication message and the comms team (marketing) is still responsible for the story and positioning.

    My feeling therefore is that if a client doesn’t have the skills in marketing it is beholden on us as the agency to guide them through the process. I’m sorry to say though that many web agencies have a lack of marketing skills and can’t relate to the marketing team.

    If you need finally convincing about this, think back to the copy interview you did with Relly in issue #154. In writing copy for the web and indeed for any medium Relly needs to understand what a product or service can do. She will be guided by a brief from marketing, not IT, not the web team. As an integrated agency we have five copywriters and the words are the message, the visual is the support and the dramatisation of that message. The copywriter is a key member of our web team.

    Hope you find these thoughts interesting.

    I debated as to whether I should respond to what Michael has written. In the end I decided not to. I want to leave it to you guys to decide what you think. In either case it is probably something we will be unable to influence, so to a large degree the debate is academic. Nevertheless Michael makes some good points which I can respect.

    Keeping it simple

    The second listener contribution this week is from Oliver in Kent. He writes:

    One of my latest clients (I won’t mention who) has the website from hell. It is far too complicated and full of pointless unintelligible content. I have tried to encourage him to simplify things but with little success. You have spoken about simplicity before, but I was wondering if you might be able to provide some advice on how to get this client to throw out some of his pointless content.

    It is a good question and needs answering in 3 ways. You need to understand the lure of complexity, how to identify it and finally how to go about reducing it.

    In fact this questions led to a blog post entitled ‘3 secrets to simplicity‘.

    Back to top

    155. Attitude

    Posted in Classic shows on March 4, 2009 by Paul Boag

    On this week’s show: Paul asks if web designers have a bad attitude. Marcus talks about contracts and we take a look at working with browsers.

    Play

    Podcast: Download (27.6MB)

    Download this show.

    Launch our podcast player

    Housekeeping

    I have a couple of pieces of Headscape news I would like to quickly mention.

    • First, Headscape has some office space we are looking to rent out. If you are looking for a small office in the Hampshire area and like the idea of working alongside us, then check out our video tour of the Barn.
    • Second, Headscape is also recruiting. We are looking for an enthusiastic, talented developer to join our team, working from of our offices in Hampshire. For more information see the job advertisement on Boagworld.

    Finally, just a quick reminder to sign up to attend the live recording of Boagworld at SXSW. We would love to see you there.

    Back to top

    News and events

    For much more web design news follow boagLinks on twitter or signup for our RSS feed.

    Atlas wows FOWA

    FOWA Miami has been in full swing over the last week. The line up of speakers was impressive as always. However, judging by Twitter one session stole the show. That was the guys from 280 North showing off a new product called Atlas.

    Atlas is built on Cappuccino, an open source framework that makes it easy to build desktop-like applications that run in a web browser.

    280 North have already demonstrated the power of Cappuccino with the release of 280 Slides, a browser based version of Keynote.

    However, Atlas takes things to a whole new level. In essence it provides a GUI environment within your browser to build powerful desktop like applications. It allows you to build Cappuccino applications without writing code.

    When you first watch their video demonstration it really blows your mind. I in no way want to take away from what they have achieved. However, after I got over the initial impact, I realised I had seen this before – It looks very much like Adobe Flex.

    Now anybody who listens to my show knows I am not a huge fan of flash. However, I have to wonder if Flash is not better tool for building complex web applications. I can see no real advantage to building it in Cappuccino. In fact as Drew points out in ‘The cost of accessibility‘, Atlas throws up all kinds of accessibility considerations, even if you ignore the fact it is built on Javascript.

    Watch the video of Atlas in action, read Drew’s post and then compare it to Flex. Once you are done, post your thoughts in the comments. I would love to hear what others think.

    Safari 4 is out in beta

    Safari 4 homepage

    So while we still patiently wait for the arrival of IE8, Apple have gone ahead and released its first beta of Safari 4.

    Available for both the PC and Mac, Safari 4 has some impressive UI improvements and a considerable bump in performance. Apple claim that their new browser is 30 times faster than Internet Explorer 7 and more than three times faster than Firefox 3.

    When it comes to UI and features Safari 4 ‘borrows’ heavily from Firefox and Chrome. New enhancements include…

    • Top Sites, an attractive display of frequently visited pages
    • Full History Search, where users search through titles, web addresses and the complete text of recently viewed pages
    • Cover Flow for history and bookmarks.
    • Tabs have been moved above the menu bar in a direct rip off of Chrome.
    • Smart Address Field, that automatically completes web addresses
    • Smart Search Field, using Google Suggest
    • Full Page Zoom

    For us web designers, Safari 4 brings 3 key benefits…

    • It is substantially faster especially for Javascript heavy websites
    • It is the first browser to pass ACID3 so its standards support should be excellent
    • It has built in web developers tools, which are essentially a rip off of Firebug.

    Generally the browser has been well received, although I note that Andy Clarke has expressed some concerns about the UI, especially in regards to tabs. He wrote…

    Tabs in a real-world filing cabinet don’t change size according to how many files you have. Don’t mess with the metaphor.

    I can see where he is coming from and have to agree. However, most of Andy’s comments are minor niggles and overall this is an impressive improvement. For more personally, safari now stands head and shoulders above other browsers.

    Cross browser testing

    Although the arrival of Safari 4 is exciting, it does bring yet another browser to test on. Increasingly browser testing is becoming unbearable.

    To make matters worse it is not always easy to run these browsers side by side. IE is famous for being terrible in this regards. However, it is not alone. Even running Safari 3 and 4 together takes some hacking. Fortunately a post this week entitled: ‘How to run Safari 4 beta and Safari 3 on the same mac’ explained how.

    There are also a growing number of services that aid in the process of browser testing. As with everything on the web, the problem is finding them. Luckily a website called the Freelance Folder has brought 7 testing tools together in a handy list.

    Litmus Homepage

    Some of the services are free, others are paid. Some provide screenshots while others allow you to navigate your site. All allow testing in most versions of modern browsers.

    The list includes…

    • Xenocode Browser Sandbox
    • CrossBrowserTesting.com
    • IETester
    • BrowsrCamp
    • Litmus
    • NetRenderer
    • BrowserShots

    Read the whole post for reviews of each service listed above.

    jQuery browser fixes

    Unfortunately no amount of testing is going to make up for the shortcomings in browsers. Whether it is a lack of border-radius support in IE or Firefox failure to render text-shadows, every browser has its limitations. In fact there are quite a few things that it would be nice if any browser did.

    Fortunately Javascript can help overcome some browser limitations and even enhance them where they all fall short.

    Of course, the downside is that plugging these holes is a lot of work. That is unless somebody has already done it for you. That is why I was so excited when Stanton pointed out ‘15 jQuery Plugins to Fix and Beautify Browser Issues‘.

    This post lists 15 jQuery plugins that provide some incredibly useful browser enhancements such as…

    • Rounded corners for IE
    • Get browsers to display columns of equal height
    • Cross browser text shadow
    • Fixed position footers
    • Preloading images
    • Fixing IE overflow problem
    • Increase the size of click targets
    • Vertically Center An Element

    A word of warning – Using third party plugins is fine if they are coded well. However, use too many and they may conflict causing problems. Use with caution and with a light touch!

    Back to top

    Feature: 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. Read More

    Back to top

    Listeners feedback:

    Contracts and legal stuff

    I went to have a look on the forum for a good question and found this posted by Dave:

    I am in the process of sorting out contracts and legal stuff. I came across this article – http://24ways.org/2008/contract-killer – from 24 ways and Andy Clarke and I think it is a fantastic example of a contract which is well written and doesn’t sound too stiff (if you know what I mean). Does anyone else have any examples or tips when writing a contract.

    Why have a contract in the first place?

    Bearing in mind I have never actually had to refer to one of the hundreds of contracts Headscape has produced in the past seven years, this is a fair question.

    The main reason is that it focuses both parties’ minds on the job and what is required to make that job happen. It’s a kind of comfort blanket too knowing that if anything does go wrong, there’s a bunch of stuff in place to help resolve it.

    How do we do it?

    We split all of our contracts into two separate documents: a ‘Statement of Work’ and ‘Terms and Conditions’.

    The Statement of Work is simply a description of the project written in ‘standard’ English. Roughly speaking, it’s a more solid version of the original proposal replacing, for example, ‘We could design X’ with ‘Headscape will design X’. It covers tasks, responsibilities, testing, technologies, project management, timescales, pricing, payment milestones etc. Basically, it is a detailed outline of the project that could be compared to the ‘Schedule’ of some contracts.

    We have a standard set of terms and conditions that ideally (from our point of view) just simply refer to the statement of work in question therefore binding our terms and conditions to that particular project.

    Our terms and conditions are written using fairly legalistic terms. Though this can sometimes mean that our clients, who may not be versed in legalese, have to take advice on what we’re proposing, I can’t remember a single complaint. I guess what I’m saying is that this appears to be the norm and taking legal advice on any contract, written in plain English or legalese, has got to be a good idea.

    I agree that legalese can by irritating. Although I can understand a fair amount of it, it has taken a long time for me to learn even the small amount that I do know.

    I once had a lawyer tell me that, when he was attending a class at law school on the subject, the teacher said that legalese existed only to allow lawyers to charge the rates that they do. I think his tongue was in his cheek, but on reflection, this actually makes sense if you view legalese as a kind of legal code that takes years of study to master.

    I’m not sure. I guess my only concern in producing a contract using layman’s terms is if it is dismissed in the event of a dispute.

    Our terms and conditions include the following:

    • The date of the contract
    • Who the contract is between (actual legal entities)
    • Definition of terms
    • Obligations
    • Deliverables
    • Payment
    • IPR (who owns what, what they can do with it, and when)
    • Confidentiality
    • Liability (often the biggest sticking point)
    • Default
    • Termination
    • Communication
    • Governing Law (which country’s law applies)
    • Signatures of the parties (most important!)
    It’s not a fight – be prepared to negotiate

    It is quite rare that our terms and conditions come back with no amendments. We believe that responsibilities and liability are evenly balanced but often a client’s lawyer will disagree. A cynical person might say that they are looking for issues to justify their fee, but it is possible that a particular point may not be right for some clients.

    For example, we include the line “The Contractor shall have the right to incorporate, in a readily viewable location, a credit and hypertext link in the Deliverables.” In other words we can have a ‘Web design by Headscape’ link on the site. Some clients object to this and, if so, don’t make a big deal out of it. Just go with it.

    However, there are times when you will think certain amendments or additions to the contract are unfair. Be prepared to stick to your guns but make sure you explain why. If you’re in any doubt, take legal advice.

    Some organisations will flatly refuse to sign our terms and conditions and insist that we use theirs. From our point of view this is not ideal because these terms and conditions are usually created for contractors that have absolutely nothing to do with web design. They often talk the physical delivery of deliverables and the like but, experience has suggested to me that these contracts, generally speaking, are all very similar. The only thing that we insist upon in these cases is that the statement of work is referenced in the client’s terms and conditions.

    Make sure the damn thing is signed!

    Bearing in mind the effort that is put into creating these documents, always make sure that they are signed. This sounds obvious but I have had the odd clients over the years that, to avoid their internal legal team, has given the ok on the documentation but always found an excuse not to sign it.

    It’s easy to say ‘well, we’re getting paid’ in these situations but, if things go wrong, you will
    not have a leg to stand on.

    So, in summary, contracts are good for everyone and worth investing effort in them and make sure you take legal advice if you’re not sure what you’re a client is asking you to agree to.

    Back to top

    154. Top Ten

    Posted in Classic shows on February 25, 2009 by Paul Boag

    On this week’s show: Relly Annett-Baker talks about good copywriting, Paul learns how to be a more efficient designer and we look at the ultimate website launch checklist.

    Play

    Podcast: Download (31.8MB)

    Download this show.

    Launch our podcast player

    Housekeeping

    SXSW

    Boagworld is doing loads of good stuff surrounding this years SXSW. The full details can be found here. However, the highlights are…

    • A live Boagworld show on Saturday 14th 6.30PM at the convention centre – With guests: Andy Budd, Daniel Burka, Joe Stump and Jeremy Keith. Please sign up on upcoming or follow via uStream.
    • The Great British Boozeup on Monday 16th at 7:30PM at Shakespeare’s Pub – An evening of great beer and an all British soundtrack. Again please sign up on upcoming.
    • Boagworld SXSW coverage – Instead of spamming both twitter and your RSS reader with content from SXSW, we are bring it all together on one handy streaming page.

    So whether you are actually attending SXSW or not, hopefully there will be something for everybody.

    Back to top

    News and events

    The ultimate website launch checklist

    Making a website live is a scary process. There is so much that could go wrong. However worse still, there is so much you could forget. When it comes to launching a website, you can’t afford to take chances.

    Well, BOX UK has been compiling a website launch checklist that takes some of the risk out of the process. This list includes everything from validating your HTML to announcing the launch on Twitter.

    If you are responsible for launching websites, then this post is a good starting point for your own checklist.

    Mr Budd is on fire (not literally)

    Normally when I write about the news, I focus on specific posts that have appeared over the last week. However, instead I want to draw your attention to Andy Budd.

    In case you are one of the three people who haven’t heard of Mr Budd,let me give you a quick summary. Andy is a user experience specialist and founder of ClearLeft – an agency that does a mixture of web design work and training. Andy is also author of CSS Mastery, an excellent book that I highly recommend.

    The reason I want to focus on Andy is because he has really started to churn out some superb posts recently. Although an accomplished author and speaker, Andy has written less on his blog over the past year or so. However, in this last week he has released two cracking posts.

    The first is entitled "Don’t treat your website like a commodity" and focuses on how we approach the market. It warns against trying to artificially create a need for your site. Instead he suggests shaping your site around user requirements.

    The second is entitled "Is your website like a leaky bucket?" and is in many ways a continuation of the previous post. In this one he warns against the mentality of continually driving new users to your site and instead encourages us to focus on retaining the users we already have.

    With these kinds of quality post coming from Andy again, now is the time to add him to your RSS reader (if you have not already).

    A win for the generalist

    I am very much a jack of all trades and master of none. Others have accused me of ‘having enough knowledge to be dangerous’.

    In the world of web design, specialists are the order of the day. As a result I am beginning to feel obsolete. However, perhaps that is a false perception.

    If like me you are a generalist, then you may draw comfort from ‘Bringing Holistic Awareness to Your Design‘, a post on Boxes and Arrows. In the article they explain that if you want to build websites that score high in user satisfaction, you need a team with a good general understanding. In particular they wrote…

    The more each team member understood the business goals, the user needs, and the capabilities and limitations of the IT environment "a holistic view" the more successful the project. In contrast, the more each team member was "siloed" into knowing just their piece of the whole, the less successful the project.

    Now, the article does not apply that specialists are wrong. It merely points out that in order to build a successful website you need to see the bigger picture.

    It goes on to identify 5 ways that you can ensure your team keeps this broad perspective. They are…

    • All team members conduct at least some user research
    • Team members participate in work and task flow workshops
    • Team members share and discuss information as a team
    • Team members prioritize information as a team
    • Team members design together in collaborative workshops

    This is certainly something we have begun to take on board at Headscape and we would encourage you to do the same.

    Back to top

    Interview: Relly Annett-Baker on Copywriting for the Web

    Paul: OK, so joining me today is Relly Annett-Baker who is a copywriter over at poppycopy.co.uk. Hello Relly, how are you?

    Relly: Hello, how are you?

    Paul: So here we are, on the phone, after a false start.

    Relly: I know, it’s good for an internet-based podcasting that we end up using the phone, but there you go. It’s reliable, I like it.

    Paul: Yes, all that digital technology, it’s nothing but trouble. Good old analogue.

    Relly: Yes, analogue beats everything.

    Paul: OK, so we’ve got Relly on the show today to really talk us through some of the kind of fundamentals of copywriting, and copywriting specifically for the web and how we go about doing that. So, Relly, I guess the best thing to do is start with the absolute fundamentals here, and we’ll start by asking you what do you think makes good copy, how do you define good copy?

    Relly: Erm, good copy starts with good writing, which sounds, you know, really obvious, but erm, really, unless your spelling and your grammar and your sense is not there, you’re not going to write good copy. So, that’s, you know, the start of it, so if you’re going to write copy, make sure you can write prose well, to begin with. Erm, beyond that, it’s then about… The difference between copy and normal writing is that you’re selling something, essentially, whether it’s a service or, er, an actual product, or, erm, even, you know, just an entire, just an idea. Erm, so, it’s about benefits, rather than specifications. A specification is, you know, what you put into your brochure when someone wants to know whether a dishwasher is going to fit in their kitchen. But, the benefits is much more about the time they’re going to save and be able to spend with their family, using your fantastic, very quick, very efficient dishwasher. Erm, and the other thing that good copy should do, above everything else, is entice a reader to investigate. Especially on the web, your copy has to earn it’s place; it has to earn an extra second of eyeballing, because people just scan on, we get so much information thrown at us, especially on the web, that your copy need to be clear enough that it can be easily understood and also enticing enough that someone wants to stick with you and find out more, rather than flick on to the next thing they can look at.

    Paul: Umm. I mean, you talked there about "especially on the web", what do see as being the, kind of, primary differences between writing for the web and any other medium?

    Relly: I guess the biggest difference is that print mediums are fixed, that’s why we have different editions of books or magazines that come out, whereas the web is fluid, so, the difference between wikipedia and the Encyclopaedia Britannica, and there are pros and cons for both of those mediums, erm, that they use, but mainly that you can alter things as you go, nothing’s ever sort of set down as "right, that’s what we said and we can never go back and change it". So, erm, the other thing is the web is used primarily for people that skim-read a lot of information and use it to gather information before they decide to go on and request a brochure or find out more about what it is that you’re offering. It’s usually the first point of contact for people looking up, so it needs to make a good first impression, erm, and as such it also needs to communicate what your company is like, what sort of, you know, erm, formalities you have, erm, how big you are, how small you are, and how you like to operate and convey that, er, which print very rarely needs to do, it’s often, by then, erm, when a print brochure comes into someone’s hands, they’re already aware of your brand and they’ve got a better idea of who you are.

    Paul: Mmm, I mean, there’s the kind of one issue that often comes up with the differences between the print, er, printed medium and the web, is that, you know, that because people scan, copy on the web should be kept short. I mean, is that something that you would agree with? I know that I’ve seen, you know, some articles written on A List Apart written before, that say "no it’s not about the length of the copy, it’s about how engaging it is". So, I’m quite interested in your opinion on that.

    Relly: Yeah, I would very much agree, that it’s much more about, erm, engagement rather than length. Often with print, you get told you have, you know, space for 250 words and that’s how long your copy has to be. With the web, your copy can be as long as it needs to be, but that’s not necessarily as long as you’d like it to be. But as long as you can keep people engaged and keep them with an interest to keep on reading, get more information about you, and then, er, essentially they can read 5000 words about you, but if they don’t press the button at the bottom that says "get in contact" or "ring us" or "do something", then that’s kind of all for naught. What you want is to, erm, your copy to be long enough to persuade someone that they want to take the next step and get in contact with you and make a, you know, make that step towards doing business with you.

    Paul: Mmm, I mean you talk, you’ve talked a lot about engagement already, how do you go about engaging people as you write copy? What kind of tricks and techniques are there, or is it probably a lot more complicated than that?

    Relly: (laughs) Erm, I wouldn’t say it was the sort of thing where there’s, erm, there’s one way to do it; there are different, different, erm, styles and it really depends on your audience. Erm, often when we think of copy we think directly of advertising, and when we think of advertising we think of billboards. Billboards have, literally, two seconds to engage you and fix a message in your head. So, they have to have a certain amount of shock-value, and that’s usually accompanied by a large image that ties that together. The web is a very different beast in that respect, in that you’re making a one-on-one relationship; you don’t have to talk to everyone in the street, you can concentrate on who you think your best customer is. You do research about you customers and your users, and then you write for them, and you write in a way that’s going to, erm, keep them reading. Erm, so it comes down to a lot of research about who you’re writing for.

    Paul: Mmm, that’s really interesting, you talk about writing for a specific person or, er, a specific group of people, because, it sounds then like you guys suffer from the same problem that designers would suffer from, when a client turns around and says ‘our target audience is the general public’, and they won’t narrow it down any. So, er, is it fair to say that you’ve got the same need to prioritize audiences that a designer would have?

    Relly: Absolutely, you cannot write something that is going to engage everyone all the time, you have to know who your audience is. Erm, and that often involves doing, you know, research that, erm, the clients themselves don’t necessarily take on as part of the need for copy, but, erm, often the product tells you what sort of copy you need to write. If you’re, erm, writing about a teddy-bear shop, it’s quite obvious that you’re not generally writing for a, sort of, you know, middle-aged, managerial businessman; you’re writing for either, erm, older women who collect them, or younger children and therefore you’re writing for parents. But when you get into services, it gets a bit more complicated and so you have to do more research about the people who make contact currently on the website, if there is an existing website, or, you know, what business they’re going for and who actually makes them, makes that next step, you know, and who predominantly makes up their sales; those are the people you should be writing for. I often say to, erm, to people who are writing, who are starting to write their own copy, to have a style guide and to practice that – try writing a letter to your best customer; obviously, you don’t have to send it, but, you know, as if you were going to address them, face to face, what would you talk about and how would you introduce your product, and what specifically would they be interested in about it. And once you’ve practised writing about your products in that manner, it feels difficult ‘coz it feels like you’re cutting off 50% of your potential audience, but if you can target on, you know, the 10% that make up your actual, erm, sellable audience, then your erm, your returns will be much higher.

    Paul: Mmm, very interesting. I like the idea of getting people to practice by writing a letter. I can imagine that works very well. Let’s talk about, umm, some of the common mistakes when it comes to copywriting, ‘coz let’s face it, you know, the majority of websites aren’t, er, produced and written by, you know, er, trained copy-writers, or even (Relly laughs)… they’re either written by, erm, the designer when he gets completely fed up with waiting for content from the client, or it’s written by the website owner. Umm, in either case, you know, they’re not obviously as experienced as you, so I’m interested in some of the really bad mistakes you see coming up again and again.

    Relly: Erm, the obvious one is when people take their brochure copy and just move that straight across to their website and say: "that’ll do, that’s perfect, that’s exactly what we want."

    Paul: OK, we we always say that, why is that wrong?

    Relly: Why is it wrong? Because, erm, your brochure should really be for when people have made contact with you and have an interest in your product. So then you can, you can work on selling them, you can, you can work on, er, getting past any of the objections that they might have, through a longer length of copy when they’re ready to address those issues, when they’ve already seen the positives. So, erm, your website should be… As an example, if you take, erm, say a hotel that’s, erm, setting itself up for events, or weddings, what a bride wants to see when she goes to the website is she obviously wants to see pictures of a lovely wedding, but she wants to know how the day is going to work for her, and why it’s going to be her, you know, perfect day. A bit further along the line, she wants to know how much glass hire is and how much it costs, you know, to have rooms in the hotel and she can be really direct in those. But, initially that first bit of copy needs to be one simple paragraph explaining why your hotel is absolutely perfect for her wedding day, as far as she’s concerned, the biggest day on the planet, and you have to make her feel she’s the most important person. Once she’s, once she feels like she wants to make the contact and book, the brochure can explain in far more detail what the liability insurance is, what the room size is; she needs to have a rough idea of these things, but they don’t need to be laid out for her, then and there.

    Paul: Mmm, are there any other mistakes that you see quite a lot?

    Relly: Yeah, people don’t revise or keep on top of their copy; so they kind of treat it like it’s been printed, and that’s it, they can’t ever go back and change it, or they feel they can only change it if they also change the design.

    Paul: Yeah.

    Relly: We’re starting to get past that a little now, erm, companies are getting a bit more used to the idea of blogs, and so they can keep updated in that respect. Erm, other mistakes people often end up writing for their client or their boss, rather than the actual audience, which goes back to, you know, what we were saying before, which is, you know, that’s a difficult one, everyone faces that where, you know, their boss says: "I think it should be like this", and if you know better, that’s, you know, that’s you having to then lay out why I think this works better because. Erm, but don’t, you know, be afraid to make the point that you are writing for the audience, the people that are going to buy and here are their needs and here are their requests, and this is how the copy has addressed that.

    Paul: Umm.

    Relly: And, I guess the other thing is that, erm, people (laughs), people who, er, don’t write very often, they fall into two categories, erm, especially with designers, this is so true, that designers either did art at school, because they wanted to get out of essay writing (Paul laughs) and therefore they haven’t written anything for a long time, and so they’re a bit rusty and they kind of need to maybe practice a bit before they lay something out and, you know, maybe hand it onto someone else and say: ‘does this make sense to you? Can you, can you read this out of context and understand, you know, where I’m going with it?’ Erm, I often talk about, erm, people using, er, text readers for the same thing; you know, I know they’re used in website design to check, erm, accessibility, that someone, you know is, er, able to have the text read to them and understand what’s going on they should be able to navigate around the website. It goes perfectly well for copy as well, copy is very much part of your navigation: it’s the information you’re imparting to that person. So that’s always a good way that, you know, if someone, if someone can read or be read the copy out of context and they get, you know, 70%, 80% of the idea of what’s going on, then you’re on a, you know, good track that way. Often you find that people, the other thing that happens is that people start writing and they get so excited about the fact that they’re writing, the prose just flows from them, like they were actually Lord Tennyson reincarnate (Paul laughs) and they come to the end and they’ve built up to a massive, dramatic conclusion (Paul laughs) about why their product is the best thing since sliced bread and actually that dramatic conclusion generally needs to be the opening statement, because it’s what catches hold of people and gets them to read onwards.

    Paul: I mean is, I’m fascinated by this whole area of kind of trying to create a tone in your copy, er, because I’m not a copywriter, I write quite a lot, but in the sense of blog posts and things like that and so, whenever I’m writing, I’m writing in my own voice, if that makes sense. But, obviously when you’re writing for another site, when you’re trying to reach a very specific audience, when you’re writing within that tone of the website, that’s a very different kettle of fish and I’m interested in how you do that, how you go about setting a tone; how you go about sticking to a tone, you know, how do you do it? (laughs)

    Relly: Ah, the creation of a style guide is very, that’s probably most important here. There are two things that I recommend when, umm, coming up with the, sort of the voice, the tone for a site, is to think about the persona of who that person is that’s writing, that’s especially true if you have multiple people who are writing as the same person, erm, often you find this now with companies that have begun to use Twitter streams and so on to communicate stuff and they they need to remain the same person, the, erm, NASA rockets do that very well, Discovery and the rest of them, they they’re able to communicate very well, both scientific facts and just, you know, prosaic information about the fact they’re bored of sitting on landing pads, launching pads and things like that and it’s quite nice because it’s able to communicate a human voice to something that essentially is a very complicated machine, erm, and the way that they’ve done that is to think: "well, if I, you know, it I was going to be a person talking about these experiences, what would I say?" and sometimes, you know, the most complicated, fascinating machine on earth, saying the most mundane things communicates more about their team that it could do than take a very long, scientific specification of what they were doing. So, it’s again going back to understanding your audience. NASA have understood that their audience on Twitter, they’re not space buffs, they’re people who are gererally interested, because most human beings are interested when a rocket goes up to space, it’s, you know, it’s an amazing thing, it doesn’t matter if you’re 6 years old, or 36 years old, it still seems, you know, astounding, that it happens. So, they’ve gone back and they’ve thought about, you know, how can we communicate to people every day and they treat the rockets as if they’re just people hanging around doing their jobs. just like everyone else uses Twitter. So, the first step is to understand your audience, and it takes a certain amount of, erm, it is quite cool to say but dissection, it is cutting out the people that you don’t want to talk to; people often know who their customers aren’t, even if they can’t quite focus on who their customers are and who their customers are becomes clearer with more and more research. Erm, a lot of what a copywriter does as research, right at the beginning, crosses over with information architecture, it’s a lot of looking at, erm, how best can we communicate these points and who really needs to know them and in what order? So you kind of, you go back and you assess, so this company is, erm, is selling er… they might be selling, we used dishwashers and washing machines earlier, so who’s the primary researcher and purchaser? It’s probably going to be, erm, it’s split probably 50-50 between female and male, as for the initial research, but they’re probably going to be above the age of 24, averagely; they’re probably going to own their own home and they might well have children and that gives you the sort of insight to the sort of family life that they have and what they, therefore, want to get out of that product. Erm, so then it’s erm, then it’s a case of looking at, I often go back then to erm, manufacturers, look how manufacturers’ websites work, how they describe their own products; what sort of visual advertising they’ve used to communicate these things and how that can be translated into words, what benefit are they selling with the visuals, often if I’ve been supplied visuals for the website, they can tie in together quite well. And then I create a persona, the person that is writing, you know, being the person who is writing for the website. So sometimes I’m a middle-aged man, sometimes I’m a teenage girl, sometimes, you know, I’m a cool, skating dude, it really, you know, it really depends on what, erm, angle I’m going for

    Paul: Sure.

    Relly: With the copy. I keep a swipe file, which is basically things that I take from magazines, from newspapers, from other advertising literature, from books, from articles, that I think has been written really well and I take it away and I say, I kind of take it apart and say: "what about that headline functions so well?" and "what about, what is it about this piece that talks so well to the audience that it’s that it’s going for?" that, erm, that’s especially good if, even if you’re not the target audience and you’re still engaged enough to read it; that’s, you know, often quite fascinating. One of my favourite places to, erm, take, er, hints and tips from, of all places, is the Daily Mail and the Sun (Paul laughs), believe it or not, because they are so good at putting across an emotive idea in very few words, there is nothing like a Sun headline for giving you a kick in the pants, for feeling, you know, and often you read it and you find yourself, erm, agreeing with the statement, out of hand, before you pull yourself back and go: "now hang on, no, hang on this is the Sun, I’m going to read this story first before I make up my own mind." (Paul chuckles) But, you know, they’re very good at doing that, and, erm, I mean it’s not ideal for everyone’s website, obviously, but to have the ability to do that, to take just a few words and make an emotive statement is really useful in copy, because what you want people to do, more than anything else, is feel that they must do something about getting hold of your product, they must find out more, they must buy it then and there, they must, you know, whatever is appropriate, you know, you’re not going to find many people who are going to one-click buy a conservatory so that’s not necessarily, you know, going to work so well, but you might well be able to get them to arrange to have someone to come round and measure for a conservatory and that’s the next step to getting them to do what you want them to do. Copy is all about behavioural management, essentially.

    Paul: Yeah. I mean, it’s got a lot in common with design, you know. As I hear you talk, there’s so much overlap. I mean, but what’s so fascinating is that, you know, a client will spend a fortune on design and they will spend a lot of time and effort and forever express an opinion over look and feel and design, yet they don’t seem to want to invest money in writing good copy and they’ll say things like, you know: "content is king", yet they, there is this perception, I don’t know, is it a perception that they can do it themselves? Why isn’t it? Why is it so hard?

    Relly: I don’t know. We, we poor copywriters, we are the Cinderella’s stepsisters of the web design world. Er, it’s especially true in web design, more than anywhere else that I’ve seen, erm, probably because the medium is that much newer, that, and it sprung out of interactivity, as opposed to, erm, books are about staid reading and advertising sprung from that; television and radio sit somewhere in the middle, but essentially it’s a written script, sometimes with pictures added. The web is a different medium altogether, it’s much more about doing, interacting and as more and more social media stuff springs up, you know, that’s more and more true and don’t get me started on the amount of companies that have got terrible facebook pages and so on. Erm, but again, it is that belief that it can be done by yourself; that’s not necessarily, you know, not true, you know, people can write their own copy, in the same way I can design a website – it might look like a dog’s dinner when I’m done, but I can do it. It depends, I can, I can start off, to turn it around, I know enough, I have enough of a little, you know, little amount of dangerous knowledge, to be able to put a blog up, design my own blog header in Photoshop and upload it and be able to update my blog day to day, but that doesn’t mean to say that I’m necessarily ready to design a site for a, you know, big multinational company that wants to sell direct from its website to multiple places around the world. The same goes with, erm, with copywriters. I think partly the reason that we get so little investment put in at the beginning of projects is that, erm, we’ve come to see creating a website as a visual thing, clients very often ask about how a site looks and they don’t care so much about how it works underneath, providing it works, which is the equivalent of asking a baker to bake an amazing cake and you get it delivered and it’s four tiers and it looks fantastic and it’s got these, you know, subtly crafted sugar-craft dancers on top and flowers trailing all around it and you cut it in half and it’s sawdust. And, you know, the copy very much does come under the sawdust category, we kind of get a bit left behind because everyone can write a bit and it doesn’t take that much, erm, knowledge to at least lay out something that makes sense, erm, I think it does kind of get neglected; erm, I often sort of say to people that, you know, that the copy is as much part of the navigation and the function of the site as anything you do with the menu buttons or whatever else, erm, and what we really need to do is to have designers… there are some designers who have the attitude that whatever happens after sign-off is no longer their concern, so the amount of sales that happen, whatever else, that’s not their problem, they’ve done their bit, they’ve designed a site, it works and it goes out. Whereas, really what we, what you’re then doing is designing for your client, erm, a very pretty picture-book of all their products, but that’s not necessarily a sales tool, so we need to look now much more at, erm, at websites as sales tools for companies and to people, you know.

    Paul: So, I mean, where’s the line here, mind, because, umm, you know, I can imagine website owners sitting listening to this now going: "well, I mean she seems to be suggesting that we get a copywriter to write absolutely everything on our site", umm, but, you know, when you get into the realms of, you know, corporate blogs and things like that, I mean it’s going to cost a fortune, is it not, to get a copywriter involved at every stage. Where should a copywriter be involved, where shouldn’t they be involved, how do they fit in to the process?

    Relly: Right, that’s a really good question. I don’t believe for one minute that you need to have, unless you have a site that need constant updating, you don’t need to have a content editor on-site all the time; in the same way that you don’t need to have a website designer on-site all the time, unless your website is constantly evolving. If you have a web team and your content changes a lot, then you might well want to think about getting a content editor in.

    Paul: OK.

    Relly: If you run an online shop and you change a few products a week, and you might introduce a few new products, er, via an email marketing, whatever, you might want to consider how much of that you want to give to a copywriter. If you’re updating a company blog and you’re sending, occasionally send out, erm, emails to old clients and invitations to new clients, you probably don’t need to get a copywriter, unless you feel it’s a better use of your time, and I think that it is the division a lot of the time, is that if you’re, if something really needs to sell, if it needs to make an impact, erm, I guess you wouldn’t find an advertising agency going ahead and taking on a billboard campaign, without getting a copywriter in, or their own in-house copywriter; it’s not going to be the managing director going: "well, we’ve got the artist to do this fantastic picture and we’ve bought all the advertising space, we’ve got a whole campaign rolled out, so I’d better think what we’re going to put on the, er, on the advert then." It just doesn’t work like that and that’s exactly, that should be exactly the same with your website. If you’re looking to launch a new campaign, if you’re selling something specifically, if it’s going to make a big difference to the way your company’s going to go, you want to get professionals in, and in this case it would probably be a copywriter would be the professional that you require. Erm, you know, you probably wouldn’t want to go and fiddle with your own plumbing, unless you have a very deep interest in DIY. It’s the same thing. Erm, but on the flipside of that, is that it’s, copywriting isn’t some arcane art that people can’t learn, in the same way that most people started learning web-design by sitting down in front of a computer, you know, bashing something out in Frontpage and going: "well, that kind of works", and then four years later cringing at what they’ve done. I think it’s very much the same for me, when I started writing copy and content, I was a radio producer and I have been responsible for some the worst chart hits in history (Paul laughs), you know, ascending to the chart because of the copy that I wrote, you know, to persuade people to buy the singles, you know, the competitions that we came up with, you know; it was my job, it paid my bills, buy I can’t say, you know, getting the cheeky girls to number 1 is my proudest achievement.

    Paul: Oh dear.

    Relly: And I was at least partly responsible for that (Paul laughs). I have to take my part in history on that one. Erm, you know, again it’s that thing, you know, anyone can go back and do it if they want to learn, you know, how to write copy. Just be aware that your first few attempts probably want someone to look through, but don’t be disheartened if you get to the end of it and think: "that’s not really what I wanted." You can always go halfway with a copywriter; I run workshops where I go into companies, talk to them about what their needs are, help them come up with a style guide, so they can say: ‘we’re going to write, it’s going from really simple stuff, like we’re going to have abbreviations and we’re not going to us the Oxford comma (Paul laughs), if that’s of any interest to any of you punctuation geeks out there, erm, right through to these are the sorts of people we’re addressing, these are there interests so we’re going to work these into this piece of copy, and, you know, I can then work with your staff members who will continue to write and then you’ve got, you know, a trained battalion of copywriters in-house ready to write things for you, on your behalf. And that’s often, you know, I often say to people that it’s not impossible to write copy, it just takes time to do it. As with anything else, it takes time to code a website well, properly and so that you can make a job out of it, it’s exactly the same with copywriting, but nothing stops you from building those skills up as you go.

    Paul: That’s brilliant. That’s absolutely brilliant. It’s really good to hear a copywriter’s perspective on all of this stuff, because I don’t feel there’s enough really said about that part of the website and it’s been great to have you in on the show, Relly, and I really appreciate you taking the time.

    Relly: Thank you very much.

    Paul: So, thank you very much.

    Relly: Thank you.

    Thanks goes to Simon Douglas for transcribing this interview.

    Back to top

    Listeners feedback:

    Being a more efficient designer

    Adam from Wales has written in with an interesting question:

    Adam: With the economy tanking and client’s squeezing budget, can you give us any tips about being more efficient so we can turn around projects quicker.

    It is a good question and one that got me thinking about creativity and its relationship with productivity. I also thought a lot about myself and how I work. All of this eventually led to…

    10 Tips for Efficient Design

    Back to top

    153. Harsh

    Posted in Classic shows on February 18, 2009 by Paul Boag

    On this week’s show: 10 harsh truths about your corporate website, Ryan reviews FreeAgent and Paul highlights the differences between print and the web.

    Play

    Podcast: Download (20.3MB)

    Download this show.

    Launch our podcast player

    Watch the behind the scenes video

    Housekeeping

    Consultancy Clinic

    I wanted to followup on the consultancy clinic idea I mentioned a few episodes ago.

    As you may remember I was toying with the idea of doing one-to-one chargeable skype calls for those who want my advice. I get so many people asking for help that I am unable to answer them all. After all, I have to work for a living!

    A consultancy clinic would allow me to help people with their web strategy, while at the same time keeping the Headscape directors happy! Instead of having to commission a full blown consultancy project, you can just have a chat with me on a pay-as-you-go basis.

    Anyway, the reason I bring it up again is because I have decided to go for the idea. I have launched a consultancy clinic website, where you can get more information and book an appointment.

    However as well as wanting to pimp the service, I also wanted to mention the site itself. I decided to use this as a test case for the graded browser support I wrote about recently. I have therefore written a blog post outlining the approach I used on this site and how it worked in practice.

    Even if you are not interested in the consultancy clinic, you maybe interested in how the site was built.

    FreeAgent Discount

    The guys over at FreeAgent are offering a 25% discount to all boagworld listeners until the end of Febuary. Just enter the code newfac when subscribing and the discount will apply for 6 months. Find a review of FreeAgent later in the show.

    News and events

    Feature fatigue

    This week Gerry McGovern writes about what he calls the ‘Hidden power of content‘. In fact it is mainly a commentary on a Time Magazine column about buying habits.

    You maybe wondering why I mention it here? Well for two reasons.

    First, it is an interesting post for those of you who run ecommerce sites. It talks about how your product copy needs to focus on more than features, if you want to encourage long term satisfaction in your customers.

    Second, he writes about the idea of feature fatigue. This is very relevant to all website owners and something I touched on recently in my post ‘5 options when website budgets get slashed‘.

    We love to add more and more features to our websites, but that is not always the right decision. Users have become overwhelmed with features and are looking instead for simplicity and ease of use.

    Read the post for yourself and ask how it applies to your site.

    Striking font stacks

    I am increasingly excited by typography on the web. Not because of the possibility of font embedding or techniques like sIFR. No, what really excites me is the work being done right now using font stacks.

    The beauty of font stacks is that even if a user doesn’t have your preferred font, it can still display an alternative.

    A lot of designers have been working hard to help us squeeze the most from the fonts installed on our machines. Huge amounts of research has been done on common fonts, as well as the best stack combinations. The trouble is this information is spread all over the web.

    However, this week Paul discovered an excellent post that brings all of this research and best practice together. ‘Striking web sites with font stacks that inspire‘ is a great post that not only lists the latest thinking on font stacks, it also provides some incredibly inspiring examples of them in use.

    If you are looking to become a great designer then understanding font stacks is essential. This post is an excellent place to start.

    Tips for improving your HTML and content

    Our final featured post this week is ‘5 Top Tips to Beautify Your HTML and Enrich Your Content‘ by Mike Brown over at Sitepoint.

    HTML is a deceptive language. On the surface it is amazingly simple and anybody can be writing HTML in a few minutes. However, the longer you work with it the more you discover the variety of ways in which it can be implemented – some good, some bad.

    This post shares some very basic best practice for working with HTML. Advice includes:

    • Using short URLs
    • Being consistent in your markup
    • Minimize uses of class and id attributes
    • Add title attributes and other metadata to enrich content
    • Use comments and whitespace to help readability and ease maintenance

    All basic stuff but ideal for beginners and a useful reminder when the rest of us get sloppy.

    Back to top

    Feature: 10 Harsh Truths About Corporate Websites

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

    Back to top

    Listeners feedback:

    Review: FreeAgent

    Way back in show 131, Stanton and myself answered a listeners question about project management and invoicing applications, and I mentioned FreeAgent in my line up of apps that I thought you listeners would be interested in.

    I’m now going to discuss the app in more detail, as I’ve been really getting into it and using it to it’s full potential.

    FreeAgent is a fully featured online accounting tool wrapped in a sleek, comprehensive and easy to use interface. It’s aimed at Sole Traders, Partnerships and Limited Companys, they offer a free 30 day trial to get you started and after that there’s a price plan ranging from £15 – £25 a month at the time of recording this review.

    I’m a simple code monkey and the thought of managing my taxes and invoices sends shivers down my spine. So I love that FreeAgent just takes me by the hand and guides me through the whole process.

    Accounting is project based, which doesn’t suite everyone, but that really depends on your personal preference.

    You simply start off by creating a client, then you assign a project to that client, you add timeslips to the project and using your hourly rate FreeAgent tells you what you’ve earned and what you owe the tax man and the whole thing is pretty much that simple.

    As I’ve said it’s fully featured, you can create invoices, manage expenses and mileage, upload and analyze your bank statements, create a login for your accountant, view real time profit and loss reports the list goes on and the guys are constant adding new stuff.

    Even if you decide you don’t like using FreeAgent after you’ve signed up you have the option to export your data at any time and try something else, so there’s no fear of loosing anything.

    This week sees the launch of a redesign to freeagentcentral.com and the FreeAgent app itself and I’ve been one of th
    e luck ones to get a sneak peek behind the scenes and I can tell you that the guys have been putting a lot of effort into improving the general interface based on user feedback. They’ve refreshed the colour scheme to make things easier on the eye for long term use and restructured some of the navigation to make moving from projects, time tracking and invoicing much more intuitive.

    In my opinion it’s definitely worth a look so if you want to know more about FreeAgent head over to freeagentcentral.com, watch the 2 minutes video introduction and take the tour. They’ve even got a number of demo’s so you can go in and play with the app before you sign up. Even more incentive to have a look would be the 25% discount the guys are offering to all boagworld listeners, just enter the code ‘newfac‘ when signing up for a free trial and the discount will last for 6 months once you subscribe.

    The difference between print and web

    Jake Knight asks a brilliant question, that I am amazed we have yet to address on the show.

    Jake Knight: What are 5 things you would want any print graphic designer to know first and foremost about designing for the web?

    So it is a top 5 list you want? You have been reading too much Smashing Magazine! Okay here goes – The top 5 things every print designer needs to know about the web…

  • Let go of pixel control – One of the hardest things for print designers (and marketeers for that matter) to accept that you do not have pixel perfect control on the web. Different browsers, resolutions, monitors, operating systems and video cards all alter the way your site is displayed. Add to this the users ability to change font sizes, colours and browser dimensions, and it becomes impossible to have the control you get in print.
  • Don’t be afraid of the code – Many print designers shy away from coding HTML. They rely instead on a ‘techie’ to handle this side of things. That is a mistake. To really get to grips with the web you need to understand how it works. HTML/CCS/Javascript all shape and influence design (for better or worse). Also, it really isn’t that hard. HTML in particular is a very simple language.
  • Web Typography is not so bad – Okay so you haven’t got the freedom of print, but typography on the web can be just as creative. By using font stacks, line spacing, and kerning you can create truly gorgeous typography. Also when you just have to have a particular font, there are techniques such as image replacement and sIFR. If you are a typography bluff and want to discover what is possible, check out Richard Rutter’s blog.
  • It is an interactive environment – One of the most common mistakes of print designers is to focus on aesthetics and forget usability. The web is interactive and web design has more in common with signage design than brochure design. Your job is to help users complete tasks, not just to produce attractive design.
  • Your skills are transferable – Everybody goes on so much about the differences between print and the web. It is easy to get demoralised and conclude you could never make the switch. However, in reality most of your skills are transferable. Layout, colour theory, typography and composition are just some of things that are universal no matter what the medium.
  • So there you go Jake, 5 nuggets of advice for anybody considering moving into the web from print.

    Back to top

    10 things a web designer would never tell you

    Posted in Design on February 5, 2009 by Paul Boag

    These arty-farty web designers are always telling you how your site should look. Don’t listen to them! Don’t they know the customer is always right? Here are 10 things a ‘good web designer’ would never tell you about choosing the perfect design.

    Working with web designers is a nightmare. You will never meet a more opinionated bunch of snobs. They are always going on about ‘white space’, ‘composition’ and how they went to art college (like that counts as a proper education!). When it comes to choosing the design of your site, they are the last people you should listen to.

    What follows are 10 things you need to know about managing a web design project, that no web designer will ever tell you!

    1. Always request speculative design up front

    Before you pick which web designer to work with make sure they submit some designs for your site upfront. Whatever you do, don’t pay for this work. If they really want to work with you they will swallow the cost.

    Some of them might start bleating about not doing ‘speculative design’ and that only designers desperate for work would do design for free. Personally I ignore this BS. If they are ‘so successful’ that they can’t spare the time to do unpaid work for me, then I don’t want to work with them.

    What is great about speculative work is it is not constrained by ‘understanding the business’ or ‘user feedback’. Its all about creativity. Surely a good web designer can come up with great work out of thin air, even if they don’t know who the target audience is and have never spoken to the client. I want something that makes me go wow. Who cares if it ‘fulfils my business objectives.’ The more bells and whistles the better!

    Screenshot of no-spec.com

    2. Don’t get hung up on end users

    Web designers are always obsessing about the end users. They worry that users won’t like this or that they won’t understand that. Its pathetic.

    People like to be told what to do and they will ultimately follow your lead. I once had a web designer complain because I wanted to collect users phone numbers on a sign up form for our newsletter. Apparently ‘users’ don’t like being asked for unnecessary personal information. Can you believe it! How the hell am I going to cold call these people if I don’t have their phone numbers. Sometimes you wonder how these idiots survive in business.

    Instead of focus on user needs, focus on what you can squeeze out them. Times are tough these days and so you need to maximise your returns on every one of these sheep. You have to be tough in business.

    Asta Development Website

    3. Rely on your gut instinct, not testing

    Talking of users – what is this obsession with user testing? Just sounds like a way for web designers to charge more money if you ask me.

    After all you have probably been working in your job for years. You know all there is to know about your audience, right? Even if you did run user test sessions, stakeholder interviews or whatever other made up technique is the latest fashion, its not going to tell you stuff you do not already know.

    Admittedly, these sessions occasionally turn up stuff you might not expect, but can you really trust the results? Surely your years of experience count for more than a few hours of testing.

    Of course, the other problem is that user testing is massively expensive. I heard from a friend that it involves usability labs, videos, two way mirrors and ‘facilitators’ (whatever those are). That all sounds pricey to me!

    Some web designers will tell you that they do it by going into user’s homes and talking with them in their own environment. They justify this by saying you learn more because the user is relaxed and you can see where they live. Personally, it doesn’t sound very professional and if it isn’t expensive, how could it possibly give good results?

    useit.com

    4. Form a committee to provide feedback

    Admittedly I maybe sounding a little arrogant, but I really am not. I think it is important to get the opinions of other people. I just think web designers are not the people you should be asking. They live in a techy bubble and do not understand what it is like to be an ordinary user like us.

    I suggest forming a committee to approve any designs produced. After all web designers keep telling us that design is subjective. That means you shouldn’t rely on the opinion of just one person (especially if that person is a designer). What you need is a committee to thrash out what the site should look like.

    Ideally you would call a meeting with the designer in the room and get them to produce something there and then under the direction of the committee. However, most designers tend to get ‘emotional’ when you suggest that. So instead I recommend giving them the freedom to produce something themselves and then discuss it as a group.

    Now inevitably this will lead to disagreement. Some people will like the colour, others will hate it. This is natural. What you need to do is seek a compromise that will please everybody. If you can have the designer on hand to try out new ideas in the meeting this will really help. Before you know it you will have a design everybody can tolerate (although admittedly not everybody will like it).

    A committee of people working out how to reach a compromise on a design

    5. Become obsessed with detail

    “The devil is the detail they say. Nowhere is that more true than on a website. Unfortunately you cannot rely on a web designer to have that attention to detail. Its hardly their fault. They are ‘arty’ people after all and their brains just don’t work that way.

    If you want your design to be ‘just so’ you will need to micro manage every aspect of the design process. Don’t be afraid to tell your designer exactly what you need them to do. Be as specific as possible. After all, they call themselves pixel pushers.

    A twitter post where a user declares he is a pixel pusher

    Also insist on consistency across all browsers. Web designers tend to be sloppy in this area. It might look great in Safari (apparently this is a browser – who knew!) but in Netscape 4 it looks awful. They will give you some rubbish about not all browsers being capable of rendering modern design. They will say that as long as it is usable on all browsers, that is what matters. The hell it is! You don’t put up with that kind of rubbish in print design, so why should you on the web?

    6. Enforce corporate style guides to the letter

    Your organisation has a corporate design guide for a reason and yet web designers think they can flaunt the rules. They will talk about the differences between print and the web. They will go on about colour on screen, web typography and dots per inch. However, the real reason they want to ignore your guidelines is because their egos will not allow them to work within limitations.

    You must take a firm hand over this issue and stick to the letter of the law. Enforce pantone numbers and ensure they use corporate typefaces. They might mutter something about limited fonts on the web but this is just not true. I know for a fact that sites built in flash can use any font you want. With that in mind I always recommend that sites are built entirely with Adobe Flash.

    Oh yes, and watch out for abuse of the logo. Most style guides say that the logo must have a certain number of millimetres around it to allow ample white space. I recommend taking a ruler and measuring the space around your monitor on screen. Better still, print out the design so you can be even more accurate.

    24 Ways article containing the words Branding Guides be Damned

    7. Fit as much on the homepage as possible

    Let’s take a moment to discuss the design of your homepage in particular.

    Without a doubt the homepage is by far the most important page on your site. If I look at my own website statistics the majority of people who come to my site never get further than the homepage (I have no idea why this is the case!) This is a problem.

    The solution is obvious when you also consider the importance of minimising the number of clicks a user has to make to reach content – Put as much content as possible on the homepage.

    This also solves the problem of everybody within your organisation wanting homepage real estate. Instead of endlessly discussing whose content is most important, simply put it all on there.

    Of course with so much content on the homepage people might complain their content is lost in the crowd. The best solution in such situations is to either make it bigger or animate it. I find flashing text particularly effective.

    HavenWorks.com

    8. Ensure all content appears above the fold

    Unfortunately you are limited in the amount of space available on the homepage. This is because all content has to sit above the fold.

    The fold refers to the point where users have to start scrolling. As we know users do not scroll. In 1994 Jakob Nielsen found that only 10% of users would scroll when presented with a web page. 15 years on I see no reason why this would have changed.

    Some designers will tell you that the fold is a myth. They will argue that it does not exist because different browsers, resolutions and toolbars all effect the vertical available space. All I know is that on my computer I have 470px of vertical space before I have to start scrolling. I am a fairly typical user and so you should ensure all content is within this area.

    The only exception to this rule is if your boss has a different amount of vertical space. If he is going to be looking at the website I suggest designing for his browser. Alternatively simply print out the site for his approval.

    A web deisgner holding a 'there is no fold' banner

    9. You only need to test in Internet Explorer 6

    Web designers like to claim they need to spend hours testing on every browser combination. However, in reality this is just another way to extract more money from you.

    All you really need to do is build the site so it works on Internet Explorer 6.

    Internet Explorer is the most dominant browser having by far the largest market share. Although there are different versions of IE most companies run IE6. As corporate customers are the people with the real money you should concentrate your testing on their browser. Also surely if it works in IE6 it will work in IE7! You can trust Microsoft not to break the web.

    If you want to be super cautious, add a message to your site telling users it is optimised for internet explorer. Users can then download that browser if they want to see your site.

    Website displaying message about downloading IE

    10. SEO is more important than design

    Getting the design of your website right is important. However it is no use if nobody sees it. Your number one priority has to be driving traffic to your site.

    The best way to do this is through search engines. Fortunately there are a plethora of tricks and techniques to fool Google into ranking you highly. You can use hidden text, cloaking pages, redirects, doorway pages and keyword stuffing to force you up the ranking. Google kindly list these techniques in their Web Master Guidelines.

    The problem with some of these techniques is that they undermine the design and content of your site. They can also affect the usability and accessibility. However, this is a sacrifice worth making in order to keep those new users rolling in.

    Some web designers place a higher emphasis on repeat traffic. However, in my experience it is hard to get a user to return a second time. This is almost certainly because they have seen everything already. Why would they come back? Concentrate your efforts on creating a steady stream of new users.

    Example of how BMW used keyword stuffing and redirects

    Conclusions

    If I could leave you with a single thought from this post it would be this – your web designer does not work with you, he works for you.

    You need to take control of the design process. Its your site and you should get the design you want. The role of the designer is to implement your idea. Do not allow him to drag you down into endless discussions about ‘users needs’, ‘accessibility’ and ‘usability’. These are all distractions from the primary aim – to impress your boss and earn that next promotion.

    This article was based on a presentation I gave at Bathcamp and is a sick twist version of content taken from my book ‘The Website Owners Manual‘

    151. Budget

    Posted in Classic shows on February 4, 2009 by Paul Boag

    On this week’s show: Paul shares 5 tips for when your website budget gets slashed. We have a review of Dropbox and discuss ways to improve the typography on your site.

    Download this show.

    Launch our podcast player

    Housekeeping

    Two pieces of housekeeping this week. 

    WCAG2 Video

    A couple of weeks ago I did an internal presentation to the guys at Headscape about WCAG2. The idea was to bring them up to speed on the new accessibility guidelines and also to put accessibility back at the centre of our processes.

    At the last minute I made the decision to record the session and put the video online. Although the audio is awful (hence not using it in the show) it maybe useful if you have not read up on WCAG2 yet. There is also a transcript if the audio becomes too much.

    You can watch my Introduction to WCAG2 here.

    Win a copy of ‘A Practical Guide to Designing for the Web’

    Mark Boulton has just released a book that covers the underlying principles of all good design. Whether it be online or in print, good design is governed by certain best practices. This book introduces the reader to these principles, including subjects such as…

    • How to start the design process
    • Research and ideas
    • An introduction to typography
    • The basics of colour theory
    • The rules of good layout

    The book is unsurprisingly beautifully designed. However it is also well written and engaging. I can highly recommend it.

    You could go and purchase a copy right now for only £12 (and I would encourage you to do so). Alternatively you could win one of three free copies by entering our twitter competition.

    For your chance to win a copy of this inspiring book, twitter your top design tip using the hash tag #designTip. For example your tip might be…

    #designTip – If you wish to draw attention to a design element surround it with whitespace.

    The closing date for this competition is Friday 27th February, so get your tips in before then.

    The winners will be chosen by Mark and we will direct message them shortly after the 27th. To ensure we can do so please subscribe to the Boagworld Twitter feed.

    The winners will also be announced over twitter and on the boagworld podcast.

    See the excellent tips that have already been submitted here

    News and events

    IE8 Cometh!

    The big news this week is that IE8 has taken one step closer to being officially released by announcing their first release candidate.

    Screenshot of the IE8 Readiness toolkit

    According to the IE blog:

    The IE8 product is effectively complete and done. Our next step, after listening to feedback from the final testing feedback from the community, is releasing the final product.

    Although they do not provide a release date it is fair to say that it will not be long now.

    Whenever I talk about IE8 people immediately ask if they can stop supporting IE6. My recent article on graded browser support should make my opinion on that clear.

    However, the more important question is are you ready for IE8? Do you know what CSS properties it supports and have you tested your websites in it?

    Microsoft provide a handy table of CSS selectors and properties that IE8 and indeed all other versions of IE support.

    Once you have looked at that check out the IE8 readiness guide for developers. This has loads of information about IE8 support for CSS, Javascript and various proprietary features.

    It also has a small piece of code you can fall back on if you are experiencing serious rendering issues on existing websites. By inserting this code into the head of your HTML document it forces IE8 to render in the same way as IE7. I am sure this will be a useful stop gap measure for website owners unwilling to pay for updates to their sites.

    15 Tips for Freelancers Starting Their Own Business

    Next up some great advice for web design freelancers. Think Vitamin have published a post entitled ‘15 Tips for Freelancers Starting Their Own Business‘.

    In actual fact the advice applies to all freelancers, not just those starting out.

    It is a fairly arbitrary list, but it has some good stuff in there. Just a few of what has been included are…

    • Move Out of Your Back Bedroom
    • Don’t be Afraid to Pass
    • Work on your Sales Technique
    • Learn About Personality Types
    • Maintain a Verbal/Email Relationship

    If you are a freelancer looking for advice I can also highly recommend FreelanceSwitch.com, which is an entire site dedicated entirely to helping freelancers. Check it out.

    Facts and Figures

    This last week seems to have been a week of facts and figures.

    The first figure that caught my eye was that Adobe AIR has been installed 100 million times. That is an impressive figure, even if it is being overstated as some believe.

    BBC iPlayer

    Moving web applications to the desktop is an area I find particularly exciting. I am not sure it is always necessary. However, platforms like AIR make it scaringly easy, as we discovered when we did a proof of concept recently at Headscape.

    The same announcement from Adobe also stated that Flash 10 has a 55% market penetration on Internet connected computers and they expect that number to rise to 80% by Q2 2009. This is an improvement on the adoption speeds of previous versions.

    Other facts and figures to appear this week came from the "state of the web" survey carried out by Web Directions South. This is a survey of professional web designers and developers. Some interesting figures pulled out of the survey by Roger Johansson included:

    • The number of Mac and Windows users are almost equal – both are used by 46.8 % of respondents
    • As many as 4.7 % use some version of Internet Explorer as their primary browser
    • Only 29.5 % test their sites in IE 8
    • Many more use XHTML than HTML
    • Over 10 % still use tables for layout
    • Almost 70 % still use presentational markup
    • Only 69 % create print stylesheets

    Not sure these figures are particularly useful, but interesting none the less :)

    Sprite Optimization

    Finally today, I
    would like to draw your attention to an interesting post by Dave Shea on ‘Sprite Optimisation‘.

    Let me briefly explain what CSS sprites are in case you are not aware. Let’s say you have a button with three states – unvisited, visited and hover. Instead of having one image for each state of button you can use a single image containing all three states. You then use CSS to position the image in such a way that it only shows the current state.

    In fact Dave Shea wrote an excellent article on ‘CSS sprites‘ back in 2004.

    Dave’s new post demonstrates that this technique is now being taken to the extreme with sites like Amazon, Google and Apple cramming large numbers of sprites into a single image.

    Amazon's use of Sprites

    Whether this is entirely necessary for the types of sites most of us are involved in is debatable. The technique also has some drawbacks on devices such as the iPhone, where performance can be effected.

    That said, it is a way of substantially reducing the number of calls to the server so causing pages to load faster.

    If you are suffering from performance problems or have a project that requires lightning download then check out Dave’s post and also a CSS sprite implementation guide he refers to.

    Back to top

    Feature: 5 options when website budgets get slashed

    Your site is in desperate need of a redesign, content is out of date and the technology is archaic. Unfortunately times are tight and your budget has been cut. What do you do? Read More

    Back to top

    Listeners feedback:

    I am very conscious that I have not been encouraging listener contributions and that is slack of me. This is a part of the show I really want to grow. As I have said before, Boagworld is about the community, not just my personal opinion.

    With that in mind you can contribute in three ways…

    • Email – I cannot always respond personally but I read everyone.
    • Phone – You can either Skype ‘boagworldshow’ or call 020 8133 5122 and leave a message.
    • Forum – I often take questions from the forum, so make sure you join that too and get involved.

    Talking of the forum, both of this week’s listener contributions come from there.

    Listener Review of DropBox

    From time to time we do listener reviews on the show and there is a section of the forum dedicated to reviews.

    This week I have selected a review from the forum by Dave Redfern. He reviews DropBox, which although not strictly a web design tool will be useful to all.

    Dropbox homepage

    Dave writes:

    I came across dropbox last month thanks to the good people over at the mac roundtable podcast. Because i work on several computers from windows and mac machines in the same house, windows machines at work and at uni i am paranoid about making sure my files follow me around.

    The basic concept of getdropbox.com is you install the software on each computer you have, then any files you wish to keep synced between them all you drop in this folder. If it is a public machine you can still access your files from their website although it is a little more clunky. You don’t need to set it to upload changes at a certain time or activate it, the software will automatically sync the folders whenever anything is changed.

    A nice feature is within the dropbox folder there is a public folder and anything put in here can be accessed by anyone via a website link. the get the link all you need to do is right click on the file and select ‘copy link address’ and then paste it where ever you need. it is great for sending things to friends or showing clients screenshots of mock ups.

    Preferences are very limited to limiting the bandwidth used at anyone time and changing the foler (although when i tried this feature i kept crashing my finder!) but simple is good sometimes.

    It is free to sign up and you get 2gb of webspace free. you can upgrade to 50gb for $10/month or $100 for the year which seems reasonable.

    the software is available for mac, windows and linux so perfect for anyone.

    I will give it 3.5/5 at the moment. there is still some work to do on the software but a great start and very promising.

    Personally I think 3.5/5 is a bit harsh but I know what he means. I love dropbox and have just paid for the 50gb account, but the web interface could do with some improvement. Also a native iPhone application would be nice.

    That said we use it loads at Headscape to share files privately. It is perfect for that and online backup (including versioning) and I would highly recommend it to everyone.

    Font Embedding on the Web

    There is an interesting thread on the forum about font embedding that I also wanted to mention. Started by Dven he writes:

    It’s a pretty popular subject but wanted to raise this to hear what your thoughts are on it all.

    Basically a designer in our office found this link: http://www.fontburner.com. Thought that it be a good idea to maybe use in the near future. Now personally, I’m against embedding non-standard web fonts in this way.

    The designer’s reaction. "its pretty much the way the design on web is going – limitations in type have always been a problem – not anymore. Its not the best solution, but pretty soon there will be a better one."

    Be good to hear your thoughts?

    After checking out Font Burner I discovered that it was a quick and easy way of adding sIFR to your site. We have talked about sIFR before on the show. It is a technique that uses flash to replace HTML text with your desired font.

    FontBurner homepage

    I was pretty impressed by FontBurner but as Laura said…

    It’s not the most semantic way to embed different fonts, as it requires <div class="font-name">text</div> if you want to change anything but <h1>.

    Later in the thread Dvan went on to say…

    These types of solutions are always prone to not working somewhere along the line. Guess I am kind of a very semantic guy and prefer to do things the ‘standard’ way.

    Personally I do not feel that strongly. I think techniques like these are sometimes necessary to overcome browser limitations. That said, I do share his concern about these things not always being very reliable.

    I actually rarely use sIFR. My preference is to make better use of font-stacks. These can be very powerful if used well. It is basically another variation on progressive enhancement. If the user has the nice font they get it, but if they don’t they get a substitute.

    The reason most designers resort to sIFR is because the client insists on a
    particular font. I would prefer to educate the client than resort to sIFR. By educating them over this issue you are laying the ground work for conversations about graded browser support and various other progressive enhancement issues.

    On the subject of web typography, let me leaving you with a smashing magazine post that has come out this week – 50 Useful Design Tools for Beautiful Web Typography.

    Back to top

    10 techniques for an effective ‘call to action’

    Posted in Design on January 22, 2009 by Paul Boag

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

    Jeff from Brighton recently wrote to me asking:

    Occasionally I hear you talk about the importance of having a call to action on the show but you never go into much depth. I recognise the importance of having a call to action but how do I encourage users to complete them?

    Having an effective call to action is an essential part of any website. A call to action is not just limited to ecommerce sites. Every website should have an objective it wants users to complete whether it is filling in a contact form, signup for a newsletter or volunteering their time.

    A call to action provides…

    • Focus to your site
    • A way to measure your sites success
    • Direction to your users

    How then do you create an effective call to action? Here are 10 techniques which help achieve just that.

    1. Lay the groundwork

    Before a user is willing to complete a call to action they have to recognise the need. Infomercials do this very well. Before they ask people to respond, they first identify a problem and present a product that solves that problem.

    You also need to communicate the benefits of responding. What will the user get out of completing the call to action?

    Take for example the VoIP service Skype. Immediately above their call to action (a download button) they have the following text:

    Make calls from your computer — free to other people on Skype and cheap to phones and mobiles around the world.

    They clearly explain what the user will get by downloading Skype.

    Skype homepage

    2. Offer a little extra

    Sometimes you may have to sweeten the deal to encourage users to complete a call to action.

    Incentives could include discounts, entry into a competition or a free gift. This is the approach Barack Obama used on his fund raising website. If you made a donation of $30 or more you got a free t-shirt.

    Obama fundraising website

    Of course the beauty of this offer was that not only did he pursued you to donate, he also turned you into an advertising billboard!

    3. Have a small number of distinct actions

    It is also important to be focused in your calls to action. Too many and the user becomes overwhelmed. Studies in supermarkets have shown that if the shopper is presented with too many varieties they are less likely to make a purchase.

    By limiting the number of choices a user has to make we reduce the amount of mental effort. Effectively you guide the user around the site step by step.

    The number of appropriate actions will vary from site to site. However, it is not so much the number of actions as the distinctiveness of each.

    Take for example pbwiki.com. They have three calls to action:

    • Create a wiki
    • View Demo
    • Buy now

    Although three is not an unacceptable number, there is not a clear distinction between ‘create a wiki’ and ‘buy now’. What should I do first – buy a wiki or create one? I am confused. A better approach would be to push the buy option later in the process once the user has committed to building a wiki.

    pbwiki homepage

    4. Use active urgent language

    A call to action should clearly tell users what you want them to do. They should include active words such as:

    • Call
    • Buy
    • Register
    • Subscribe
    • Donate

    All of these encourage users to take an action.

    To create a sense of urgency and a need to act now, these words can be used alongside phrases such as:

    • Offer expires March 31st
    • For a short time only
    • Order now and receive a free gift

    Carsonified use this approach when selling their workshops. To create a sense of urgency they offer discounts to those who signup early.

    Carsonified Workshop page

    5. Get the position right

    Another important factor is the position of your call to action on the page. Ideally it should be placed high on the page and in the central column.

    picsengine.com does this well placing their ‘see in action’ centrally on the page above the fold.

    Picsengine homepage

    6. Use white space

    It is not just the position of your call to action that matters. It is also the space around it. The more space around a call to action the more attention is drawn to it. Clutter up your call to action with surrounding content and it will be lost in the overall noise of the page.

    PlanHQ does an excellent job of focusing users of their calls to action by surrounding them with a lot of empty space.

    PlanHQ homepage

    7. Use an alternative colour

    Colour is an effective way of drawing attention to elements, especially if the rest of the site has a fairly limited palette.

    Things (the GTD application for the mac) does this expertly on their website. While the rest of their site is predominately muted blues and grey, their calls to action are highlighted orange. This extreme contrast leaves you in no doubt as to the next thing you should do.

    Things homepage

    Of course never rely solely on colour because many users are colour blind and will not see the contrast.

    8. Make it big

    As web designers we often get annoyed with clients who ask us to make things bigger. It is certainly true that size isn’t everything. We have already established that position, colour and white space are equally important.

    However it cannot be denied that size does play a large part. The bigger your call to action, the more chance it will be noticed.

    Mozilla have certainly taken this approach to heart on the firefox homepage where their download link dominates the page.

    Firefox Homepage

    9. Have a call to action on every page

    A call to action should not just be limited to the homepage. Every page of your site should have some form of call to action that leads the user on. If the user reaches a dead-end they will leave without responding to your call.

    Your call to action does not need to be the same for each page. Instead you can use smaller actions that lead the user towards your ultimate goal.

    37 Signals understand the importance of having a call to action on each page. At the foot of every page of their Basecamp website they clearly display links to their tour and signup pages.

    Basecamp

    10. Carry the call through

    Finally, consider what happens when a user does respond to your call to action. The rest of the process needs to be as carefully thought through as the call to action itself.

    One particular word of warning – if you require users to provide personal data about themselves, resist the temptation to collect unnecessary information.

    Marketing people in particular like to build up demographic information. Although I can appreciate the value of this, it brings a danger users will drop out of the process.

    WordPress.com is an excellent example of how to minimise the amount of data collected. They only ask for the minimal information required to setup a blog.

    WordPress signup process

    Conclusions

    An effective call to action is the linchpin of a successful site and involves drawing together best practice in usability, creative visual design and powerful copy writing.

    However, if it is done right it can generate real measurable return on investment and in the current economic climate that is what we all want.

    Many thanks to Lee Munroe who found most of the examples I have used in this post.

    148. Recession Cheer

    Posted in Classic shows on January 13, 2009 by Paul Boag

    On this weeks show: Surviving the recession with Andy Budd, providing effective browser support and free boagworld consultancy.

    Download this show.

    Launch our podcast player

    Housekeeping

    Unfortunately we have a bit of housekeeping to get out of the way before we begin:

    • Boagworld Christmas Appeal – I really want to thank everybody who gave so generously to this year’s Christmas Appeal. You guys have raised over £2000 for Sarah and Simon’s work in India and they are both over the moon. This money will allow them to provide better facilities for the growing number of children they work with, and doubles the amount raised last year.
    • Transcribers – After such an amazing effort for the Christmas appeal I feel bad asking you for more. However, we really need people to help transcribe the podcast interviews. We believe it is important to make our show as accessible as possible and we need your help to do that. If you feel you could help or have questions about what is involved email Ryan Taylor at [email protected].
    • .net Magazine offer – Fortunately my next piece of housekeeping allows me to give something back to you guys. I know you love the offers and competitions we run from time to time and this is a particularly good one. .net magazine have been kind enough to offer boagworld listeners some massive discounts on their annual subscription. In case you haven’t heard of .net magazine it is the UKs premier web design magazine and has some truly phenomenal content each month. If you are based in the UK, you can now get the magazine for 50% off. That is only £9.75 every 3 months. In the USA the discount is even bigger at 54%. That means an entire years subscription is only £64.99. In the EU you pay £55 for a year and the rest of the world pays £67. Those are excellent prices for a really good magazine. To take advantage of these offers visit the special boagworld offer page.
    • Free consultancy – My final piece of housekeeping is a little competition we would like to run. We are always giving away other people’s stuff but never give away anything ourselves. To rectify this problem we are giving away a day of our time to a lucky winner. Myself and Marcus will provide a free days consultancy where we will dispense advice on ways you can take your website forward. If you are interested in entering, email myself by the end of January. Include your name, company (if you have one), URL and why you want our help. We will pick the most deserving case and contact them at the end of the month.

    News and events

    Obviously a lot has happened in the world of web design while we have been on our Christmas break. To make matters worse, I must confess to not following the news while we were away. I have therefore gone for the first four stories that caught my eye. Apologies for the lack of professionalism!

    A roundup of 24 ways

    Way back in show 146 I mentioned the return of the 24 Ways website. As I explained on that show 24 ways is an advent calendar for web geeks. Each day throughout December they publish a daily dose of web design and development goodness to bring a little Christmas cheer.

    As I said before 24 Ways is without a doubt one of my favourite web design sites. However, it does have one fatal flaw – it releases one article every day throughout December and I just can’t keep up. December is always mad with clients wanting stuff wrapped up before Christmas and people taking holiday felt right and center. I simply do not have time to read everything they publish.

    Fortunately their archive of articles are still all waiting for me on my return and make perfect reading as I struggle to return to work.

    This year has a truly bumper crop that I cannot wait to get into. The top titles that have grabbed my attention are:

    • Sitewide Search On A Shoe String by Christian Heilmann
    • The IE6 Equation by Jeremy Keith (Deciding when to support IE using Algebra!)
    • The First Tool You Reach For by Kevin Yank (A look at CSS tables)
    • Making Modular Layout Systems by Jason Santa Maria (Gaining greater flexibility in laying out content)
    • Shiny Happy Buttons by John Allsopp (Styling HTML buttons without resorting to images)
    • Recession Tips For Web Designers by Jeffrey Zeldman
    • Contract Killer by Andy Clarke (Writing the perfect contract)

    Most of these I have yet to read but they promise to keep me entertained and informed until next year.

    WCAG 2.0. is official

    Probably the most significant story while we have been away is the release of WCAG 2.0. WCAG 2 has taken an age to be released but has also come a long way from its controversial beginnings. When I read some of the initial drafts it was horribly complex and anything but accessible. However the final release is extremely well thought through and communicates complex concepts and ideas in an easy to understand manor.

    I think what impresses me most about WCAG 2 is the way the guidelines are conveyed. It has four layers of guidance which include:

    • Principles – These are broad principles of accessibility which need to be understood by everybody. If you had to explain web accessibility to senior management you would probably talk in terms of these top level principles. They include the need for a website to be perceivable, operable, understandable, and robust.
    • Guidelines – There are a total of 12 guidelines organised into the 4 overarching principles. These are ideal for website owners or project managers that need to understand more detail on how to achieve the broader principles but do not need to understand the technical detail.
    • Success Criteria – For each guideline, testable success criteria are provided that allow designers and developers to know specifically how to conform to a guideline. These are the equivalent of the WCAG 1 guidelines and are still organised into Priority 1, 2 and 3.
    • Techniques – Finally, designers and developers can also access techniques that may help them to fulfil the success criteria but are not in themselves mandatory.

    It is a very logical approach and makes it easy for anybody to understand how to make their site accessible. With these guidelines now official it is important that you begin to learn about these guidelines now, even if you just start with the 4 broad principles.

    Issuu Smart Look

    From WCAG 2 to something that encourages website owners to ignore accessibility! I often find myself torn over whether to share something on this show or not. Part of me wants to teach and encourage best practice, but another part is more pragmatic and accepts that sometimes we have to compromise. The next item is an example of the latter.

    Website owners love to post PDF, Word files, and Powerpoint presentations on their site. It is quick, easy and gets their content online with minimal fuss. However, it creates accessibility problems requiring users to have appropriate software or plug-ins. It also makes it hard for search engines to index their content and increases demands on bandwidth.

    If you are a website owner and you do this – stop it!

    That said, if you have no choice or you are a web designer being forced at gunpoint by your client, then there maybe some hope.

    Document publishing site Issuu has released a promising Javascript tool called Smart Look that allows users to view PDFs, Word files and Powerpoint presentations in much the same way you would view an image using one of those Javascript overly script.

    The best thing about the service is that it involves very few changes to your site. All you have to do is copy and paste some Javascript into each page. Your downloads will then be miraculously presented in the new format.

    A List Apart discusses content

    Finally, I wanted to mention two articles posted on A List Apart over the Christmas break. Both article tackle the subject of Content Strategy. Without a doubt content is the most ignored aspect of our websites and yet is also the most important. It is great to see the profile of content increasing and seeing sites like A List Apart promoting it.

    However, I do have doubts about the way content specialists are promoting their work. This particularly shines through in the two recent List Apart articles. First, there is an obvious sense of frustration that people do not value their profession. This is entirely understandable. However, sometimes it comes across as them ‘justifying their own existence’ rather than emphasising the value of content. Second, and probably more significantly, they seem to be fracturing their profession into more and more specialist areas. Where once there was a content editor there are now content strategists, copywriters, editorial specialists, content analysts and more.

    Although this specialisation is not out of line with the way the entire web design sector is moving (after all once upon a time a ‘web designer’ built your entire site) I don’t believe the majority of clients are ready for this complexity.

    Everything I read in these two posts was excellent, but both struck me as expensive and complex. I still struggle to convince clients of the value of investing in content and I don’t feel these articles do anything to aid that cause. Of course, that wasn’t really their aim. However, what I need is a simple and coherent argument for investing in people to write good copy before we start breaking the skillset down even further.

    That said, these are great articles and certainly worth reading, if for no other reason than to understand the importance and complexity of our content.

    Back to top

    Feature: Effective Browser Support

    Browser support should focus on usability and accessibility rather than pixel perfect design. Sites should render in all browsers, but provide advanced features and aesthetics to those which can support it. Read More

    Back to top

    Interview: Andy Budd on how to recession proof your business

    Paul: So here we are a new year and our first interview of the year and who else would we get on the show except Andy Budd? Hello Andy.

    Andy: Hi Paul. How are you doing?

    Paul: I’m doing very well. It’s been so long since we’ve had you on the show. Probably for good reason.

    Andy: Are you running out of guests or something?

    Paul: Yeah, we’re just having to repeat now, endlessly. There’s only three people that can string a sentence together, that’s the problem, of which I am not one of them.

    Andy: Aww, you do yourself a disservice.

    Paul: So we thought we’d pick a nice cheery subject. Me and Andy had a little chat earlier about what subject we would talk about today and we thought, "New year, new opportunities, exciting times, let’s talk about the recession and the economic downturn." So here we are. Everybody’s been going on so much at the moment that it’s all doom and gloom and I have to say, I don’t know about you, but you know I’m seeing with regularity on twitter people saying, "I’ve just been made redundant," and it’s a bit of a scary time, isn’t it really?

    Andy: Um yeah I think it is. I think a lot of people at really good companies, really good people at Yahoo! and whatever have been made redundant in the last few weeks. Last.fm have been having redundancies as well and it’s like, "Oh wow, really smart people are being made redundant," so it is a bit of a worry for everybody I think.

    Paul: The trouble is, everybody’s a bit cagey, aren’t they about their own situation and what’s going on so I thought, "Let’s talk a little bit, try and clear up some of the mystery around it," and I thought, "Let’s start by talking a little bit about our own experiences," you run a small agency, I run a small agency. I mean from our personal point of view at Headscape we have seen a little bit of a downturn. Not dramatic. You know I keep kind of waiting for the other shoe to drop and everything to dry up but certainly we’ve seen maybe a slight reduction in the value, the budget that people have and they seem to be taking longer to make a decision and thinking more carefully about what they’re doing. Is that similar to what you’re experiencing with Clearleft or is everything lovely with you guys?

    Andy: No, I think that’s probably very similar here. I mean I know sort of before Christmas we really hadn’t experienced much of an effect at all, in fact kind of October, November, December, particularly October – November, was the busiest time we’ve ever had as a company. We were kind of really really rushed off our feet, but things have slowed down now. I guess the difficult question though is, "What have they slowed down?" I think in part it’s because of the recession, but partly it’s because people have been on holiday over Christmas and stuff so I think the real what we just need to see is what’s gonna happen over the next few months. Christmas is one big milestone because obviously a lot of companies their financial years end on the calendar year and they will start to get new budgets at the start of the new year. So what normally happens is January is usually quite quiet anyway and it starts to pick up toward the end of January when people have now got their budgets and they’re setting their schedules and their priorities for the coming year. Another kind of key point is March. You know March – April when a lot of other companies’ financial years kick in. So I think we need to kind of give it a couple of months, give it until March and then we’ll have a much better idea about the effect it’s had on clients’ budgets. But yeah, I would agree. I think people are just more cautious. I think all of this discussion about doom and gloom, frankly a lot of the reason why we are in the situation we are at the moment is because of media. The more people worry about this stuff, the more cautious people are going to be and it becomes a bit of a cyclic effect. But yeah, I’d say the same. I’d say clients are being a bit more cautious. We haven’t had too many issues with companies. We had one Icelandic bank that pulled out of a project in November which was quite amusing. They contacted us like a week before Iceland, kind of, you know, blew up. And we were like, "Yeah, we could have seen that coming," but apart from that it’s OK. Slackened off but it’s seeming to be OK at the moment.

    Paul: So what about you? You’re talk about clients being cautious. What about you at Clearleft? Are you guys being a bit more cautious in what you’re doing? You know, your outgoings and that kind of thing?

    Andy: I think we’ve always been reasonably cautious and I think that hopefully will set us in good stead for the next six to nine months. One of the things that we were really really conscious is running a good stable business and we’ve seen a lot of scare stories from the last .com boom with companies growing really really rapidly. They’d basically expand as much and as fast as they possibly could to fulfill the demand. That’s really great in the good times when people are throwing money and projects at you, but as soon as the projects dry up you’ve suddenly got a lot of mouths to feed, and I don’t think that’s necessarily true of Yahoo! but I think it’s probably true of some of the startups like Last.fm. You know, Last.fm have grown hugely over the course of the ten or twelve or eighteen months, and then all of a sudden when people start reigning in their budgets there’s not the work out there and they have to make people redundant. I think we’ve always tried to grow at a steady rate, you know we’ve been through boom times where we’ve been literally turning work down and we could have hired another couple of developers, couple of designers easily, but we chose not to because we didn’t want to get into that situation of the work drying up and not having any business. So yeah, we’ve been fairly careful how we’ve grown.

    Paul: Do you think there’s, I mean, the kind of other side of the coin is to take the approach that perhaps Carsonified have done where they’ve actually been proactive in cutting their overheads by admittedly laying off staff in preparation for what is to come. I mean, you know I don’t kind of want to get personal about the guys at Carsonified but that’s certainly an approach that someone like Jason Calacanis would recommend. That actually before things get too bad you should shrink your business so that you’ve got you know, "a long runway," as he puts it, of money behind you over the long period. Is that and approach that you would consider? Well obviously you’re not going turn around and say, "We’re going to lay off all our staff now," but do you know what I mean?

    Andy: Yeah, absolutely understand the question. The answer to that is, "Absolutely not," but it’s actually a two-part question. Um, you should, if you’re running your business well, you should ideally have a certain amount of money in the bank to cover operating costs. Now again, one of the things we were very clear of when we set up Clearleft is we would always have, would always aim to have six months of operating money in the bank. Now it’s not always like that. Sometimes it’s four months, sometimes it’s five or six. But that’s kind of what we try and aim to do. So before taking any money out of the company, before buying a nice car or giving ourselves a bonus we try and make sure that there’s enough money in the company that should we lose a couple of clients or should anything bad happen we can carry on paying people’s wages. I think in this industry, in the web design industry it’s all about people. We can’t build good products, you can’t build good services without having good people. So it’s the people that make the companies, it’s the people that make the industries, and I think as the boss, I think as an employee you have to put the good of your company and the good of your staff ahead of your own personal gain. So I think there are two ways of running a company. I think some people run a company almost like a general that commands their troops from the back of the battle front where they send all these people out ahead of them and they get picked off one by one until eventually you’re the only person left. I actually think as somebody running a company you have to take charge yourself and I would much prefer to lose, I would definitely cut my lifestyle and cut my wages before I would let anybody go in the company because you start slashing staff now and then when times are good you have a hiring problem or you get known as a company that will just sacrifice their staff. And I’m not speaking about any particular companies specifically but I think it’s important to realize that the wealth of your company is in the people that work for you. So yeah, I would always consider that as a last option, not a first option. Might not be good accounting sense. I’m sure if you’re just looking at sort of the figures, it might not be good from an accounting sense but people come and work with you and they stick with you through the good times and the bad and I think you’ve got to afford them every opportunity so that’s kind of my philosophy.

    Paul: I think to some degree it could be good from an accounting sense as well. I mean it’s very easy to underestimate the cost of rehiring staff. By the time you take into account finding the people in the first place, that often involves going to the dreaded recruitment agency and the horrible costs and pain of that, you know if you don’t have a big network of people you can draw on. But also the cost in time of interviewing and all of that kind of stuff can really mount up so I guess to some degree it depends on how long this goes on, if it goes on at all. I mean we’re still waiting for something to happen. I can understand the whole philosophy about having a runway if you’re a startup company without regular revenue that’s dependant on venture capital or whatever but if your business is like an agency or if you’re a freelancer or something like that then hopefully you’re going to continue to have revenue coming in from work.

    Andy: Well I think if you’re running your business responsibly you need to make sure that there’s always a runway. There’s some proverb or fable about making hay while the sun shines or whatever. You need to try to put a bit of a war chest, for want of a better word, in the bank or you’re getting good money because you know times, you know winter is coming and you need to kind of buckle down, but some people just go and as soon as they’ve got money they go and spend it on nice cars, nice apartment, holidays or whatever and as soon as things start to get tough then you’re in difficulty. But yet like I said I think you should always have a bit of money in the bank. You shouldn’t expand too quickly and I think if you end up hiring a large number of staff and then letting them go sort of shortly afterward it’s probably an indication of you probably shouldn’t have hired that many people so quickly in the first instance so it’s difficult. I don’t think there’s any right or wrong way of doing this. Everyone’s got their own approach.

    Paul: I mean of course a lot of the people listening to this show aren’t going to be running their own businesses anyway so that kind of comes on to another question about if you’re working somewhere at the moment what should you do? Are you better off just tucking your head down and hoping that things go well in the company you’re working for or should you look at maybe now is the time to start your own business. I mean there was an interesting article by Drew, isn’t there, about you know the myth of stability and that actually you’re almost more stable being in control of your own destiny as a freelancer cause at least you know what’s happening with your business in preference to being employed. So, what advice would you give for people perhaps worried about their job at the moment?

    Andy: That’s a difficult thing. There’s always been this myth that if you go and work for a big company there’s stability but I think recent events have shown that’s not true. If you’re running your own company you obviously have a much better understanding of what’s going on and you’re much more able to control the near future. Obviously you can’t plan too far ahead because most web design companies only book up projects three to six months in advance. So you can only really plan financially up to a certain stage but I think it’s good running your own company to a certain extent because you have a bit of a master in your own domain. You know what’s going on. On the other hand there is a certain level of security of working with a company, at least in the UK, a large company particularly because if you do get made redundant you get a redundancy package. If you’re a good productive member of the community or productive member of the company there’s a good chance they’ll try to rehire you in a different role. So I don’t think there’s any certainties there.

    Paul: Do you think it would be a ridiculously stupid time to go freelance?

    Andy: I think it’s a difficult time to go freelance. I think the problem at the moment is that there’s a lot of people freelancing in the industry and there’s a lot of people who are just not very good. I hate to say that but I think there’s a lot of people who are getting by at the moment on a subsistent wage who are a bit too much of a jack of all trades and a master of none and are kind of operating in a slightly more bottom end of the market. So I think that one of the first things that’s going to happen with the economic shift is the bottom end of the market is going to get even tighter and you’re going to be finding it really difficult if you do a little bit of PHP and a little bit of HTML, a little bit of design, a little bit of this, and a little bit of CMS stuff. It’s going to be a lot more competitive. However, if you’re really good at one thing, if you’re a really awesome designer, if you’re a really awesome coder, if you’re a really great Rails developer, if you’re a great User Experience person, if you’ve got a real skill that you’re well known for there is always going to be a market for good people. There’ll be more people on the market. There’s people being made redundant from Yahoo! and other companies who are really really good at what they do so it’s gonna get more competitive so I wouldn’t necessarily say that it’s a good opportunity for people to necessarily go freelance unless they’re really really talented and have a good existing stream of revenue and they know a lot of people but I think there’s opportunities in other areas in terms of setting up your own projects and doing startup and doing work outside the office. I think there’s interesting opportunities there.

    Paul: So if there are people listening to this show that are going, "Crap! He’s just described me. I’m a freelancer that works on that kind of bottom end of the market." What should these guys be doing? How can they go about improving their position?

    Andy: I think again while the industry was going at a rate of not to new, last year there was so much demand for people, companies, clients would hire anybody no matter what your skills were. I think now we’re in a situation where to really stand out you’ve got to be good at what you do. You’ve got to be highly skilled, and I think people need to see training as an investment. I think we’re really bad as an industry of investing in ourselves of investing in our own personal development. We’re all very happy to go spend £500 on an iPhone or £1000 on a new Mac but spending 500 quid on a training course, people go, "Well that’s just a waste of money," but I don’t think it is. I think you need to invest in your personal development and your professional development so I would say figure out what it is you’re really good at, figure out what it is you enjoy and then see if there are training courses go on or conferences you can attend that can help teach you those skills.

    Paul: You missed a perfect opportunity there to pimp UX London, didn’t you there?

    Andy: I guess so, yeah.

    Paul: You’re just too nice. Tell us a bit about UX London, Andy.

    Andy: A lot of what we do again, you know me and you know what the company’s like. A lot of what we do isn’t necessarily about our gain as individuals just purely from a financial point of view. We run conferences like dConstruct because we want everybody in industry to benefit. We want people to get better at what they do, to produce better websites and I think by doing that everyone benefits. And again UX London the whole purpose of UX London, it’s a conference we’re organizing in London in June it’s a very targeted conference. It’s much smaller numbers than dConstruct. It’s 160 people and it’s a real education-based event, to teach people how to be really good User Experience designers, User Experience developers, information architects and usability people. So we’ve got some of the best speakers in the industry coming over. We’ve got Don Norman who’s like the Godfather of User Experience, we’ve got Dan Saffer, we’ve got Peter Merholz, Jared Spool, Jeff Veen, we’ve really had an opportunity here to play fantasy league conference and put together the kind of event that we wish that we could have gone to five years ago. Particularly User Experience is a growing field and I think within the recession or within the looming economic crisis, companies are going to be spending less and less or are going to be able to spend less and less on acquiring new customers and where they’re going to need to spend their money is satisfying existing customers and making sure that the customers that they’ve got don’t go to other brands, other companies and are much better at converting and User Experience is one of the ways we can do this. So I definitely think if you’re interested in getting into the User Experience realm going to something like UX London would be a great opportunity. It’s essentially three days of workshops and practical hands-on stuff. I mean it’s not just a standard talking head kind of conference it really is getting in there and learning new skills. Not just UX London, there’s all kinds of conferences and events out there, there’s all kinds of training courses. There’s development training courses, there’s usability training courses, there’s designing courses, but pick something you’re really passionate about and get really really good at it and if you get really good at it people will find you. There is still a massive demand for Rails developers, there is still a massive demand for good visual designers and there’s still a massive demand for really good UX people and I think those three practices are going to get more and more important so yeah that’s what I’d say.

    Paul: You said something there about if you get really good at something people will find you. Do you think that that’s actually going to remain true or are we going to have become more active at going out there and finding work? I mean to some extent people like you and me are we not a little bit spoiled because we’ve already built up this reputation, people are aware of us, because in my case because of the podcast, because of your book and the various things that you do. Is that all that you do to win business? Write a book or put on a podcast? There’s got to be more to it than that.

    Andy: It doesn’t hurt, I can kind of say that but that’s the situation we’re in now obviously but the reason that we were able to do this, the reason that I was able to write a book and you were able to do the podcast was because five, six, seven years ago we just sat around writing blog posts about what we were passionate about, what we were interested in and the Internet has an amazing capacity for putting like-minded people in touch, whether it’s through your blog, whether it’s through your twitter stream, whether it’s through meeting people at conferences. I mean again, going to a conference is a great opportunity to network and meet people and I think there’s a community in the Web and you need to be a part of it. If you’re not part of it, if you’re just sitting on the fringes then you’re going find it a lot more difficult to pick up work, but if you throw yourself into this community and actively participate it’s not that difficult, if you’ve got a skill, if you’ve got a talent it’s not that difficult to make people aware of it. You do have to do a bit of promotion though, you do have to write some articles or contact a magazine and say, "Hey do you mind if I write something for your magazine?" Or go around to some of your favorite bloggers and leave messages on their blogs and write to them and say, "Hey look, I’m doing this, that and the other." I’m probably going to get inundated with responses now but we’re always on the lookout for really good people. Despite the number of people working in the industry we find it really difficult finding good visual designers we find it really difficult finding good Information Architects and we find it really difficult getting good front end coders. We see a lot of average people. There’s a scary number of really bad people out there, but finding good people is difficult and we’re not just falling over people in the street. I’m spending a lot of my time actively asking around and asking friends and contacts and doing searches on Google for people so if you make yourself available and you go out of your way to put yourself in that situation it can only be of benefit. I was talking to you before we started the podcast about something we’re doing at Clearleft is that we run an internship program and part of the purpose of this internship program is to get people that haven’t had that commercial experience, that maybe have just left University after doing a graduate degree or maybe are in the middle of a Master’s Degree or maybe are just transitioning to a different career area and maybe they were starting off doing more design and they want to get more codey or they were a coder and they want to do more information architecture and actually having the opportunity to go and work for a company for ten weeks is an amazing training opportunity, sorry if I sound like I’m promoting myself a bit too much but we had a really great guy come in over the Summer a guy called Amild who was from Sweden and he was part way through a University course and in the Summer he came over and he worked for us for ten weeks and he got to work on real-life projects he got to sit down and program with Natalie and argue semantics with Jeremy and be involved in every single part of the process and doing that, you get so much knowledge and training out of going and working hands on like ourselves or yourselves, much more so than you’d probably get doing little side projects over the course of a couple of years I mean I know we’ve had a couple of interns now and the amount of stuff that they know when they leave working with us is two or three times the amount they knew when they came in and actually ironically people come to Clearleft quite often a little bit cocky because they’ve heard about us and they know we’re good at CSS and Web Standards and they come in thinking, "Yeah, I do this," but when they sit down with someone like Natalie and she explains all this stuff their eyes and their universe ends up opening and it’s like, "Oh my God I didn’t know this stuff existed. I didn’t know people would go to so much effort to craft a nice, well designed, well put together website." So yeah we’re running an internship for Spring so if anyone listening out there wants to come work down in Brighton in the Clearleft offices for ten weeks and is really interested in good front end code and HTML and CSS then please go to clearleft.com/jobs and there’s some details of the internship there. We’ll be running it again during the Summer maybe May, June July time. At the moment we’re looking for a front end developer to be an intern. The last intern, the last before one intern we had was more of a User Experience person, we might be looking for design intern next we might be looking for a bit more of a generalist so I can’t really tell you what we’ll be looking for in the Summer, but at the moment yeah we’re looking for a front end developer to come and help us out.

    Paul: I think as well, if I was in that position to have the guts to just approach random companies and I get people contact me regularly asking whether we do internships which we occasionally do and a lot of time I’m having to say no to people, I don’t mind them writing. Having the guts to approach a company to say, "I really like what you do, I’d love to work with you." I think that’s great. You’ve just got to go for it and put yourself out there whenever possible.

    Andy: Absolutely. If you’re trying to get work, send your CVs around, drop people emails saying "Hey, I’m a freelancer. I’m doing this. I’m doing that, " and stay in touch. It’s really difficult for you as a business owner to keep in your head of who’s available, you don’t have a clue who’s available when and the people we end up working with, the freelancers we end up working with, you work with them once and you probably never let them go again because they’re usually really good. They’re usually awesome and once they start working with us, we stick by people. So it’s worth once you send your CV to someone, drop them a line every couple of months, every time you’ve updated a website or you’ve done something you think is particularly interesting and just keep on the radar and the more you keep doing that, the more you promote yourself the better it will be.

    Paul: Of course that works very well if you’re a freelancer, this whole thing of getting involved in the community and building relationships and all of that. It’s great if you’re a freelancer where you’re working for someone like Clearleft or Headscape in that kind of relationship but what about people that are working directly for clients who aren’t part of the Web Design Community? They stand outside of that, have you got any advice for engaging with them, how to find out about what jobs are out there, how to get on those tendering lists and that kind of stuff?

    Andy: Well you don’t need to be getting on tendering list I’d say because most organizations that have tendering lists have got a lot of hoops that you need to jump though, it’s very time consuming, there’s usually financial constraints about how big you are as a company, how many staff you’ve got, all that kind of malarkey which I’m sure you’re very familiar with. I think it’s really difficult as a freelancer. I think there’s a glass ceiling in the kind of scale and size of work you do. I think it’s tough. I think you end up doing smaller projects but lots of them, usually for not a huge amount of value and so it’s really difficult when somebody big comes along and says, "Show me the last big project you did," and it’s, "We haven’t really done any because I’m a freelancer and I’m working directly with clients," so the way you can get experience and exposure of working with larger clients is to go and be a freelancer with agencies and actually if you’re a freelancer it makes much more sense to try and approach two or three decent agencies that continuously pass you work than it is to constantly try and get small £1000, £2000 projects. Then also if you’re doing that you’ve got a lot of marketing to do, all of the accounting, the bill chasing, it’s a lot harder and like you say I think it’s gonna get a lot tougher at that end of the market so yeah I think being a freelancer you’re probably best off targeting agencies if you want a more stable income.

    Paul: Here’s a tough question and I certainly don’t know the answer to this so I forgive you if you don’t either I mean we’re seeing people being made redundant at the moment, we’re also seeing people that have gone through years of University training going, "I’m gonna become a Web Designer," and they’re stepping out into probably the worst economic situation since the .com bust for web design. What are these guys supposed to do? How are they going to go about finding a job? Does this just come back to the networking issue again?

    Andy: I think we’re in a really interesting position. We’re in a really tricky position for a lot of recent graduates. When me and you started doing websites, or when I started doing websites the designs I was producing were rubbish. It really was terrible. The markup was terrible, the design was terrible, but luckily every other website out there was also equally bad so we weren’t worse or better than anyone else we were just meh. As we’ve matured and as the web’s matured we’ve got better at what we do, we got better at the stuff we produce. I went to a local agency in Brighton that kind of supports the local digital markets had a portfolio clinic last year where they had people fresh out of University and the quality of the designs they were producing was about the same level of the quality of design I was producing when I came into the market, but the problem is the bar has now been set so much higher so it’s really really tough. If you go into a three year degree where you spend one semester learning Dreamweaver, one semester learning Flash, coming out built a really lovely Flash animation of a monkey riding a bike and thinking, "OK, I’m gonna get loads of work with my great Flash animation skills," you’re gonna be coming into quite a harsh marketplace. What you need to do is you need to train yourself. You need to up skill. You need to do as much work as possible. You need to get your skills up. You need to get your design up. You need to specialize and to be really good at one thing. Be really good at design. Be really good at HTML and then you’ve got a chance of getting a foot in the door. Internships are good, training are good, but you need to have innate skill and actually in a kind of a weird perverse way I think the shake out is possibly good for the industry because like the last industry shake out is a lot of people who probably shouldn’t have been working in this industry, who didn’t have the passion ended up losing their jobs and going on and working in another industry, but people that stuck with it are the people who are good at it and passionate about it, stayed with it and survived through it and so I don’t think it’s necessarily a bad thing. I think there’s a problem with education that is trying to convince kids that they can go through a three year Bachelor’s Degree and come out and get a job. I think the industries that are going to be hardest hit in this recession are obviously financial industries are kind of stuck, or kind of enterprise level applications that any people working at enterprise apps are going to find it tough. I think people that are working in particular vertical markets, if you’re just a company that just solely focuses on doing startup business, the startup funding is drying up. It’s not gone completely and there’s a big argument to say that actually in times of economic recession that’s the time you want to invest in innovation, you want to invest in startups because once you come out of that recession you’ve got a product that’s ready to go that has been developed for a lot less money because resources are much more prevalent. You can hire developers much cheaper now and if you can start building your ideas up now very very cheaply, come two years time you’ll be two years ahead of the competition and if you’ve got a really really good idea you’ll come out of the market ahead. But I think at the moment if you’re only focusing on developing sites as startups you’re going to have a problem, you need to have a diversified portfolio of clients. I think the other thing is if you’re focusing on getting the majority of your income from just one or two big companies and that is quite common particularly in the entertainment industry. I mean are these Flash games developers or Flash entertainment sites developers that will just work with one or two large media brands. If suddenly they start pulling back on their funding you lose one client that is worth thirty percent or forty percent of your revenue you’re gonna be stuck so I think as a freelancer coming out of the industry it would make sense to focus on where there is growth in the market where the market’s stable. I don’t think it’s in producing Flash games necessarily and I don’t think it is producing multi million dollar blue chip corporate websites I think it is in creating websites that show real return on investment and that is in usability and accessibility, that’s web standards that’s understanding the psychology of human behavior. It’s all those kind of things we’ve been talking about for the last couple of years are becoming even more important.

    Paul: You said an interesting thing point though. You talked about innovation and I think that’s quite a good place to end though all of this situation is going to effect innovation and kind of the evolution of the Web, do you think these kinds of slow downs will affect the growth of the Web?

    Andy: It’s obviously going to affect the growth of the web because by the very name of recession it means growth of the economy isn’t growing it’s receding so I don’t think it’s going to be a time of growing much I think companies, large companies particularly are going to be taking stock and focusing on what they do well, their core assets. However I think what happens is it provides space for smaller companies to grow so you’ve now got these big companies competing for the same market as you so you can come up with new innovative ideas. You can come into the market much quicker. You can do it much cheaper. You are much more able to spot gaps in the market or gaps in the experience curve you know you’ve got a lot of companies doing this. You’ve got people like TripIt who have seen that there’s a gap between buying tickets and managing your calendar so identifying a gap in the market, "Because the airlines aren’t helping manage your trip, we’ll help you manage it for you," I mean dot was doing exactly the same thing so I think if you’re smart, if you’re clever and good at what you can do and you can see opportunities, there will always be opportunities, big companies going out of business, people cutting back on their R&D, people cutting back on their spending gives you an opportunity because it means less competition in the marketplace, there’s more available talent, there’s more available attention which is a big thing. You can grab people’s attention doing something different. There’s opportunities for making people money, in times of recession people are going to want to save money so if you can come up with an app that helps people save money, helps them, obvious examples are big slew of apps at the moment revolving around either managing your finances or getting better deals on car insurance all this kind of stuff, anything that can actually make people better off or more efficient. Productivity apps I think are gonna thrive.

    Paul: Thank you Andy! That was both good and depressing at the same time!

    Andy: Oh thank you. I’m glad talking to me you find depressing. Cheers!

    Paul: Actually it isn’t depressing. I’m very upbeat about the coming year. I feel that, "OK, we are in an economic slowdown but it does provide lots of opportunities." Even being made redundant has its upside. As somebody that was made redundant and then went in to set up Headscape I really know and understand that these things can be turned to good so I think yeah, I’m positive about the coming year although hopefully I won’t be made redundant from my own company because that would be embarrassing. So there we go. Thank you very much Andy! We’ll get you back on the show soon and Happy New Year!

    Andy: Happy New Year to you too and to all the Boagworld listeners out there!

    Thanks goes to Todd Dietrich for transcribing this interview.

    Back to top

    137. Adobe

    Posted in Classic shows on October 1, 2008 by Paul Boag

    In this week’s show, Aral Balkan joins us to discuss the release of Adobe CS4 and we discuss how not to get blacklisted by google.

    Download this show.

    Launch our podcast player

    News and events

    Adobe CS4 is released

    The biggest news of the week is the release of Adobe’s CS4 suite of products. This includes new versions of Photoshop, Flash, Illustrator, Dreamweaver, Fireworks, the list goes on.

    This leaves every web designer asking the question, is it worth forking out over one thousand dollars for the latest set of enhancements? As always it depends on how you use the products.

    The most significant changes are in workflow and interface. Adobe have been adding features to their applications for years and some of the interfaces have become unwieldy. This release addresses a lot of these issues. They have brought buried features out of the menu and into palettes and toolbars.

    Also, if you tend to work entirely in the Adobe universe, you will be interested in the workflow improvements. It is now easier than ever to move work between applications and manage your entire workflow throughout your site development process.

    However, workflow and interface improvements are probably not going to make you upgrade. After all how excited can you get about that kind of stuff?

    What may tip the balance are the new 3D features. For example in Flash you have substantially improved animation tools for 3D objects and in Photoshop it is now possible to import 3D objects into a 2D image and manipulate them. I can see many web designers moving from buy stock photography to entire 3D models because it provides substantially more control.

    However, if you are still debating about whether to upgrade to the latest version of Photoshop, go and check out a feature called ‘content aware scaling‘. It will blow your mind.

    For more on the new features in Adobe CS4 listen to our interview with Aral later in the show. Also check out Adobe TV for video demonstrations of all the new features across the entire range.

    Fire Vox

    Next up is a Firefox extension that allows you to transform Firefox into a screen reader.

    We all know accessibility is important. We all know we should develop with screen readers in mind. However, many of us fail to test in screen readers because they are expensive and time consuming.

    Well, now you have no excuse. Fire Vox is an open source, freely available talking browser extension for the Firefox web browser. Think of it as a screen reader that is designed especially for Firefox.

    In addition to the basic features that are expected of screen readers, such as being able to identify headings, links, images, etc. and providing navigational assistance, Fire Vox provides support for CSS speech module properties. It also works on Windows, Macintosh, and Linux.

    Installation is slightly more fiddly than your average extension but if you follow the instructions it is easy enough to get up and running.

    Once installed, it is probably one of the easiest screen readers I have used. They also provide some excellent tutorials on their site to get you up and running.

    I highly recommend it.

    Irresponsible content publication

    According to Gerry McGovern, on the 8th September, a story about the bankruptcy of United Airlines parent company began circulating on the Web. Within hours of the story’s being released, their shares had dropped by 76 percent.

    What has this got to do with web design I hear you ask? The answer; the story was 6 years old. Somehow it had been picked up by Google News and quickly caused panic among share holders.

    Gerry uses this as an example of the dangers associated with out of date content. He goes on to talk about how our ‘content management system mentality’ has led to an online environment without editorial control.

    The production of content for our sites has become so distributed and unregulated that nobody is responsible for reviewing or removing content. We put content online without considering if it is needed or whether it has an expiry date.

    The content of our websites has been largely neglected and I believe the time has come for website owners to put the same investment into content as they do into the build of a site.

    For those of you who are web designers, I would encourage you to start talking to your clients about how they plan to manage the content on their sites. Who will be responsible for the relevancy of what they place online?

    Code CSS the clear:left way

    It is always interesting to see how others build websites particularly when it is a high profile company you respect. One such company is Clearleft who are known for the quality of their CSS and Javascript.

    One of the developers at Clearleft is Natalie Downe. She recently spoke at Barcamp London about the methodology Clearleft use when coding in CSS.

    Although I didn’t get to hear her speak she has put her slides and notes (PDF 64.2mb) online. Fortunately, her notes are extremely comprehensive and it gives a real insight into her approach.

    Obviously, there is not a single approach to building websites. However, Natalie shares some interesting ideas about ensuring your CSS remains maintainable and can be easily handed to other developers.

    Interestingly we follow a similar approach at Headscape although we do differ in a few key ways. Nevertheless it is fascinating to see how others do it and there is a lot to learn from what Natalie shares.

    Back to top

    Interview: Aral Balkan on the new Adobe Products

    Paul: Ok, so joining me today is Aral Balkan, good to have you on the show.

    Aral: Oh, thank you Paul, it’s always great to be here.

    Paul: It’s been a little while, but it’s good to have you back, and we’ve got Aral on the show today, really to talk about a couple of random things really…

    Aral: The story of my life!

    Paul: …yeah, the story of your life, yeah, um, one of which is the new Adobe suite of products that are coming out, but before we get onto that, let’s talk about <head>, previously Singularity, what’s all that about for a start, what happened there?

    Aral: Uh, with the name change?

    Paul: Yeah.

    Aral: It was quite unfortunate, about 2 weeks ago or so, I got a letter from a company called Singularity Ltd, and they’d apparently trademarked "Singularity" the word, and you know how trademark law works, it’s got different categories apparently, and these categories are really wide, so a single category coul
    d include things like training and conferences, so this company was not actually doing a conference called Singularity, but they trademarked it under the same class, and so they weren’t too happy that we were using the name, and we had a talk as well, I called them up because I was like, oh crap, might as well just talk it out, and it just seemed like they wanted to have a legal conversation through the lawyers and stuff, you know, I’m not really into that, we only had 2 months to go and, you know, we’re a first year conference so I didn’t have the budget or the time really to get into that sort of a conversation and so I was like, yeah, you know what, this is going to hurt but let’s re brand, so I took a weekend out, redesigned the site, redesigned everything, and then we decided to go with the new name. I actually really like the new name…

    Paul: Yeah, it’s a good name.

    Aral: …it’s kind of edgy, it’s short, it’s memorable, and you know, given everything else, I probably wouldn’t have changed the name 2 months ago if I’d had a choice, but still, I like it.

    Paul: These things happen don’t they.

    Aral: These things do happen apparently, yeah.

    Paul: So tell us a little bit about <head>, what is it? You know, it’s obviously a conference but tell us a bit more about it.

    Aral: Well, it’s this conference and we have this amazing guy; Paul Boag speaking at it.

    Paul: Well, obviously, yeah!

    Aral: And that’s really all I need to say! How do you like that one?

    Paul: That’s perfect. Keep going, you’re doing well.

    Aral: It’s a virtual conference, so all of the sessions are streamed live over the Internet, and they’re interactive so you can ask questions as you’re viewing them, and the speaker can answer those questions. We’re using Adobe Connect Pro in order to do that, so it’s a tried and true system that’s been around for quite a few years actually, surprisingly. Also we have a couple hubs in London, in Manchester, we’re going to have one here in Brighton, one in Belgium, and there are a few more that still haven’t been finalised, but we may have 1 or 2 more hubs, and the one in London for example is taking place at the Magic Circle which I’m very excited about, it’s a lovely venue. Have you been there?

    Paul: I’ve heard of it, but I haven’t actually been there, I’ve heard of other people talk about it.

    Aral: It’s awesome, I was there last week, and it’s basically like the magician’s society in the UK, so it’s been around for about 100 years, and it’s got a museum where you can see actual items from Houdini and other people. Did you know that Prince Charles apparently is a member of the Magic Circle?

    Paul: Oh, that doesn’t surprise me.

    Aral: And he apparently had to do a little trick to get in with these cups and this ball, and he got accepted into the highest order of the magic circle, just kind of crazy!

    Paul: There you go! So when is this conference?

    Aral: The conference takes place October 24th to the 26th, and it’s everywhere, so you sign up to attend, and you can watch it from home, or if you’re in one of the cities where we have a hub, you can go from there.

    Paul: I mean, why virtual? Why did you decide to have a virtual conference rather than the traditional get-together kind of thing?

    Aral: Personal reasons Paul! No, um, actually seriously I do a lot of talks at conferences, so I fly around a lot, and the flying around bit and staying in strange hotels, sometimes it’s a great experience but depending on the hotel that you’re in, that’s not the bit that I really enjoy. You know, you go to a hotel, you don’t have wi-fi, the wi-fi costs 3 billion dollars or something, and I got to thinking whether that was actually part of the conference experience, the positive part of it for me, and I thought maybe not, and we do stuff on the web, that’s what we do, that’s the line of business that we’re in. So I thought why not try and see if we can create a conference that’s virtual, but yet try to keep some of the aspects of conferences that we like the most, like the social interactions, and that’s where the idea of the hubs came from, and that’s why it’s interactive and people can ask questions and communicate during the conference. And it’s an experiment, you know, it’s a first time conference so we’re trying it out, we’re going to see what works, see what doesn’t, and then we’re going to evolve it next year.

    Paul: I mean what I find incredible about it is, I guess because people don’t need to travel, you’ve got an absolutely incredible line-up of speakers.

    Aral: We do have some great speakers!

    Paul: And you’ve got so many of them as well, there’s, what is there? Over 70 odd speakers?

    Aral: Yeah, yeah, we’ve got 70 plus speakers, we’ve got amazing people; Tim O’Reilly for example is speaking, he’s doing a keynote in the London hub in person, we’ve got Jason Fried, and we’ve got yourself of course…

    Paul: I don’t think you could put me in the same category as those 2, but keep going. I like the sound of it, that’s good.

    Aral: Course we can! Dude, I’ve seen you in so many conferences, you rock! Um, and we’ve got Molly, Jeremy Keith, we’ve got so many people, I mean Rafi Haladjian, he’s the father of the Nabaztag bunny… I have one here! Yeah you saw it, when I came over with you guys.

    Paul: Yes, I know how obsessional you are.

    Aral: So, I mean, we’ve got amazing people. Gary Vaynerchuk, Wine Library TV, he’s awesome, I’m going to see if we can try and get a live video hook-up during the London hub with him, he’s just awesome, and just a whole bunch of people, I’m forgetting half of them, Richard Moross from moo.com, another one of my favourite companies.

    Paul: It’s just a stella list, absolutely unbelievable. Do you think people are going to miss out from the fact that they’re not going to have that face-to-face experience?

    Aral: I sure hope not, you know, we’re trying to build things that compensate for that, and next year especially I’m going to concentrate much more on the hubs. You know, I’m thinking of scaling it down next year because we’ve kind of gone for everything this year, which is exhilarating, but at the same time for a first year conference it’s a lot to do. Next year I’m thinking of maybe scaling it down a little bit, concentrating on 1 or 2 hubs, and try to build new interactions for connecting those hubs. I’ve got some really cool plans for it.

    Paul: I mean, one of the kind of interesting things about this as well is the kind of underlying technology of all of this. I mean, how is it working, how are you going to connect all of these people? I mean, you’re talking about thousands of people, 70 speakers, you know, here I am sitting in the middle of Dorset in the back and beyond, you know, and how are all these people going to see my presentation?

    Aral: Well, we’re using Adobe Connect Pro, so that does have a limit currently of 2,000 people in a room, so that’s where we’re limiting our attendance, we’re definitely not having more than 2,000, and I don’t think that’s going to be a problem. But Connect has a lot of features for basically connecting people. You can see the streamed audio and video of a presentation, but you can also interact both by typing, or you can send your own video feed. We’re probably not going to use that because of bandwidth concerns, but people can interact with other people who are in the session, they can chat with them and with the speaker, and so at the end of every session we’re going to have a question and answer, and the speaker will go through all of the written questions that they’ve received during the talk and answer them, and that format has really worked in the past as well for meetings that we’ve done.

    Paul: So, this is not a technology I’ve come across before, this is something that’s kind of publicly available from Adobe is it?

    Aral: Oh yeah, totally, Adobe Connect Pro has been available for several years. I think the full name, and it’s got one of those really long names, is Adobe Acrobat Connect Pro.

    Paul: Right.

    Aral: I know, I don’t know where they come up with them. But it’s a really cool piece of software for doing meetings and these sorts of virtual presentations. It used to be called Breeze.

    Paul: Ahhh, that’s the name I recognize.

    Aral: Yeah, there you go. It’s been around for years and years, so it’s really really stable, and Adobe actually has a new version of it, I don’t know what they’re calling it, I remember it’s beta name I think, but they have a free version for up to 3 or 4 people, so if you Google for that, or like in the transcript or something you guys can find it and link it, that’s really cool because you can just start playing with that. It used to be called Brio. I don’t know what they’re calling it now it’s been released.

    Paul: The other thing that I noticed from Twitter was that you mentioned that you built the website using Google’s App Engine.

    Aral: Yes.

    Paul: Tell us bit about that.

    Aral: Wow, it’s been a fun ride!

    Paul: You sounded somewhat stressed at certain points through the period.

    Aral: It has been really great.

    Paul: What is it first of all? Explain to people what it is.

    Aral: So Google App Engine is Google’s foray into providing access to the cloud; to its infrastructure. So basically Google has this massively scaleable infrastructure that hosts, it’s search and on it’s various applications on. So Google’s App Engine is Google’s way of saying "ok, here’s the technology that we have for building these infinitely scaleable applications, and we’re going to make it available to you in a very simple manner so you can build your applications on it and host them on it". And it’s really cool, the idea is awesome, and you’re going to be hearing so much more about it as they add more features to it. It’s currently in pre-release, so of course it was quite a gamble to base the website on a pre-release technology, but I’m still convinced that that gamble is going to pay off because basically the way I see it, there are the most intelligent developers in the world working at Google basically working for my application. Every feature they add basically adds a feature to my app in a way that I can use. So once they integrate things like the Google APIs, once they integrate other features, not that I have any insider information, but it just makes sense that they would do that, I think it’s just going to become a more and more powerful platform.

    Paul: But you found it a little bit painful at times.

    Aral: Well of course. It’s pre-release, right? And pre-release technologies have issues, so they’re figuring things out. It’s not something that, again, has been done before, Amazon has a really cool platform with simple DB, S3, S32 and those technologies which provide the same thing, but in some ways, Amazon’s platform is much more tested, much more tried, but it’s also more difficult to develop on, I mean, you need a lot of skills, you need to be a system administrator in order to build on EC2, or at least have some knowledge in that area. You need many more skills. With Google App Engine, if you know Python, you just download this SDK onto your machine, you install it and you have a local version of their environment on your machine and you can write a few lines of Python and start running your application on your local machine, and then you just enter one command and suddenly it’s on Google’s servers, and the theory is that a million people can hit it immediately and it’s not going to go down.

    Paul: Yeah, which for a conference like this where a large number of people are all going to be using a site at the same time, it’s vital.

    Aral: Yeah, and I mean we’re not going to stress it at all with our numbers, but you know, if you think of the next Flickr or the next Twitter, although you can’t currently build a mess
    aging app on it, but apps that will get those numbers, that might get those numbers, they won’t have to go through the standard stages of development. Because these days, today, what happens is you build an application, you build it using some sort of rapid framework like Rails or Django or whatever, you build it, you put it up there, and if it gets really popular, then you basically have to go in, you have to re-architect a lot of things. You know, for some apps like Twitter, they’ve basically had to rebuild the application as it’s running. And that’s a lot of work. Google App Engine turns this on its head. You have hurdles to get by when you’re building the application, but you can test it, just with yourself, and if your application runs correctly for you, if you can get it to that point, then it will run that way for everyone that hits it. Or at least, that’s the idea, that’s where they’re heading for.

    Paul: That sounds really exciting, I look forward to seeing that develop.

    Aral: It is.

    Paul: You’re very brave taking it on so early.

    Aral: Well you know what, that’s the thing. A few people have told me when I was bitching and moaning when we had a few issues, and let me tell you, Google have been amazing, I have direct contact with a couple of engineers on their team, and they have been amazing in helping me out and working with me, and I’m working with them to try to improve it. But a few people when I was bitching about it were like "well, you know, you just got what you deserve for using pre-release technology". But the thing is, someone has to, right?

    Paul: Exactly, yeah.

    Aral: Someone has to, so the next time somebody tries a beta piece of software, tries to build it and provides feedback, instead of going "ha ha, I told you so!" kind of think, well you know, I’m probably going to end up using this in a few years time and I’m going to benefit from the lessons you’ve learnt. So some people have to be early adopters, and yeah, getting burned with certain things is part of it. But it’s just how it goes. But what interests me the most, Paul, about Google App Engine, and about like, EC2 et cetera, is that we’re kind of entering the age of the commodity web, where the web, where building scalable applications on the web becomes a commodity just like electricity or water. You know, so we won’t have to worry about things like hosting and this and that, it will just be like another meter reading, you know,um, I’ve made my app, here it is on the web, and I get charged for it by CPU cycles, by the amount of resources that I’m using, just like electricity.

    Paul: I mean, that will be awesome. If we can reach that point where we don’t have to worry about scaleability and things like that, that would just be incredible.

    Aral: Yeah, I think we’re nearly there.

    Paul: That’s superb.

    Aral: Yep.

    Paul: Talking of you working with people, you said you were working closely with Google over this, I know you’ve got an excellent relationship with the guys over at Adobe, and no doubt you’ve been playing with CS4, tell us a little bit about it. You were over at the launch of it were you not?

    Aral: Yes I was, I wasn’t actually speaking about CS4, but I was at the launch and I got to see some of the demos there. It’s a huge suite, you know, I didn’t have the chance to play with everything, so seeing some of their demos, it’s really cool, it looks like they’re really concentrating on integration between the products, they’ve been doing this for a couple of releases now, but it’s really starting to pay off. When Adobe bought Macromedia, everyone was like, well you know, how are they going to integrate things, and people were fearing it was going to be an instant process and some of the tools would be ruined. That hasn’t happened. But they have been integrating the products over the years with these release cycles. So, one of the demonstrations that I saw that was really cool for example was in In Design, which is a desktop publishing tool that they have, you can build a magazine, and then you can click a button, and then have that be an interactive magazine in Flash that you can put on the web with like a page turn effect and stuff like that.

    Paul: Wow.

    Aral: And that’s actually quite awesome.

    Paul: Yeah.

    Aral: I spent a bit of time a couple of years ago to build an app that did that from PDFs, and that software is still going strong and being used on the web, but now you can just do that with In Design and Flash. And things like that, it really worked on the workflow between various tools, and it makes a lot of sense because web video is such a big thing now, and being able to take things from After Effects and Premier into Flash and back and into DreamWeaver and put it up on your site, they’re really working on these workflows so they’re not joined to tools. I think that’s really for me the most exciting thing, apart from some of the cool stuff in Flash.

    Paul: What have they done in Flash then that’s so cool?

    Aral: Some of the cool stuff in Flash? Well, we have bone support now, IK support. You can draw like a stick man for example and then you can take this bone tool and trace over its various limbs, and then have this puppet that you can play with, and the cool thing is, you can publish this and this puppet is interactive once you’ve published your movie as well, it’s not just an authoring. So you’re going to see some amazing advances in like online games that use this, and in animation. For animators, it’s just going to make their lives so much easier. And that’s just like one of the new things they have.

    Paul: Did you get a look at Photoshop and whether there have been any major changes in that?

    Aral: Yeah! Well they’re really concentrating on the 3D stuff in Photoshop from what I can see. There’s a lot of 3D tools, you can bring in 3D models into it, you can paint into them, they stay 3D as you’re painting into them and outside of them. There was this one demo which I thought was really cool where they took an old-fashioned car and it was like a 3D model, and they just rubbed off the roof, and then it became like this convertable, but it’s still 3D, and they started painting the seats, which is kind of cool. I think that’s going to, again, it’s an integration with your
    other tools, with your 3D tools. It does look really cool, I can’t wait to play more with it.

    Paul: I guess the only other one that’s directly relevant to web design would be DreamWeaver. Did you get a chance to look at that?

    Aral: Yes. Yeah, I did, and it seems to have gotten a whole bunch of new features as well especially with the CSS and their live preview of CSS. But to tell you the truth, I don’t really use DreamWeaver. I started out with, well no, ok, I started out with Front Page many many years ago.

    Paul: You should be ashamed to even admit that.

    Aral: Forgive me, I know, but I switched to DreamWeaver right away! But recently, you know, I just do a lot of my stuff in Text Mate, and I don’t know why that is, but I just find some of these tools to be way too heavy, especially for HTML, and I really like to have control over what I do. And Text Mate is light, I’ve begun to favour lightweight tools a lot.

    Paul: Yeah, I must admit, I use DreamWeaver for a very long time as a text coding tool, not as a WYSIWIG, but in the end, it was just so slow to open up compared to other stuff and it just seemed to be chunky.

    Aral: Yeah, I kind of went through the same thing, and I really, like I say, I really enjoy Text Mate. It is such a simple simple editor and it just works.

    Paul: Ok, so that’s really great Aral. Going back to the conference just very briefly, by the time this comes out, people are going to have missed unfortunately the early bird discount, so how much are they looking at for this conference?

    Aral: Well the main tickets are $149, but who knows, maybe we can do something special for listeners of your podcast.

    Paul: Oooooh!

    Aral: If they are going to miss it.

    Paul: Ok, well you let me know that, and we’ll tag that on after this interview, I can do that easily enough.

    Aral: Ok, cool.

    Paul: You can find out about the conference over at headconference.com and I’ve got to say, this does look absolutely incredible. Am I right in saying that also people that have attended the conference, there’s no way you’re going to be able to listen to all 70 speakers over those couple of days. So they can go in and watch the videos after the event? Is that right?

    Aral: Yep, all of the videos are going to be recorded and you’ll be able to watch them at any time.

    Paul: So I mean, absolutely superb for a $149 or whatever it is, that’s an incredible deal and you will never come across a conference that’s got quite this line-up of speakers, and certainly of course, you don’t have to pay for hotel bills, you don’t have to pay for travelling, and you don’t even have to pay for time out of work.

    Aral: Exactly, yep.

    Paul: Sounds pretty good. Aral, thank you for coming on the show and we’ll get you back again in the future.

    Aral: Thank you Paul, oh it will be great, I love being here.

    Paul: Ok, good to talk to you.

    Aral: Take care, Paul.

    Back to top

    Listeners feedback:

    Review of Stackoverflow by Teifion

    I’m a developer not a designer so if you understand my incoherent babbling please keep in mind that this review probably won’t be as useful for designers but please, fall asleep after I stop talking.

    About a month ago I joined a site called Stackoverflow. Essentially it is a cross between a Forum, Digg/Reddit, Wikipedia and a Blog; you ask questions and answer questions, you also get answers to your questions and you generally get them very fast. It is now in public beta.

    It’s a simple idea that could be great and could also be completely useless. Jeff Atwood and Joel Spolsky have managed to make it very useful.

    Now it’s time to add some actual content to the review or Paul will call me silly names again. Questions in Stackoverflow are allowed to be on any language or topic related to programming and here’s where the designers might be interested, this includes source control, HTML, CSS and even things such as keyboard layouts.

    The question that you should ask yourself right after "why am I listening to Teifion" is "Why is this better than google?". The answer is a simple one, Google cannot look at your site and tell you why a div is wider than you want it to be while a site with 8000+ members probably can. I am given answers to my questions within 5 minutes bar I think 2 obscure questions.

    Don’t feel that you are too new for the site either, you can ask anything from very simple to very complex questions, anything from "what is a class?" to "how do I benchmark a PHP or Python script via the Unix terminal and not from within the script itself?".

    I strongly recommend that everybody check it out.

    Don’t Get Blacklisted By Google

    Jason from Toronto recently wrote to me with a questions about search engine optimisation:

    I am desperate to improve the search engine ranking of my company website but I am confused by the contradictory advice online. We have even considered hiring an SEO company, but aren’t sure who is reputable. The last thing we want is to be blacklisted. Do you have any advice which might help?

    It is true that Google comes down hard on sites who disregard their webmaster guidelines. Probably the highest profile example of this was when they effectively removed car manufacturer BMW from their search results for using doorway pages.

    Read More Here

    Back to top

    Choosing a hosting company

    Posted in Development on September 5, 2008 by Paul Boag

    Hosting companies are a dime a dozen. They all offer very similar packages and all seem competitive on price. How then do you choose between them.

    Presuming that your site does not require anything particularly unusual in terms of hosting, you will be faced with a plethora of providers to choose between. Some will be temptingly cheap in what is a competitive marketplace. However, be wary of buying on price alone. There are a number of other criteria you should consider:

    • Uptime
    • Support
    • The control panel
    • Limitations on growth
    • Hidden charges

    Let’s take a look at each, starting with uptime.

    Uptime

    The last thing any website owner wants is for their website to be unavailable. Many hosting companies therefore provide uptime guarantees. Figures range from 95% uptime right through to 100%. But what exactly are they guaranteeing and is it something you should worry about?

    In most cases uptime guarantees are worthless. They do not actually guarantee that your website will be available 100% of the time. This is merely a figure they are striving for. If they fail, they will compensate you. However, the nature of this compensation varies. In most cases it involves refunding a portion of the money you pay for the hosting. However, this could be insignificant compared to the losses in sales. You should always clarify what compensation is being offered.

    Remember that even the largest organisations have downtime. It is a problem that can never be entirely avoided. Websites can be unavailable due to connectivity issues, poor code or any number of reasons beyond the control of your hosting company. As a result they often specify exclusions from compensation in their terms of service.

    In short uptime guarantees are meaningless. They are simply a marketing tool. Instead, search for reviews of the hosting company or look at their support forum. If their are lots of complaints about downtime think twice. However, in most cases the service offered in regards to uptime is fairly universal.

    Instead of asking how often your site is likely to go down, ask what happens when it does? What kind of support can you expect?

    Support

    Support is arguably the single most important factor in choosing a hosting company. Whether it is your website going offline or a piece of functionality not running, it is inevitable you will have problems with your hosting. You will need to quickly reach somebody who can help.

    But how can you tell if a hosting company offers good support? Look for the following things:

    • 24/7/365 support – When your website is offline you need to be able to get help instantly. Check that your hosting company offers support 24 hours a day, 7 days a week 365 days a year.
    • Telephone support – There is an increasing trend towards email only support. However, technical problems can be hard to diagnose and prolonged conversation via email are time consuming. When your site is offline you need the immediacy of a phone call. Ensure that option is available to you.
    • Speedy response – Whether contacting your hosting company by email or phone you should expect a speedy response. It is unacceptable to be sitting on hold while your site is down or waiting days for a response to an email query. I recommend calling the technical support telephone number before you sign up for their service. How long do you have to wait before you get to speak to a real human being? Also, send a question via email and see how long it takes to get a reply.
    • In country support – Personally I prefer speaking to local support staff. Being put through to call centers in far flung locations can be frustrating when discussing complex technical problems. If you do not share the first language of support staff misunderstandings are easier. By calling the support number before signing up you can establish whether there will be communication problems.
    • Knowledgeable staff – Another drawback of call centers is that they are often manned by individuals with limited technical knowledge. This can be frustrating when endeavoring to resolve technical issues. Ideally you should be able to speak directly to the individuals manage the web servers. If you are not technical ask your web developers to speak to the support staff at the hosting company before signing up. They should be able to judge their technical competency.
    • Technobabble free support – Talking to technical staff can be equally frustrating if support staff are overly technical. Being confronted by technobabble when you want to find out is why your site is down can be extremely annoying. By calling the support line before purchasing you should be able to get a sense of their communication skills.
    • Self service support – Contacting technical support is the last resort. In most cases you should be able to find the answer to questions yourself through your hosting companies support site. Look at their site and see if they have frequently asked questions, a knowledge base, forums and most importantly a list of current known issues. Facilities like this can save time so make sure they are available.

    Self service should also extend beyond support. Most hosting companies also provide a control panel for managing your site.

    The control panel

    Calling technical support every time you want to change the password will become frustrating. That is why most hosting companies provide a control panel for basic maintenance. This includes, managing email, changing passwords, uploading files, backup and accessing site statistics.

    Evaluate the control panel and discuss it with your developers. If the hosting company does not have a demo available on their site, call and ask for access to an example. If nothing else this will demonstrate how responsive their customer service is.

    Once you have access, ask yourself whether it provides all the functionality you require? Is it easy to understand and use? For example, how does it handle the management of multiple sites? This is particular important as your online presence grows.

    Limitations on growth

    As your site becomes more successful you will become more ambitious in your plans, and visitors will flock to it in ever larger numbers The question is, will your hosting company keep up with this growth?

    In order to answer this question you need to understand three things:

    • Can you manage multiple websites centrally? - You may start with a single site but if it is a success you could want to launch more. It could be a sub-site that supports a marketing campaign or a site dedicated to a subset of your audience. In either cases the site will need managing. You will want to avoid multiple logins to administer multiple sites. They will need to be managed centrally. Check with your hosting company that they provide a single interface to manage multiple sites.
    • What is the upgrade path? – As your site grows in terms of visitors and complexity you may find the need to migrate from shared hosting to dedicated. You may even need to upgrade your dedicated box to something more powerful. It is important to understand how this process works. You want to avoid the need to backup your entire site and install it all over again. A good hosting company should make this a seamless transition.
    • What happens if you exceed your bandwidth limits? – The more successful your website the more expensive it will be in term of bandwidth. Most hosting plans come with a bandwidth limit. This is because the hosting company has to pay for each piece of data a user downloads from your site. They therefore have to cap how much data they allow to be downloaded. Normally this is more than adequate for most site. However, what happens if you exceed your bandwidth limit? How much extra is it going to cost you and what happens if you exceed your limit unexpectedly without a higher rate package in place? Will it costs you even more? Does the control panel provide a way to monitor current bandwidth use?

    It is not just bandwidth that can become expensive. You may discover there are other hidden charges too.

    Hidden charges

    Some hosting companies can appear to be inexpensive on the surface but have a hidden cost. Establish what is included in the monthly charge and what is not. I have encountered hosting companies who have made additional charges for:

    • More than a predefined number of email accounts
    • Advanced email functionality such as exchange server or spam filters
    • A technician to physically restart your web server
    • Add-on technologies
    • The ability to run databases
    • Access to website statistics

    The list could go on. There is nothing wrong with hosting companies using this form of modular pricing. In fact it can keep the price down if you only require basic functionality. The problem comes when they do not clearly communicate these additional costs and they therefore come as a surprise.

    The above is a draft extract from Paul’s upcoming book ‘The website owners Manual‘. To get instant access to the rest of Paul’s book signup to the early access program.

    133. Agile

    Posted in Classic shows on September 3, 2008 by Paul Boag

    In this weeks show we talk to Jackson Wilkinson about Agile and answer your questions on web design courses and showing off development work.

    Play

    Podcast: Download (26.8MB)

    Download this show.

    Launch our podcast player

    News and events

    The Target accessibility settlement

    Previous we reported that the retail chain Target was being taken to court over the inaccessibility of its site. Many hoped this would be a landmark case that would clarify whether the Americans with Disabilities Act applied to the web. As with the Disability Discrimination Act in the UK the wording is open to interpretation.

    Well after 2 years of legal battle Target has agreed to pay $6 million in compensation and correct the accessibility problems on the site by February 2009.

    Some are complaining that the case has failed to achieve all it could. They argue that although $6 million sounds like a lot of money it is small change for Target. What is more, they argue, Target has admitted no ‘wrongdoing’ and the case has done nothing to clarify the law.

    These are legitimate points but I prefer to take a more positive view. This has been a significant embarrassment for Target and although $6 million is a small figure it is substantially more than they would have paid to address the problem from the start.

    Finally, as Matt May points out on the WaSP website, this case may not clarify the law, but that does not matter. As web designers, our role should be to educate clients about the importance of accessibility rather than campaign for tighter legislation. In my opinion the benefits of accessibility are considerable and if presented correctly do not need laws to enforce them.

    Long live IE8. Goodbye IE6?

    This week saw the release of IE8 Beta 2 and I have to say that things are looking good. Quirksmode says it is shaping up nicely and Sitepoint has even asked whether web designers will switch from Firefox back to IE (the overwhelming answer was no!).

    If you build websites and have yet to take a good look at IE8 then now is the time. I suggest you start with Microsoft’s own ‘readiness’ documentation for developers. This talks about all of the new functionality. You may also want to look at their separate documentation which lists the new CSS properties supported.

    As IE8 teeters on the brink of release there is a growing movement to stop support IE6. With 37Signals, MobileMe and now even Facebook effectively dropping support for IE6 it would seem the tide is turning. There is even now a site dedicated to the demise of IE6. On it the author writes…

    Internet Explorer 6 will be SEVEN years old on August 27th. It came out a few weeks before the Twin Towers fell. It came out before the Nintendo GameCube. It came out before the first iPod.

    Makes you think doesn’t it.

    OS form elements

    Paul Stanton sent me a link this week to a great tool for you designers out there.

    When I am working on a design for a site in Photoshop, one pain in the ass is creating form elements. You have to open a browser, find the form element you want, screen grab it and then edit it to remove all of the background elements. Its not a big job but it is annoying.

    If I had any sense I would keep a library of all these form elements. However, somehow I have never gotten around to it. Fortunately I don’t have to now as there is a great site which provides them all for me.

    The site is called the Designers Toolbox and includes web form elements for IE, Firefox and Safari under both Windows and Mac. They can be downloaded in PSD format and even include browser windows at various resolutions.

    Blogging software reviewed

    Finally, it wouldn’t be boagworld if we didn’t plug at least one Smashing Magazine story each week. Damn them and their compelling content!

    This week they have published a review of 10 blogging applications including…

    • WordPress
    • Movable Type
    • ExpressionEngine
    • Drupel
    • TextPattern
    • Joomla
    • b2evolution
    • Nucleus CMS
    • Serendipity
    • Mephisto

    The subject of blogging software, or content management systems in general, is a controversial one. This post alone has generated 137 comments, mainly consisting of people promoting their own personal preference. People are passionate about the system they use and often it can be hard to get a balanced evaluation. This makes selecting a system that is right for you difficult.

    This post does a fair job at providing some subjectivity to the discussion. It addresses the pros and cons of each system and indicates the kind of site the system would be best suited for.

    It is not a comprehensive guide, but is useful if you want to see what is out there.

    Back to top

    Interview: Jackson Wilkinson on Agile

    Paul Boag: So I’m pleased to have joining me today Jackson Wilkinson. Good to have you on the show.

    Jackson Wilkinson: How’s it going Paul.

    Paul Boag: Very well indeed. Just for those people that don’t know of you can you kind of give people a little bit of background so that they kind of know the angle you’re coming at things.

    Jackson Wilkinson: Sure. I’m a user experience strategist at Viget Labs which is outside of Washington DC in the US. We’re essentially a full service web consulting shop. As a company we do design and development mainly in Ruby on Rails. We also do sort of the pre-product, pre-development strategy, that’s a lot of what I am involved in. We also do marketing. So specifically I attack working on the web from that angle of improving and setting the user experience at a product level before hand and then usering it in to usually the design phase after that. I tend to dabble in a lot of things. I was formerly a developer and have also been a designer here and there and try to keep my hands dirty in a lot of different areas.

    Paul Boag: Cool. So I mean the reason we’ve got you in to talk today is to talk a little bit about the idea of agile developement. Particularly how it kind of applies not to the developer side of things that a lot of other people have talked about but you know to the design side of things, to the design community. But before we get into that let’s take a step back and start off by explaining to those that don’t know what agile development is. Could you kind of give us a potted summary of agile development.

    Jackson Wilkinson: Sure. I think the short form answer to that is that, agile is basically a process for software development, typically software development, that is the opposite of your typical waterfall process where you have this big planning stage up front. You decide what every screen’s gonna look like. You decide how every feature is going to act and so on an so forth. Instead the agile proccess focusses on short rapid bursts of development which are usually called iterations, and essentially you’ll work on your product for somewhere between two and four weeks at a time implementing little bits of functionality so that you have a completed product every two weeks or so. The idea is that you’re able to adapt to change. You know if you decide that requirements need to change two months into the project that’s not a big deal because it only affects this two to four week period of development. You don’t have to go back and redo everything that you’ve already done. I think that’s pretty much the short form version there.

    Paul Boag: Okay. That’s good. So in what kind of projects is this normally used on? You mentioned software development but what other kind of things?

    Jackson Wilkinson: Well the proving ground so far, agile’s pretty new in so far as development processes can be new. It’s proving ground has largely been on the web. So web apps and web products have really been the biggest place where agile has been used but that’s not to say that that’s the only place where it has been or where it could be. Many larger products, many end user pieces of software. Largley ones that affect developers or that affect designers have been used and have been developed in an agile way. Definitly if you’re thinking sort of the 80/20 rule the vast majority of agile development has sort of been on the web for web apps. That tends to push those boundaries anyway, that web industry.

    Paul Boag: So this has been, this can be used on larger projects? It’s not limited to smaller more self contained things then?

    Jackson Wilkinson: Sure it certainly can be used on larger projects. It really depends on the structure and the climate at the development shop where this is happening. If you’re a really large shop that has lots of beauracracy and lots of stake holders and your client needs to get approval from 5 different places then this notion of quickly changing rapid development, quickly developing specs and the rapid pace of development is probably not as conducive. But when you’re in an evironment that has senior level developers who have a lot of autonomy and everybody tends to trust each other to roll with the punches, or you just have a lot of trust in your entire team then an agile process can work on any kind of software. Whether it’s a two month project or a two year project.

    Paul Boag: Interesting. I mean from what I’ve heard of agile development before it’s a technique that’s growing in popularity amongst developers. You seem to think that some of the elements of agile development can be applied to designer’s as well. Tell us a little bit about that.

    Jackson Wilkinson: The main reason why I’ve been thinking about this lately and why a lot of others have been thinking about this lately is that certainly as developers work on web apps they interface with designers a lot. If you’ve got this notion of a two week iteration then, maybe an example of an iteration might be that you’re working on a sign up process or you’re working on a registration process for one iteration. Then you go on to, you know if you’re making a social network for quilters, then you’ll add in social networking features after that or something along those lines. If you’re only constraining your work to those two week batches then often times the designers will be basically in this position that they will be forced to hustle to meet the development schedule. That’s not necessarily conducive to the design process as we normally think about the design process. That’s kind of how I came to thinking on this topic and how a few others have as well. The challenge really is to take some of those elemental notions of the agile process and to try to shape the design process around them so you can best use them to your advantage. A lot of times that means if you’re a user experience type of person or an information architect you’re planning process probably won’t be 4 to 6 weeks long or even longer with lots of user interviews. Instead you’re focussing on the law of diminishing returns where you’re talking to a couple users and getting there feedback and doing a little work on some interfaces and testing them out and moving on from there or as a designer you’re working on 5 or 6 screens at a time. Sort of in the silo of what’s going to be happening on the next iteration and then those get implemented. As you see what’s worked you constantly are improving your interface and improving your design as you see these things implemented. You’re in fact taking feedback from what’s already happened and using that feedback either from internal users or external user tests or even just what the developer’s and your friends and other designers are saying about it as it gets implemented. You’re pushing that back into your own process to in fact build a better product for the next iteration and do a better job there.

    Paul Boag: How does that work from a kind of, you know the broad overview point of view? You know, as somebody that’s designed interfaces for fairly large and complex sites that would go beyond the two or three week or whatever cycle. You do so many different things with the different templates that you produce. What you do on one set of screens may affect what you do on another set of screens further down the line. If you’re working on all the individual iterations or silo’s of work is there not a danger that problems get ignored because they’re outside of the current cycle of development? Is that making sense?

    Jackson Wilkinson: Well that certainly makes sense. That’s a challenge that a lot of folks new to the actual process experience where your essentially thinking we’re done with this piece of the product we’re totally going to ignore it from now on. That’s really one misconception and mistake a lot of folks make. Instead you should be thinking that part of each iteration is going to be addressing observations and addressing things you’ve discovered about the work you’ve already done. You’re third iteration is probably largely based on developing new features or developing new parts of your application. At the same time you’re going back and making tweaks and making changes to the work that you did in your first and second iteration based on testing or things that you’ve discovered about it or changes you have to make based on things that you know now that you didn’t know then. That way it definitly keeps everything moving. It keeps the whole product getting better at the same time.

    Paul Boag: But isn’t that end up requiring a lot of re-work? You know you kind of are constantly doing things over and over again?

    Jackson Wilkinson: Ideally it doesn’t require that much re-work no more than you would spend that time in a waterfall process determining what exactly you want in the first place. Certainly the agile process kind of comes with this belief that mistakes aren’t necissarily a bad thing and that you kind of embrace the notion that you may be wrong but you embrace that notion thinking that you’re going to be quickly making decisions and quickly making your best judgements about something based on what you already know. The time that you’ve saved by quickly making those judgements will completely of set and hopeful you’ll still be in the black when you have make a couple of changes down the line.

    Paul Boag: So it’s basically doing away with the laborous documentation and the specing up of a project at the beginning and okay you loose some of that when you have to then re-work stuff but overall you end up, as you say, in the black.

    Jackson Wilkinson: That’s the idea. That’s the hope. It seems to work out pretty well for us. It doesn’t always work with every type of client or every type of project. If it’s a client who isn’t a really adaptable to change on a regular basis or something like that. The notion that you’re not going to have this big spec doc up front may be a little unsettling for them but hopefully on an agile team you have a client, whether it’s internal or external client, that is buying into your expertise and really trusts your process and knows that your going to end up with really what works best in the end.

    Paul Boag: There are differences between how this process applies to a designer rather than a developer. Are there changes and tweaks that need to be made?

    Jackson Wilkinson: Yeah. In the end changes and tweaks tend to happen pretty equally to both the development of the site and the design of the site. Essentially if you’re a designer who is taking responsibility for the entirety of the interface and you’re designing that inteface completely, then you’re going to basically be making changes that could affect the developers as well. That’s something that designers need to keep in mind. They need to work very closely with developers to understand what the changes that they’re suggesting imply and really you make changes based on the time available in this iteration and what really is going to be most effective to change in the time you have available to you.

    Paul Boag: So you have to be quite strict about these time scales from the sound of it? You were saying there that you only make the changes that you can within the current iteration before you deadline runs out. Am I understanding that correctly?

    Jackson Wilkinson: Yeah, one of the biggest challenges there is knowing what size changes you want to bite off of this project. So you’ll have this mountain of changes that you eventually want to make and a lot of the project management involved is figuring out what you’re going to place in the next iteration. Doing as much work as you can on those bits and then reassessing at the end and hopefully having a new product or a new potential release, even if it’s not quite ready for release, a potential release finished at the end of that end of that two week block to evaluate everything you know at that point.

    Paul Boag: I mean I can imagine there’s a lot of people listening to this that may be a little bit nervous about the idea. They’ve come from a very kind of waterfall driven mentality, where you know you pass things from one person to another. On the other hand they concede the potential in it and are maybe interested in finding out a little bit more. Where do suggest people start if they want to experiment with agile development? How do you do begin?

    Jackson Wilkinson: Well I think that capital A agile proponents would probably say that you really need to dive in. I’m not sure that I buy that. I’m more perhaps a post-agilist, in thinking that you really need to just do what works. What works for you might be different than what works for somebody else. If you’re really ingrained in a process that has a lot of aspects of waterfall, has a lot of upfront planning, then you know you still can do a lot of the agile things to dip your toe in. The first thing that I might suggest doing is that even if you have a long planning process upfront where you determine the full scope of work. You determine even many of the streams and many of the design elements that are going to be implemented. Still break those goals up into two to four week iterations. At that point you still have the comfort of the planning that you’ve done ahead. If you concentrate on creating a self-supporting product within two or three weeks then you’re half way along that train. You can see how that goes. You’ll probably find that after you’ve gone through a couple iterations you’re thinking about things you’d want to change back in the planning section. That then maybe that’s okay at that point. You’re realizing how this self driven process works. As you become more and more comfortable then take away some parts of the planning. Maybe put the visual design to be a piece of the iterative structure while you’re still maintaining the feature scoping and the wire framing up at the front end of the project. Dip your toe in it first and then your whole foot and then maybe eventually you’ll be in up to your waist.

    Paul Boag: So mean there must be resources out there? Lets send people away from this interview with something constructive to do. Where should they be going to learn more about this? What’s the next step they can take?

    Jackson Wilkinson: Sure. If you’re a designer there isn’t necissarily a lot that addresses agile in the design case right now. Most of the agile books and the agile resources that you’ll find tend to deal mostly with a strict development structure. Certainly if you’re simply interested in looking at things and what the agile process is in general then you can look for books that deal with extreme programming or agile. You’ll find countless numbers of them. I’ll certainly give a list to you Paul so you can put them on the website afterward. Beyond that there are a few websites that deal with the agile design process. Emily Chang wrote a post call the agile web design manifesto. It’s a couple years old now but most of the concepts still remain. Where you’re kind of marrying this notion of design with agile development. She offers some good suggestions and especially the comments that follow her post are super useful to look through. If you’re involvedin IXDA which is an interaction design group. There are numerous discussion’s on there mailing list about how agile processes fit in to. The whole notion of the message boards is probably a good source in this case. I’ll certainly be happy to forward along a list for everybody to check out.

    Paul Boag: Excellent. Thank you very much for your time. That’s really interesting. We’ve kind of touched on agile development very lightly on a number of occasions but we haven’t really looked at it in any kind of depth I guess, or kind of broken down what it is and how it works. It’s great to have you on show. Thank you so much for your time and I look forward to looking through that list.

    Jackson Wilkinson: Yeah. Absolutely thanks for having me. I really enjoyed it.

    Thanks goes to Curtis McHale for transcribing this interview.

    Back to top

    Listeners feedback:

    Courses on web design

    Jonathan asks: I am looking to get into web design and was wondering if there are any colleges or courses you could suggest. However, I do not have any A Levels.

    I get questions like this fairly often, but tend to avoid them for two reasons. First, I went to college 15 years ago and so am out of touch with what is available (web design courses didn’t even exist!). Second, this is a country specific question, as nations have different educational systems.

    However, because it is a popular question I will address it. There is certainly some generic advice I can give:

    • Look for practical courses – I did two courses between school and work. The first was a BTEC and the second a degree. Although the degree was supposed to be a more advanced course, the btec was far more useful. That was because it taught me hands on skills that I still use. My degree on the other hand was very academic and abstract. Where possible choose a vocational course.
    • Focus on web design – I receive a lot of CVs from people with computer science or art degrees. This tells me two things. First, when they selected their course they didn’t know specifically what career they wanted. Second, that if I hire them I have to train them. I would prefer somebody who specifically wants to be a web designer and already has a good grounding in the basics.
    • Consider an apprentice scheme – If you have not performed well in the education system, consider an apprentice scheme instead. You will learn considerably more working for a web design company than doing an academic course. You will also get paid at the same time! Even if you cannot find an apprentice course in your country there is nothing to stop you arranging this yourself. Find a friendly web design agency willing to take on a trainee and also attend a part time or evening course.
    • Learn business skills – Web design is not just about design and development. You need to understand business principles as well. You will be required to manage your time and potentially other people. Also, if you decide to become a freelancer you will need to understand sales, marketing, tax, invoicing and many other aspects of business management.

    Showing off development work

    Teifion asks: As a designer you can show off your work in a portfolio. As a programmer I cannot. What is the best way for developers to show off their work?

    There is no doubt that it is harder for a developer to demonstrate his skills than a designer. However, it is not impossible. Let me suggest 4 approaches you could use:

    • Sandbox – Have an area of your site where you build prototypes of functionality. It is a chance for you to experiment and show off your skills. Even large organisations take this approach. For example Google Labs showcases development projects which are far from finished.
    • Blog – A blog gives you a chance to expose some of the code that lies behind your work. It also demonstrate your knowledge and techniques. Many developers shy away from documenting their work in this way. However, it is an effective promotional tool when seeking employment.
    • Case studies – If a blog feels too much like an ongoing commitment consider writing occasional case studies. This works especially well if you have commercial work to showcase. A case study should not only demonstrate your coding skills, but also your ability to interpret a brief and formulate a solution.
    • Screencasts – If writing fills you with dread, why not produce a series of screencasts. Screencasts allow you to show your code in action. You can demonstrate work and also show the process used to develop that approach.

    You should not limit yourself to just one of the options above. Ideally look to combine approaches to effectively communicate your coding ability.

    Back to top

    132. Drobo

    Posted in Classic shows on August 27, 2008 by Paul Boag

    In this weeks show Paul and Marcus return to talk about the abundance of content management systems and ask the question “Are there too many?”,  as well as discussing Paul’s new Drobo and backing up.

    Play

    Podcast: Download (24.5MB)

    Download this show.

    Launch our podcast player

    Vote Boag

    To start with we’d like to ask a favour of all the loving Boagworld listeners, would you vote for our panel at SXSW this year. We’ve called it Clients Are Stupid…? and the official description is as follows:

    Why do clients seemingly make idiotic decisions? How come they fail to ‘get it’? Learn how to improve communication with your clients and enhance your working relationship. Be more successful at pitching ideas, getting design sign off and ensuring projects stay on track. Don’t let your projects become a battleground.

    Check out the panel page for more information on what we’ll be discussing and we’d appreciate the vote!

    Special Discount

    On last weeks show Ryan and Stanton talked about FreeAgent, an online accounting and project management tool for freelancers. Ed Molyneux, FreeAgents founder and CEO, has written to us to offer a special discount for Boagworld listeners:

    We’d be really pleased to offer Boagworld readers/listeners a discount of 20% on all ongoing subs if they sign up with the referral code boag99 before the 15th September 2008. They get a 30-day free trial before having to subscribe, and monthly subs range from £15 for Sole Trader freelancers to £25 for Limited Companies.

    So thanks Ed, and listeners be sure to check out freeagentcentral.com to take advantage of this offer.

    News and events

    Step away from the keyboard

    One of the curses of being a web designer or even a website owner is that we spend too much time in front of a keyboard. Whether we are writing content, coding or planning a site structure, it is normally done in front of a PC.

    I have tried to escape the shackles of the keyboard but with only limited success. Sketching can help and I do a lot of information architecture work using pen and paper. However, these approaches don’t allow the flexibility and speed of a PC.

    However, this week I have come across two little products that help to escape the PC. The first is called GUIMagnets. They are basically fridge magnets with GUI elements printed on them. These including text fields, radio buttons, dropdown menus and more. Used in conjunction with a whiteboard you can quickly prototype page layouts in a much more tactile way.

    The second product is an alternative to whiteboards. The problem with a whiteboard is that you don’t always have one handy when you need it. They are large, static and relatively expensive. What you need is something that provides the benefits of a whiteboard but without the disadvantages. Magic Paper is that alternative. Magic Paper is made from lightweight, flexible plastic that can be rolled up and carried anywhere. When you want the whiteboard you simply smooth it onto a wall and it is held in place with static. You can then use it like a whiteboard and remove it when you are done.

    Hopefully these two products will encourage you to leave the PC behind, at least some of the time!

    Creating slick CSS

    Next we have some tips for you CSS coders. If you have grasped the basics of writing CSS and want to improve, then you should read the ‘7 principles of clean and optimised CSS code‘. As the title suggests this post provides 7 ways that you can improve the quality of your CSS coding. These include:

    • The use of shorthand
    • Avoiding hacks
    • Using whitespace wisely
    • Pruning any frameworks or reset code you use
    • Future proofing your CSS
    • Documenting your work
    • Making use of compression

    Bitter experience has taught me this is excellent advice. Even if it is old news to you it is worth reminding yourself of these points. It is easy to fall into bad habits.

    While on the subject of CSS, I also want to quickly mention a site called Conditional-CSS. This site provides a mechanism to deliver specific CSS to specific browsers without relying on hacks. It uses either PHP or C to achieve this and uses a very similar formatting to IE conditional comments.

    It would be unwise to become too reliant on this approach because it could cause problems as new browsers emerge. That said, it is potentially useful in certain circumstances and is worth checking out.

    Focusing on the wrong thing

    Talking of reminding yourself of best practice make sure you read Gerry McGovern’s post on Google and Yahoo! Gerry examines why Google makes 10 times the profit of Yahoo! even thought it has significantly less page impressions.

    Gerry argues that Yahoo! focuses too much on its products/website and not enough on the needs of their users. In essence Gerry is emphasising the importance of putting your customers first.

    Although as website owners and designers we should all know this, we often forget it in the scramble to add new features, and implement new technologies.

    Screencasting beginners guide

    Our final post today is an introduction to screencasting by smashing magazine. This is a subject I covered myself in show 122 and for good reason. Screencasts are becoming increasingly popular and it is important that we know how to implement them.

    The article looks at why you should make a screencast, tips for creating a good screencast and reviews of the different tools available.

    Its a good post that provides all you need to know to get started. It also provides some excellent tips that are worth taking on board. My favourite is…

    Editing may be an option, but sometimes its better to simply start over and have a nice flow to the production rather than piecing together snippets.

    Editing is for wimps :)

    Back to top

    Feature: Too Many Content Management Systems

    I know we live in a capitalist society. I know we are supposed to believe in choice. However, there are just too many damn content management systems. Another extract from the Website Owners Manual in this weeks feature.

    Back to top

    Review: Drobo And Backing Up

    Since posting on twitter about my new Drobo, I have received a number of requests for a review of this backup and storage solution.

    Back to top

     

    126. Scaling

    Posted in Classic shows on July 14, 2008 by Paul Boag

    In this weeks show we learn lessons from the botched iPhone launch here in the UK. We chat to Jeff Veen about the designer / developer relationship and Marcus talks about adding jingles to your website.

    Download this show.

    Launch our podcast player

    Watch the behind the scenes video (Part 1)

    Watch the behind the scenes video (Part 2)

    News and Events

    The Mobile Internet has reached critical mass

    This week saw the release of a new report by Nielsen Mobile entitled “The Worldwide State of the Mobile Web“.

    The gist of the report suggests that the mobile web is considerably more popular than many of us would believe. 15.6 percent of mobile subscribers in the US and 12.9 percent in the UK, use the mobile web regularly. In the US this equates to 40 million users. A substantial number.

    Interestingly the most common device used for accessing the mobile web is not a smartphone but rather the Motorola RAZR. This reenforces the answer I gave Wayne in last weeks show. I said we cannot design exclusively for devices such as the iPhone.

    With people like the VP of Google stating that the future of the internet lies with mobile users, there can now be little doubt as to the direction things are moving. This is especially true now that we are seeing unlimited data plans.

    Web Standards Curriculum

    A regular complaint I hear from students is that they are concerned about the out of date techniques they are taught at school or college. With many institutions still teaching table based design it is a legitimate concern.

    Fortunately they are not alone in this concern. Opera and Yahoo! have teamed up to produce a web standards curriculum. This curriculum teaches best practice in web design and is broken down into modules that can be taught either by themselves or part of existing lesson plans.

    If you are a student or educator definitely check this out. Hopefully you can get it adopted at your institution. Even if you cannot, there is nothing to stop you working through the course yourself.

    Working with designers

    Although our next post reads slightly like a rant (I should know what a rant sounds like!) it nevertheless communicates some excellent advice.

    It is a post aimed at clients and provides 12 tips for working with designers. Advice includes leaving preconceived notions at the door, be specific in your requirements and design for your customers and not yourself.

    There is no doubt that many clients serious misunderstand the role of the designer. However if I was a client reading this, I might find the tone hard to swallow. Despite that I would encourage those of you who work with designers to read this article. My favourite quote is…

    Just as writers are not just people who can type, designers are not just people who can use graphics programs.

    Web form design patterns

    Our final post this week is a survey Smashing Magazine have done on 100 popular sign up form. The idea of the survey is to give you a better understanding of what makes an effective sign up form.

    Of course, just because other sites do things in a certain way, does not make that the best approach. You should never blindly follow the crowd. Nevertheless this is a fascinating read.

    The post is split into two parts and contains information such as…

    • How the link to the sign-up form is titled
    • The placement of sign-up links
    • Whether the sign-up form is a single or multiple pages
    • How labels are aligned
    • How many fields are mandatory
    • What help and tooltips are provided
    • How validation is managed
    • How error messages are designed
    • Is it necessary to confirm the email address
    • Is it necessary to confirm the password

    The list goes on.

    If you are looking to justify design decisions you have made or need some help designing the perfect signup form, this is a great place to start.

    Just a quick reminder that the news we feature on the show is only a fraction of what myself and Paul Stanton post on the website. To get a more comprehensive view on what is happening in the world of web design, make sure you subscribe to our news RSS feed.

    Back to top

    Feature: Lessons to be learnt from O2

    I am not sure whether you noticed but this last week saw the launch of the iPhone 3G. It would certainly have been hard to miss it.

    I don’t want to add anymore to the endless discussion surrounding this launch. However, I would like to focus on a side issue. I want to look at how O2s website handled this momentous event and what we can learn from their mistakes.

    Back to top

    Interview: Jeff Veen on working with developers

    Paul: So I’m very excited to have Jeff Veen joining me today on the show. Good to talk to you Jeff!

    Jeff: Oh, it’s absolutely my pleasure. Thanks for having me!

    Paul: Well it’s really good to get you on the show. I’ve wanted you on for ages, but I haven’t had the guts to kind of approach you so I sent Ryan to talk to you instead. I feel vaguely like, you know, you get at school discos where you fancy a girl and you send your best friend over ’cause you don’t have the guts to do it yourself. Or is that just me?

    Jeff: Well I’ll tell you, I’m happy to have this dance Paul. It’s great.

    Paul: Right, well for those that don’t know you Jeff and don’t know your background can you just tell us a little bit about yourself and how you ended up in a situation where you ended up working for Google. You know, how did that come about happening? ‘Cause that’s what we’re going to talk about a little bit today is your experiences of being at Google.

    Jeff: Well, I tell you I’d been working with developers, as kind of more on the design side for quite a long time. Do you remember hotwired.com from Wired Magazine?

    Paul: Oh yes, definitely.

    Jeff: Way back when, right? Like we launched that back in 1994 and that’s really when I got started on the web, was coming over to Wired, working on their online properties like Hotwired, Webmonkey, and HotBot search engine, you know stuff like that. So I was with them for quite a while, they went through an acquisition and brought us over to Lycos, that big search engine. And then from there I started a company called Adaptive Path. Adaptive Path is a user experience consulting group in San Francisco. It was seven of us, we were all friends from the industry. We really focused on research, design, information architecture, usability, stuff like that. And I did that for a number of years with them and then finally convinced my partners that doing a product would be something interesting for us to try. We had done consulting. We had done some events. So we were kind of looking for the next thing to try. So I put together a small team of developers and some other designers and we made a product called Measure Map. That was a web analytics tool aimed specifically at bloggers. And just as we were about to launch it, we had done a bunch of work on it, Google gave us a call and said, “We love what you’re doing. We want you to come over and bring that to Google.” So we went through an acquisition there and that’s really how I got to Google.

    Paul: Ahh, I see. ‘Cause I remember very vividly Measure Map coming along and getting very excited about it and then it kind of disappeared.

    Jeff: A little bit, yeah.

    Paul: Yeah, ’cause you got swallowed into Google.

    Jeff: Well Google was very clear that they had a lot of respect for the work that we had done around designing Measure Map and wanted us to apply that expertise to their big Google Analytics product which had recently, sort of. They had acquired a company called Urchin, which had kind of an enterprise analytics package and they had made it free, and that had brought it to a whole new audience that really, sort of, didn’t quite understand how analytics worked. So we brought some of the best practices of design into Google and redesigned Google Analytics to make it sort of, kind of maintain all the power that it had, but make it much more accessible to a broader audience. So that’s really what we spent our time doing at Google.

    Paul: OK, so we saw Google Analytics and those changes that you made to Google Analytics appear a few months back, and you know, were very impressive. But I’m quite interested in what happened. How did that come about, and how did that process work? So you arrive at Google, you walk through the door of Google. Now, one presumes that there was an existing Analytics team already working. Is that right?

    Jeff: Yeah, that’s right. There was probably about twenty developers or so that were working on the Analytics application. Almost entirely all, sort of back-end engineers. As you can imagine, something of that size and scope, it’s a pretty impressive technical feat. The amount of data that they’re tracking every day, really just continues to blow my mind how much scale they have over there. So there was really, really talented engineers that had been working with the product for quite some time. That product had been around for a number of years. I think they were in version six of the product. But, to their credit, the Director of Engineering, a guy named Paul Moret, really knew that he had to change that application for this new audience that he had, sort of had started to grow by being at Google. So he was really behind the idea of completely rethinking. “Like lets,” he said, “Let’s start from scratch. Right, we have a lot of users. We have a really powerful product that I want to completely rethink how this happens.” And so, yeah, we really just rolled up our sleeves and sat down with him and his team and really sort of became one team. Got in there and made a lot of change. One of the things I think that really helped us be successful there was that we had a pretty robust methodology for user research that really resonated with a lot of the engineers that we were working with. It was really sort of. It was like I said, pretty mature, had a lot of data behind it so we could really show a lot of the work and helped us really get over a lot of the perceived subjectivity of design. So, you know, you can imagine this team comes in. We are a bunch of relatively technical designers, but still designers. And we sit down with these very, very technical engineers and we kind of showed them a process of how we were going to talk to a lot of the existing audience, a lot of the new segments of the audience, take everything that they told us and kind of boil it down into a lot of actionable next steps. And a way of prioritizing what features and changes we wanted to make. And so rather than us kind of going off, doing a bunch of design work and presenting it to them, we really involved everybody, or as many people as we could, in the process of how to change that application at its very basic level. So I think the results of doing all of that with the technical team was that we built a lot of trust between us. So that we could take some of their fundamental assumptions and really question those, but include them in that process so that there was a lot of give and take.

    Paul: I mean yeah, because your initial reaction when you look at a company like Google, that it is a very developer-centric company. So I was kind of half-expecting you to say that you encountered quite a lot of resistance to the kind of design changes that you were introducing, but from the sounds of it, because your methodology is quite scientific, for want of a better word, you know it’s very logical, etcetera that it sounds like it went down quite well.

    Jeff: Yeah, it did. It feels like we’re using the scientific method: doing testing and research and analysis and things like that. Ultimately though, so much of design is really, really hard to measure. Especially when it comes to matters of taste and perception and things like that. I mean, we can measure click-throughs and we can measure conversion rates and things like that, but ultimately the changes had to come from just being good designers. So having this relatively, kind of quantitative analysis that we did just allowed us to sort of speak on the same terms with the engineers. Have them trust us, and then let us make the changes we felt in our gut we should be making. So a lot of times I’ll be working with somebody who is very technical and they want to say, “Well if you make that change, can you show us some data that’ll prove that that’s the right change to make?” And almost never can I do that. Right, like we can do little tests and we can do some A/B testing and multivariate testing and stuff like that. And that’s good for little incremental changes but when you’re fundamentally changing an application it’s almost impossible to measure the accuracy of the decisions that you’re making. And that can be hard for somebody who really is a very analytical thinker, very quantitative in the decisions that they make, to sometimes kind of let go and say “No. You’ve go
    t to trust us. It’s just going to be better.”

    Paul: So were there other techniques that you used beyond providing data to kind of bridge that gap between the way that maybe designers see the world and that of developers?

    Jeff: Well I’ll tell you another thing that I really believe in, is prototyping rather than just drawing mockups. One of the benefits I had going into Google is that I had a remarkable team at Measure Map that were quite technical. A very good front-end developer who could do lots of JavaScript, AJAX, CSS markup kind of work. A talented Ruby developer, and then a guy who was great with Flash and ActionScript. So bringing this team together, all of them good designers, but all of them with very technical backgrounds, we could come in and very quickly start to realize what a redesign might look like. Also the thing that really helped us was that Analytics internally had a very well-developed API. So we could say “All right, show us how this API works, then we’re going to immediately start experimenting on top of it using real data. We can bring users in for usability tests and they can see their data in our prototype in a matter of weeks, rather than months and months of development.” So having that separation between design, front-end and back-end, through a robust API allowed us to prototype so quickly that they could immediately say, “Wow! Look at all the work this team is doing!” Rather than us standing in front of the projector pointing at Photoshop comps or something and saying “Imagine what it would be like to click here.” We just had a thing working that people could log into anytime.

    Paul: Yeah, I can really understand how that would make an enormous difference. So I’m presuming that you talk about your little team of people that went in there and started doing prototyping and stuff like that, but obviously you’re going to want to engage more with the developers that are there. I mean, the traditional danger has always been that as a developer and a designer you work independently. The designer does his thing. He hands it over the partition to the developer. The developer goes away and does his thing. Now I presume you wanted to avoid that. So how did you establish that working relationship? How did you end up working closely together?

    Jeff: I have almost no interest in that sort of “waterfall method” where somebody goes off and does research, hands it off to designers, designers then do some of their magic, hand it off to developers. I’ve never been successful at doing that, primarily I think because I learn so much from the process of building things. So again, it was just, really one of the first things we did was invest a lot in getting the teams to trust one another. And that meant really just spending time with each other. So that meant almost every day just scheduling some time in the conference room for us all to kick around ideas, to look at some of the existing work that they were doing, some of their future plans and just spending a tremendous amount of time with them. We also just had our desks right next to the development team. We were embedded, we were just right there. So we felt like part of the team. We’d all go eat lunch together. I mean simple things like that just make the development process so much more, so much easier because there’s real people working with each other rather than faceless “other people” handing specs over. So putting a lot of time in: absolutely crucial to success in a process like that.

    Paul: So obviously you got to work with a great group of people over at Google. Some of the most talented developers in the world I guess. So I’m really interested to know, what was it you learned from them? You spent all this time with them, what was the kind of thing that you took away as a front-end interface designer what did you learn from this amazing group of developers?

    Jeff: Well, a couple of things really. I think the thing that struck us the most when we first got there was just the enormous scale of everything. Like Google, as you can imagine, Google has lots and lots of users, but they have a tremendous diversity of users too, literally from around the world. A statistic that we throw out all the time is that seventy percent of Google’s traffic comes from outside the United States. So the audience that we were used to designing for is really the small minority of people, and in fact the rest of the world is where all of the products are being used. So we had to think about that diversity of audience even in the design decisions that we were making every day in that everything that we were designing was going to be translated in up to forty different languages. So that was probably the first thing that really brought our attention. The second thing was the unbelievably high standards that Google had for their products. Like you said, I totally agree, they’re some of the best engineers in the world. They have coding standards. They have testing standards, QA standards that were absolutely remarkable. I just learned so much about how every little detail fits into place to make a product that’s as robust and as really scalable and useable by a global audience that Google has. It was really like I got a crash course in some of the best computer science education I could possibly ever ask for.

    Paul: Very cool indeed. So for the designers that are listening to this now, the front-end people that maybe are working with developers day in and day out and secretly behind their backs are having a bit of moan about those developers, they’re finding them quite tricky to work with, what advice would you give them about interacting and working with developers?

    Jeff: Well, like I said, you’ve got to spend time in the trenches with them. That I think is just the most obvious thing that I can recommend doing. For both sides. It was hard for me to trust a lot of developers, like “Oh, you’re only concerned about your servers, you don’t care about users at all.” Which of course is completely false, but that’s an inherent bias that I would have. So again, spending that time: incredibly important. I think one of the things that I try to educate the most while I was there was that the level of detail, the care, everything that goes into the coding standards that engineers have, we have that same standard for the interfaces that we build. So I think sometimes, and I hate to generalize across developers, because I’ve worked just the entire spectrum of developers. One of the themes that I hear from time to time is that design is something that kind of happens at the end. Like “We do all the hard engineering. We get all of these systems in place and write all of this code and then we need some designers to come on and put the interface on so that we can actually launch this thing.” That I think cheapens a lot of the work that we do, and it’s a little bit demeaning for the discipline of design, of user experience. So I think we have biases on both sides and that frankly understanding more about what goes into the process both from a front-end and a back-
    end point of view is kind of what brings us all together.

    Paul: So if you could communicate one thing to the developers, one lesson, the question the other way around I guess. I guess in some ways it’s the same answer, isn’t it? It’s kind of stick with one another.

    Jeff: Yeah, a little bit. Also there’s some really simple techniques that I’ve used, for example: even before we started we’d schedule a usability test with the existing product and get the engineers into the room behind that one way mirror and we would just watch. And we would watch people flail around with the interface and struggle and get frustrated and push the keyboard away. I mean that’s just golden. People see that and they’re just like, “Oh man, we’ve got some work to do.” So making it as clear as possible, what our users are trying to do, how we can all collaborate together to help them: incredibly, incredibly important. That said, it wasn’t, you know when I did consulting at Adaptive Path I was inside lots of companies. I worked with some of the biggest companies in America and saw inside of them and, to be honest, Google is truly a user-centered company. I was just so impressed with that. Broadening that idea of user-centered technology development is something that we worked on. Making it more of a balance between front-end and back-end is more some of the things we worked on. But ultimately I think Google really understands that putting users first is the way to be successful. Just look at the search results page with it’s very simple but incredibly effective advertising techniques, and you know, Google never had a front page that was full of the sort of portal design stuff that Yahoo! and other companies have done. So really, it was very fertile ground for the kind of work we wanted to do when we got there.

    Paul: Very interesting. I’ve just thought of one other question that I get asked a lot from people looking to get into web design: they say, “So what am I better off doing, you know, where’s the best place to work? Is it in the large company? Or is it doing something in a small company by yourself?” Now you’ve obviously done both of those and there is no definitive answer, but what would you see as the pros and cons of a large company in comparison to working somewhere smaller like Adaptive Path?

    Jeff: You’re right, in my career I’ve got swung back and forth between big and small. There are definitely benefits and drawbacks to both of them. In the bigger companies I think just inherently things move slower. Now, I mean Google is renowned for it’s “bottom-up culture” and good ideas are always emerging from people taking their twenty percent time. None of that is a myth. That all really happens. But at the same time, like I said, when millions of users, or hundreds of millions for some of the products. You just have to take a lot more steps, and what that does is it increases the distance between the idea that a designer or developer has, and a user actually seeing that idea. And one of the things that I love about this sort of entrepreneurial startup environment is that you can think of something, you can try it out, you can get it in front of your users. You can do that in an afternoon. And you can’t do that with a product like Gmail or Adwords or something like that because there’s so much inherent infrastructure and risk, things like that. I think it’s incredibly worthwhile for people to have both experiences, and frankly see what they like best. One of the things I really have learned in my career is that there are people that like to start things, and that there are people that like to run things. And there is no inherent judgment between the two, but once you understand “Ooh, I love having a big system and having that system run perfectly, and putting all the things in place to keep that, you know.” And that’s fantastic. I’ve learned, in my career, that I’m kind of on the other side. I love starting with nothing and building up something, and at some point I need to hand it off to somebody who is much better at running and maintaining, right. So those are the kind of things you learn by doing a lot of very different projects and product development and stuff like that as your career kind of goes on, I think.

    Paul: So you’ve left Google now? So what’s the next step? What are you up to at the moment? Let’s finish on a looking forward note. Where are you going? What are you doing?

    Jeff: I was at Google for just over two years and left about six weeks ago, and to be honest I’m spending a lot of time right now cycling and trying to sleep late, and things like that. I tell you it’s a tremendous luxury and I’m not taking it for granted at all. The immediate next thing is that I’m organizing a little conference with my colleague Bryan Mason, who I have worked with at Adaptive Path. He and I are doing a conference in San Francisco in August about starting companies. Yeah, as I was leaving Google I was thinking, “Well, what should I do next? What would be interesting?” So I talked to a bunch of my friends who have been entrepreneurs, or who are now investors and I just asked them, “Tell me your story. How did you get to where you are?” And I found those stories so interesting that I thought, “Man, we’ve got to share this. This is great.” And I thought, “Well, I could do a podcast or something like that.” But then I thought, “I love getting people together and having sort of a community feel.” So we thought: we’ll get one day, San Francisco in August. We’ll get everybody together and we’ll just have these conversations. So I’m really looking forward to it. It’s called “The Start Conference” and you can find it at thestartconference.com. That’s what we’re doing now.

    Paul: Excellent stuff. Thank you so much Jeffrey for coming onto the show and talking about that. The issue of designers and developers working together is something that’s really important and I think there’s a lot of work still to be done, and it’s good to see that there are people out there that have got it right and are going in the right direction.

    Jeff: I appreciate that Paul.

    Paul: Thanks for your time.

    Jeff: Thank you.

    Thanks to Todd Dietrich for transcribing this interview.

    Back to top

    Listeners feedback:

    Adding a jingle to your site

    Chris writes: A client of mine wants to incorporate 4 second jingles at various points on their website, triggered on page load, to reinforce their servicing brand. My first reaction is that this could get annoying but was curious as to your thoughts on the use of audio on the web.

    I don’t think that there is any set ‘rule’ here but basically I would agree 100% that you shouldn’t do it because it will annoy the hell out of the site’s users.

    There is an argument that audio branding can be included if th
    e user only has to hear it once. However, I would dispute this as well for the following reasons:

    • It may well still annoy (and therefore have a negative effect upon) the site’s users
    • Users aren’t expecting it and it could embarrass them in an office environment
    • Quite a lot of users will have the sound off. Therefore, if you decide that the audio is only an ‘add on’ for the brand then you may as well conclude that it’s not necessary at all.

    I have talked about audio on website before and reached the conclusion that, even though technology and bandwidth makes it more doable, it’s the wrong medium for audio. I think I likened it to having a soundtrack while you’re reading a book – it’s just wrong!

    Of course, there are no doubt exceptions to this rule – really well thought out and produced audio indicators on a web app for example – but, generally speaking, audio branding on a website will have a negative effect. If your client is insistent, try and persuade him to include a video download on the site where audio will certainly work.

    Fixed or bespoke pricing

    Jon writes: We are a small web design and development company (4 people) and have tended to concentrate on higher value bespoke work. We are probably about to merge with another slightly larger company in a neighbouring town. This other company have traditionally aimed at a somewhat lower value market.

    My question is about pricing. The other company operate to a very structured price list (£x for a 5 page brochure site, £Y for a basic ecommerce site, £Z for an ecommerce site with knobs on etc). We have always priced each project individually using a mixture of time costing, guesswork, and a “how much can we get away with” approach.

    Do you think that a merged company approaching a wider market and value range would be better to adopt one approach or the other, or continue to do both? Would the existence of one approach damage the ability to operate effectively at the other end of the scale?

    I guess the big question here is – are you going to remain as two different entities with some shared resources, or are you going to merge more fully and share work between the team no matter where it is sourced from (i.e. will one of their designers work on a future project from one of your existing clients)? If it is the former (which I suspect it isn’t) then I would keep the two pricing models the same as they are. I wouldn’t try and hide the fact that the two companies have ‘merged’ though, just explain that there are two teams delivering different services.

    However, if the two companies are merging more fully, then I think this is actually fairly fundamental stuff. It’s almost like you’re all starting again and need to write a business plan. I think you would be opening yourself up for much criticism if you tried to operate both pricing plans.

    I suppose other questions to you would be:

    • Which pricing plan is most effective (who is making the most profit)?
    • What does each company’s order book look like? I.e. have you just signed a massive contract at your higher rates?

    This is interesting stuff and I’d like to know how it works out. I suppose the biggest unknown for me (that may well answer all of my other questions) is that I don’t know the reason for the merger in the first place.

    Back to top

    118. Geo

    Posted in Classic shows on May 20, 2008 by Paul Boag

    On this weeks show we look at geocoding, Tom Coates talks about Fire Eagle and find out how we achieved the tabbed menu effect on the Headscape website.

    Download this show.

    Launch our podcast player

    News and events

    New tools for web designers on the way

    A few months ago the guys over at clear:left put up a holding page for an application called Silverback. Exactly what Silverback was became a topic of much discussion and a considerable amount of buzz.

    This week Andy Budd has finally revealed exactly what Silverback is on his blog. He describes as…

    An OSX application to help people run their own low-cost Guerrilla usability tests. It captures screen activity, records audio and video from your built in iSight, and then composites it into a handy Quicktime movie for later use.

    I have been fortunate enough to play with an early beta and I have to say it’s a great idea. It has the edge on other "screen capture” programs because it is designed specifically with usability testing in mind. For example, you don’t need to export the movies as soon as they are recorded. You can save them until you have finished a day of testing when more time is available.

    If you ever do user testing get yourself over to the Silverback site and signup for the beta.

    It would of course be remiss of me not to mention GetSignOff.com as we are on the subject of tools for web designers. Like clear:left Headscape have been developing an application and this week we provided our first walkthrough showing exactly what it does.

    In essence GetSignOff is a web application that allows you to present designs to clients in a more professional manner, manage the feedback you receive from them and organise the multiple iterations of each design.

    To really get a sense of what it does you need to view the screencast so be sure to check it out.

    Effective online delivery of video

    There can be no doubt in anybodies mind that online video is huge. It has taken a long time to arrive but with broadband so widespread it is now a reality. Increasingly users are expecting video content from websites and it is up to us as web designers and owners to deliver.

    Delivery is fairly straightforward when you can use sites like YouTube or Vimeo. However, that is not always possible. Constraints on size and quality can make these services unsuitable. Not to mention their over demanding terms of use. So what do you do if you are forced to host and deliver video yourself?

    My advise is to read an excellent article on the Digital Web Magazine that looks at the various approaches for delivering video over the internet. It explains concepts like progressive download, RTMP streaming and HTTP streaming. It is a superb source of information for anybody who has to host and deliver their own video content.

    Some Javascript slight of hand

    Our next story is some slight of hand by Robert Nyman.

    I find myself increasingly using Javascript to show and hide content. However, being a well behaved standards designer I have to be careful how I build pages. I avoid hiding content with CSS because if I do and Javascript is disabled, users have no way to show the content again. Instead I use Javascript to hide the content so that if it is disabled the hidden elements will show by default.

    The downside is that you can get flashes of content because Javascript has to wait for the page to fully load before it can hide content.

    Fortunately Robert has come up with a nifty little workaround where he uses Javascript to load a CSS file, which in turn hides the content. This happens before the body has been loaded avoiding the flash of content.

    If like me you occasionally suffer from content appearing when it should not, then bookmark this approach for later use.

    Overcoming creative block

    Our final news story today is a post on overcoming creative block. Creative block is something we all suffer from whether our job is perceived as being a creative one or not. Every job requires some degree of creativity and we all know what it feels like to stare blankly at a computer monitor unsure of where to begin.

    This post provides a list of excellent tips on how to overcome brain freeze from going for a walk to throwing away the piece you like most. It really is a superb read. Another one to bookmark for the next time your creative juices fail to flow.

    Surprisingly he has missed my number one technique, sitting on the toilet… or is that just me?

    Back to top

    Feature: Location Aware

    The web is full of exciting innovations at the moment. However, it is geocoding that personally excites me the most. In this weeks feature I explain what it is and why I believe it offers so much potential.

    Back to top

    Interview: Tom Coates on Fire Eagle

    Paul: Ok, so joining me today is Tom Coates from Yahoo. Good to have you hear Tom

    Tom: Nice to be here

    Paul: So I’ve just been hearing from Tom that he’s got a massive line up of interviews to do for a product that he’s been involved with called Fire Eagle. So he’s talking to the Guardian, the BBC and lots of important people, but thank you for sparing a few minutes to talk to us too. We’re very honoured.

    Tom: No problem at all.

    Paul: So, lets kick off for those who haven’t come across Fire Eagle before. I think you talked about it at dConstruct last year.

    Tom: Yes

    Paul: That was when I first heard about it, perhaps you could tell our listeners a little bit more about what it is, and what it does.

    Tom: So Fire Eagle is a service that helps you share information about your location, online. So that’s both for people, and more importantly for different sites and services. The other side of it is that it sort of fixes a problem with the development community for the use of applications that use your location. In that it makes that process much easier. So in principal, it means that from a user’s perspective, you can capture information about your location and use it in lots of different places. And from a website owners perspective you can start to think about how your service can respond to someone in the world without having to do a lot of donkey work.

    Paul: So it’s not primarily, in itself, like another web application like Twitter where you’ve got to sign up for and take part in it? I
    t’s more of a API framework type of thing.

    Tom: Well, when you think about it, it is both, because if you think about it as a place to sort of store information about your location. We give you the tools to go in and update that information, decide who to share it with, and manage that information. So in some ways it’s like your location preference page, which helps you control that information. So yes you do sign up for it, it uses a Yahoo ID, the same one you use for Upcoming and Flickr, but really, once you’ve started capturing your location or sharing it with particular services, you don’t really need to come back. We’re not trying to build a sexy fun service for day-to-day use, but we’re trying to make something that makes it easier for you to build, and other people to use, services.

    Paul: OK, so how exactly does the service work Tom. I’ve seen other location based stuff where you have to do horrible things like enter grid references or terrible stuff like that. How do you use Fire Eagle?

    Tom: What you do with the site, is you go to the site, and you log in with your Yahoo Id and you do a simple terms of service thing, which asks how often you want to be reminded that you’re sharing your location. From that moment on you’re up and running. The simplest thing to do, is go to a web page called where am I, and you can type in your address and, we will work out where you are in the world, and we’ll plonk it on a map. Now that in itself isn’t terribly interesting. So the interesting thing about it, is that we’ve opened up the API’s so that anyone in the world can build something that could update your location, and anyone in the world could build something that could use your location. So we have an application gallery, and you could go along to that, and on that at the moment there are services like Navizon, which work out where your location is by nearby wifi signals. Or Loki which is from SkyHook the same people who power the iPhone location thing, and Dopler and all kinds of stuff. You can tell those services that you’re OK sharing that information with Fire Eagle. So I have an application on my phone at the moment from Navizon that works out where I am every 10 minutes and tells Fire Eagle where I am. So that location just sits in Fire Eagle and then I can decide to share it with people. So as an example a plug-in for movable type that Ben Trott has built and that means that you can put on your blog, a little map of where you are right now which is quite fun. What we do is, to help maintain your privacy, you choose which services you’re comfortable with sharing your location with, or get an update from. You can say to what level of granualarity you’re comfortable sharing with it. So you can say, just share my city, or my state (if you’re in America) or your neighborhood or your exact point. Then you can hide information at any time, or delete all information in the system.

    Paul: Oh, OK.

    Tom: So basically it means that you would go and find one really good way to get where you are, or lots of little ones all around the place that compliment each other, and sort it out into the middle of this little repository of data, that you can then say, yes I’d like to use this on Flickr, or on Facebook, or on moveable type, or wherever.

    Paul: So the way you’re describing it is that there are multiple entry points into it, where you type in your exact location, weather it’s your mobile phone updating it?

    Tom: Yes

    Paul: You know I even noticed from looking at the site that you can now Twitter your location in.

    Tom: Yes

    Paul: And that there are multiple output points, where it’s going to Movable Type, or to wherever else.

    Tom: Yes

    Paul: So what type of things are we going to see with this. What are you expecting people to develop? Is there any cool stuff at the moment that you can tell us about?

    Tom: Yeah, well there are a fair number of cool things that have already come out, which is kind of interesting. I mean one of the things on the engineering side – so there is a bit of a problem with location based services, and everyone’s been talking about it for a very long time, you know they have all these kinds of things that you couldn’t find friends more easily, or find out things about your neighbourhood or whatever. And the problem is, and has always been, that it’s quite hard because what you have to do is, every time you want to use an application like that, you have to install another application on your phone, or go through another extended rigmarole about how to do it. So our plan is that we take that away, so what you basically do is you find any piece of software that gets your location usefully, and you install it, and it updates Fire Eagle. So from that moment on any application in the world that is Fire Eagle enabled can go and get that. So any website in the world could respond to where you are, without ever having to build the thing that works out where you are. So some examples – Navizon as I said is this lovely little application that runs on most mobile phones, captures your location. There is a thing called Fire Bot, which is a Twitter Bot, and on that one you can do a Twitter direct message, with a text string of where you are. So you can say I’m in San Francisco, or I’m in London, or I’m in.. as I am now, at Yahoo’s offices at 125 Shaftesbury Avenue. And you can type that in and you can then share that with all the applications you’re comfortable with. We’ve also taken Cell ID information, so if you have a mobile phone, many of those on a technological side expose the Cell ID. So that’s the tower, or mobile phone mast kind of thing. Quite a lot of people are doing interesting mappings based on that. That in particular is at a very early stage so we don’t actually get much good information from that, but, you know we do take in all different types of data. You could have a GPS log coming from a mobile phone, or anything that could get long/lat coordinates, or anything that could get text string of the place you’re in. On the other side, is the things that could use it, which is where the fun starts. There are all kinds of things that people have built. And more coming. So there is a service that Leonard Lin, the founder of Upcoming made for us, called FireBall, and FireBall was particularly useful in San Francisco in the last couple of weeks because of the Web 2.0 Expo that was out there.

    Paul: Oh yeah.

    Tom: And the idea with that was you could either send a Twitter message of where your location was, or if you were getting it from FireEagle, it would automatically use that. And at any point you could say "Where are my friends” and it would go to Twitter, find out all your Twitter friends and plonk them on
    a map for you. And you could do that on the iPhone as well because it would send you a file that could then be opened by the Google maps thing. So you could literally call your little maps thing on the iPhone and it would say "Here’s where all your friends are”, which is really lovely, and really nice, because it’s all about your friends there.

    We’re building a Facebook App, this is no particular secret, we’ve talked about this before, and its going to be one that means you can decide to share your location on Facebook with your friends, which is going to be quite fun. A guy called Simon Willison who I used to work with, who has built a thing called WikiNear. There are over a million geo-coded articles in Wikipedia, which basically means someone has put in the longitude and latitude of where the thing talked about in the article is. So Simon’s thing is a little web page for your mobile phone, and you bring it up and it says "Here are the 5 nearest interesting things to you”.

    Paul: Cool!

    Tom: Which is pretty fun, so you can wander around London and here’s the British Museum and you can click on that to go to the media wiki page to talk about that.

    Um, there are other things like that, I mean LightPole is a little company that we’ve been working with. They’re doing things like local services around you, which again is mobile phone focused. A company called Outside.In, they do things like try to work out where all the blog posts and news stories are about, and they can bring that information to you if they know where you are – and they are going to get some of that information from FireEagle – which is really cool. So as I said we’ve got this Moveable Type thing. So there are all kinds of stuff that is going on at the moment. We build these wonderful little widgets, which I really like, they are for OS 10, and one of them is a little updater. You can type in your location, press a little button and it will update it to FireEagle. One of them tells you the weather where you are right now. So if you travel a lot, it will give you the weather forecast of where you are. And one of them shows you nearby flickr photos, so it just goes and gets those geocoded photos from Flickr and gives you every day a little photo montage of all the cool things that are going on around you. So lots of interesting new uses really.

    Paul: It’s interesting you mentioned Flickr. I mean you can imagine the reverse of what you just described with Flickr, so if your location is been taken each time, it would know the location where you took that picture and geo-code that picture on Flickr. Is that the kind of thing that you’re planning to do?

    Tom: I mean there are a lot of really interesting uses based around geo tagging. So whenever I write a blog post, it would be really awesome if my Moveable Type blogger could go and look up on FireEagle where I was, and say "This article was entered here”. So you could say "What do you think about Gordon Brown in Edinburgh” as apposed to "What do you think about Gordon Brown in London” or "Wales”, and that would be really fun as a good way of slicing through this enormous amount of blog posts that are out there.

    Twitter messages as well, that would be lovely – it would be really great if every time you wrote a Twitter message they went and grabbed your location, and you could say, well I want to explore the public conversations going on in my neighborhood right now. That would be lovely. Um, and with Flickr as well, when you click on a photo on your phone, uploading it immediately. If you havn’t got the location on that device, being able to get it from FireEagle would be really useful. And you know obviously whatever amount of information they can get, so perhaps FireEagle only knows you’re in London, that’s still useful – you know you can still help people find photos just because they are in London. Or if they are at an exact point that’s also good. The only thing about Flickr is that often people take photos and upload them later. And at the moment because we want to make sure that we’ve thought about all the implications, and we don’t want to weird any one out, we’re making sure that we don’t keep any ones history.

    Paul: Oh Ok

    Tom: So it’s literally just your current location we look after for you.

    Paul: Ah, that’s good.

    Tom: Yeah we’ve talked to a lot of people about this, and we have been very careful about the privacy and control. These are the two watch words of the project. We are incredibly conservative, we don’t want to worry’s any one out. So at any time you can press a button to hide your information. Information will still come into FireEagle, but it won’t go out. Or you can delete all your information on FireEagle at one time, so we won’t keep any records at all if you do that. At the moment we don’t keep any location history at all – any tracking, or location history there. And we even by default will send you an email once a month saying "Are you still OK sharing”, and if you don’t reply to the email, or you don’t click on the link in the email, then we’ll stop immediately. It’s just so there is no risk of you doing anything, you know, accidently, exposing it in ways you’re not comfortable with.

    Paul: I mean when I first heard you talk about this it struck me as hugely exciting, that location based information is an area that I’m massively excited about. And I think there is so much potential to add a new level of context, you know, on the data that we see on the web. Something that has been very much lacking since the beginning. And there is so much potential here, for pretty much anyone listening to this show, whether you’re a design or a web site owner.

    Tom: Yeah

    Paul: So where would people start to find out more information about this. Where’s the good place to begin?

    Tom: OK, so one of the parts of the project that took surprisingly the most time, was actually making sure that the documentation was really good. At the moment it’s an invitation only service, so we have a few thousand people using it and testing it at the moment. We’re opening it up to more invitations pretty regularly. It’s only been out in the wild about 6 weeks. So if you’re interested in using FireEagle, just go to the website, put your email address in the box, and over the next few weeks we’ll be sending out more invitations.

    Paul: And what’s the website address?

    Tom: Oh, it’s FireEagle.com

    Paul: OK

    Tom: So that should be nice and easy to find. On that site, if you can get an invitation, and if anyone spots us around the
    place, ask us, because we have little cards we can give out. There is extensive documentation on how it works, that really falls into two big chunks. Partly it’s this use of this new standard called OAuth. Which is a really good way, meaning sites can talk to each other on behalf of users, and you can set your preferences around that. So getting your head around OAuth is really useful because so many services – I think Google and Yahoo have both announced that there is going to be support for OAuth as a standard now. So that’s really great, we’re all really happy about that. And the other side, is the FireEagle APIs themselves, which are very simple, sort of three main ones. 1. Where is the user. Again, all of this only happens if the user has given explicit permission for this service to see it.

    Paul: Sure

    Tom: One is update the location of the user, and one is ambiguous query, so such as, you say you’re in London, which is great, but there are hundreds of London’s in the world. So there is one service where it says "which London” and you can say "this one”. So they are the three core queries , it is very very simple. We have another couple of ones, for particular web services, to bring back users of my application within that particular area, like SOHO or London.

    Paul: Yep

    Tom: Another one, bring back the hundred who have updated their location most recently. So just think, just to make it easier for developers to build useful services.

    Paul: Cool, that just sounds really exciting, and I can’t wait to see some of the stuff that is developed in the future. Tom, thanks so much for coming on the show.

    Tom: No problem, I hope that was useful

    Paul: That was incredibly useful, and I’m sure there will be a lot of people hounding you for invites, well there probably already are thousands of people hounding you for invites. Have you got any idea when it’s going to go "Full Open”?

    Tom: Yes, I do have an idea when it’s going to go full open.

    Paul: But you’re not going to tell me.

    Tom: Well its within the next couple of months. We want to make sure we’ve had conversations with some really interesting people, so that we have some really cool stuff to show off at the same time. So you’ll just have to wait and see on that line I’m afraid.

    Paul: Oh, so that’s really exciting and thank you again for coming on the show.

    Tom: No problems. Cool.

    Thanks to Nathan O’Hanlon for transcribing this interview.

    Back to top

    Give Away: Fire Eagle Invites

    So as we mentioned in the interview, Fire Eagle is currently in beta, but if you can’t wait for the full release and want to get playing with it right away your in luck. We have around 20 invites available for boagworld listeners. To claim one, e-mail [email protected] with the subject heading of "Fire Eagle Invite" and Ryan will send you your code, while stocks last…

    All tickets have now been claimed!

    Back to top

    Listeners feedback:

    Tabbed menus?

    David Bridle writes: How did you get the tabbed menu to work in the headscape website?

    When writing the answer to this question, it turning into quite a lengthy explanation. So I wrote a blog dedicated to it, which can be found here.

    Back to top

    114. Forum

    Posted in Classic shows on March 4, 2008 by Paul Boag

    On show 114: Should designers stick to designing? What goes into a usability test script, and we talk to Alex Mogilevsky from Microsoft about Internet Explorer 8.

    Play

    Podcast: Download (32.8MB)

    Download this show.

    Launch our podcast player

    News and events | User testing scripts | Alex Mogilevsky from Microsoft | Listener emails

    News and events

    Before we look at the news I want to share a bit about boagworld. There is so much happening with both Boagworld and Headscape. If you are interested read my random news post.

    However, for now I just want to mention the forum. For a while now the forum has been experiencing technical difficulties. Fortunately that is behind us and I want to encourage you all to check it out.

    I can honestly say that the boagworld forum is the best forum I have ever been involved in. Not because of anything I have done, but because of the awesome people on there. They are so amazingly helpful and I have never seen a flame war or newbie bashing.

    Please take a few minutes to sign up. Even if you don’t regularly participate, you can at least add your location to our listeners map :)

    Instant mobile sites

    I want to mention a website called MoFuse.

    I have talked before about the importance of the mobile web. With a new generation of internet enabled phones we need to “moblise” our sites quickly.

    MoFuse makes the process painless. It takes your RSS feed and tailors it for different mobile devices. For example an iPhone user would receive a different experience to a WAP user.

    As well as RSS you can add static pages and customise the design. It is an impressive service and the basic setup is free.

    I should stress that this is not an ideal solution. It does not replace a carefully crafted mobile site. However, it is a good starting point, especially if all you want is a mobile version of your personal blog.

    And yes, I did create a mobile version of boagworld (m.boagworld.com) that allows you to stream the podcast on your iPhone.

    Layout, do’s and don’ts

    My next news item is a post by Andy Rutledge on bad layout conventions. He highlights two problems.

    The first is three column layouts where the main content is framed by two side columns. Andy argues this creates several problems and demonstrates how things could be improved by taking the Apple store (which uses this layout) and redesigning it so that the two side columns are to the right of the main content.

    The second problem is organising different sections of information into long vertical columns of varying lengths. This requires a lot of scanning and scrolling. Again, Andy demonstrates the problem by fixing it on an example site. He uses a horizontal approach where the sections span the width of the page rather than being sorted vertically.

    At the same time Andy posted this article, the guys at Web Designers Wall posted some inspirational grid based designs. Interestingly I saw the Web Designers Wall post first and was inspired by the list of sites. However, after reading Andy’s post I returned and noticed the problems Andy has identified. Suddenly my opinion was changed.

    I recommend checking out both posts. They will change the way you view layout.

    jQuery for designers

    At the beginning of the year I said designers should learn Javascript. I have also said in the past that we should avoid frameworks and learn Javascript from scratch. However, Christian Heilmann challenged this assumption in our recent interview.

    This week I found a tutorial aimed at introducing jQuery to designers. What I read blew me away. Not only is jQuery small (approximately 29kb) it also reduces the amount of code I need to write considerably. It will quickly earn back those extra bytes.

    However, what I love most is that it reads like CSS. To find elements by tag, class or id you don’t use getElementBy as you would in Javascript. Instead you specify it in the same way as CSS using # . and tag names.

    Finally, it makes animation easy. You can slide things around, change their opacity and much more. Check out the extensive documentation to learn more.

    Although I haven’t used it on a project yet, it is looking hopefully.

    Back to top

    Feature: User testing scripts

    I have talked before about the benefits of user testing. I have discussed how to user test on a budget. Now, I want to look at some basics that go into every usability test script.

    Back to top

    Expert interview: Alex Mogilevsky

    Before we get to the interview with Alex it is worth saying that he contacted me a few days after this interview saying that it could be out of date by the time of broadcast. He was of course correct as last night Microsoft announced that IE8 will be standards compliant by default. Although I still do not have a problem with Microsoft’s previous position, I know a number of people disagree with me. It is encouraging to see Microsoft listen to the community and change its approach accordingly. I am sure they will have to endure criticism from other quarters for this decision and we need to encourage them.

    Paul:Okay, joining me today is Alex from Microsoft. Now Alex have you noticed how I avoided trying to say your surname there? How do you pronounce it? Ah well I haven’t got a hope have I? I’m doomed. But it’s good to have you on the show anyway. Now it’s really nice of you to come on. We thought it’d be good to get you on the show to talk a little about IE because I understand that that’s what you’re currently involved with. But before we get on to that can you give the listeners a bit of a background as to who you are and what you do and kind of how you ended up being involved with IE

    Alex: Uh yeah I’m at Microsoft for about 15 years now and I worked on all kinds of projects from word to publisher and IE now. I first worked on it at the end of A5 so it is my, technically it is my fifth version of IE although the real big one that I worked on was IE 5.5.

    Paul:Oh okay.

    Alex: I have a reason to not like .5 version (of IE) because that was really a big project for me and I have to explain that it was 5.5.

    Paul:(Pauls laughs.) Yeah it may be a .5 version number but it was massive to you. I get the idea. Well obviously um part of the reason that we got you on the show today is to talk about version targeting. But we also want to talk about a lot of different things as well. How you see the browser developing in the future? What the futures of browesers generally is? But let’s kick off with the subject of version targeting. Did you expect the kind of level of reaction that you got off of the back of this?

    Alex:It was surpising to see huge negative reaction from people being published. I don’t know there were probably hundreds and hundreds of comments on IE blog. It’s hard to find the positive one. When you talk to somebody who is actually creating content for the web I get a little time to explain the concept is, everybody agrees that well there is some content there, there has to be a way to figure out what the author was thinking when they were creating it. So you should be kind of marking that content with some clue for the browser to render it properly. It is quite amazing to me that people who disagree with version point fingers at Microsoft. That it is totally Microsoft’s thing.

    Paul:I mean it’s interesting isn’t it, cause one of the reasons that people said that Microsoft introduced versioning was because there was such a kind of kick back over IE 7 breaking the web, as it has been put. Um Would you think that IE 7 has been perceived as a failure within Microsoft? Many people seem to have thought of it, you know, there is this perception that is the way it is perceived in Microsoft. Is that actually the case?

    Alex: Well. It depends on how you define failure. I think from one point of view it didn’t do enough from another it did too much. So go with what everybody ask us. We go and do more standard, and we didn’t get standard enough. It’s not 100% of standard but the little that we did broke so much that we really learned the hard way that we can’t make any progress without doing something about not breaking exsisting web.

    Paul:Do you think that with the kind of issue, you know, one of the main comment that I’ve read about the version targeting is the fact that by default um, that you have to kind of opt into version targeting in effect to opt out of it. That by default it will render as IE 7 for time and memorial. Do you think that that’s likely to change before the release of IE 8 or is Microsoft fairly set on that now?

    Alex: I don’t think we have any other option. What would that option be, is go and visit every website on the web and opt it out and then carefully figure out which ones are actually designed to work with IE 8 even though they couldn’t have possibly known what it means.

    Paul: So do you think that it would be too much of a burden on people out there creating websites, that when they’re seeing a problem and they’re saying why does IE 8, you know, break my website. Telling them to just add another single line of code, you know, do you think that’s asking too much?

    Alex: Well I think any assumption like assumes that every site out there actually has a person who understands why it is what it is and is actually capable of fixing them. The vast majority of people publish and they don’t know what a version is. They don’t know if their site is in Quirks mode or standards mode. They look at this as a browser bug. But, maybe there is something that is relying on a bug in previous browsers where old browsers were compatable in being non-standards.

    Paul:I’m in agreement. I think you’ve come up, I mean it is a compromise what you guys have come up with, but as compromises go I think it is a very good one. I think it’s much more important to keep the web an environment that anybody can put information up on without having to be an expert in web design. If that means as professional web designers we’re slightly inconvenienced that seems to be a price worth paying from my point of view. But let’s move on from version targeting cause we’ve talked about it far too much on the show. Let’s talk a little bit about the process of developing a web browser. I think for a lot of web designers we’re entirely on the side of, obviously, you know putting things into a web browser. Getting things to render correctly. How do you go about creating a web browser? What’s involved? What should we be aware of?

    Alex:Well a web browser is an enormously complicated thing. There is a reason that new browsers don’t show up too much. You have to build at the same time a decent editor, a rendering system that can render almost any kind of text and graphic. It has to be fast. It has to have object model. It has to parse a variety of different things. And is has to be compliant with a standard which is a book of at least 2 or 3 inches thick if you count HTML, CSS, and object model.

    Paul:You say that developing a browsers is hugely complex and obviously it is, and that’s part of the reason that browsers don’t come around very often, or updates to browsers. But, on the other hand we do seem to see other browser manufacturers moving much quicker than Microsoft. Why is that? Why does there seem to be slower movement out of Microsoft than elsewhere.

    Alex:I’m not sure that much quicker is the right way to describe it. The reason a lot of browsers are way ahead of Microsoft in a particular standard support is I think for two reasons. First we actually care about standards and we are nice people.

    Paul:(laughing) You’re implying that no one else is nice and no one else cares about standards. I’m sure that’s not true.

    Alex:No not really. This is how this happened. When we started working on browsers, which was, IE 1, 2, 3, 4 in the 90′s, there wasn’t so much of a standard. There was some idea you can mark text with tags in angle brackets and it will render somehow. So a b means bold. Eventually some kind of defacto standards developed. Every site was built for Netscape and it was important to be like Netscape. It was pretty much a standard. So when we built a browser at that time we were trying to be as compatable with that standard as possible. Then what happened, Netscape just went away for a few years and we were left alone. There was nobody to compete with. That is a hard place to be. You have to be compatable with the web. You can’t break anything. How do you make progress at that time. There was no versioning. At that point we decided to be nice and return the favour to other browsers and we went away for 5 years and were sitting for 5 years on the beach and letting everybody else catch up.

    Paul:That was really generous of you. That was a wonderful thing. That’s a good answer I like that Alex.

    Alex:Now everybody’s caught up we can be in the game together.

    Paul:Okay. So now that everybody’s at the same level you’re going to go for it majorly. So that brings us quite nicely on to the future of browsers. You know, particularly IE 8. Obviously you can’t really tell us anything that isn’t already publicly known and I wouldn’t expect you to. But, not everybody that listens to this podcast already knows all that is publicly out there about IE 8. So tell us what kind of direction you’re going in. How are you going to compete with these other browsers out there now that they’ve caught you up?

    Alex:Well the biggest thing to know about IE 8 is it is back. We have a real team of people who is really serious about building a good browser. The biggest investment in this one is obviously standards. That’s the biggest thing that everybody was unhappy about with the previous versions. We get as much as we can of good standards support right here. We are making major investments in CSS 2.1 doing whatever it means to be compatable. Interestingly enough it has to be defined what it means to be compatable, to say that you are compatable. We are doing as much as we can in this area. There will be a lot of exciting user interface features there. But I don’t think I can tell about that because I am really a core technology person and I learn about our UI implements from demos.

    Paul:Fair enough. So, internally are you working towards a deadline of any description over this? I presume we’re not talking about another 5 years here? We’re talking about a much shorter period of time.

    Alex:Definitely it is way closer than 5 years.

    Paul:(laughs) That’s good. You want to narrow it down any from that or am I pushing my luck?

    Alex:Yeah I don’t think I can have a number. Unless it is publicly known and I haven’t checked in the last couple of days. But you are going to see it pretty soon. I am going to set your expectations pretty low. Don’t expect this to be done in quaters because what we are doing with new standards layout it isn’t crazy and insane trying to rewrite things like this in less than 10 years.

    Paul: So you’re suggesting that before too long we might see a beta. You’ve obviously come under a bit of an attack from Opera and they’re have been several comments about that. And then you’ve come out and said that you’ve done that acid test. How big a deal really is that in the real world? Do you think it is a fair test of a browser?

    Alex:Well it is an acid test. As I understand in chemistry it checks the presence of a chemical, right? I guess it is a variant like that. I spent days taking this apart and figuring out what every line means and what features do you have to have, and how are they supposed to work to render a particular pixel in a particular place. It is quite and interesting test in the way that it tests very few features but it test the features in corner cases of intersting features of a standard. So you would assume if you get that far, if you manage to render text at all and you render Acid 2 you are in really good shape.

    Paul:So is is fair to say…The danger is, and I have heard some people say this, with IE 8 you’ve just been going after being able to say yeah we pass the Acid 2 test. You could kind of develop those things in isolation. My hope, and I suspect your hope as well, is that you’re going to go beyond that. It’s almost inconsequential that you passed the Acid 2 test. It’s part of a broader aim to introduce better standards support. Is that a fair comment?

    Alex:Yes it is. It probably would be not unreasonable to have another browser that doesn’t have an particularly promise but passes the Acid 2 test. We are really trying to be as close to standard as possible.

    Paul:Let’s broaden it out cause we’ve kind of picked on IE quite a lot here. Let’s broaden it out to talk about where browsers are going generally in the next few years. I mean, what do you think we’re going to see happening in browsers generally?

    Alex:Well from my point of view as standards and layout, I see actually multiple browsers being 100% compatable with CSS 2.1 which most helps both browsers and standards to really get into the new steps. We’ve heard a lot of criticism on standards not moving. Like CSS 3 some people are saying that trying to make sense of all the different parts of CSS 3 what is the next step there. In my opinion I am as unhappy with CSS 3 not moving as designers are. For this to move you have to have a solid ground of the previous version not only being a solid standard but also being supported properly. Then addding every little feature to CSS 3 become important because now we can have several implementations of that. As far as standards go I am really looking forward to the world after IE 8. And there are all the different directions of being mobile. Bringing more of the technologies into the browsers that they can perhaps take a bite out of flash or out of .pdf. Where you can have real content that was unthinkable for a browser a few years ago. Into every place that has a good browser. So I’m really optimistic. One thing to understand about developing a new browser is it’s exciting who writes is how has it. But for a web designer it is like making wine. Something happens today that will actually make the difference in the life of a web designer 10 or 15 years from now. Whatever is being shipped today, everybody you care about now has this one.

    Paul:What we need you guys to do is drop support for IE 6 really quick cause then we can use it as an excuse to drop support as well.

    Alex:This goes back to versioning a little bit. There is 3 kinds of versioning. There is versioning of a standard, version of a browser and version of a document. The version of a document is something that we are not going to drop ever. If something is written for IE 6 today 100 years from now we will still want to render it this way right? We wouldn’t go to the library and throw away all the books that are older than 100 years.

    Paul:That’s a very good point.

    Alex: In this sense many pages today are in Quirks mode. Google is in Quirks mode. If you try to render it in 100% standard it will look a little different. It will look quite odd by the way.

    Paul:That’s a whole other discussion. Google and it’s standards support. What about typography? Are we going to see some improvements on that front? I mean we’ve noticed some of the other browsers starting to support web fonts and things like that. Can we expect a similar thing from IE?

    Alex:IE supports font embedding for several versions now. There was an extremly complicated discussion within the standards group on how do you create a standard for downloadable fonts that can be standardized but is also friendly to font manufacturers. To people who own fonts. It’s easy to implement a hyperlink to a font that will be downloaded and used. Then it encourages to just put fonts out there, which you’re not supposed to do.

    Paul:Obviously this isn’t down to Microsoft cause this is the whole standards group discussing this. That strike me as no different than what we do with imagery at the moment. Images can be pirated and that’s somebody’s intellectual property. It’s kind of just the way things have been. Do you feel that their is a kind of tightening up on things like that. Like people are more concerned about that then perhaps they were in the early days?

    Alex:It is a good comparison of the difference of, whats the difference of an image or a song or a movie or a font. It is just so much more expensive to build a font. It is so easy to share if you just put out a file that if we make it easier to share we will just business model for a lot of small design companies who just build fonts. So we have to be very careful on how exactly it is being done. I think we are fairly close to be able to come up with a workable standard. We’re just not there yet.

    Paul:Okay. So that is something that will probably turn up at some point but not necessarily in IE 8.

    Alex:Well if that standard is embedded OpenType it is already there.

    Paul:Yeah that’s true. Let’s just touch on briefly another kind of criticism that really hasn’t been aimed at the IE group but Microsoft as a whole, which is this whole issue of Office. The latest version of Office. I know a lot of people who are passionate about HTML emails who were deeply disturbed to see that the latest versio of Outlook doesn’t use IE’s rendering engine. Can you give us any kind of insight into what happened there? I mean obviously it’s not your area but it does affect you guys to some degree.

    Alex:I wasn’t part of this decision but I can very well understand how that happened. When Office 2007 was being planned IE team pretty much didn’t exsist. We completely rebuilt the team for IE 7. I am not joking that we were 5 years on the beach. IE team stopped exsisting after IE 6. People went off doing their own different things. Of people working on IE 7 and now IE 8 there is litterally a handful of people who worked on IE 5. Maybe even less. It is a brand new team. When Office 2007 was being planned in 2003 there wasn’t anybody to talk to. The biggest concern about HTML email is security. So even is somebody wanted to build in IE 8 currently in a product to read email it would put a major requirement on IE to be able to be able to open all of these emails securly. If you take browser security and application security for things like Outlook it is a multiplier. It is way harder to build it that way. So I think that is totally sucks that you can’t send HTML email but I think that they decision that they had to make in Office 2007 was really difficult.

    Paul:Interesting stuff. It’s been great. I’ve really enjoyed chatting with you Alex. I feel like I’ve got a little bit more of an understanding of what’s gone on inside of Microsoft and where things have gone. It sounds like a big part of all of this was your own success. That because other browser manufacturers disappeared and you were kind of left alone there wasn’t the kind of investment internally within Microsoft to keep things moving forward and it’s had ramifications. It’s very interesting.

    Alex:Yeah. Thanks for talking to me. I have to say that you have a great podcast. I’ve been learning a lot from you. You don’t even imagine how much you yourself have on the future of internet. Just putting together this show.

    Paul:(I can just see Paul’s head growing) Oh well thank very much Alex. I’m sure I’m not that important really but I’ll pretend I am. Thanks very much for coming on the show. We’ll get you back in the future. Perhaps once IE 8 is out in beta. You can talk a little bit more then. That would be fun.

    Alex:I would love to. Thank you.

    Back to top

    Listeners email:

    Implementing RSS

    Our first question is an audio question about RSS. It asks what tools exist for adding RSS to a clients website.

    The simplest solution is to use a blog. Whether you use Movable Type, Word Press or Blogger they will all generate an RSS feed. Blogs are also easy to update and can be customised to integrate with the rest of your site.

    However, a blog might not meet your clients requirements. For example, they might wish the RSS feed to link to a non-blog page or even a third party site. One option is to use a social bookmarking tool like Delicious. This creates an RSS feed of all links added. Alternatively you could use a desktop application such as FeedForAll. FeedForAll is a cross platform application that allows users to easily create, edit and publish RSS feeds. It also comes with a PHP script that converts RSS into HTML via PHP. This is ideal for embedding RSS into your website.

    Hope that helps.

    Should designers just design

    Our next question comes from Travis…

    I have recently been asked to join a web development/design team as their full-time UI designer. My responsibilities would include the UI design only and not css, html ajax, etc. I know the basics of css and html and have designed standards-based sites from scratch, and am eager to learn more code to further my skill set. I have been discouraged from learning code while in this new position, and focus on the UI design. Do most web design firms share this same structure?

    Excellent question Travis and one that causes much lively discussion. Infact Cameron Moll asked the same question and the last I saw there was 114 comments!

    My answer is that designers should be able to code. Personally, I don’t believe you can be an effective interface designers without an understanding of the underlying code and the constraints of HTML and CSS. I respect those who say that design shouldn’t be constrained by technology. However, in the real world its more complicated.

    Setting that debate aside I would suggest that not knowing code is going to damage your career. Personally I would not hire somebody who cannot build as well as design a site. Consider your next job and whether you can afford to stay somewhere that actively discourages you from expanding your knowledge of the web.

    To leave an audio comment for the show skype “boagworldshow” or call +44 20 8133 5122.

    Random News

    Posted in News on February 29, 2008 by Paul Boag

    Boagworld has moved, the forum is back, Headscape has rebranded, our product is shaping up, the book is progressing and I seem to be speaking loads.

    Wow! Life feels like it is moving at 100 miles an hour at the moment. I am busier than I have ever been, but it is all incredibly exciting.

    Here is a random collection of the cool stuff that is happening.

    The Boagworld website has moved

    For a while now we have had problems with the hosting of boagworld. You may or may not have noticed it depending on how you use the site. However, the forum was particularly bad.

    Well, we have now moved over to Media Temple and the site is flying. Check out the new enhanced forum and add yourself to the boagworld listeners map.

    Headscape is rebranding

    Setting up Headscape was an unusual process. We took a number of clients from our previous company and so was busy from day one. However, like any company, we needed things like letterheads, business cards and branding. The result was that I threw together our logo in under an hour and moved on with the next thing.

    Well it is 6 years on and we are still insanely busy. However, it is time to finally get a professional to produce our brand identity. The obvious choice was Mr Hicks and what a stunning job he has done!

    The new Headscape Logo

    Unfortunately, because we are still run off our feet we haven’t managed a proper launch. Although Jon has provided most of the marketing material we need, the website is still down to us (we thought it wouldn’t look good if he designed that!)

    However, rest assured we are working on it and it should appear before too long! What is more, this has spurred me on to look at redesigning boagworld. We will see!

    Our product is coming

    Part of the reason things are so busy is because we are developing a web based application. It is looking pretty good and it won’t be long before we start a closed beta. However, if you are coming to SXSW then grab me and I’ll show you a sneak peek to whet your appetite.

    For now all I will say is that it will “make getting design sign off a breeze“.

    The book is progressing

    A number of you have been asking how the book is coming along. Well, after stalling for a while it is moving forward again. Best of all we are reaching the point where I am able to release some of what I have done for you to check out!

    Also my publisher run a special scheme which some of you maybe interested in. Although we intend to give the first chapter away for free, you can also sign up to receive draft chapters as they are written. You do have to pay for the privilege but will receive the final book at the end. Think of it as being a beta tester for the book.

    I’ll let you know more as things progress.

    Speaking

    Not that I have a lot of time for writing at the moment as I seem to spend half my days preparing presentations. Here are just a few of my upcoming speaking engagements. If you happen to be attending any of these let me know (especially if you are coming to the Great British Booze-up). I would love to hook up!

    • SXSW – Social networking and your brand
    • Highland Fling – Conference host and interviewer
    • @Media 08 – A panel on business and management
    • FOWD – Promoting and selling web design services
    • Singularity – No idea what I am speaking on yet!

    So in short… I am busy! Despite that, its loads of fun.

    108. Future of

    Posted in Classic shows on January 23, 2008 by Paul Boag

    On show 108: The differences between work for an agency or being an in-house designer. Hosting bandwidth intensive content and what happens when Paul designs a web design conference.

    Play

    Podcast: Download (22.7MB)

    Download this show.

    Launch our podcast player

    News and events | Daniel Burka and Leslie Chicoine | Listener emails

    Unfortunately Marcus is not on this week’s show. His Father died a few days ago and obviously he has lots of stuff to deal with. Hopefully he will be back next week. However, if you are desperate for your Marcus fix then check him out on Nevermind the Buzzcocks.

    News and events

    Future of Web Design

    Imagine for a moment if you will that an email lands in your inbox asking you to create your perfect web design conference. Who would you invite to speak? Daniel Burka from Digg, Andy Clarke maybe? What about Jon Hicks or Jina Bolton?

    Well that is exactly what happened to me when the guys over at Carsonified asked me to chair this years Future of Web Design conference. They asked me who I thought my dream line up would be and together we worked on assembling them. Sure, there were some restrictions, apparently raising the dead caused a problem and hosting the conference on the moon was out of the question. However, overall we did pretty damn well.

    So on the 17th and 18th of April in London I get to attend (and contribute to) my dream conference. The line up includes all the people I have already mentioned and more. The only thing missing is you guys. It would be really cool to have a bit of a boagworld meet-up while we are there so get on over and sign up today. It will cost you £145 including VAT or £480 if you want to attend my workshop as well.

    However I know some of you are poor students or have tight ass bosses so we are also giving away two free tickets. If you want to win the two tickets email me with FOWD in the subject line with your name and contact details. We will pick a winner in a couple of weeks.

    Advancing advanced search

    My second story of the day is an excellent post on the Boxes and Arrows website. It tackles the subject of advanced search. Search generally is possibly one of the most neglected aspects of website navigation. This is amazing as it is the primary means of navigation for 50% of those who use websites.

    I have seen some stuff written about search results but next to nothing on advanced search. What is more advanced search is not only ignored by writers but also by users. Few choose to use the functionality it provides, only turning to it as a last resort if all else fails.

    In this article Stephen Turbek suggests that we need to re-design advanced search from the ground up. Instead of advanced search being a tiny link often overlooked, it should be an integral part of the search results page where complex filtering can be carried out through a graphical interface. Its hard to explain exactly what he is talking about without seeing the examples he gives so definitely check out the post.

    If you ever have to work with search then this is a must read.

    Starting from a blank canvas

    Next up is a blog post from Cameron Moll on how to start a new design. We have spoken before on this show about how hard it is to come up with a design from scratch. Nothing can sap your creativity more than a blank sheet of paper (or empty Photoshop file!).

    Cameron gives some good solid advice including sketching rather than diving into Photoshop and also drawing from previous work. However, he also suggests some less well known approaches such as starting with a grid and (most interestingly) working on the core content first. On the latter point he is referring to the fact that we often tackle things like headers and navigation first only coming back to the content at the end. Moll suggests this should be the other way around. This is good advice as it focuses the designer on what the site is really about rather than the interface used to navigate it.

    You suck at Photoshop

    My last find of the week is a really superb set of tutorials I found on youtube. I am not entirely sure how useful they are but they are definitely entertaining.

    Most screencasts maybe informative but are often deadly boring. Not so with “You suck at Photoshop”. These basic Photoshop tutorials have a twist as the person recording the screencasts vents his rage at a cheating wife. Check out the video below and you will see what I mean.


    Back to top

    Expert interview: Daniel Burka and Leslie Chicoine

    Paul: OK so joining me today is Daniel Burka from digg.com, hello Daniel.

    Daniel: Hello Paul.

    Paul: Nice to have you on the show again, it’s been a while.

    Daniel: Well thanks for having me again.

    Paul: We’ve also got Leslie Chicoine joining us as well from satisfaction what’s the url again, remind me.

    Leslie: Sure it’s getsatisfaction.com.

    Paul: getsatisfaction, that’s the bit I was missing, I should have been prepared and had that on my screen, but there you go I’m badly organised. And of course how can we do an interview without having Marcus here as well, hello Marcus.

    Marcus: Hi Paul.

    Paul: laughs

    Marcus: getsatisfaction.com, you must be able to sell that for millions to a porn agency.

    Paul: laughs

    Marcus: laughs Sorry, I’m off on one already.

    Leslie: I’ve heard those jokes so many times.

    Marcus: Yeah, ok, I’m so predictable.

    Leslie: laughs

    Marcus: I always have to ask people from America were are you and what’s the weather like? I know it’s a really boring English thing to say but it really is horrible over here at the moment.

    Leslie: Well we’re in sunny San Francisco, I think the weather about 55 Fahrenheit right now.

    Paul: Yeah, that’s so unfair isn’t it? Why do we live here, I just don’t know why we continue to live in Britain in winter.

    Daniel: I was just in Canada last week and it was like 20 below freezing so it’s really nice to be back.

    Paul: I bet laughs

    Marcus: Not that cold here that’s for sure, it’s just wet, it rains all the time in the winter.

    Paul: So Daniel, I’m dragging it back to the subject now Marcus if you hadn’t actually noticed while you go off on weird tangents that’s fine. Daniel we’ve had you on the show before and so hopefully our listens will be familiar with your background and if they haven’t heard of digg.com they should be ashamed of themselves. Leslie your new to the boagworld podcast so maybe should kick off with you, and if you could just tell us a little bit about getsatisfaction and a little bit about yourself and your own background if you would.

    Leslie: Sure, well let’s start with getsatisfaction, basically I’m trying to re-do what customer service is there’s a lot of depressions happening on line about companies and how companies aren’t getting involved so we’re trying to get companies and customers together in the same space. Talking about products and issues and ideas for the future and yet we’re also trying to make sure it’s a level playing field so that neither side has control of the conversation so we’re acting as an intermediary allowing true conversations that are open to the public and that everyone can see and anybody can get involved in, but we’ve actually got people talking about customer service for companies, the companies aren’t there yet but getsatifcation.com/apple is a very popular section and there’s nobody from apple on the site yet. But there are also sections like the one for google and the one for twitter and we have google employees and twitter employees involved. It’s a very different take on customer service because it’s not just customer service rep it’s people who are programming, people who are designing, people who are in the HR department, all getting involved and having much more direct contact with customers

    Paul: So do the companies all have to pay in order to participate in this or is this a free service? How does this work, what’s your business model?

    Leslie: Well, all the features we have right now are free; our business model is still being developed, not to say that we don’t have one, we just have a lot of different directions and we want to make sure that whatever direction we take fits them in our philosophies, but we’re hoping that in the future for us, we see the potential in the analytics and the data that we collect. Your on the site are your telling us a lot about the different products and the services that your using and can tell companies to make connections between what products you use and like, and what other products and service you might also be interested in.

    Paul: Yeah, of course.

    Leslie: We start collecting more information about who you are and why your there in the first place.

    Paul: Well I guess the other great thing, if you thinking of building a web app of any description then this is a great mechanism that already exists to handle the customer services enquiries you get without having to build all the functionality that is needed to do that as well so I imagine your attracting a lot of smaller companies as well?

    Leslie: Yeah, it’s actually been a really interesting display, we’ve got small web apps, we have larger web apps such as google, digg.

    Daniel: Even pounce is on there, I mean when we set up pounce originally and we wanted a way to communicate with our users and we immediately just set up a satisfaction page, signed up and it’s been great for use.

    Paul: Yeah.

    Leslie: Yeah, that’s all pretty easy, another thing actually too I forgot to mention, what’s truly great about the service is often times there customer service issues that span multiple companies so a great example was a guy who was having trouble getting a refund on an airplane ticket and he wasn’t sure if it was American Airlines or expedia.com so through the site he was able to post the issue to both sides and have them both look at it and communicate together there.

    Paul: Personally Leslie what is it you do at satisfaction?

    Leslie: Sure, I’m a designer, kind of an open title primarily I do a lot of UI design, I do a fair amount of contact development, I actually design a little bit of the business strategy as well we have developers who actually do the coding but most of what I do is wire framing.

    Paul: Oh.

    Leslie: My background though is actually game design.

    Paul: Really?

    Leslie: Really. laughs

    Paul: So, that seems an interesting leap to go from game design into kind of a web app like this. Is it a big difference?

    Leslie: It’s not really, because so much of what I learned in games design was how you design mechanics that let you create particular types of dynamics so you want people to act a certain way or, well in our case we want people to have a really positive attitude and there’s actually things in the design that makes people happier and make the conversation more open and positive, everything from the wording that we use to how we break down the steps, try and keep it all simple, if you go to the site you’ll notice it’s all very white and clean and light and that again add to that kind of feel and it helps people be more communicative.

    Paul: Hmm… Interesting stuff, so the reason we thought we would setup this call today is really so we could talk a bit, well it was a conversation I had pervious with you wasn’t it Daniel about the fact that you come from an agency background and you used to work for a company, what’s the name of the company again?

    Daniel: Silver Orange

    Paul: Yes, that was it and they were what you would call a normal web design agency and while you were doing that digg was one of your clients is that correct?

    Daniel: Yeah, so I helped found Silver Orange there were six of us what started the company back in 99 I think, but yeah we were a pretty typical boutique web job.

    Paul: And what interested me about the conversation we were having previously, was the way you kind of when from working at Silver Orange across then to working for digg so you’ve kind of gone from working at an external agency were you had lots of clients and that kind of stuff, to working as an in house designer on a single project and I thought that was quite an interesting discuss and quite an interesting area to cover and you mentioned Leslie to me, and that you’d been having a similar conversation in a coffee shop somewhere with her and we though lets setup a few minutes and have a chat about some of the kind of ramifications of that and I guess the good place to start is, perhaps Daniel that you kick us off, what you see the difference being between working as an in-house designer somewhere and working for an external agency, is there a big difference?

    Daniel: Absolutely, I mean it was actually quite interesting, I was back in Canada last week for some awards, kind of a yearly state of the union meeting and I’m still involved with the company a bit, I went back there for that, again this exact same discussion with one of our designers, and he was really jealous that I’m currently re-designing the digg comment system and he thinks it’s really interested that I’ve designed it twice now and I’m coming back again and doing it a third time and that kind of iterative development is something you frequently don’t get to do in the agency environment. That’s one of the real pro’s of working, I think as an in house designer is that you don’t build something and just hand it off you get the chance to build it, received feed back, watch how people use it gage some metrics over time and come back an re-design it and continue to improve something.

    Paul: I mean, would you agree with that Leslie? Is that one of the things that attracts you working at satisfaction?

    Leslie: Definitely, there’s something about being able to see a project through and then check back on it again and again, but I think that’s one of the things that makes it difficult, you no longer have and perspective, so we’re were talking about, particularly at the coffee shop, when you working at the agency, you come in and what makes you special is your new perspective and when your working at a company, you no longer have that so you need to make sure you can somehow come back fresh to the same project and when you iterating, bringing in new eyes, trying to see what needs to be changed becomes a challenge.

    Paul: At one point in the sentence there you said again, and again…

    Marcus: laughs

    Paul: And I heard Marcus snigger at that, he obviously picked up on that as well. I mean that’s the thing, as somebody who works for an agency I have to confess, I think I would go absolutely crazy working on one website over a long period of time, probably because I’ve got the attention span of a newt, ya know do you ever long for that variety of work to work on?

    Daniel: Yeah, absolutely, it’s usually really fun when you’re working for an agency especially clients who give you a lot of leeway and a lot of respect, that you walk through the door and you immediately see 80% of the problems on there site and you say, listen this is what you need to do, this is what you should fix and you get immediate reaction, it’s really fun right?

    Paul: agrees

    Daniel: You can bring so much change so quickly and somewhere like digg for instance, I mean I only have one or two sections of the site now that I’m looking at were I’m like, ok there’s still huge room for improvement here I know want to kind of tear it down and think of it from scratch and in all the other places there’s kind of refinement, refinement, refinement and it’s way more challenging and that’s what makes it fun but it’s also a bit more tedious, it’s not something fresh.

    Marcus: I was gonna ask what the different skills you need, but I think you’ve kind of answered that, maybe being more dog-eared and determined, are there any major different skills between working on multiple projects and working on the same site all the time?

    Leslie: Definitely, I think especially when your working at a company verses an agency the projects your working you have to have a better understanding of there application though out the rest of the business so when we’re iterating and we’re working on small details, the changes we make are for business needs or metric things that we’ve gotten so that kind of judgement is not something that I personally had as much experience with when I was working at an agency, and actually the team that works on getsatisfaction was initially a consultancy but it was weird have the whole team have to switch over.

    Paul: Oh right.

    Leslie: So initially when we were a consultancy the actually people who weren’t really involved with what projects we chose or really even finding out that much about the company, the founders were the one who really had to do that research and now we all have to do that kind of research.

    Daniel: I was interesting because I was in a different position at Silver Orange as one of the founders, ya know I did have quite a say on which projects we take especially the UI projects were I was working more solo with a client, ya know, if I didn’t want to take a project we wouldn’t take it, working with clients I kind of got to know there business a lot before I started to get into it, you learn as much as you can, kind of a week or two to get into a project but at somewere like digg or like pownce, it’s a lot more about thinking strategically and thinking much more in the long term because if you pin yourself into a corner it’s literally yourself and you’re the one who’s gonna have to be able to dig yourself out of it later on.

    Paul: Do you guys every, digg and getsatisfaction, ever bring in external specialists from time to time?

    Leslie: Definitely, we were talking about needing fresh perspective and bringing new people in is always a great way to do that. We occasionally, what we do is we have design sessions and we have guests whom we get their opinions and show them what we’re doing and see if they have new ideas.

    Paul: I mean it’s quite interesting that isn’t it because I mean we do a lot of work for a whole variety of different clients and you go to these different companies and they have internal design and development teams and you think why are we actually being brought in here were they’ve got the skills in house but they’re not really utilising what they’ve got and there’s a perception that if you bring in someone from the outside they’ve somehow got more skill than perhaps an in house team, do you feel more or less valued as an in-house employee than you did perhaps externally?

    Leslie: laughs You don’t get that same sort of shiny, new feeling as an in-house designer I definitely feel more valued at this point than I did in the consultancy because one of the burdens of getting things right is on my shoulders now. So you really just can’t throw my ideas out the window. But it is actually interesting when people coming into a company, you can see in people’s eyes; they get a little nervous right? That the person coming in is gonna be more valuable than them right?

    Paul: Yeah.

    Daniel: I’m so excited, I’ve just hired another designer at digg, so there’s three of us now, and he’s awesome and I’m so excited to get someone in here who, a, can code better than me and b, he’s bring an entirely new perspective to the site, so ya know, it’s really nice to have fresh eyes so this is the best of both worlds because a, he’s now an in house designer and b, he’s just joined so he’s like completely fresh too it and I’m gonna capitalise on that as much as I can in the next couple of months before ya know he gets too deep in it a get’s into the aquarium.

    Paul: I suppose you haven’t really been doing it that long, being an in-house designer but do you think there’s a point were you have to move no, when you think perhaps you’ve been there too long and been institutionalised into a certain way of thinking?

    Daniel: I don’t think so, I mean I know this older guy who used to be the creative designer at apple, and the creative director a Polaroid ya know a bunch of really big companies and he’d been in the same job for a decade I think, but he was able to think incredibly creatively and leverage the people under him too bring the best into projects. I think as long as your able to adapt, I mean you can’t just keep coming through the door and doing the same kind of work all the time, I think your able to adapt to that in-house philosophy, I think you can definitely keep at it.

    Leslie: Yeah I don’t have that much experience with that, but I think that’s the way too do it. Even with just the year that I’ve had at satisfaction you find yourself having to play a lot of games or do things to freshen the project or freshen the work.

    Daniel: Right. I find too, like at somewhere like digg there’s so many different projects within the whole. It’s not like I’m working on the homepage every single day this year, that’s one very minor part of the site, you break down projects into components, like re-designing the comments is very different to re-designing the user profiles, I see them as very independent projects obviously tied stylistically and ya know from a user interface strand point they’re tied together, but they’re very different challenges which mixes up your job a lot.

    Paul: What’s quite interesting with both your experience is that you’ve worked for agencies that worked on these applications your currently full time involved with and you saw that point with digg and satisfaction were you thought, ok, it’s not the right business move to have an external agency now, we need to bring that in house and I’m just kind of quite interested as to what happened in that process and whether you’ve got much of an idea of what that tipping point is, were you go from thinking yeah we can use an external agency for this to a point were we really need to do this in-house?

    Leslie: I’ll let Daniel answer that one.

    Paul: laughs

    Daniel: So for digg it really happened that, originally it was a project Kevin had and was just throwing it around and wanted to see if it would get traction, and when it started to get traction he hired Silver Orange to come in and re-design the interface so it was a lot more usable and the site was gaining momentum gaining momentum and it kind of got to a point were they started thinking ok, this is a serious business, it’s got viability and they decided to start a company around it, in a much more serious and methodical way and that was kind of the point were they decided, ok, one of those positions is gonna be a designer, I’d been coming down, probably once a month down to San Francisco from Toronto and I one point Kevin was like, you should really move here, so he convinced me to move down and even for the first bit it was kind of interesting, I hope a lot of companies can do this kind of thing, it was quite flexible, I was working one week a month on Silver Orange project, so it was good for digg because they didn’t have to pay me as much and at the time there wasn’t enough work for a full time person and that way for me it was a nice period of time because I had the best of both worlds, I’d work on a bunch of client projects one week a month and then long term in house designer three weeks out of the month.

    Leslie: It was a totally different situation for getsatisfaction because we had the whole company as a team look for a project to start, so for us it was really letting go of our client work.

    Paul: Okay.

    Marcus: I bet that’s hard.

    Leslie: At satisfaction we let go of most of our development work first and let go of our design work and then turned this completely into satisfaction. But I did have that period like Daniel were I was saying were your working on lots of projects and along side your long term project.

    Marcus: I can’t imagine slowly giving up project work; I guess it’s the sales man in me. I find it hard to turn any business away.

    Leslie: Yeah, it’s actually very difficult to let people go when they want you and they still need you to do work for them.

    Daniel: Silver Orange have actually got an idea for a project and they’re thinking of totally scaling back, and I don’t think, well we’re definitely not gonna drop all client projects but we’re talking about cutting down and a few people on the team, ya know kind of pumping other projects and drawing in other people as they’re required, and I think that’s also an interesting strategy as long as you can be disciplined enough to commit enough time to it.

    Leslie: Yeah, I think our team decided up front that there was a stopping point that we would not be disciplined enough and that we would have problem with time being spent on things that were interesting or new instead of the core project.

    Paul: I mean we’re looking, ya know we obviously knock around different ideas and web applications, we perceive, are a way of expanding the business rather than necessarily replacing one with the other so well I guess there are lots of different ways of slicing the cake I guess.

    Daniel: Yeah, that’s the same philosophy Silver Orange is likely to follow.

    Paul: It’s interesting.

    Daniel: I mean it’s frustrating when you’re building other peoples projects all the time, you know you’ve got the skills in house to build something awesome, but smart people come up with ideas why should we be building for them when we can do it ourselves. laughs

    Paul: Yeah, completely.

    Marcus: This is so familiar, we’ve been having, well since day one I guess the simplest example is your own website in an agency, that always gets put to the bottom of the pile and we’ve been thinking about developing different applications for quite a while now but just trying to get people off paid projects and onto that, is, well it’s impossible.

    Paul: laughs

    Marcus: Well were we’ve got to now is, proper contracts have been written up between two different departs within Headscape if you like so that it is an official project, these set applications we’re working on at the moment.

    Paul: When you say it out loud like that Marcus is sounds so pathetic.

    Leslie: laughs

    Marcus: But it’s true.

    Paul: laughs But that’s how we’re getting around the problem. But I’ve got to admire this all or nothing approach or right we’re gonna go for it, but anyway.

    Daniel: I think there’s actually something really curious about the bay area, I think it’s really different in attitudes here like ya know, figure out what’s the worst that can happen, ya know and if the worst that can happen means things don’t go so well in 6 months and you can barely pay your rent, if that’s the worst that happens then what ever just go it. And I think that’s why so many projects here get off the ground. I think that’s great. There’s a real sense of optimism here.

    Leslie: And a lot of support too, if you’ve got an idea. There’s very few people here who are secretive with there ideas. They’re always talking about all their ideas and sharing and talking about building something rather than trying to hide it.

    Daniel: But it’s competitive too. The people here, ya know there’s such a big audience for a lot of these products it’s like why should we quibble over the similarities of our projects lets just find a way that we can do stuff together and throw around ideas and it’s really fun.

    Paul: Yeah it’s good. So for a lot of the people that are listening to this show, some of them are students that are coming out of university and are looking for their first movement into the web design world. We’ve got other people that are, what I would call enthusiastic amateurs who are looking to move full time into web design, you’ve got lots of different ways you could go these days if you’ve got web design skills I guess choice number one if you go say go for it I’m gonna build my own web application, choice number two is you could go a join a web agency and work on a variety of third party work and choice number three I guess is to become an in-house designer for a company, whether that be a trendy web 2.0 company or whether it be an in-house designer for I dunno on-line banking or whatever, how do you go about making that decision and what advice would you give people about were to begin? Are you going to damage your career if you start off by working in one place? Should you be doing lots of different types of work, ya know, what’s your advice?

    Leslie: I think we both sort of agree that the real thing your looking for is good people, so whichever of those situation gets your around other great designers, other great teams with projects that your excited about, it probably doesn’t matter as much as you might think that it would.

    Daniel: Right.

    Marcus: It’s a bad question Paul.

    Daniel: If I was getting into the industry right now, I wouldn’t want to get into a huge agency were I don’t know what sub-section of that agency I’m going to be in, what team I’m gonna work on, I mean joining a group of less than 15 you can get a good idea of who your actually gonna be working with and that kind of apprenticeship with really brilliant people is easily the best way to advance.

    Paul: Yeah, I like that, I like that a lot. I must admit I hadn’t thought of it from that perspective and yes Marcus it was a rubbish question.

    Marcus: laughs

    Leslie: Well that’s the one that everyone’s asking.

    Paul: Well yeah, we get asked that question all the time. My mistake is I should have asked what advice do you have for people starting out in there career, I shouldn’t have constrained you by giving you these different options.

    Leslie: I don’t think this is just starting out. This is something your constantly asking yourself, am I in the right spot and I doing the right thing to advance my career, but as for actually starting, once again come back to this all the time, if there are good people around me then I’m in the right spot.

    Paul: Yeah.

    Leslie: If I’m inspired by the people around me I’m in the right spot.

    Paul: I’m gonna have to move Marcus I’m sorry. I work with you…

    Daniel: laughs

    Leslie: laughs

    Paul: laughs He’s used to it, he likes my abuse. laughs

    Marcus: I’m also not a designer so.

    Paul: No, your not, that’s very true. Although I don’t think I consider myself a designer anymore either.

    Marcus: You took the words right out of my mouth Paul. laughs

    Paul: I just thought I’d beat you to the punch.

    Marcus: You did.

    Paul: Okay, thank you guys for coming on the show, that was really, really interesting, you came up with some really good stuff and yeah I’m sure we’ll get some really good stuff back after listening to you. Thank you for coming and we’ll get you on the show again soon.

    Marcus: Thank you.

    Leslie: Thank you.

    Daniel: Thanks a lot Paul.

    Back to top

    Listeners email:

    The cost of bandwidth

    Eric: How do you deal with high bandwidth sites without bankrupting your clients? Is the quality of downloads compromised with these “unlimited bandwidth” sites?

    Well Eric I have to confess that I have largely avoided the escalating costs of hosting this podcast thanks to the kind sponsorship of switchpod. However, for those of you who haven’t managed to gain sponsorship or who are looking for solutions for clients then there are numerous options available.

    As Eric said in his audio question there is Libsyn which is a well known multimedia hosting provider that has amazingly competitive rates. I am not quite sure why Eric has an issue with them as I have heard very good things about them.

    Another option is to host your video or audio with the Internet Archive. This service is free although I hear reports that performance can be an issue.

    Of course if you are dealing with video then there are a whole host of possibilities from youtube to viddler. Some services are better than offers so be careful. For example some resize your video or limit the file size and length.

    If you are hosting for clients be sure to check the terms and conditions of these sites as some of them preclude their use for this purpose. Also check ownership as you can be signing over the rights to reuse your video to the site owner.

    Lastly in response to Eric’s concerns about the download quality of unlimited bandwidth sites, I have to say I have yet to experience any. I can see how this could be a problem when you get to really big numbers but that is not something that has effected me. Sounds to me that Eric might have been talking to companies trying to justify their own inflated prices and limited offers.

    Working with audio

    Harry: Given that you like to receive questions in audio format, can you, or any other boagers recommend any software that does the job?

    We certainly do like receiving audio questions Harry (I notice that yours was an email!) Also now we are doing a listeners email section it is even more important. That is why we have made it even easier. I have signed up for a skypein account which means you can send me a message either by skyping boagworldshow or by calling 020 8133 5122.

    However, lets just presume for a moment that you want to record and edit audio for another reason beyond commenting on boagworld. As a web designer or website owner you probably don’t have to do much audio work. As a result you won’t want to shell out a lot of money. I would therefore recommend you check out Audacity. Its a free audio editor for both the mac and PC which is as good as many of the professional packages. It provides all of the basics you need and exports to a number of different formats. Definitely worth trying out.

    So now you have no excuse not to send an audio question, comment, or suggestion into the show.

    Post navigation

    ← Older posts

    About this site

    Photo of Paul Boag

    Hi, I am Paul Boag. I am a co-founder of web design agency Headscape and host of the boagworld podcast.

    If you are looking for advice on designing, developing or running your website then you are in the right place.

    I recommend starting with:

    • A guide for those new to the site.
    • Searching for a specific topic.
    • Following me on twitter.
    • Subscribing to updates from me.
    • Reading more about me!
    • Subscribe to Boagworld
    • Learn about Headscape
    • Hire me

    I am not the only person at Headscape sharing great advice. Make sure you check out these guys too!

    Others worth following

    • Chris Sanderson (Designer) Chris Sanderson (Designer)
    • Craig Rowe (Developer) Craig Rowe (Developer)
    • Dan Sheerman (Front End Dev) Dan Sheerman (Front End Dev)
    • Ed Merritt (Designer) Ed Merritt (Designer)
    • Leigh Howells (UX Consultant) Leigh Howells (UX Consultant)
    • Marcus Lillington (UX Consultant) Marcus Lillington (UX Consultant)
    • Rob Borley (Future Tech Guy) Rob Borley (Future Tech Guy)
    or contact me

    Privacy and Cookies