Web Design News 16/07/10

This week: A presentation from Relly about Microcopy, using Twitter for customer testimonials and saying ‘no’ to clients.

This week: A presentation from Relly about Microcopy, using Twitter for customer testimonials and saying ‘no’ to clients.

Microcopy – All the small things

Microcopy is the ninja of online content. Fast, furious and deadly, it has the power to make or break your online business, to kill or slay your foes. It’s a sentence, a confirmation, a few words. One word, even. It isn’t big or flashy. It doesn’t leave a calling card. If it does its job your customer may never notice it was there.

In this session from @Media2010 conference, Relly Annett-Baker takes you through the ins and outs of microcopy and sympathises with designers and developers who are often lumped with writing microcopy in the form of error messages or instructions and loads you full of great ideas for helping you fine tune your microcopy.

Using Twitter for customer testimonials

Screenshot of twitter testimonial on the Grabaperch website

One of the problems when using customer testimonials is the legitimacy can often be questioned and you’re often left wondering if the site owners have written them, or even how old they are. Rachel Andrew has written an article showing how she has harnessed the positive tweets on Twitter into testimonials for her Perch CMS. Rachel uses Twitter’s ‘favourites’ list to flag tweets for inclusion as a testimonial rather than a hashtag which is open to gaming and abuse.

Using Twitter in this way clearly tracks the testimonial back to the user who wrote them as well as when it was posted making them much more valuable both for the company, and for the users who read them.

Just say no to clients

The client isn’t always right. We know it, but we rarely challenge clients when they’re wrong which can cause problems in our relationships with them. In this article on Think Vitamin, Rob Mills presents two cases where problems could occur if you try and accommodate unreasonable client requests.

Client pulling hair

For example: client ideas which may not be appropriate for the project, and while you should at least listen to all the ideas a client may have, there’s a delicate balancing act here. The client knows their business better than you ever will, and you have the expertise and knowledge to recognise when an idea might have a negative effect, Rob highlights this by recommending that you work with the client to reach a compromise.

All in all, it’s OK to say no (in most cases) as long as you clearly explain why, and you collaborate with the client, you should both end up happy.

Is ‘John the client’ stupid or are you failing him?

Meet John the client. John runs a reasonably large website. He is a marketeer who considers himself smart, articulate and professional. That said, he doesn’t know much about web design and so needs your help.

John comes to you with a clear set of business objectives and asks for a quote. What happens next leaves John confused, frustrated and extremely unhappy.

Explain why you are asking about money.

Before giving John his quote you ask a little more about the project. After chatting for a few minutes you ask him about his budget. A fair enough question you think. After all there are so many ways you could approach the project. Without knowing the budget it is impossible to know where to begin.

In your mind, building a website is like building a house. Without knowing the budget you can’t possibly know how many rooms the client can afford or what materials you should use to build.

John on the other hand is instantly suspicious. Why would you want to know his budget? The only reason he can think of is that you want to make sure you don’t under charge when there is more money available. Anyway, he doesn’t really know his budget. How the hell is he supposed to know how much a website costs?

Money Grabber

Image credit : Be careful not to come across as money grabbing.

John goes away determined to find a web designer who isn’t trying to screw him over. Fortunately for you all of the other designers he asks also fail to explain why they need to know about his budget and so you manage to win the project anyway.

Justify recommendations in language John can understand.

Once you have won the job you arrange a kickoff meeting to nail down the final specification. However, John is instantly regretting his decison to hire you as his worse fears are confirmed.

In his eyes you are immediately trying to squeeze more money out of him as you waffle on about the importance of usability and accessibility.

John doesn’t care about disabled users. No disabled users use his website anyway!

As for usability, surely it is the job of the web designer to make the website usable. Why do we need expensive usability testing? He is pretty sure usability testing involves expensive things like cameras, usability labs and two way mirrors.

Unfortunately you believe you have explained the issues clearly. You talked about WCAG 2 and mentioned Jacob Neilsen. You are beginning to wonder if John is stupid.

People looking confused

Image credit : Avoid technobabble if you want your clients to understand what you are talking about.

Maybe if you had talked about accessibility in terms of search engine rankings and usability testing as a way to increase conversion then John might have listened. As it is John puts his foot down and refuses to pay for any of these ‘ unnecessary extras’.

Include John in the process.

You go away from the kickoff meeting pleased to have a signed contract. However you have the feeling in the pit of your stomach that this is going to be another one of ‘those’ projects. Nevertheless you pick yourself up and dive into the design process.

Almost immediately you get a phone call from John asking if there is anything for him to see. You explain that it is still early days and that that you are not ready to present. John sounds disappointed but resigned.

A short while later you are ready to present the design to John. You are really pleased with the result. It has taken a lot more time than you budgeted for but it was worth it. The final design is extremely easy to use and will make a great portfolio piece.

Person hiding

Image credit : Stop hiding from your clients. Show them work early and include them in the process.

When John sees the design he is horrified. From his perspective you have entirely missed the point. The design clashes with his offline marketing material and fails to focus on the right selling points. Also he is convinced his suppliers will hate it and although they are not the end user, their opinions matter.

After a tense conference call you go away demoralised but with a compromise that will hopefully make John happy. You wonder in hindsight whether it would have been better to show John some of your initial ideas and sketches. Perhaps you should have produced a wireframe first.

Educate John about design.

After much agonising and compromise you are once again ready to present to John.

John is much happier with the new design and feels it is heading in the right direction. However, he does have some concern. For a start he has to scroll to get to most of the content and yet there is empty whitespace on either side of the design. He tells you to move key content into this wasted space.

Also as he thinks about his young male target audience he realises that the colour scheme is probably too effeminate, so he tells you to change it to blue.

While John is feeling somewhat happier you are feeling crushed. It feels like he is doing your job for you. The string of feedback about moving this and changing the colour of that, feels like it has reduced you to pushing pixels.

By this stage you are sure the client is stupid, and just want the design signed off. At no stage do you stop to ask John why he is requesting these changes. Perhaps if you had understood his thinking then you could have explained concepts like screen resolution or suggested an alternative to corporate blue which is so massively overused on the web.

Teacher teaching maths

Image credit : Educate your clients so they make more informed decisions.

Instead you wash your hands of the design and just give John what he wants.

Communicate with John regularly.

Now that the design is complete you turn your attention to the site build. At least John won’t care about your code. Now you can finally do things right.

Its a big job and it takes a lot of time. Even though you put too much time into the design and then washed your hands of it, you have your pride. You are not about to cut corners with the code. After all other web designers might look at it and judge you!

You work damn hard, putting in more work than you probably should do. John even managed to slip some extra functionality in at the scoping phase, which turns out to be a pain in the ass.

John on the other hand is wondering what is going on. He hasn’t heard from you in weeks. Surely the site must be read now? He decides to drop you an email asking how things are progressing. You reply with a short email saying everything is progressing nicely. After all, you never did like project management and you are sure John would prefer you building his site rather than writing him detailed emails.

John receives your email and finds himself becoming increasingly frustrated. What does ‘progressing nicely’ mean? He writes back asking for an expected completion date and you reply with a rough estimate.

The date comes and goes without a word from you. After all it was only an estimate and several complications have delayed things by a few days.

John finally looses his temper and calls you. He has arranged a marketing campaign to coincide with the launch date you and because he hadn’t heard from you he presumed everything was on schedule.

Phone with the receiver taped up

Image credit : Make sure you are communicating with your client regularly.

You try to defend yourself against John by citing the scope creep and unexpected difficulties. However, it is hard to respond when John said ‘all I needed was a weekly email keeping me up-to-date on progress’.

Explain John’s ongoing role.

By this stage the relationship has broken down entirely. You finish the work and the site finally launches. Begrudgingly John pays the invoice after delaying it for as long as possible.

What amazes you the most is that John says he is bitterly disappointed with the final result. How can that be when you gave him exactly what he asked for? This guy isn’t just stupid, he is also a jerk!

Of course John sees things differently. He came to you with a list of business objectives he wanted to achieve and the site failed to meet any of them.

He hoped that he could launch the website, see it meet its objective, and move on to the next project. Instead, after an initial spike in interest the number of users and enquiries fell overtime and the site stagnated.

Seedling being cared for

Image credit : Ensure your client understands the ongoing care his website will need.

What John did not realise is that sites need continue love and support. You cannot build it and then abandon it. John needed to nurture his website by adding new content, engaging with his visitors and having an ongoing plan for development.

If only somebody had told him.

The moral of the story.

It is amazing me how quick we are to judge our clients.

As web designers we communicate and empathise for a living. Our job is to communicate a message to our client’s users. We create usable sites by putting yourselves in the position of the site visitor. This allows us to design around their needs.

Why then do we so often seem incapable of either empathising or communicating with our clients?

Perhaps it is time for us to use the skills we have grown as web designers and apply them to our own customers.

How moodboards can save time, money and your sanity!

Mood boards are a traditional design tool. However, few web designers use them. This post looks at how they can transform your process, increase profitability and reduce the stress associated with design sign off.

Headscape has been using mood boards as part of our design methodology for some time. We believe they are an invaluable tool that helps both the client and the designer.

However, before you can understand the benefits of mood boards, it is important to acknowledge where the traditional design process falls down.

Where the traditional web design process fails

Obviously everybody approaches the design process slightly differently so it is unfair to refer to a traditional approach. However it would appear that many agencies and freelancers follow roughly this process:

  • Ask the client a bit about what they want from the design
  • Ask the client to identify some websites they like.
  • Produce 3 design comps in Fireworks or Photoshop.
  • Ask the client to choose a design from the comps presented.
  • Iterate until the client is happy.

This was certainly the approach we used until we realised it was not working.

We identified the following problems:

  • When asked what they wanted from their design, most clients focused on personal preference rather than business or user needs.
  • Clients often referred to sites that were either inappropriate for their audience or were selected based on content rather than design.
  • Producing multiple design concepts was time consuming for the designer and expensive for the client.
  • Multiple concepts led to frankenstein design, where the client would try to combine the ‘best bits’ from each comp.
  • The designs went through a lot of iterations because the designer did not have a full understanding of the clients requirements.

We utilised several approaches to overcome these problems. However, the most successful component was mood boards.

What is a mood board?

A mood board is basically a collection of graphical elements that set the tone for your design. Typically these include examples of:

  • Typography
  • Imagery
  • Colour
  • Layout
  • Style

Often these elements are lifted from other sites or even from sources such as magazines.

An example mood board

They are not meant to represent the final design, but rather provide an indication of how the site may feel.

When you first start producing mood boards it is difficult. You may have a strong sense of how the site should look, and so it can be hard producing alternative approaches.

Increasingly we produce four mood boards:

  • One that is our initial gut reaction.
  • One that is a more conservative version of the initial board.
  • One that is more extreme.
  • One completely ‘out there’ approach that is probably inappropriate.

Admittedly you could get away with the first three, but the fourth enables the designer to be more creative and potentially discover a completely different approach.

How mood boards can help

The reason mood boards made such a difference to our process was three fold:

  • They put us in control - Previously it was the client who was making design suggestions and selecting inspirational sites. By using mood boards we were the ones setting the tone and suggesting the direction. After all that is what the client is paying us for!
  • They are quick and easy to create – Developing design comps is time consuming and expensive, especially for something that may ultimately be discarded. Mood boards can be produced relatively easily, which means they are viewed as disposable. As a result the designer is not overly committed to a particular path and the client can see multiple revisions.
  • The client focuses on design, not content – We found that when clients looked at a design comp they were more concerned with the content than the design. Because mood boards do not contain real content, this problem is avoided and the client can focus on typography, imagery and colour.

The introduction of mood boards made an enormous difference to the running of our design projects. However, over time we have made some mistakes that have reduced the effectiveness of mood boards.

Mistakes when designing with mood boards

If used correctly mood boards are an extremely powerful tool. However, it is also easy to fallback into old habits. If you are going to use mood boards, be careful to avoid the following mistakes:

Designing a website and not a mood board

One problem we encountered was that we were so conditioned to build websites that it was hard not to. Every time we produced a mood board it ended up looking like an actual site.

A mood board that looks like a final site

The solution

The way we are resolving this issue is by changing the format. Instead of designing on a 1024 by 768 canvas, we have switched to creating A4 mood boards. In fact we also try to minimise web elements such as navigation or search boxes.

Making them too finished

An associated problem was that clients were getting confused. The mood boards were looking so polished that they were no longer sure what they were looking at. Was this a mood board or a design comp? What were they supposed to be providing feedback on?

The solution

We are still battling this problem. However, one approach I have adopted is setting constraints on the designer. Typically this involves limiting what Photoshop tools they can use.

When all the designer can do is copy and paste elements they have found elsewhere, the mood boards cannot become overly designed. The emphasis shifts from designing detail to looking for inspiration and setting the mood.

Spending too long on a mood board

Of course, the final problem relating to overworked mood boards is time. As our mood boards started to become more and more like design comps, they took longer to produce.

This had two consequences. Firstly it cut into our profit margins. Secondly, the designer became increasingly attached to the mood boards and find it hard when the client don’t like them.

The solution

The solution to this one is simple. We are beginning to set time limits on mood board production. We are now asking designers to spend no more than one hour on a single mood board. Most of that time is spent sourcing elements rather than doing design work.

By taking this approach we can afford to produce multiple iterations of mood boards and experiment with many different directions.

Conclusions

I am aware that we are in a minority by using mood boards. However, I would suggest that every designer should consider them as a tool.

If you design multiple comps then this could be a real cost saver.

If you pursue a single approach, this will enable you to explore other avenues with minimal effort.

So, what do you think? Do you use mood boards already, or do you think it is an outdated tool that has no place on the web? Whatever your thoughts I would love to hear them in the comments below.

170. Versus

On this week’s show: Paul talks about the conflicts surrounding design decisions, and Teifion challenges a BBC article that asks “Are the days of the web amateur numbered?”

Play

Download this show.

Launch our podcast player

News

Please start from the beginning

Not long ago I read Malcolm Gladwell’s book Outliers, which includes many stories about how well known individuals got their big break. There is something fascinating about people’s backgrounds – the opportunities and experiences that help shape a career. I am often surprised that people’s success has more to do with circumstances than talent.

Our very own Ryan Taylor shares this fascination and so has started a new video series where he asks industry figures about their background. He started the series by interviewing me. Apparently he wanted to practice before interviewing important people :-) He has since moved on to talk to Drew McLellan and has Mel Kirk and Sarah Parmenter waiting to be released.

I think there is a lot of potential in this series. The web is still such a young medium and few trained to be a ‘web designer’. It is therefore fascinating to see how people came to the industry. There is also a lot to be learnt for those starting out in their careers. Be sure to pop along to Ryan’s site and subscribe to his RSS feed. I look forward to future interviews.

Running a card sorting exercise

Establishing your site’s information architecture can be one of the most challenging jobs for a website owner. You face two major obstacles. The first is your organizational bias. You can become so institutionalized by the way your organization works, that it can prove  hard to view things from an outside perspective. What seems logical to you can make no sense to an end user. Second is internal politics. Information architecture can often become an area of contention with different parts of the organization vying for top level billing. This can lead to IA by committee, which never leads to a user centric approach.

Card sorting is one way to overcome these challenges. It is an objective way of organizing the information on your site, around user’s needs rather than company structure. It works by putting users in control of creating that structure by asking them to sort cards containing content in a meaningful way.

At first glance, running a card sorting exercise can appear intimating. However, as a post on Sitepoint demonstrates, it is actually straightforward. “Run Your First Card Sort” is a step by step walk through of everything involved in running a card sorting session. Although the method laid out is not the only approach, it does tackle the key steps including…

  1. Preparation
  2. Recruitment
  3. Running the session
  4. Interpretation and reporting

If you haven’t run a card sorting session before and would like to make your IA more user centric, then I would highly recommend this post.

The complete Google Analytics power guide

I have watched with fascination as Google Analytics slowly decimated the website statistics sector. When Google Analytics was launched it was a relatively simple product, more aimed at smaller websites and blogs. However, over time it has become increasingly more powerful and useful to even the most stats hungry power user. Enterprise products have struggled to compete with a product that offers so much functionality for free.

However, with this increased power came more complexity. What was once a simple product has become increasingly harder to master. Although Jeff Veen did some amazing work at simplifying the interface, it is still hard to harness its full power. The result is that many fail to use it to its full potential while others are too intimidated to try.

This is unfortunate as Google Analytics offers so much information to an experienced user. It paints a picture of how users are truly interacting with your site, while informing your sites structure and content.

Fortunately “The Complete Google Analytics Power User Guide” equips website owners with all they need to know to squeeze the full potential from this incredible powerful tool. This series of posts include detailed information on every aspect of the program from setup to tracking goals and funnels. Best of all the various posts have also be brought together in a single 45 page PDF, making it a lot more accessible for offline reading.

If you ever use Google Analytics or are interested in what it can do for your site, this is definitely worth downloading.

Estimating time for design projects

One of the toughest parts of being a web designer is estimating the price of projects. There are so many variables. So many ways you could approach a project, and so many things that could go wrong. Nobody likes estimating a job and rarely do any of us get it spot on. It is a minefield of pain. On one hand you need to add contingency  for the unseen, but on the other, if you add too much you become uncompetitive.

Effective Strategy To Estimate Time For Your Design Projects is a new Smashing Magazine post that endeavors to address these issues. It begins by looking at what causes a project to be misquoted. Reasons include…

  • Unknown technologies
  • Grey areas in the specification provided
  • Bespoke development in unfamiliar areas
  • The cost of sale being too high
  • Lack of time to quote properly
  • Too high a desire to win the work
  • No previous time tracking to refer back to
  • Estimating time for a project is not fun

It then goes on to address each of these issues with a particular emphasis on granular planning and the need to track time.

I have mixed feelings about this post. It provides an excellent structure for creating quotes and even has a list of common tasks to quote against. However, it feels a little labor intensive at points, going into more detail than most can justify. I guess to some extent it depends on the size of projects you undertake.

That said, it certainly makes you think about your quotation process and encourages you to be more efficient in the way you price projects. This can never be a bad thing.

Before I move on from news – if you live in UK mark the 22nd June down in your calendar. That is the date tickets for dconstruct go on sale, and judging by previous years they will sell out shortly thereafter. Myself and Marcus will be there recording interviews for the show. However, we are also going to arrange a meetup over lunch so hopefully that will be an extra incentive to come.

Back to top

Feature: Clients vs. Designers

Establishing the look and feel of a site can be a point of contention. Web designers can become frustrated because their expertise is not respected. Client are annoyed because their designer does not listen to them. How then do we ensure the design process runs smoothly?

Read The Battlefield of Design – Clients vs. Designers

Back to top

Listeners feedback: Amateur vs Professional

Teifion Jordan sent us a very insightful review of a BBC article that I wanted to share with you…

The article is titled “Is the web’s amateur hour over?“, a provocative title for those that blog, contribute to open source, have a flickr account with photos licensed under CC and so on and so forth. The article opens describing somebody that revels in the name “Antichrist of silicon valley”, anybody that revels in a name such as that is either crazy or doing it for the attention and page views it brings them. It sums up the rest of the description pretty accurately.

The article then explains how he dislikes things such as Wikipedia because they’re maintained by people working for free, how seasoned professionals are being put out of work by amateurs on youtube. At this point the article moves onto showing that all the big tech bloggers, these so called “amateurs”, are actually seasoned journalists.

The crux of the article is of course Amateur vs Professional, does the fact that anybody can start a blog mean that anybody is a journalist? Does having a flickr account make you a photographer? Yes and no, technically yes but in reality most people will never gain enough of an audience to become influential or make money from it. Professionals are paid and generally for a good reason, a professional blogger probably has experience and good writing ability, an amateur probably won’t.

But we’ve still not come to the actual issue, I’ll say it again. Amateur vs Professional, yes that’s it, it’s the 2nd word in, verses. The sensationalist man described at the start of the article seems to feel that there is a competition on between those that work for free and those that work for money. More importantly, he feels that those that work for free are making it harder for those that work for money to find work!

But that’s really not true is it? If it were true then wouldn’t we all be using Linux because it’s free? Wouldn’t Open office be the de-facto standard of office software? Why would Apple even bother making the iPhone if Google is just going to make Android? Why does Paul bother to make websites when anybody could just do it for themselves?

There are I think three main reasons. Quality, Trust and Support. Open Office is a nice piece of software but it’s not got the features of MS Office, it’s not as high a quality product. Linux is really really well supported if you know where to look, for most people however they’d much rather get a normal computer which they already know how to use and can phone tech support for. And trust, if you pay Paul huge sums of money to make a website for you then you trust he will do a good job, that he knows what he is doing.

So no, I don’t think it is Amateurs vs Professionals, I think it is Amateurs and Professionals. One does not exclude the other, instead one will spur on the other and generate often healthy competition. Think about how much IE6 stagnated because nobody was competing with it any more. Now that people are competing with them on browsers MS are starting to get their act together somewhat.

Next, the work of an amateur can be used to help a professional. PHP is a free product but countless people make money writing websites in PHP. Throughout this “review” I have maintained the position that on average a paid for product or service will be of a higher quality. This is true, on average it will be better but not always. There’s a reason that if I had a 2nd computer it’d be booting Linux and not Vista, there’s a reason I develop websites in PHP rather than C#. It’s because the free option is better or the paid option not good enough to warrant the cost in my opinion.

Lastly I want to come to why. We’ve all seen them, the blogs that must have about 3 readers one of whom is the Mum of the author, I know they exist because I write one such blog. Why do people post up bad photos to Flickr? Why do I spend a lot of time running an online game from which I make no money? It’s because everybody has a hobby or two and this is the way that they peruse it. There is nothing wrong with this and should in fact be encouraged. What may now be a bad set of photos on a flickr account could in a few months with encouragement and tips a very good set of high quality photos. What may for now be just a programming hobby could in a few years turn into a very very good language.

Paul started up this podcast because he thought it’d be fun and may or may not have been high from using the computer for too long. It’s come a long way since then with thousands of listeners and an entire community built around it. Thus I end with the idea that while something may be amateur now, it can become professional in time and that this is good.

Back to top

Big mistake

Every web design agency screws up from time to time? We’ll tell you our screw ups, if you tell us yours!

I recently received this email from Dinu…

Looking from afar, established agencies like yours seem to be almost perfect. However, I’m sure you’ve had to deal with missed deadlines, over-booking, etc. I would like to hear about some of these #fail stories (just to get a “you are not alone” feeling for the rest of us), and also to know how you managed to overcome these common pitfalls.

Its a great question and one that few in the industry discuss. After all who wants to admit their failures. To be honest, I am just as interested as you to hear how other web design agencies screw up! As a result, I am going to keep this post short. What I want to do instead is open it up to general discussion in the comments – What have your big mistakes been? Please share, I am dying to know.

That said, it would be rude to ask for your failures without revealing my own! Here are my top 5 (there could have been many more!)

1. Not nurturing our biggest client

We nearly lost our biggest client once. Our work was good. We delivered on time. We kept our pricing realistic and fair. However, we nearly lost the client because we started to take them for granted.

When we first started working with them, we were hungry and enthusiastic. We would be proactive and suggested loads of ideas. Overtime however, we got stuck in a rut of delivering whatever they asked. We stopped innovating and suggesting alternatives.

Fortunately we had a good enough relationship with the client that they didn’t drop us immediately. Instead they told us they wanted the “magic back” and so we worked hard to repair the relationship.

We discovered that a good agency has to do a lot more than deliver. They have to be proactive, enthusiastic and work hard to provide the best customer service over the long term.

2. Ignoring culture when recruiting

We made a major mistake recruiting a developer. His qualifications were good and on paper he looked great. He even interviewed well. However, when we got him on board it quickly became apparent we had made a terrible mistake.

His previous job was working in the public sector and he could not adjust to the culture of an agency. The speed and variety of work overwhelmed him and the cultural shift proved too much.

This wasn’t his fault. It was ours. We should have spotted the problem before we  offered him the job.

3. Not challenging clients

In the early days of the company we were so desperate to please clients that we basically did whatever they asked. I remember one client in particular who turned into a micro-manager, picking over every aspect of the design. We would dutifully make a change only to have him decide he didn’t like it, and get us to change it back. Unfortunately once the relationship had been established it was very hard to change, and we were a doormat to this particular client for a long time.

Things have moved on  and we now view our relationship with our clients as collaborative. We work together to produce a great website. Part of providing a good service is a willingness to challenge bad decisions and provide our design expertise. We used to be nothing more than pixel pushers, and clients were paying for a better service than that.

4. Allow scope creep

This is a mistake we didn’t just make once, but rather again and again. In fact we still occasionally do this now, although we have become much better.

Because of our desire to please clients, we would allow them to add new features late into the development cycle. However, ultimately we were doing our clients a disservice. Scope creep leads to additional expense and slipped deadlines. It also adds complexity, which can often damage the user experience.

Features added late in the development cycle are often less considered and rushed in their implementation. Ultimately this can lead to a second rate product.

Today we encourage our clients to phase development and so move new suggestions into an upcoming phase.

5. Under pricing project

We still do this! However, the reason we do it now is at least different to the early days. If we under price now it is because we have made a miscalculation over the time a project will take. In the early days we would under price because we were desperate for the work.

However, as with scope creep, under pricing can lead to cutting corners. It is easy to fall into the trap of taking shortcuts to keep the project profitable and ultimately that costs the client. Also, it is hard to ever pull back from low pricing. Once a client has been given a low price they will expect the same for future projects.

Under price at your peril!

So, what about you? What are the biggest mistakes you make running your web design business? Let us know in the comments.

165. Creativity

On this week’s show: Jim Coudal shares his thoughts on monetizing creativity, Marcus talks about questioning clients and Paul gets excited about eye candy.

Play

Download this show.

Launch our podcast player

News

The power of asking questions

I am spending a lot of time recently advising clients how to ‘engage’ with their users. Engagement seems to be the buzzword of the moment, and to some degree rightly so. Engaging with your users is important for a number of reasons including (but not limited to)…

  • It increases loyalty and repeat business
  • It encourages users to promote you and your services
  • It informs your products and services

Although a lot of people understand the importance of engagement, few know how to do it effectively. As is so often the case website owners turn to technology as the solution. They launch forums, add comments and sign-up for twitter. However, when it comes to engaging with human’s, what you say is considerably more important than the medium through which its said.

Take for example your blog. Just because you have comments enabled, does not mean users will post. As is pointed out on the Pro Blogger website, if you want to encourage comments you need to ask questions.

Pro Blogger provides 10 reasons why questions are good, before going on to share 12 tips for asking them. Some of the suggestions are extremely useful, such as using the answers you receive as the basis for another article. Its a good post and definitely worth reading.

The do’s and don’ts of modern web design

I don’t normally highlight new web design sites, but this one caught my eye. Called “the do’s and don’ts of modern web design” the site is essentially a directory of web design posts. What makes the site different is that each article is boiled down to a single  concise tip that is either assigned to the “do” or “don’t” column.

The Do's and Don'ts of Modern Web Design Site

Posts are also tagged according to their level of complexity (beginner, intermediate or advanced) and users can  view posts by popularity or date.

The user also has the option to read the entire post or simply rate the advice being given.

As a blogger I do have some concerns about this site. The idea of somebody boiling my posts down to a single point is disturbing to say the least! However, as a user there is something very convenient about getting short condensed snippets of information. We are all busy people and too many bloggers take forever to come to the point (myself included).

Uses for hover

The Web Designers Wall has released a post this week entitled “Maximize the Use of Hover“. If you are a designer it is definitely worth reading.

I am a huge fan of using hover in my design work. This is primarily because it makes additional information available without cluttering up the user interface. It keeps things simple and prevents the user becoming overwhelmed.

The post breaks this argument down further and identifies 4 reasons to make greater uses of hover. Their reasons include…

  • Using hover to beautify layout
  • Using hover to minimize clutter
  • Using hover to display additional information

Each point is supported by some great examples of hover in action. The post also ends with some links to useful ‘hover’ tutorials to get you started. One is a CSS only tutorial while the other uses jQuery. Personally, I use jQuery a lot for achieving hover effects simply because it is visually more attractive and also easier to build.

In defense of eye candy

I want to conclude this week’s news with one of the best articles I have read in a long time. ‘In Defense of Eye Candy‘ on A List Apart is a well constructed argument for the importance of aesthetics.

The author (Stephen Anderson) explains how aesthetics affect…

  • our understanding of a user interface,
  • the level of trust we have in a brand
  • our ability to complete a task.

It is a beautifully considered case that delves into the world of cognitive perception and provides some excellent examples of how aesthetics alter our attitudes. One particular favorite is the example of the Sony AIBO and their decision to make the robot look like a puppy. Stephen writes…

Here, you have a robotic device that isn’t perfect. It won’t understand most of what you say. It may or may not follow the commands it does understand. And it doesn’t really do all that much.

If this robot was an adult butler that responded to only half our requests and frequently did something other than what we asked, we’d consider it broken and useless. But as a puppy, we find its behaviors “cute.” Puppies aren’t known for following directions. And when the robot puppy does succeed, we are delighted. “Look, it rolled over!” What a great way to enter the robotics market.

However, ultimately the entire article is summed up in the following quote…

According to a 2002 study, the “appeal of the overall visual design of a site, including layout, typography, font size, and color schemes,” is the number one factor we use to evaluate a website’s credibility.

Back to top

Interview: Jim Coudal on monetizing creativity

Paul: So, joining me today is Jim Coudal. It’s good to have you on the show.

Jim: Thank you.

Paul: Thank you for coming along. We’re actually sitting here at the Future of Web Design. Jim has just given his keynote presentation, and I’ve also got Marcus here, hello Marcus.

Marcus: Hello Paul. Hello Jim. (Laughs) I’m not normally in on the interviews, that’s why it feels a bit weird.

Paul: Yeah, you’re not used to this bit are you really?

Marcus: No, I’m not used to being at the Future of Web Design doing it either. He does the interviews over the phone usually.

Paul: Yeah, this is weird – face to face. Um, so, brilliant brilliant presentation as always, um, and I wanted to talk to you about some of the different, um, issues relating to creativity, because you seem to talk a lot on that, and obviously at, um, Coudal Partners, isn’t it, Coudal Partners, yeah, you have to deal with this kind of issue all the time and working with creative people and how to encourage creativity and you do some very interesting stuff.

Jim: I mean, first to say, I think part of the structure of Coudal Partners is in response to a, er, earlier career frustrated with creative things, so really Coudal Partners, er, everybody there is artist or writer. So, you know, there is no, you know, we probably without business plan for 13 years, you know, there is no superstructure of account planning or any of that.

Paul: OK.

Jim: That’s possible, I think, because we’re all responsible people, but it’s also possible because we’ve made a concerted effort over the last 5 years to reduce the amount of revenue that comes from clients.

Paul: OK.

Jim: So, erm, we. Our biggest clients now are companies we own.

Paul: Right.

Jim: So, which is a blessing because we can do whatever the hell we want, and a curse because things don’t work out. (laughs). You konw, you’ve still got to make payroll.

Paul: Yeah, totally.

Jim: So, yeah, I think that the, you know, we’re all adults and we’re all responsible people and we all have a variety of interests and I’m reminded of a story. Do you know Cabel Sasser, from Panic, Panic Software in Portland – Transmit, and Coda and all that?

Paul: Oh, yes.

Jim: Well, he posted, at that time, Panic was just Steven and Cabel and he posted a video on his site, because everybody said: “what’s a typical day like at Panic?”

Paul: Yeah

Jim: So, he posted a video on his site, and I think it was like 20 minutes, of 2 guys with headphones on, staring into computer (all laugh), and like about 10 minutes into it, one of them gets up and goes to the washroom and then comes back and puts his headphones back on and stares at his computer.

Paul: Right.

Jim: And so, I watched the whole video and I wrote him right back and I said: “Cabel, it’s amazing, it’s exactly like that here!”(all laugh) Everybody has this idea that, you know, the rock and roll is blaring and, you know, someone’s having a bong in the back, or whatever, but it’s very much a individual efforts in a collective environment.

Paul: Ah, see that’s very interesting, because you’ve got a company full of creative people that are obviously coming up with lots of creative ideas and the question is: “how do you monetize that?”You know, you’re trying to move away from client work and we all understand how client work is a nice neat model and a way of making money, but you know, you guys are coming up with ideas all the time and they’re very broad-ranging. So, how do you decide which ones, you know, you can make money out of?

Jim: I mean, the purist answer to that is, the ones you’re most excited about. Erm, and try them all and get ready to bail on the failures, you know. The one question I always get whenever I speak, the first question I really get is: “Jim, what is your most spectacular failure?”people always say, and my answer is always the same is that we’re working on it right now! (all laugh) Its going to be a beauty! Erm, you know, we… Ideas tend to take the path of least resistance and frequently that path is being talked to death. It’s very easy to have a good idea and then sleep on it and then the next day come up with a thousand reasons why you can’t do it. Er, in this day and age, where we have, at Coudal, we have the superstructure, we could pretty much sell anything in a couple of hours. We have built our own e-commerce background for, we own a brand called Jewelboxing, which sells custom DVD and CD packaging systems, we own Fieldnotes, which is a, er, series of memo book, cool memo book, designer’s sort of memo book, and various other things and so we can put an idea into play very quickly, and, erm, and just a little less quickly find out if it’s going to work. The key to the whole thing, though, is that, erm, when we started this idea of creating products and services, erm, as opposed to, erm, doing work for hire, we sort of looked at the things we had, what were our assets and what were, you know, what were the things that we had, and what we had was this site coudal.com which generates a lot of traffic and the site is strange. It is not, it is sort of a daily magazine of web design intellectuals, I guess, for like a better term. And, erm, many people don’t get it at all, but a lot of people do so we figured that those people must be like us, in some way. I mean, it’s, it’s impossible to think that they are people who are unlike us, who are coming to the site and a) understanding it, and b) coming back tomorrow. So, these people must be like us. So, if we make that leap of faith and we develop products that we want, there’s probably a lot of people like us out there and we don’t actually need 5% of the global notebook market to make a lot of money, you know, so, erm, the same goes with our ad network, The DECK ad network, which is tremendously successful because it targets web-designing creative professionals like us, so the idea is, if you’re true… The question is how do you decide which ones you do, and my answer is it’s the ones you’re most excited about. I think that the secret underneath that is, if you make something you’re excited about, somebody else is going to be… Somebody like you will be excited about it as well. So, erm, but not everything has to make money; a few things have to make money, we have mortgages, we have tuitions to pay, for our kids, you know and we’re not getting rich, but, you know, we’re pretty satisfied creatively and we have the freedom to do pretty much whatever we want, so…

Paul: I mean, I think a lot of people that will be listening to this show that may be a creative, um, are kind of creative, um, within an organisation that isn’t creative and you talked about the frustrations you experienced, you know, they’ve got to, kind of, justify to management and all the rest of it, that they need time to play and to experiment and to try new things. I mean, how, have you got any advice for those people about how they tackle that, you know, how they, they kind of demonstrate the need to be creative, if that makes sense.

Jim: This is, I’m going to come off like a smart-arse, but I think that the real advice to somebody who’s truly creative and in that situation is to quit.

Paul: Right, OK.

Jim: I mean, you’re never going to succeed in that environment; you may succeed, but you’re not going to be happy or fulfilled. But outside of that I realise that there is a wide range of things and I… But, I don’t have any advice, because I tried everything I could, within a corporate structure as a creative director of a large ad agency, erm, and it got to the point where we were doing work I wasn’t proud of for people I didn’t like, and, you know, no amount of money can make that feel better; like, you work for a month on a project and, the revisions and the bullshit just steals your soul and by the time you’re done with it, you don’t even want to show it to anybody, like, there’s no amount of money that can make that feel better as a creative. So, so, you know, I think, you know, we all have to make our bargains, but I’ll say one other thing, Paul, is that I know a lot, through this whole, we’ve talked about this moving from work for hire into a more, what Zeldman calls sort of a design entrepreneur, sort of, er, piece. We’ve talked about it a lot in public so we’ve got a lot of feedback and I’ve spoken about it on a number of occasions, so I’ve met a lot of people who are sort of in the same place and there are a lot of people who are in the same place.

Marcus: We are.

Jim: Who are creative firms, what you’re doing for other people. The guys at Threadless are good friends of mine, you know, like all these people who have taken the skills that they used to use on behalf of clients and put them to work, their craft, on behalf of themselves, and every one of them, without exception – I will include you in this and I’ve never even asked you this question. Every single one of them says exactly the same thing about the process and they almost always say it in exactly the same words.

Paul: OK.

Jim: And what they say is: “I should have done this sooner”.

Paul: Yeah, totally.

Jim: So, my unanimity and this response continues with Paul, who agrees with the whole thing, but sometimes you know that first leap is kind of difficult. I would say that if you don’t have kids and you don’t have a mortgage, you better get on it.

Paul: Yeah.

Jim: After you have kids and a mortgage you got to make other decisions but, you know, we did it when we had kids and mortgages.

Marcus: So have we. It was your chat with Brendan Dawes at the 2007 Southby.

Jim: The ‘Short Attention Span Theatre’?

Marcus: Yeah, but you were talking about The Deck and various products and it was kind of, I was sat watching it, not with you, you were in another talk…

Jim: You were in another talk? What the hell!

Paul: I know, it’s disgraceful, I’m ashamed, I’m sorry.

Jim: That was a funny day because that was like Twitter was just new and so like people were twittering that, because Brendan Dawes is such a great speaker, he’s so funny and so they were twittering that: “oh, you got to come and see Coudal and Dawes”, and so we encouraged that so we’re like, so everybody tell people in the other rooms to come over here and we’ll give them a book and so people started doing it and then people started coming in and I’m like: “oh, my God, I feel so bad for the people next door”, you know, so it was really an interesting kind of a…

Paul: Social experiment.

Jim: It’s like live social reviews. Anyway, go ahead.

Marcus: It was great, I mean, basically what it did, Chris and I – another partner and I in our firm – we basically walked out of that speech and said: “we’re doing this wrong”. We were just thankful that clients wanted to work with us at that time and more and more clients were working, but it was kind of like we got this huge team of very creative, very talented people, let’s do something ourselves and ever since that day, I mean, we haven’t been as successful as, as successful in doing that as you have, but I think you put the nail, you hit the nail on the head…

Jim: Well, it takes time, I mean, we didn’t just flip the switch, I mean we went from 75% client work, 25% our own work and then eventually we got to 50%; I remember, I remember that month when I was doing month-end numbers and I saw that on gross revenue we had made more money from our own than we had made from client teams for the first time, I remember that being a significant moment for us as well.

Marcus: Time for a drink.

Jim: So, you know, um, that’s interesting, you know Brendan’s doing the same thing.

Marcus: Yeah, I know, I keep up with him on Twitter, but it was the fact that you said you can do things quickly and we’re always, we get these great ideas and then it’s like that’s going to take 3 months, or that’s going to take 6 months.

Paul: We faff around a lot.

Marcus: And client work gets in the way.

Jim: We share space in Chicago, in a big loft space, with 37 Signals.

Paul: Oh, I didn’t know that.

Jim: And they are, they’re rapid to the, to a fault, where their ideas, if they have a good idea, let’s whack it together and put it out there and then, you know, let’s launch the ship and then we can turn it once it’s moving, but we can’t turn it if it’s still up here in dry-dock, you know, which is an interesting thought, so you know, and it’s… The thing is when we’ve worked for clients, the problem with exclusively client work is that you have to feed the beast, so if you get good at it, you’re screwed (all laugh), because you get more work.

Paul: That’s exactly what we’re finding.

Jim: And then you’ve got a bigger payroll and overheads, so now you’ve got to take more work and eventually you’ve got to take a project that you might not take that…

Marcus: We’re screwed, Paul.

Paul: Yeah, we are, we need to do something.

Marcus: We keep hiring more people.

Paul: This is turning into a therapy session for us.

Marcus: I told you that.

Jim: How do you feel about that, Paul?
(all laugh)

Jim: You know, generally the thing is this, the opposite it true, because the best thing that ever happened to us is that our client business went to hell, through no fault of our own.

Paul: Right.

Jim: Right after September 11th, you know, a couple of clients cut budgets and all of a sudden, nothing will get your attention faster than not having the money in the bank on Wednesday to make payroll on Friday, so…

Paul: Which is often the way with this whole, you know, leave if you’re somewhere where you’re not happy and set up by yourself. Often you need that push.

Marcus: It happened with us, yeah.

Paul: I mean we worked for a dot-com and that went under, so it pushed us into doing something ourselves. I mean that’s interesting, that… When you, when you left the big agency, and you set up by yourself, was it just you or did you set up with other people?

Jim: One other fellow.

Paul: Right.

Jim: And one accountant.

Paul: Because that’s a lot of problem, there are a lot of freelancers out there, that are working in isolation, and that’s quite hard as well, from a creative point of view to, you know.

Jim: Very difficult.

Paul: I mean, where, where do you look for inspiration? You talked in your talk about looking to the past, which I thought was very interesting, but what kind of, where do your ideas come from?

Marcus: That’s a fair question.

Paul: That’s a really unfair question, I’m sorry.

Jim: Erm, I think they come from Dublin, no I don’t know. Let me take the two parts one at a time.

Paul: Yeah, I’m sorry it’s a messy question.

Jim: The first thing about working alone, erm, we are not a distributed company, unlike a lot of companies, we actually, we’ve tried some of it and been unsatisfied with the results. We actually all get together, we all get together in the same space and then don’t talk to each other (all laugh).

Paul: But at least you’re together.

Jim: But there is some advantage in adult conversation, there is advantage in: “hey, how about this?”There is: “can you look at this and see what you think?”or “do you have a headline for that?”You know, there’s some advantage in, sort of, serendipitous conversation, there’s advantage in going to the tavern and having some beer and blue-skying, you know.

Marcus: Boardroom B.

Jim: Yeah, conference room B. Er, conference room D, whatever, whichever conference room it is. So I find it difficult; now, I’m particularly good at working alone as an individual.

Paul: Right.

Jim: But as a firm, maybe we’re not so good at it. So, you know, I need help because I’m like Brendan, I’m a great starter but not such a good finisher.

Paul: Yeah, I’m the same.

Jim: So I need people to sort of clean up after me and make sure things get done. I’m OK with it.

Paul: It’s so nice to hear someone else say that. It’s OK that I’m like that, Marcus.

Marcus: Well, I’m kind of not far from it, to be honest, but Chris and the rest of the guys…

Paul: We’ve got a whole company that exists purely to pick up our rubbish.

Jim: And they just roll their eyes, like: “there’s another idea from those guys, like that’s going to happen”. Well, that’s the thing, we have this thing, maybe I talked about it in the, Brendan talked about this thing: ‘The Book’ – we’ve had this thing for a long time which is this repository of un-, unrequited love, of ideas that we never did. Um, and we’re getting so good at it that we know immediately when an idea is for The Book; it doesn’t stop us from blue-skying about it, say OK, in fact sometimes we say: “here’s one for The Book”. We know immediately that, you know, everybody knows immediately. We have this other, we used to have this thing, we haven’t been doing it lately. We have this other thing is that when we’re brainstorming about something, it helps if, um, you, er, talk about potential taglines and headlines, while you’re brainstorming an idea, but you don’t want to get the conversation caught up in the specifics of the headline or tagline that you’re suggesting. So, we used to have this thing where, if you keep your hand over your head when you are talking, it means: “like this, but not this”. (Paul & Marcus laugh) Try that sometime in one of your creative meetings, seriously. “I want this to be, sort of, you know”, Tim is holding his hand on his head, sort of thing. Erm, collectively ideas come from a variety of different interests, I think, and obsessions. I mean, it wouldn’t be too difficult to go through the archives of all the links we’ve posted at Coudal and figure out that we, you know, you could build a Coudal robot pretty easily that is a Stanley Kubrik freak, who is into Swiss design from the mid-part of the century, who is a James Joyce and a, er, Terence Malik fan, you know; it would be pretty easy to see Bob Dylan, you’d be able to see the sort of influences in some places. And, erm, I think to have a lot of different skillsets together, like Steve in our office is a film, primarily, he writes some copy and does a lot of things, but primarily he’s a shooter and an editor and a creative guy and I don’t do either of those things, you know, and, erm, Brian is a print guy, I mean everybody does everything at Coudal but we have like a bunch of different skills and so i guess that’s it, I don’t know.

Paul: Yeah, that’s good.

Jim: I probably didn’t answer anything.

Paul: Well, I think the trouble is with a question is that it’s, you know, to some extent it’s different for every person, you know.

Jim: Different for every day.

Paul: Yeah, that too, yeah. So, you know, that’s understandable.

Marcus: I thought you were going to go off into the into the equation of, I don’t know, maybe you covered that in your talk? The er, what was that…

Jim: The ‘General Theory of Creative Relativity’; we don’t have enough time for that.

Marcus: Let’s move on.

Paul: You could google it if you want to know about that.

Jim: Yes, actually that was the South-by talk for last year, and that, erm, was a pseudo-scientific to sort of come up with an equation to solve all creative problems, erm, and somebody said: “what is the answer?”and then someone from the audience yelled: “42”.

Paul: Well, obviously. It would be, wouldn’t it. Um, let’s just wrap up by talking about layer tennis, because you’re kind of quite well known for layer tennis and, just explain the basic principle for those that maybe haven’t heard about it before.

Jim: Layer tennis started 5/6 years ago as Photoshop tennis and it started in our office where we were, we just swapped a file back and forth continually adding layers and type and images to it and it was sort of a collaborative dance, and, erm, we just had the idea that maybe people like to watch it, so we put it online and invited designers that we know or, even better, designers that we admired but didn’t know, to participate and we had the brilliant, somebody had the idea to do it on Friday afternoons because no work gets done on Friday afternoons anyhow, and so we did it for a couple of years, it was tremendously popular, and then we left it on the back burner and went on to other things and in the meantime we had been working with Adobe on a couple of things and they were looking for an innovative way to promote their CS3, Creative Suite 3, and we said: “well, we have this Photoshop tennis thing, we could sort of restructure this in a way”, one of the big parts of CS3, a big, big step forward for me as a user was, the interoperability of the apps, it was the bringing together the Macromedia applications, as well as original Adobe applications into one place in which you could really move a file back and forth from vector to Photoshop to Flash, whatever. And so we proposed that we re-launch it as layer tennis to, not only that I didn’t want to have someone else’s trademark in my trademark, so we re-launched it as layer tennis and now I think we’re in the tenth week of this second season, we’ve had some tremendously talented designers from all over the world and basically what happens is there are 10 layers, somebody serves by serving up an image or image and type and, or illustration, or Flash animation, whatever it is, and the other designer takes the original source file and revises it in someway, either adds to it or changes and then he sends it back to the original guy and they trade the file back and forth over about 3 hours and each of their volleys gets posted live to the web. In addition, we invite a third person, frequently a blogger, or a writer, or a smart ass, to write play-by-play…

Marcus: That’s the bit I like!

Jim: To write play-by-play commentary. Quite frankly, that’s the hardest job (Paul: Yeah) on any Friday, to write play-by-play commentary; and then everybody watches and twitters about it and votes who they think the winner is and, you know, we’re doing 30-40 thousand people every Friday are tuning in to watch the match live, which is like, if you think of it, that’s a full football stadium, so we’ll have a couple more weeks of the regular season and then we have, we’re going to do some play-offs and hopefully there’ll be layers tennis season 3 next year, so (Paul: excellent) it’s interesting because we’ve tried to get out of the client business, right, and now we’ve got this sponsored web event which is sponsored by AARRGH! Adobe, a client. But, I think the difference is that it’s on our terms and they, it’s through good being in San Francisco, they couldn’t have been greater they’re great supporters of it and they take great ownership in it, so…

Paul: And the other thing about it is that, you know…

Jim: It’s relevant.

Paul: You did it anyway, you know, it was an idea you’d had previously that you then found somebody to help fund it and sponsor it.

Jim: And make it bigger and better, right? And it’s relevant to the product, like, you know, I’m not sure that Budweiser layer tennis would have the same relevance.

Paul: No, of course.

Marcus: Friday afternoon?

Jim: Maybe a little sloppier, but, you know, so, I think, it was just a lucky, you know, I mean, we’re pretty smart about things, but that was, kind of, a lucky break for both of us, I think that Adobe gets a lot of valuable exposure out of it that is not seen as “advertising-y”, you know, layer tennis exists on our site, it’s not on the Adobe site, it is seen as an independent, which it is, very like you said, it existed before the sponsorship and will exist after it and it was seen as an independent thing for the good of creativity on the web that Adobe is a good citizen for sponsoring and, you know, that’s a nice thing, maybe that’s the future, you know, that sort of which is actually…

Paul: Collaborative relationship

Jim: And that’s actually looking to the past as well, because think about the beginnings of television, or at least in the United States, the beginnings of television were a single company which sponsored a single hour drama, they would be the ‘Hallmark Hall of Fame’, where, here we have this lovely drama brought to you by Hallmark and they’re all about emotions and drama’s all about emotions, you know, and then somehow we got to the point now where we have an hour where we have 22 minutes of 30 second commercials, you know what I mean, like, you know, there’s, you know, so…

Marcus: It comes down to the fact that the content’s got to be good and it’s something that people want, and if it is good, then you’re going to get sponsored; it’s like sports, isn’t it? From that point of view.

Jim: It is a sport, I mean, in a way, the layer tennis thing is attractive, I think, because we do compete as designers all the time, like my firm will compete with your firm for a piece of business, but we never compete head-to-head (Paul: No) and never, ever, ever, compete head-to-head in public. So, it’s nerve-wracking, the designers are like: “Oh yeah, I’ll play”and then they get to see the site, “oh my God, 15 minutes”, you know, and the poor writer, like the designer at least volleys and then gets to breathe for 15 minutes while the other guy has the file, whereas the commentator has just got to be funny all the time, you know. I just did, for the first time ever I did commentary myself two weeks ago.

Paul: Ah, that’s why it’s showing up that you’ve got sudden sympathy for it.

Jim: And all the other commentators were writing me, like “ah, now you’ll see, asshole”(Paul & Marcus laugh), but I bailed out, I’m such a terrible typist I did it, I did audio.

Marcus: That’s alright

Jim: Yeah, I just talked about it, you know I got nervous that I wasn’t doing well enough, so I called my friend John Gruber and brought him into the booth, so everybody got mad at me, because I didn’t do it the way I was supposed to.

Paul: You cheated.

Jim: I did, but I have that option.

Paul: Hey, it’s your game.

Jim: Since I’m the commissioner.

Paul: Exactly, yeah.

Jim: The ‘Royal and Ancient Society of Layer Tennis’

Paul: So, what do you think people are getting out of it, you know, as they watch layer tennis? Is it just to waste a Friday afternoon (Jim: Yes) or do you think there’s a… I was going to, I was expecting some profound answer about the value of it.

Jim: No, I mean, I think it’s interesting and I think it’s entertaining and I think people like to see designers they know and with talent compete in a interesting situation, but it’s the almost perfect sport for procrastination.

Paul: Right (laughs)

Jim: Because nothing happens for 15 minutes and then something happens (Paul: Right), so you just leave it open in a tab and you can do your work and then bounce over and see it and, er…

Marcus: Is there not the kind of moment – sorry, Jim to interrupt – of kind of like: “I would never have thought of doing that?” and then you take that away to something you’re working on, so…

Jim: Yeah, we could…

Paul: Yeah, yeah. Let’s pretend, let’s pretend there’s value in it.

Jim: I can see, because you do so much client work, you’re getting good at rationalising things (all laugh).

Marcus: This is why we did this, and this is why it’s going to cost you.

Jim: This is my idea and this is why it’s great – it’s the Python skit about, you know,“I want you to help me sell all of this string that I’ve got left over”, “oh great, string, good for tying everything up, perfect for putting around your backyard”, he goes, the problem is that the string is all cut into 6 inch lengths: “just the right length!”

Paul: Well, that’s great, Jim, thank you very much for that. Where can people find out more about you and about layer tennis and stuff.

Jim: Coudal.com pretty much has links to everything; layertennis.com is where that is and I’ll make a pitch for our products, go to fieldnotesbrand.com and buy some notebooks and add a note that says you heard it on this and we’ll throw something extra in the package.

Paul: Excellent. Good stuff, thank you very much, Jim.

Jim: You’re welcome.

Marcus: Cheers!

Thanks goes to Simon Douglas for transcribing this interview

Back to top

Listeners feedback: Questions, questions, questions

We have this question from Iestyn:

I’ve done a quick search on your site and on Google but can’t seem to find what I’m looking for. I’ve been in the print industry for 9 years now and finally making the jump to web design with a friend of mine. What I’d like to know before getting our first client would be what questions should we ask the client about what his or her requirements are, as the client might take some stuff for granted or wouldn’t have thought of some things? And what questions are we likely to receive off our clients? To be able to have a questionnaire at hand to refer to and to go back to if the client changes his/her mind.

Users

One of the most important areas to consider when first discussing requirements is user focus. Does the client think in this way or are they looking for a site that meets internal expectations for design and content?
Who are the target audiences? ‘Everyone’ is an unacceptable answer. Get the client to prioritise their audiences.

Talk about your expectations of the roles of client and agency. You don’t want them to comment “I don’t like the red” rather you are looking for “I don’t think red will work for our users because…” Stress that it is their responsibility to highlight issues but yours to solve them.

When reviewing information architecture, ensure that content is grouped for users, and not based on internal structures and ensure that labelling is clear and descriptive.
This will underline the importance of the role of the user to the client and hopefully start them thinking in a way that will help you deliver a more usable site with fewer hiccups during the build.

Goals

It’s important to get to the bottom of why a client has a website and what they want it to do for them. What are their business goals and why?

For example, are they looking to increase sales via the site? The goal may simply be ‘we want more sales leads through the website’. But, more leads do not necessarily mean more sales. The quality of the lead is likely to be paramount. The design of the site should not simply encourage more leads, it should help to encourage more high quality leads.

Measurement

When you have a good understanding of the client’s business objectives, it is then a good idea to agree how best to measure them. You are not necessarily putting a personal guarantee next to each of them, but it will help you focus on the priorities for the site.

The good, the bad…

It’s very rare to be asked to build a brand new site these days. Chances are there will be a number of previous versions of the site that you are being asked to redesign. These old sites are goldmines of information.

Ask the client to list what works on their current site and why. It’s possible, for example, something that is popular is distracting users from achieving calls to action associated with the business objectives.

Ask the client what their top three issues are with existing site and ask them to prioritise them. Ask them what the most important content is on the site and ask them to prioritise it.

This information needs to be checked against user requirements and business goals. I’m heading off track here… back to questions.

Other sites

Even though I have said that clients need to focus on what their users want from their site, it is also important to cover competitor sites and sites that they admire. Let’s face it, these people have to live with the site every day – they do need to like it!

When reviewing competitor sites try to focus on areas that differentiate each site/company. Are there any common issues? For example, do all the competitor sites avoid plain English? Is this an issue for the user base (or not)? Could the client make it a differentiator for them?

USP

Make sure that you have a good understanding of why people ‘buy’ from your client? What makes them different?

Also, make sure that you are aware of any strategic goals and possible changes in directions that might be coming up in the future.

Nuts and bolts

General areas that you need to cover on top of all this could be:

  • Branding/corporate identity – what, if any, are the constraints?
  • Technological constraints
  • Assets – such as content and imagery
  • Timescales, milestones and project management
  • Contracts
  • Support

So what about you?

Most client concerns will focus on your reliability. Have you done this type of work before? Was it successful? Did you deliver on time and on budget?

There is a mutual trust issue at the start of any client/contractor relationship. We have found that the most effective method of calming any client fears is to actively encourage them to speak to your existing clients. If you’re really brave, let them look through your portfolio and let them select the client!

I guess this wasn’t really a checklist of questions but I hope it was useful.

Back to top

Hampshire Web Developer required

Are you a web developer living in the south of england? Once again, Headscape is looking for a talented, enthusiastic developer to join our team. We really need to stop expanding ;)

It was only 5 minutes ago we hired Helen but we are already looking to hire a new developer. We are looking for somebody with a computer science background, who is passionate about the web and can work out of our Hampshire offices.

Who we are looking for

We are looking for a server side developer who is absolutely passionate about the web and keen to develop new skills and experiences.

We are looking for somebody that loves finding innovative solutions to problems, enjoys working as part of a creative team and excels under pressure.

We need somebody with a computer science background preferably with a first or upper second degree.

Although Headscape is almost exclusively a .net development house, we do not require you to have specific experience in this language. As long as you can write great code, we will teach you the rest. (Anti-Microsoft Bigots need not apply!)

What we can offer

Headscape has a lot to offer employees. Just some of the benefits include…

  • A great working environment (watch our recent tour below)
  • The chance to attend industry conferences
  • All the training and careers development you need
  • The opportunity to work with an amazingly talented team
  • Loads of challenging and complex work that will stretch your skills
  • Some great client work to add to your CV
  • A decent office chair! :)

As for salary – Headscape always try to pay well and also pass on our success in the form of bonuses when things go well.

Where you would work

One of the best things about working for Headscape is our offices. Check out the video tour below. This was originally recorded to show people the room we have for rent. However, it also gives you a nice idea of where you would work.

The office is based in Lockerley, Hampshire. This makes it well placed for those living in Bournemouth, Winchester, Southampton, Romsey, Basingstoke and Portsmouth. However, its such a damn nice place that it is worth relocating for!

Interested?

So are you interested? If so (and you are not a recruitment agency) then email your CV to [email protected] or call him on 01722 320596.

Case Study: Wiltshire Farm Foods

One of the biggest challenges of running a successful website is balancing the needs of users with those of the business. This is especially true when an existing business model conflicts with user needs.

Although not always the case, one situation where this conflict can arise is with franchise based businesses. For the last few years I have been working with a franchise business called Wiltshire Farm Foods. Although, their business model has been phenomenally successful it caused significant problems for their online customers.

When business models and user needs conflict

When hired to redevelop the Wiltshire Farm Foods website I saw an opportunity for a quick win. Before a user could enter the website, they were required to provide a postcode. This was a massive barrier to entry as users do not like handing over personal information (such as a postcode) without being given a reason. From looking at the website statistics it was obvious many users were abandoning the site because of this requirement. I couldn’t understand why the company had created such a huge usability hurdle.

The Old WFF homepage

The answer was simple – Wiltshire Farm Foods had chosen to give their franchisees control over pricing. Without knowing where the user was located it was impossible to provide a price.

The decision to give franchisee variable pricing was a good one in the pre e-commerce era. However, as the importance of the web grew, it created a significant problem when competing against large supermarket chains with a national distribution network and standardised prices.

Although this was a problem for online users, the model worked for the business as a whole. Wiltshire Farm Foods had an incredibly successful relationship with its franchisees. Some had been with the company since day one. The business was driven by the entrepreneurial spirit of its franchisees and independent pricing was a key component of that success.

Working within constraints

With the variable pricing constraint remaining unmovable it became a case of managing the impact. Our first step was to move the point at which users were asked for a postcode. Instead of requesting it up front, we only asked for it when users asked for a price. This allowed users to view products and clearly linked the request for a postcode with pricing. We also explained why this step was necessary to reassure users this was not a ploy to send them unsolicited mail. However, ultimately we could not get around the extra step required to see prices.

It would have been counter productive to dig our heels in and refuse to compromise the user experience. Instead we took a pragmatic approach and worked within the business constraints. Ultimately this worked in our favour. When Wiltshire Farm Foods saw the increase in sales that came from moving where users entered their postcode, it encouraged them to consider changes in their business model.

Users now get a web price for each product when they arrive on the site for the first time. This price is then ‘adjusted’ once they login or provide a postcode. The user is notified of the change and because the price normally decreases they are generally happy. It is not ideal but it is a dramatic improvement that has greatly increased sales.

Turning a negative into a positive

Although the introduction of web prices is significant, it has not been the biggest change in the site. The real change has happened in my own thinking. In the beginning I saw the franchise model as a hurdle to overcome. However, I have since come to realise the benefit it has to the overall user experience, especially for the site’s target audience.

The Wiltshire Farm Foods audience is elderly with the average purchaser being in their eighties. Not only does this audience have certain accessibility requirements, they also have a number of concerns that need addressing.

One of their biggest concerns is security, both when purchasing online but also when meals are delivered. They are nervous about letting strangers in their house and yet need help unpacking and storing their meals.

The Wiltshire Farm Foods franchise system accommodates this perfectly. Customers always get the same driver and feel they are dealing with a local supplier rather than a national brand. They can even pay with cash on delivery and place new orders directly with the driver.

The problem was that the website did not reflect this local caring service. I was so preoccupied with the negatives of the franchise system, that I failed to identify it as a major selling point.

Franchises can offer personal service

Fortunately as I grew to understand the business model, I was able to grasp what Wiltshire Farm Foods had known since the beginning – that service was what set them apart. Wiltshire Farm Foods did not need to be overly concerned about universal pricing because they offered things no national supermarket could. They offered a friendly, caring service from police checked uniformed drivers. These drivers would even unpack meals and take next orders. However, most importantly they were a local supplier who customers came to know personally.

Once I understood this important selling point it fundamentally altered my approach to the site. The homepage shifted away from merely showing products to promoting the service that was supplied alongside the meals.

WFF homepage

The homepage now focuses on promoting these ‘value added’ services through the use of animation. However, more importantly we made a feature of postcode entry. Entering your postcode no longer just revealed your region specific pricing, it introduced you to your local franchisee. Gone was the faceless national brand and instead you were given the names and phone number of your local supplier. Soon you will even see a photograph of your local franchisee and details about their delivery schedules.

Screenshot of the local outlet information

All of this helps to reassure the user and personalise the experience. Computers are seen by many (especially the elderly) as impersonal and cold. Techniques like this humanise the experience and connect with users.

Lessons learnt

There is a lot that can be learned from the development of the Wiltshire Farm Foods website. We can learn about the importance of understanding your target audience and their motivations. We can learn how a perceived limitation in a business model can be turned into a strength. However, what excites me most is the opportunities provided by the Franchise model to engage with users in a more personal way that is lacking in many websites. With the growth of online social interaction there is the potential for an unprecedented level of customer care.

Bamboo Juice

I was fortunate enough to speak at the first everBamboo Juice conference on the subject of selling web design services. If you were there or are just curious, this page will allow you to access my slides.

My talkwas entitled ‘Winning business in tough times‘ and covered the following…

As the economy slowly collapses like a giant soufflé, where does that leave us as web designers? How do we ensure the work keeps rolling in? Paul shares his experiences of winning new business in the tough times while still nurturing existing clients. He explains how business development is everybody’s concern, not just the sales team.

You can eitherdownload a PDF of my slides(31.1mb – includes speaker notes) or watch here thanks to Slideshare.

161. In or Out

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

Play

Download this show.

Launch our podcast player

Housekeeping

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

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

I am therefore pleased to announce Micro-Boagworld…

View Micro-Boagworld posts here

Subscribe to the RSS feed here

Boagworld AudioBoo Homepage

Back to top

News

Pricing and projects

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

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

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

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

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

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

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

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

IE8 and IE6

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

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

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

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

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

Once IE6 is gone we will be able to…

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

Simple and impressive design techniques

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

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

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

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

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

Influencing user behaviour

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

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

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

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

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

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

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

Back to top

Feature: When to outsource web work

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

Read the full article

Back to top

Listeners feedback:

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

A good introduction to Javascript

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

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

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

A good but free survey tool

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

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

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

A review of Clicktales

Peter shares his experiences of Clicktales…

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

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

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

Web Design for ROI

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

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

Rich adds: I agree this is an excellent book.

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

Pro Paypal e-commerce

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

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

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

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

Back to top

 

When to outsource web work

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

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

Lets take a moment to compare the choices.

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

Using an in-house team

Using in-house staff provides a number of benefits…

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

Outsourcing to a web design agency

However, outsourcing can also bring some substantial benefits…

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

The choice

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

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

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

160. Education, Education, Education

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

Play

Download this show.

Launch our podcast player

Housekeeping

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

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

News

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

How to create a great web design CV

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

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

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

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

For the complete list of tips read the whole post.

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

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

Design: Make it Memorable

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

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

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

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

Statistics and website owners

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

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

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

That has often been my experience too.

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

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

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

Specialist vs. Generalist: Who Wins?

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

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

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

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

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

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

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

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

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

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

Back to top

Interview: Aarron Walter on Interact

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

Aarron: Thanks for having me.

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

Aarron: Yeah, yeah.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Aarron: Thanks for having me.

Thanks goes to Andrew Marquis for transcribing this interview.

Back to top

Listeners feedback:

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

Remote user testing

Our first email is from Steve. He writes…

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

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

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

What do you think of this method?

Sounds interesting although it would not be my preferred approach.

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

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

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

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

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

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

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

Finding a job

Our second email is a rather despondent one from Andrew…

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

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

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

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

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

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

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

Back to top

Series: Building A Better Web Application by Ryan Carson

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

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

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

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

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

Back to top

159. Special Guest

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

Play

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

Download this show.

Launch our podcast player

News

Alkaline

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

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

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

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

16 design tools for prototyping and wireframing

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

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

10 Lessons every freelancer should learn

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

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

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

Back to top

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

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

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

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

Sarah: Yup

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

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

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

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

Sarah: Really?

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

Ryan: To spend in the pub (laughs)

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

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

Paul: Yeah, pays the bills.

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

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

Sarah: Really?

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

Ryan: and a mac to develop on

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

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

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

Sarah: the app store!

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

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

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

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

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

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

Sarah: No, he was an old man.

Ryan: Oh, right. OK

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

Paul: Was he in just a pair of shorts?

Sarah: Yeah

Ryan: A pair of shorts and a smile?

Sarah: No, and a newspaper.

Paul: Strategically placed.

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

Paul: That’s OK.

Sarah: Oh, sorry.

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

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

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

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

Ryan: Yes, we only like the nice clients.

Sarah: Yes, we all like nice clients.

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

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

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

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

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

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

Sarah: Yeah.

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

Sarah: Do you skim-read them?

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

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

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

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

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

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

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

Sarah: Of course! (all laugh)

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

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

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

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

Sarah: Exactly.

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

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

Ryan: Er, yes.

Paul: Yes, ah the Nettuts, oh yeah.

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

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

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

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

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

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

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

Back to top

Listeners Questions:

Is Using Off-The-Shelf Software Wrong?

Jon Writes:

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

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

Thanks and keep up the good work!

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

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

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

Therefore, the pro’s are:

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

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

Don’t implement something you don’t understand!

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

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

How do you price and quote different projects?

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

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

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

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

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

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

What is speculative design work?

What is speculative design work and why it is wrong?

So recently Carsonified launched a design competition. I posted a comment teasing them that it was speculative work. This is following the controversy surrounding the panel on the subject at SXSW.

It didn’t occur to me for a minute that anybody would think I was serious! How can people think a competition is the same as spec work? It showed a fundamental misunderstanding of what spec work is but also more importantly why it is wrong.

People think spec work is wrong because it hurts the designer. I think it is wrong because it hurts the client. I think it is time to clear this issue up!

Read ‘Why Speculative Design Is Wrong’

158. Home

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

Play

Download this show.

Launch our podcast player

Housekeeping

Headscape still recruiting!

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

Back to top

News and events

The best of SXSW

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

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

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

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

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

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

fedex logo

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

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

This addressed two separate problems we have been having at Headscape

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

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

Browser testing and IE6

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

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

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

Screenshot of Superpreview

A simplicity case study

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

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

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

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

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

An introduction to Microformats

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

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

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

Back to top

Interview: Rob Borley on Project Management

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

Rob: Hi Paul, how are you doing?

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

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

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

Rob: Indeed.

Paul: Do you actually hear it?

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

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

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

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

Rob: (unintelligible) celebrity project manager.

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

Rob: Yes.

Paul: And you became a project manager.

Rob: Yes.

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

Rob: Well, you mean other than manage projects.

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

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

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

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

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

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

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

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

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

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

Paul: I like the cornification in that.

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

Paul: Yes.

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

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

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

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

Rob: Yeah, stick to web celeb.

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

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

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

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

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

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

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

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

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

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

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

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

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

Rob: My pleasure.

Thanks goes to Meredith Marsh for transcibing this interview.

Back to top

Feature: Home Working

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

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

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

The reality of home working

Back to top

Sneak Geek

Marcus shares some thoughts about our upcoming trip to SXSW.

I’ve really been looking forward to SXSW this year. I think it has something to do with familiarity with the whole event and also that Paul and I will be doing a little more than sitting in the audience (and bars).

So, it’s my third year. Does that mean I can say ‘southby’ now instead of the interminable south-by-south-west? I hope so.

Does it mean I can call myself a geek? No chance.

Other than making me feel old (which I honestly don’t care about), being at SXSW does give me a sense that I’m out of place.

In some ways I am a geek, but none of them to do with webs and internets. Following my career as a musician, and the advent of ‘proper’ jobs, I have, and let’s make no bones about it, been a salesman. Salesman is such a dirty word. It’s the complete opposite of ‘cool’ and in no way geeky at all.

I’m not suggesting I don’t have a role within the agency I work for, far from it. I like to think of myself as the person that interfaces (oh god, did I say ‘interface’) with people who are even less web-savvy than I am. This undoubtedly works. I have been blessed with enough intelligence to listen to people like Mr Boag and relay his words of wisdom, often making recommendations based on business objectives, in ways that potential (and existing) clients understand.

I’m likely to get shot down here but, usability is largely common sense and I’ve got bags of that too. But can I do design? No. Can I do any coding of any kind? No. Therefore, I am not a geek.

Ah yes, but geeks aren’t cool. Not like musicians are cool.

So, the SXSW music conference has got to be the real place to be right? I never attended it during my pop days, but, way back in early 90s I did go to MIDEM in Cannes which is the European equivalent. This event was frequented mostly by music business tossers (apologies) who were about as far away from ‘cool’ as you can get and I have a sneaking suspicion that the SXSW music conference is similar.

Conclusion: geeks are cool. Rock stars? No, probably not but the vast majority of the geeks I have met are conscientious, innovative people that really want to make some kind of difference. And, for the most part, very entertaining speakers.
Like I said, I’m really looking forward to southby this year.