189. How to keep up with web innovations

Paul Boag

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

Download this show.

Launch our podcast player


Web design match making

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

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

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

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

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

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

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


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

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

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

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

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

Client relations

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

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

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

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

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

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

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

Myths of usability testing

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

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

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

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

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

The post ends with the following conclusions:

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

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

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

jQuery for designers

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

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

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

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

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

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

Back to top

Feature: 10 secrets to staying informed about web design

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

Read 10 secrets to staying informed about web design

Back to top

Ad: Win a Macbook Pro or iPod Touch

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

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

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

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

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

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

Back to top

Listeners feedback:

Recording the podcast

I had the following tweet from @david_o_connell:

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

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

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


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

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

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


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

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

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

Recording tips

Here’s a bunch of tips to :

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

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

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

Building Findable Websites

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

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

Building Findable Websites: Web Standards, SEO, and Beyond

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

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

The goals of findability are listed as:

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

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

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

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

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

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

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

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

Thanks and keep up the wonderful podcast.

Back to top